Last modified 4 years ago
the starting point for WP2: The CIM
- related requirements
- related use-cases
- related tickets:
- open tickets (49)
- closed tickets (90)
- notes
- wiki index
related requirements
...coming soon...
related use-cases
...coming soon...
related tickets
open
- #188
- Review system requirements document
- #190
- Metafor issues document
- #201
- Governance of mind maps for controlled vocabulary
- #206
- Medata data governance
- #218
- Present quality package slides from year 1 meeting at future telco
- #237
- include sequencing info in the CIM
- #263
- translating from our uml conceptual model to rdfs
- #267
- Handling variables within DataObject:dataContent
- #279
- Prognostic Variables
- #280
- add / revise definitions of terms used in the CIM
- #281
- formalize the way that references are used within the CIM (embedded vs. xquery)
- #355
- Support for inputs that are constraint dependent
- #499
- rationalise the use of IDs & Version w/in CIM instances
- #509
- what sort (if any) deployment/hardware/configuration information should we be tracking
- #572
- Numerical Requirements for Interesting Transitions
- #617
- Diagram with agreed terms for the CIM lifecycles
- #621
- Put start and end date into data package
- #622
- Identify definition beta testers
- #624
- Draft a letter to seek endorsement from the WCRP to form a governance committee for the controlled vocabulary
- #625
- How to govern ConCIM UML and transformation method to AppCIM and how to get CIM v2
- #635
- Look at grid information in CMOR
- #639
- Governance of CIM and associated software
- #644
- CIM version 2
- #650
- Life cycle of CIM instances
- #654
- Quality package and CMIP5 metrics
- #655
- CIM and seasonal and decadal runs
- #702
- is a better distinction between a Platform and Machine needed?
- #735
- Ensemble Type Code List
- #746
- how to reference documents that haven't been archived yet
- #778
- implement Controlled Vocabularies
- #796
- Responsible Party Subsclasses an XML type rather than a UML type
- #824
- Update ConCIM and ApCIM for quality control changes
- #848
- Namespace issues in Quality Schema
- #862
- Add required CIM software component information
- #870
- Simplification and Rationalisation on the way CIM 2.0
- #881
- import the actual versions of the ISO schemas for the CIM, instead of local copies
- #904
- mindmap modifications for grids
- #908
- CIM namespace should point to actual location of schemas
- #920
- O&M Compliance for the CIM
- #949
- CIM1.6 Tasks
- #950
- CIM1.8 Tasks
- #951
- CIM1.7 Tasks
- #955
- CIM2 Data Model
- #986
- cim v1.7
- #999
- CIM 1.92 open issues - placeholder ticket
- #1000
- CIM 1.92 GML Serialisation
- #1001
- CIM 1.9.2 Bi-directional import between Activity and Process
- #1002
- Issues with project in CIM 1.9.3
- #1003
- cim 1.9.3 issues
closed
- #46
- Metadata Gap Analysis Report
- #47
- Prototype CIM XML implementation with current external schemas
- #48
- Coordination Strategy with external schemas for CIM
- #49
- Identification of priority areas for CIM development within METAFOR
- #50
- Abstract CIM with current internal and external schema
- #51
- CIM development database definition and aggregation strategies
- #52
- Actual CIM for delivery of METAFOR tools and services
- #53
- Revised CIM, after initial population
- #54
- Final CIM, after further population and testing
- #55
- Governance Plans Report
- #105
- Formalise CMIP/ESG links
- #108
- Curator metadata analysis and comparison with CIM
- #113
- DOAP Description of a Project
- #114
- What is CIAO
- #118
- What are Curator "Use Profiles"?
- #122
- How is RDF used in Curator?
- #123
- How is OWL used in Curator?
- #131
- What is the CIM?
- #135
- Put all use case lists into one list
- #140
- Plan of attack for WP2
- #154
- CIM Meeting
- #156
- Rooms reservations for CIM mtg
- #158
- Fundamentals of Information Modelling Document
- #161
- Research whether Protege will import UML and export RDF
- #162
- Research EA exporting an xsd schema
- #163
- EA has to be checked to see if it can import UML from Hans
- #164
- get Rocky and SPencer to Toulouse
- #165
- Set directory structure for SVN based on UML packages
- #166
- Update Gap Analysis report based on CIM Meeting inAbingdon
- #167
- Sequence diagram of CIM
- #168
- Are Curator User profiles up to date
- #169
- Requirements Document for CIM
- #175
- importing NMM UML into EA
- #179
- sample ticket demonstrating how to use SVN
- #180
- full CONCIM v0.1
- #181
- software package CONCIM v0.1
- #182
- Put the activity package into the subversion repository
- #184
- Find out and review existing controlled vocabulary enumerations
- #185
- establish CONCIM to APPCIM process
- #189
- Talk about example use cases for the Met Office Unified Model
- #191
- Expose experiment relationships for CMIP5
- #196
- Metadata ingestion diagram
- #211
- Bryan to give a copy of his old UML about CF to Allyn
- #214
- Translate controlled vocabulary lists into xml schema
- #215
- CIM tidying
- #233
- look into making the CIM GML-compliant (and FullMoon compatible)
- #234
- finalise the ChangeProperty class
- #235
- Update CIM grid package with revisions agreed at Feb 24 Metafor/Curator telco
- #236
- revise the CIM to make it less (XML) implementation specific
- #239
- outstanding CIM issues
- #264
- understand the relationship between data referenced by activities and data referenced by software
- #265
- Issues with SimulationComposite
- #266
- Use of DataObject:hierarchyLevelName
- #277
- Proposed updates to the CIM Grid logical data model
- #372
- definitions needed in the mindmaps
- #382
- review the platform description and suggest attributes and vocabulary
- #416
- Advection vocabularies
- #430
- split aerosol into top level mindmap
- #463
- SERVICES SPRINT 04 - CIM Extensibilty Points
- #487
- Supporting the inclusion of multiple CIM Objects in a CIM Document
- #546
- time transformation vocabulary
- #550
- component types enumeration is too restrictive in CIM1.4
- #551
- simulationRun/simulationComposite is mandatory
- #552
- questionnaire platform information and CIM deployment information do not match up
- #575
- Referencing embedded objects
- #599
- modifications to CIM DataObjects to support Questionnaire output
- #603
- Release CIM version 1.4 when it captures all the information the questionnaire requires.
- #611
- SpaceConfig, mind maps and the grid package/gridSpec
- #636
- Review mind maps to make sure that all the appropriate information about grids is there
- #638
- When is the CIM "finished"?
- #647
- Pathway between grid package and ESG
- #657
- How does GridSpec fit into the CIM?
- #664
- vocab difference between cmip5 questionnaire and CIM schema
- #673
- Add an extra element under model component type
- #698
- duration concept
- #709
- CIM v1.5
- #711
- review whether any CVs should _not_ be extensible
- #816
- determine where to put the simulation authorship text in the CIM
- #822
- CIM1.5 needs to be frozen for questionnaire release v1.x
- #833
- add description element to simulation/ spinupSimulation and simulation/ controlSimulation
- #883
- no place to put references in the gridspec
- #885
- add extent property to the grid package
- #888
- sort out export of "configured" and "unconfigured" models
- #889
- add mnemonic property
- #890
- add refinementScheme property to the CIM grids package
- #893
- conformance class optional type property
- #901
- CIMRecordSet to be renamed and CIMRecord to be deprecated
- #903
- grid package modifications
- #912
- grid package changes
- #1009
- Create wiki page with web-embedded mindmaps
notes
The CIM is being developed in the METAFOR respository as follows:
Code
| Version | Code | notes |
| trunk HEAD | source:CIM/trunk | - |
| 1.3 | source:CIM/tags/version-1.3 | updated coupling & genealogy |
| 1.2 | source:CIM/tags/version-1.2 | formal release for EU |
| 1.1 | source:CIM/tags/version-1.1 | fixing a few last-minute wrinkles |
| 1.0 | source:CIM/tags/version-1.0 | formal release for EU |
| 0.2 | source:CIM/tags/version-0.2 | re-integrated packages |
| 0.1 | source:CIM/tags/version-0.1 | just needed a baseline |
timeline (as of v1.2)
v1.3 : 30 October 2009
- revamp coupling to better handle 1) transformers, 2) the distinction between coupling from software versus coupling from activities
- restructure genealogy classes
v1.4: 27 November 2009
- rationalise the use of version & id w/in the CIM; need to handle the id/version of the CIM, the CV(s), and the instance
Wiki Index
- WP1: the starting point for WP1: Project Management
- WP1/Amendment3: Amendment 3: Metafor project extension
- WP1/SoftwareManagement: Live Deliverables
- WP1/TelcoMinutes: Teleconference minutes
- WP1/TelcoMinutes/20Sept2011
- WP1/TelcoMinutes/Telco138_27Sept2011: Telco 138 - 27th September 2011
- WP1/TelcoMinutes/Telco139_4Oct2011: Telco 139 - 4th Oct 2011
- WP1/TelcoMinutes/Telco140_11Oct2011: Telco 140 11th October 2011
- WP1/TelcoMinutes/Telco141_1Nov2011: Telco 141 1st November 2011
- WP1/TelcoMinutes/Telco142_6Dec2011
- WP1/TelcoMinutes/Telco143_5Jan2012: Telco 143 5th January 2012
- WP1/TelcoMinutes/Telco144_2Feb2012: Telco 144 2nd February 2012
- WP1/TelcoMinutes/Telco145_6Mar2012: Telco 145 6th March 2012
- WP1/TelcoMinutes/Telco146_2Apr2012: Telco 146 2nd April 2012
- WP1/TelcoMinutes/Telco147_10May2012: Telco 147 10th May 2012
- WP1/TelcoMinutes/Telco148_31May2012: Telco 148 31st May 2012
- WP1/TelcoMinutes/Telco149_21June2012: Telco 149 21st June 2012
- WP1/TelcoMinutes/Telco150_05July2012: Telco 150 5th July 2012
- WP2: Wiki Index
- WP2/ControlledVocabulariesList: A flat list of controlled vocabulary terms for the CIM
- WP2/DevelopingTheCIM: some guidelines for developing the CIM
- WP3: the starting point for WP3: testing/populating
- WP3/Agile: Metafor WP3 Group - Agile Management
- WP3/Agile/Sprints/01: Metafor WP3 Group - Sprint 01
- WP3/docs
- WP3/telcos
- WP3/telcos/03/agenda
- WP3/telcos/04
- WP3/telcos/05: Agenda
- WP4: the starting point for WP4: Services
- WP4/Agile: Services Group - Agile Management
- WP4/Agile/Sprints/01: Services Group - Development Sprint 01
- WP4/Agile/Sprints/02: Services Group - Development Sprint 02
- WP4/Agile/Sprints/03: Services Group - Development Sprint 03
- WP4/Agile/Sprints/03/url-design: Initial Thoughts on Metafor URL design to supplement attached note
- WP4/Agile/Sprints/04: Services Group - Development Sprint 04
- WP4/Agile/Sprints/05: Services Group - Development Sprint 05
- WP4/Agile/Sprints/06: Services Group - Development Sprint 06
- WP4/Agile/Sprints/07: Services Group - Development Sprint 07
- WP4/Agile/Sprints/08: Services Group - Development Sprint 08
- WP4/Agile/Sprints/08/Agenda
- WP4/Agile/Sprints/09: Services Group - Development Sprint 09
- WP4/Agile/Sprints/11
- WP4/Agile/Sprints/12: Services Group - Development Sprint 12
- WP4/Agile/Sprints/19
- WP4/Deliverables
- WP4/MF-ISENES-Timeline
- WP4/NumSim: WP4/NumSim
- WP4/PortalDeployment: pre-requisites
- WP4/QDeployment: Deploying the questionnaire
- WP4/QSandbox: Notes on building questionnaire sandboxes
- WP4/ServicesPlanningDocument: Metafor Services (WP4, WP5, & WP6): Deliverables, Dependencies, and …
- WP4/URIstructure: WP4/URIstructure - The Metafor URI structure(s)
- WP5: the starting point for WP5: Tools
- WP6: the starting point for WP6: CIM Creation
- WP7: the starting point for WP7: Dissemination
- CMIP5: the starting point for CMIP5
- CMIP5/FileMetadata: CMIP5 Internal File Metadata
- CMIP5/QuestionaireBetaTesting: Comments, queries and issues raised by our beta testers
- CMIP5/QuestionaireIssues: Alpha 5 release of the CMIP5 questionnaire: …
- CMIP5/QuestionaireRequirements: CMIP5 questionnaire requirements
- CMIP5/QuestionaireTimeline
- CMIP5/QuestionnaireAccess: Instructions for Access to the CMIP5 Questionnaire …
- CMIP5/QuestionnaireCentres
- CMIP5/QuestionnaireOpenLetter: Open letter to our users
- CMIP5/QuestionnaireTimeline
- CMIP5/Storyline
- CMIP5/VarURIStructure: CMIP5/Variable Structures
- CMIP5_CVSoft
- requirements: METAFOR requirements
- requirements/testRequirement: requirement: make sure that thingies contain widgets (sample requirement)
- use-cases: METAFOR use-cases
- use-cases/AnnotateCIMRecord: Use-Case: Annotate a CIM Record
- use-cases/BrowseCIMRepository: Use-Case: Browse a CIM Repository
- use-cases/CaptureGridDefinition: Use-Case: Capture a Grid Definition
- use-cases/FindCIMRepository
- use-cases/FindExperimentsForModel: Use-Case: Find Experiments Based On Model X
- use-cases/FindModelsForExperiment: Use-Case: Find Models Used In Experiment X
- use-cases/FindModelsToCouple: Use-Case: Find Models To Couple
- use-cases/FindRelatedCIMRecords: Use-Case: Find Related CIM Records
- use-cases/FindRelatedCitations: Use-Case: Find Related Citations
- use-cases/KeywordSearchCIMRepository: Use-Case: Keyword Search a CIM Repository
- use-cases/QueryCIMRepository: Use-Case: Query a CIM Repository
- use-cases/ViewCIMRecord: Use-Case: View a CIM Record
- use-cases/ViewDatasetQualityReport: Use-Case: Find Related Citations
- use-cases/create-qc-record: Use-Case: Modify or Create a quality control record
- use-cases/template: Use-Case: <name>
- use-cases/testUseCase: Use-Case: a sample use-case
- tickets/1008: QC for CMIP5 Questionnaire Records
- tickets/167: CIM sequence document & diagrams
- tickets/180: notes for ticket 180
- tickets/181: notes for ticket 181
- tickets/182: The Wiki page for documenting progress on the ConCIM activity package: …
- tickets/184: Existing Controlled Vocabulary lists
- tickets/185: notes for ticket 185
- tickets/189: Use Cases for interacting with the UMUI Minutes from a meeting that …
- tickets/191: Experiment relationships for CMIP5
- tickets/192: CMIP5 Questionnaire
- tickets/193: Extracting CIM metadata from code and verifying CIM metadata and code are …
- tickets/214: Figure out how the Controlled Vocabulary should integrate with the CIM
- tickets/215: tidy the CIM (as per the Y1 meeting)
- tickets/226: restructure the wiki
- tickets/232: create a widget for the thingie (sample ticket)
- tickets/236: tidy the CIM (to make it less XML specific)
- tickets/237: include sequencing info in the CIM
- tickets/239: Outstanding CIM Issues
- tickets/241: Implement Tree Navigation for the CMIP5 Questionnaire
- tickets/244: Processing the mindmaps (bundled version) to create XML suitable for …
- tickets/245: Work in progress
- tickets/247: Ingest ESG metadata into mindmaps
- tickets/248: CMIP5 Questionnaire Timeline
- tickets/249: Questionnaire to CIM Conversion
- tickets/250: CMIP5 Conformance wiki for ticket #250
- tickets/253: Questionnaire Metadata Validation
- tickets/254: Table 1: CMIP5 constraints not enforced by the Questionnaire
- tickets/277: Proposed updates to the CIM Grid logical data model
- tickets/280: add / revise definitions of terms used in the CIM
- tickets/281: when should references use XPath and when should they embed documents …
- tickets/31
- tickets/326/aerosols
- tickets/326/atmos
- tickets/326/atmos_chem
- tickets/326/land_ice
- tickets/326/land_surf
- tickets/326/ocean: Herafter is the previous version of definitions tables for Ocean, included …
- tickets/326/ocean_biochem
- tickets/326/sea_ice: Herafter is the previous version of definitions tables for Ocean, included …
- tickets/485: CMIP5 Questionnaire
- tickets/509: What Deployment/Hardware/Configuration? Information Should Be Recorded?
- tickets/519
- tickets/55: Metafor Governance
- tickets/636: Wiki Page for Ticket #636 (Review of Grid Properties in MindMaps)
- tickets/684: Discussion of Ensemble Handling Issues
- tickets/707: THREDDS to CIM instances tool
- tickets/709: CIM v1.5
- tickets/715: METAFOR Success Criteria
- tickets/778: Integrate Controlled Vocabularies with the CIM
- tickets/78
- tickets/79: CIM Differencing Tool Design Document
- tickets/810
- tickets/862: Required CIM Software Component Properties
- tickets/868: Some Documentation of Issues associated with ticket:868
- tickets/870: Moving towards CIM2.0
- tickets/888: Definition of unconfigured vs configured model
- tickets/92: Outstanding CIM Prototype Human GUI Issues
- tickets/920: O&M
- tickets/920/options4om1: Initial Step
- tickets/920/sidl: Scientific Interface Definition Language (SIDL)
- tickets/921
- tickets/925: A Common Information Model paired with scientific Controlled Vocabularies …
- tickets/926: EGU abstract - The CMIP5 questionnnaire: web-based metadata collection for …
- tickets/927
- tickets/986: CIM v1.7
