Document Sample
downloading Powered By Docstoc
					METAFOR Task Tracker


 About Trac

 Browse Source
 View Tickets

Context Navigation
 Start Page
 Last Change

Welcome to the METAFOR project

Welcome to the METAFOR wiki and issue tracking site. This site provides a place for the METAFOR team to collaboratively de
discuss/resolve issues pertaining to that technology. The content is expected to change regularly, reflecting the current statu

The main objective of the METAFOR project was to develop a Common Information Model (CIM) to describe climate data an
produce it in a standard way, and to ensure the wide adoption of the CIM. METAFOR addressed the fragmentation and gaps
metadata (data describing data) as well as duplication of information collection and problems of identifying, accessing or usi
currently found in existing repositories. METAFOR has optimized the way climate data infrastructures are used to store know
value to primary research data and information, and providing an essential asset for the numerous stakeholders actively eng
issues (policy, research, impacts, mitigation, private sector).
The METAFOR project formally finished in August 2011. However, work on the CIM, CMIP5 questionnaire and tools and serv
informal manner. This website will remain active indefinitely.

Good Starting Points
 The Rules - how this Trac site is meant to be used
 recent changes - a list of changes to this site listed in reverse chronological order; note that the menu in the top-right can r
 wiki, tickets, or repository only (if you want to look at tickets, please select both "ticket changes" and "ticket details").
   wiki changes
   ticket changes
   repository changes
 active tickets - the set of all active tickets grouped by "component"
   tasks - active task tickets
   issues - active issue tickets
   admin - active admin tickets (reports, meetings, etc.)
 current releases of the CIM:
   CIM v1.5
   CIM v1.4
   CIM v1.3
   CIM v1.2
   CIM v1.1
   CIM v0.2
 CIM tools & services: - The METAFOR Portal - The CMIP5 Questionnaire - The Quality Control Tool
 help - links to useful documentation

 deliverables - List of deliverables in date order
 Dissemination - Dissemination materials (including leaflets and quarterly newsletters)

Organization of Wiki Pages
Each wiki page should be located appropriately. The following directory structure should be used:


Where the <top-level-components> are: WP1-7 and CMIP5. Additional sub-directories can be added as needed for specific c
page for each top-level-component should include links to all relevant requirements, use-cases, and tickets.

Further information can be found here.

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


 egg.jpg (1.9 kB) - added by allyn 3 years ago. We bet you can't eat just one!
 Metafor_logo.jpg (15.1 kB) - added by sarah 2 days ago.
 metafor_logo_banner2.png (58.7 kB) - added by sarah 2 days ago.

Download in other formats:

 Plain Text

Powered by Trac 0.11.1
By Edgewall Software.

Visit the Trac open source project at
ETAFOR team to collaboratively develop technology and
gularly, reflecting the current status of METAFOR.

 (CIM) to describe climate data and the models that
essed the fragmentation and gaps in availability of
 ms of identifying, accessing or using climate data that are
astructures are used to store knowledge, thereby adding
umerous stakeholders actively engaged in climate change
questionnaire and tools and services are continuing in an

at the menu in the top-right can restrict the changes to
hanges" and "ticket details").
be added as needed for specific components. The index
ases, and tickets.

ent attached note
, Dependencies, and …

s (sample requirement)
included …

Shared By: