the starting point for WP6: CIM Creation

related requirements

...coming soon...

related use-cases

...coming soon...

related tickets

open

#91
Revised Automatic Capture Tools
#93
Human GUI
#95
Revised Infrastructure
#143
decisions / questions
#202
Mapping Variables to Components: Obvious
#246
Questionnaire Approval Procedure
#248
Questionnaire Timeline
#249
Mapping questionnaire concepts to CIM concepts
#252
Questionnaire Validation protocol: UML sequence diagrams
#254
Questionnaire Validation Protocol: Technical Implementation
#258
Mapping Variables to Components: Controversial
#262
Controlled vocabulary for Platforms
#299
add platform attributes from CIM and from ticket:280
#314
Will License, Rights (or both) be collected by the questionnaire?
#326
Capturing definitions for terms in the mindmaps
#327
file upload of local information about model, activity, ... into CMPI5 questionnaire
#336
can we make the simulation description required?
#341
Default Font Size (Guidance Needed)
#355
Support for inputs that are constraint dependent
#356
Ancillary Files etc
#361
create an overall guidance video
#366
complete support for simulation output
#367
xml rendering code
#368
simulation validation needed
#371
Grouping experiments by core and tier etc
#376
Create roadmap for navigating the questionnaire
#389
Input file descriptions are needed that cover RCPs etc
#395
how do we expect users to define processor components in the q'naire?
#404
using TABs before viewing a simulation or model
#411
What should we do about postprocessing after the data submission
#418
need to add the progress status bar to the summary page
#424
Place of the 'Save' and 'Return' buttons
#428
Duplicate a file description needed?
#436
need alternatives for many file entries (e.g. alphabetical chooser)
#437
baseview assign needs to be laid out better for multiple entities
#450
capturing values for other
#451
coupling frequency units
#457
Should resolve inputs be for "realm" inputs only?
#478
model components changing colour if they've been filled in and/or if no field has been filled in
#482
formatting issue
#483
Experiment Length Ambiguity
#490
Display model editors on the summary page
#491
Add more explanatory text for responsible parties
#496
SAVE Warning message
#497
Component Attributes at top Model level needs explanatory text
#500
Clarify requirement to declare Variables as well as Files wrt ICs and BCs
#503
Extra text for Simulation Tab: Required Inputs and Couplings
#504
Simulation Tab: Refers to "Input Coupling" button which doesn't exist
#507
Simulation Tab: Reword text in Conformance frame
#513
Change system logic for Simulations: Conformance
#522
Review enumeration lists before release
#524
How should users define large amounts of dump variables?
#527
Provide Validated Document Export for ESG
#533
EnsembleInputMods: What info is required in the Inputs Box?
#541
Highlight mandatory fields
#542
Email address for questionnaire support
#544
Numerical Requirements: Comment out "rogue" initial conditions
#557
extra text to describe model modification
#558
Add extra text to help users link modifications to inputs
#560
change text on resolve inputs page
#571
Write questionnaire FAQ
#587
assigning modelmods to a simulation is a bit funny
#588
logout button needed in base template
#593
Need configurable URL prefix for case where Questionnaire run from non-root location
#602
Software audit to catalogue all processing software
#604
Provide a complete example of questionnaire output for ESG
#606
“Send to CMIP5” button should be renamed as “Send for review”
#607
Make the text view and html view of questionnaire public
#608
Have a look at what we can do about genealogy of files
#609
Reference in questionnaire/link to information about naming ensembles/extended runs
#610
Liaise with Karl about guidelines and examples for questionnaire on CMIP5 website
#615
Draft questionnaire launch email announcement for CMIP5
#616
What happens to old references if artefact being referred to changes?
#618
Link screencasts tutorials from the help page of the questionnaire
#619
Is there any CMIP3 metadata which isn’t in our questionnaire?
#642
Copying questionnaire instances between institutions
#643
Contact policy for modellers in the questionnaire
#645
Reviewing and quality control of questionnaire results
#646
Extended experiments layout
#648
What other screencast tutorials do we want for the questionnaire?
#653
Missing years in a run
#656
How will the questionnaire deal with hindcasts?
#661
Controlled vocabulary for zero level model type
#662
implement drop down list for zero level model type
#663
mandatory vs. optional entries in the questionnaire
#665
Update input details for "Input resolution"
#666
ensure key properties is not output as a component by the CIM
#674
Loading Activity Error
#676
User required to fill out longname to declare unimplemented sub-model
#677
Add text to inform user that there is no need to fill out own institution's party details
#678
Replicate Grid choice downwards
#679
Realm names of components should match DRS ones
#680
Grid question at top level?
#683
Document TAMIP experiments in questionnaire
#684
Documenting non-overlapping "ensembles" for CMIP5
#688
possible hole in questionnaire cardinality checks
#691
date/time fields in questionnaire should not be free text
#704
capture initial conditions for all ensemble members
#705
dropdown lists missing
#706
dropdown list windows do not close once the selection done
#707
SERVICES SPRINT 10 - Interfacing to THREDDS server for CIM instances creation
#708
SERVICES SPRINT 10 - Connection between CIM objects especially dataObject <--> simulationRun / experiment
#716
"top level" component uses "Attributes" rather than "General Attributes"
#717
simulation authors are freetext
#720
modelmods are associated with a simulation
#721
Final Release Beta Testing
#722
Compile udunits lists for qn unit entries
#723
Upload of internal infomation from XML into the CMIP5 questionnaire
#732
Metadata diference between CMIP5 output and Questionnaire
#733
CMIP5 Questionnaire Development Effort
#736
CIM schema component of validation sequence
#737
Schematron component of validation sequence
#740
invalid date format for ensemble input mod makes the questionnaire fall over
#741
Grids:correct the definition for meridional resolution
#742
Live updates to definitions in the mindmaps ?
#744
Add requirementOption as subclass of numericalRequirement in the CIM
#747
Files: "mostly used in experiment" list not working
#748
Questionnaire not working under Djanjo 1.2
#749
No Scroll bar on cf netcdf dropdown list for file variables
#750
Filter simulations by experiments on the summary page
#751
the source simulation appears in the related simulation list
#752
validation needs to be switched on
#754
Separate grids are required to describe atmos and ocean
#755
parameters point to wrong parameter values in AtmosConvecTurbulCloud
#756
Create 'Quality CIM' interface in questionnaire
#757
append value definitions to property definitions in the questionnaire
#758
pre-populate component long name box in the questionnaire
#759
Files page - re order
#760
questionnaire error if you delete a reference
#761
Incorporate CIM schema and CMIP5 validation into Questionnaire
#763
grid shortname textual description
#768
Write override for Yui button Listener
#771
model mod: parameter change appears as code change
#772
Conformance: input binding and model mod drop down boxes are too small
#774
Names used by Model Component constraint requirements do not allow them to be distinguished.
#775
workaround for lxml bug exposed by validation code
#776
JAMESTEC to JAMSTEC
#777
Grids need an export button

closed

#88
Test and / or evaluation
#89
Definition of CIM creation Tools
#90
Automatic Capture Tools
#92
Prototype Human GUI
#94
CIM creation tool infrastructure
#142
Requirements
#145
Use cases
#192
Develop CMIP5 Questionnaire
#193
Extracting metadata from code and verifying metadata with code
#194
Develop CMIP5 questionnaire list of requirements and constraints
#195
Sequence diagram/flowchart/storyline through questionairre
#197
Talk with Bob Drach re. ESG Publisher
#198
Controlled vocabulary - liaison with scientists to fill in gaps
#199
Arrange telco with Sylvia for controlled vocab and Dy-Core recap
#200
Put CMIP5 questionnaire and controlled vocabulary mind maps on Metafor site
#203
Email Allyn with already built lists of controlled vocabulary
#204
Clarify with CMIP and WGCM re Metafor's role in obtaining CMIP5 metadata
#213
Ingest controlled vocabulary mind maps into the CIM
#216
Organise grids telco
#217
Email Metafor list with UML of Curator grids package
#238
Build a django prototype of the storyline
#240
implement frames under django framework
#241
Implement tree navigation
#242
Create example images of questionnaire panes
#243
Implement questionnaire panes in django
#244
Ingest mindmap content to provide controlled vocab for the questionnaire
#245
Flattening mindmaps to deal with complex parameters
#247
Ingest ESG Dyanamical Core CV
#250
CMIP5 Conformance Mindmaps
#251
CMIP5 Conformance CIM Instances
#253
Questionnaire Validation Protocol: Establishing Policy
#255
CMIP5 Conformance: data upload and data description
#256
Coupling: Software Components
#257
Mapping Variable to Components: Obvious
#260
Reusable Concepts
#261
Ocean Dynamical Core CV
#269
CMIP5 Questionaire alpha2
#270
first choice not selected in Q param CV
#271
When an error is detected in a form, previous choices are lost
#272
Short and Long names in model description
#273
Need to provide a page for associating outputs with components
#274
Email address not replicated through
#275
Clicking on tab deletes entered info
#276
Positioning of Value and Options
#278
Consistancy with AR4
#284
redundant conformances
#285
Still get hangs on addsub
#286
modify reference from component page is broken
#287
Confusing use of term 'Template' on Summary page.
#288
Unify presentation of models and simulations on Summary page
#289
Input fields require hints / tooltips
#290
Specification of conformance method on Simulation page
#291
Behaviour of 'type' and 'implemented' fields on Model definition page
#292
Minor tweak to help text on Simulations master page
#293
How will model grids be defined?
#294
fix use of implemented tag
#295
if we edit the model we remove components from the menu
#296
How are we handling physical model ensembles in the questionaire?
#297
Consider a tab for each model within each centre
#298
can't add a reference unless it's tied to a component
#300
can't add a new reference once we've filled in the last one
#301
make sure our realm vocabs are consistent
#302
should initial conditions have a controlled vocabulary
#303
Logos for Questionnaire
#304
Component short name size limit is too small
#305
Increase screen real estate for Attributes
#306
BoundaryLayerTurbulence: Attribute properties menu not working
#307
Name and Value confusion in Model and Top Level components
#308
Additional explanation for references
#309
Finalize Contact Requirements for the Questionnaire
#310
Will the questionnaire have notes?
#311
Will the questionnaire contain version?
#312
What does components mean in the models.py file?
#313
Is Geneology the same as PreviousSimulation?
#315
Questionnaire versus netCDF harvest (Karl's email)
#316
Help us determine Attributes to be searched on
#317
What will conformance look like
#318
"other" choice: allow user-value(s)
#319
Editing rights for models of a given modelling center
#320
internal/external coupling : some remarks
#321
Vintage versus Release year, which meaning do we want in the questionnaire
#322
should connection type be per flux?
#323
periods not allowed in simulation names
#324
Change "references" to 'References and web pages'
#325
Rogue capitalisation in title "DRAFT CMIP5 QuestionNaire (alpha 3)"
#328
Bugs is questionnaire layout
#329
bug when navigating to coupling from conformance
#330
Allow delete of user specified attributes
#331
Need to ask for timestep at the realm level
#332
component tree gets garbled
#333
runoff/draingage component will not save
#334
first value in pull downs can't be selected
#335
Some components can not be saved b/c their names are too long
#337
issues with initial conditions
#338
Pre-load references into the questionnaire
#339
Improve explanations in the questionnaire
#342
conformance layout with long b.c. names
#343
Move to parameter groups instead of parameters in the attribute display
#344
Conforming to either of two numerical requirements
#345
Baseview edits don't work because of uniqueness constraint
#346
baseview deletes currently return an error
#347
need funding agency for simulations and model development in questionnaire
#348
simulation author list needed for citation list
#349
AttributeError at /cmip5/1/simulation/7/edit/
#350
make clear that the runtime inputs can only be made at the realm level
#351
Need to associate more than one boundary condition with a numerical requirement
#352
need to rename codemods
#353
need to make clear the support for two types of initial conditoin
#354
Need to get all DRS controlled vocabularies loaded into Q
#357
Files and Variables
#358
Get the new coupling vocabulary into the Q
#359
create an example modelling group and make visible through security
#360
break up the big formsets so folks can save pieces at a time.
#362
Simulation Copying
#363
Ensure that mindmap inputs are temporarily blocked
#364
need to be able to delete new subcomponents
#365
complete support for component output from newparams
#369
broken code modification y/n box
#370
No tabs at top of experiment requirement page
#373
tooltips to expose the parameter definitions
#375
temporal regridding needs "none" and "other" options
#377
remove underscores from experiment short names
#378
experiment tab page title needs to contain the word experiments
#379
Re-order model realm components in tree menu
#380
How do users separate items in user defined lists?
#381
Pencil Icon in mindmaps not interpreted as string input by questionnaire.
#383
it's possible to edit a preloaded reference and then you can delete it.
#384
duplication of component names in code mod drop down list.
#385
null option required on conformance code mod drop down list
#386
Need a "return to conformance" button on code mod page
#387
addnig variables to files is cumbersome
#388
no logging appears in the operational questionnaire
#390
model deployed without atmosphere mindmaps
#391
component timestep information missing
#392
adding new parameters when none exist
#393
Support for units
#394
change system logger
#396
Experiment names should use requirement doc ShortName
#397
Help text required for file description
#398
removal of questions for the computing platform
#399
Rename Files Tab
#400
AttributeError at /cmip5/1/simulation/2/conformance/
#401
ensure that the conformance mods offered up on the conformance page are appropriate
#402
links should allow dois
#403
Link in FILES screen is mandatory
#405
Changing no. of ensemble elements
#406
Drop down content for files and mods
#407
Ensemble characteristics issues
#408
Couplings description field
#409
Default parameter groups
#412
change platform output in questionnaire post processing
#413
need to include a vocabulary version number pretty much everywhere
#414
Adding a new party crashes
#415
Selection through 'Choose one of' and checking
#419
Comments to update in 'Inputs Required by this component'
#420
"parties" broken in alpha 8
#421
Coupling into: with AncillaryFile broken ?
#422
Copy simulation broken
#423
add number of years simulated to summary page, and do better on experiment page
#425
View and Validate crash
#426
Add new model: can we make the model name unique?
#427
'DELETE' button needed
#429
Providing a value when Other is selected from a list
#431
process aerosol mindmap into xml in questionnaire repository
#432
adjust realm definitions in questionnaire
#433
internal security issues
#434
operational error logging
#435
model mods button on conformance page
#438
handle static media files properly in wsgi deployment
#439
"Save File Description" button
#440
export button
#441
responsible parties default values
#442
Unable to save conformances and input couplings
#443
"save" button confusing in files and model mods
#444
additional param should not appear with every constraint group
#445
preloaded files not making it to list of files for coupling
#446
Spacial regridding type required even if spacial regridding is set to none
#447
saving partially completed couplings as we go along
#448
coupling description fields are required
#449
variable(file) dropdown lists in couplings will be prohibitively long ...
#452
Create a styled validation template page
#453
Add "other" in "Input Requirement" page
#454
"Input Coupling" button on the left column
#455
Coupling terms not implemented properly in the Questionnaire
#456
Review of the questionnaire text
#458
still a list of deletes available in some cases
#460
Experiment Description: from CIM docs to questionnaire
#476
CMIP5 questionnaire problem, data separation between institutes
#477
validation and responsible parties
#479
explain date format to users
#480
2D-Sources and 3D-Sources need unique names
#481
Clarifying the work about definitions
#484
conformance when no inputs: /cmip5/5/simulation/6/conformance/
#485
wiki page for reporting problems with the questionnaire
#488
Component Review Sheet
#489
sea water properties to revisit
#492
"Untick this box if there is no prepresentation of model in your model"
#493
Spelling Error: Geneology to be replaced with Genealogy
#495
Parties: Why is url mandatory and not email address?
#498
Explain the terms: Model, Realm and Component
#501
additional Tab "Model Variables"
#502
Files Tab: Reword "Return no edit" button
#505
Reword text jargon "Coupling4" on Simulation and Model Tabs
#506
Simulation Tab: Reword explanatory text about ensembles
#508
Conformance: Add extra options under "How this simulation conformed"
#510
It is too easy to delete "parties" and "files"
#511
Users should be able to delete simulations
#512
My attempt to delete a party broke the questionnaire
#514
Sort drop down lists in case-insensitvie alphabetical order
#515
Component tree difficult to read
#516
component removal can lead to problems with tabs
#517
Report that platform is required before creating simulation
#518
Make the coupling description non-mandatory
#519
Translating METAFOR Controlled Vocabulary to ESG OWL
#520
Standardising descriptions of similar models
#521
Allow un-enabling of sinlge attributes on bundled pages.
#523
Export XML not dealing with all objects correctly
#525
Clicking on a tab does nothing.
#526
Unable to reduce the number of ensemble members.
#528
Vocab: LandSurfaceVegetation requires "Vegetation Type"
#529
EnsembleCharacteristics contain unrecognised information
#530
AtmosRad-Aerosol and GHG types are not consistent with AtmosChem and Aerosol Components
#531
Recap Conformance selections in the RH "Notes" Box
#532
EnsembleInputMods: What is the meaning of "date"?
#534
Responsible Parties: Implement a copy downwards tickbox.
#535
Files: What to do if user doesn't have right to distribute link to input files?
#536
Add prefix to identify Modification Memonic
#537
What is the scope of Genealogy?
#538
Move "it will take a while to create a model" text closer to relvant button
#539
Multiple choice separator: Replace "|" with " | "
#540
If gridspec files won't exist before the questionnaire, add some new attributes.
#543
Copy Simulation does not copy ensemble members aswell
#545
pregenerate 40 models so they don't take time
#547
Multiple instance CMIP5 experiments
#548
experiment class in questionnaire needs to have document stereotype
#549
Finding the type of modification for a particular ensemble member
#554
add cf controlled vocabulary and specialise dataobject and componentinput forms
#555
store the numerical requirement id in the questionnaire
#556
Change Numerical Requirement to Experiment Requirement
#559
Extra text for model modifications
#561
explaiin that users can choose between emission and concentration requirements
#563
initial condition does not need a coupling frequency?
#564
long file names look the same and some have a single quote
#565
formatting issue in simulation conformance page
#566
contact and funder for a platform
#567
make a file a subclass of Doc
#568
tree view should not display components that are switched off
#570
No experiment requirements on duplicate simulations
#573
CF names replication
#576
aerosols associated with 2D and 3D sources
#577
formatting error on component input specification page
#578
tree view error
#580
Any simulation save loses model mods applying to the whole simulation.
#581
Q'aire Forum: Make Subject Entry Box Larger
#582
need to be able to undo related simuations as well
#583
'Other' to be placed at bottom of drop-down boxes
#585
new input error on save
#586
new files input fomatting is a bit messed up
#589
Issue with CF names in drop-down box
#590
Uninformative error message
#591
Error when 'related simulation' box left empty
#592
closures
#594
Q'aire Forum: Give Charlotte and Gerry et al moderator/admin privileges
#595
Make component longname a mandatory field
#596
Change "type" of the zero level model component from model to climate
#597
Responsible Parties: Remove "Funder" from Platform in the questionnaire.
#598
Responsible Parties: Add "contact" to Platform in the CIM.
#600
aerosol questions are topsy-turvy
#612
Short names in DRS document and in questionnaire are not the same
#613
Ticket and hassle people about the changes that need to be made to make sure that all the information from the questionnaire can go into the CIM.
#614
Create a validation wiki page
#620
Do something about simulation duration
#623
Controlled vocabulary and definitions for the top level of the questionnaire (ModelClass)
#637
Grids issue in the questionnaire
#641
What is mandatory in the questionnaire?
#658
Responsible parties still needs discussion
#659
fix translation from Metafor realm CV to ESG owl
#660
latest version of the questionnaire is broken
#667
Stochastic Physics for subgrid processes
#670
questionnaire error closed_date.html missing
#671
Use DRS forcing abbreviations in the conformance documentation
#672
Bug in filling out Platform Page
#675
realm name mapping to DRS/ESG
#681
Bug in 'IsImplemented'/'IsControlled' path leading to deleted/hidden components
#682
Support team need access to all centres in the CMIP5 questionnaire
#685
Export one OWL file from the mindmaps
#686
Test web browser compatibility for the CMIP5 questionnaire
#689
cfname value on input page is broken
#692
Ordering of 'other' and 'N/A' in mindmaps
#697
Error in XML export
#700
error when exporting to xml
#701
pre-loaded files do not have an abbreviation
#712
Template for Ensemble Description page in the questionnaire
#718
Other or other
#719
xml to esg/cim update
#728
requirement options for spatio temporal constraints
#743
ensemble class should be a subclass of Doc
#745
questionnaire death if you do not provide an ensemble description
#753
pass parameter definitions to questionnaire output xml
#765
Arrgh! changes to cimHandling.py broke my questionnaire
#766
grid updates have broken the questionnaire
#767
Render requirement options on the Conformance pages of the questionnaire
#769
separate exp number and exp name in xml documents
#770
No "rationale" on the experiment page

notes

Here is a blurb about WP6.

Wiki Index

  1. WP1: the starting point for WP1: Project Management
  2. WP1/SoftwareManagement: Live Deliverables
  3. WP2: the starting point for WP2: The CIM
  4. WP2/ControlledVocabulariesList: A flat list of controlled vocabulary terms for the CIM
  5. WP2/DevelopingTheCIM: some guidelines for developing the CIM
  6. WP3: the starting point for WP3: testing/populating
  7. WP3/Agile: Metafor WP3 Group - Agile Management
  8. WP3/Agile/Sprints/01: Metafor WP3 Group - Sprint 01
  9. WP3/docs
  10. WP3/telcos
  11. WP3/telcos/03/agenda
  12. WP4: the starting point for WP4: Services
  13. WP4/Agile: Services Group - Agile Management
  14. WP4/Agile/Sprints/01: Services Group - Development Sprint 01
  15. WP4/Agile/Sprints/02: Services Group - Development Sprint 02
  16. WP4/Agile/Sprints/03: Services Group - Development Sprint 03
  17. WP4/Agile/Sprints/03/url-design: Initial Thoughts on Metafor URL design to supplement attached note
  18. WP4/Agile/Sprints/04: Services Group - Development Sprint 04
  19. WP4/Agile/Sprints/05: Services Group - Development Sprint 05
  20. WP4/Agile/Sprints/06: Services Group - Development Sprint 06
  21. WP4/Agile/Sprints/07: Services Group - Development Sprint 07
  22. WP4/Agile/Sprints/08: Services Group - Development Sprint 08
  23. WP4/Agile/Sprints/08/Agenda
  24. WP4/Agile/Sprints/09: Services Group - Development Sprint 09
  25. WP4/MF-ISENES-Timeline
  26. WP4/NumSim: WP4/NumSim
  27. WP4/PortalDeployment: pre-requisites
  28. WP4/QDeployment: Deploying the questionnaire
  29. WP4/QSandbox: Notes on building questionnaire sandboxes
  30. WP4/ServicesPlanningDocument: Metafor Services (WP4, WP5, & WP6): Deliverables, Dependencies, and …
  31. WP4/URIstructure: WP4/URIstructure - The Metafor URI structure(s)
  32. WP5: the starting point for WP5: Tools
  33. WP6: Wiki Index
  34. WP7: the starting point for WP7: Dissemination
  35. CMIP5: the starting point for CMIP5
  36. CMIP5/FileMetadata: CMIP5 Internal File Metadata
  37. CMIP5/QuestionaireBetaTesting: Comments, queries and issues raised by our beta testers
  38. CMIP5/QuestionaireIssues: Alpha 5 release of the CMIP5 questionnaire: …
  39. CMIP5/QuestionaireRequirements: CMIP5 questionnaire requirements
  40. CMIP5/QuestionaireTimeline
  41. CMIP5/QuestionnaireTimeline
  42. CMIP5/Storyline
  43. CMIP5/VarURIStructure: CMIP5/Variable Structures
  44. CMIP5_CVSoft
  45. requirements: METAFOR requirements
  46. requirements/testRequirement: requirement: make sure that thingies contain widgets (sample requirement)
  47. use-cases: METAFOR use-cases
  48. use-cases/AnnotateCIMRecord: Use-Case: Annotate a CIM Record
  49. use-cases/BrowseCIMRepository: Use-Case: Browse a CIM Repository
  50. use-cases/CaptureGridDefinition: Use-Case: Capture a Grid Definition
  51. use-cases/FindCIMRepository
  52. use-cases/FindExperimentsForModel: Use-Case: Find Experiments Based On Model X
  53. use-cases/FindModelsForExperiment: Use-Case: Find Models Used In Experiment X
  54. use-cases/FindModelsToCouple: Use-Case: Find Models To Couple
  55. use-cases/FindRelatedCIMRecords: Use-Case: Find Related CIM Records
  56. use-cases/FindRelatedCitations: Use-Case: Find Related Citations
  57. use-cases/KeywordSearchCIMRepository: Use-Case: Keyword Search a CIM Repository
  58. use-cases/QueryCIMRepository: Use-Case: Query a CIM Repository
  59. use-cases/ViewCIMRecord: Use-Case: View a CIM Record
  60. use-cases/ViewDatasetQualityReport: Use-Case: Find Related Citations
  61. use-cases/create-qc-record: Use-Case: Modify or Create a quality control record
  62. use-cases/template: Use-Case: <name>
  63. use-cases/testUseCase: Use-Case: a sample use-case
  64. tickets/167: CIM sequence document & diagrams
  65. tickets/180: notes for ticket 180
  66. tickets/181: notes for ticket 181
  67. tickets/182: The Wiki page for documenting progress on the ConCIM activity package: …
  68. tickets/184: Existing Controlled Vocabulary lists
  69. tickets/185: notes for ticket 185
  70. tickets/189: Use Cases for interacting with the UMUI Minutes from a meeting that …
  71. tickets/191: Experiment relationships for CMIP5
  72. tickets/192: CMIP5 Questionnaire
  73. tickets/193: Extracting CIM metadata from code and verifying CIM metadata and code are …
  74. tickets/214: Figure out how the Controlled Vocabulary should integrate with the CIM
  75. tickets/215: tidy the CIM (as per the Y1 meeting)
  76. tickets/226: restructure the wiki
  77. tickets/232: create a widget for the thingie (sample ticket)
  78. tickets/236: tidy the CIM (to make it less XML specific)
  79. tickets/237: include sequencing info in the CIM
  80. tickets/239: Outstanding CIM Issues
  81. tickets/241: Implement Tree Navigation for the CMIP5 Questionnaire
  82. tickets/244: Processing the mindmaps (bundled version) to create XML suitable for …
  83. tickets/245: Work in progress
  84. tickets/247: Ingest ESG metadata into mindmaps
  85. tickets/248: CMIP5 Questionnaire Timeline
  86. tickets/249: Questionnaire to CIM Conversion
  87. tickets/250: CMIP5 Conformance wiki for ticket #250
  88. tickets/253: Questionnaire Metadata Validation
  89. tickets/254
  90. tickets/277: Proposed updates to the CIM Grid logical data model
  91. tickets/280: add / revise definitions of terms used in the CIM
  92. tickets/281: when should references use XPath and when should they embed documents …
  93. tickets/326/aerosols
  94. tickets/326/atmos
  95. tickets/326/atmos_chem
  96. tickets/326/land_ice
  97. tickets/326/land_surf
  98. tickets/326/ocean: Herafter is the previous version of definitions tables for Ocean, included …
  99. tickets/326/ocean_biochem
  100. tickets/326/sea_ice: Herafter is the previous version of definitions tables for Ocean, included …
  101. tickets/485: CMIP5 Questionnaire
  102. tickets/509: What Deployment/Hardware/Configuration Information Should Be Recorded?
  103. tickets/519
  104. tickets/636: Wiki Page for Ticket #636 (Review of Grid Properties in MindMaps)
  105. tickets/684: Discussion of Ensemble Handling Issues
  106. tickets/707: THREDDS to CIM instances tool
  107. tickets/709: CIM v1.5
  108. tickets/715: METAFOR Success Criteria
  109. tickets/778: Integrate Controlled Vocabularies with the CIM
  110. tickets/78
  111. tickets/79: CIM Differencing Tool Design Document
  112. tickets/92: Outstanding CIM Prototype Human GUI Issues