the starting point for WP1: Project Management
- related requirements
- related use-cases
- software management
- related tickets:
- open tickets (20)
- closed tickets (62)
- notes
- wiki index
related requirements
...coming soon...
related use-cases
...coming soon...
related tickets
open
- #9
- Organize Month 24 All Partners Meeting
- #10
- CIM User Survey
- #11
- Organize Month 36 All Partners Meeting
- #12
- Final Science and Technical Board (STAB) Report
- #14
- Month 24 Annual Report and Management
- #15
- Month 36 Annual Report and Management
- #173
- Letter of support PARADE consortium
- #186
- Revisit EU Project scope and D's
- #223
- Interactions with policy makers
- #562
- Test ticket
- #605
- Talk to Sylvie about the IS-ENES scoping meeting in March
- #640
- Relationship between Metafor and IS-ENES
- #669
- Prepare slides for the Metafor year 2 review
- #693
- SERVICES SPRINT 07 - Tracking ID Service
- #703
- Missing long_name for CNRM/CERFACS Modeling centre
- #710
- Year 2 review presentations
- #715
- Success Criteria
- #734
- Software Deliverables Release Roadmap
- #764
- Parameter Value Definitions
- #779
- Example Questionnaire Content
closed
- #1
- Set up Metafor TRAC system
- #2
- Create METAFOR www site
- #6
- Organize Month 6 All Partners Meeting
- #7
- Identify new partners for WP3 - Service content creation and testing
- #8
- Organize Month 12 All Partners Meeting
- #13
- Month 12 Annual Report and Management
- #32
- Get EU URL
- #33
- Register METAFOR domain
- #34
- Present an initial visitor with an overview of the project
- #35
- Acknowledge the source of funding on Website
- #36
- Include FP7 logo
- #37
- RSS feed
- #38
- Set up blog(s)
- #39
- Search Engine Optimization (SEO)
- #40
- Link to Partners Pages
- #44
- Look into Genesys for conferencing
- #96
- Get trac to sort the milestone dropdown list properly
- #97
- Get trac and joomla URLS to integrate
- #98
- Move prism wiki METAFOR pages to new METAFOR www site
- #99
- Look into redirecting metafor@lists.enes.org to metaforclimate.eu
- #100
- Sign off on Consortium Agreement
- #103
- Determine best day for teleconference
- #104
- Identify STAB members
- #106
- Get all admin names and emails
- #107
- administer enes mailman lists
- #109
- Add enes logo to template
- #110
- Partners pages linking to METAFOR home page
- #112
- username on joomla but not trac
- #115
- First Monthly Steering Committee Telecon
- #116
- GET CORDIS www site to link to the METAFOR Project page
- #117
- Who's who
- #130
- EU METAFOR fact sheet
- #132
- Create poll to set dates for Month 6 All Partners Meeting
- #133
- Create menu item to Work Packages work pages
- #134
- Look into submitting an item from the front end
- #136
- Create RDF category in Related Links
- #137
- Create new Forum for RDF/OWL discussion
- #138
- Create doodle poll for Telco 2 meeting
- #139
- Telco 2 - May 15, 2008
- #146
- List of accomodations for All Partners 6 month meeting Toulouse
- #147
- Arrange Room for All Partners Month 6
- #149
- set up svn repository
- #150
- create a list of software tools we use
- #152
- Deliverables procedure page
- #153
- Upgrade Trac to 0.11
- #155
- test svn repository
- #159
- Add issue ticket type
- #160
- Put Sarah Callaghan on metafor list
- #170
- Decide in Dec 08 if CIM V 1.0 (D2.2) M12 will be on time
- #171
- Arrangements for Luigi Fusco to attend Toulouse mtg
- #176
- Set meeting documents and leaflets to be viewable by the public
- #222
- Give the STAB access to the full Metafor site
- #226
- Restructure wiki
- #227
- Mail list with what to do if website or Trac breaks
- #282
- Discussion about remapping wiki roadmap and Gannt chart
- #374
- return to simulation button needs simulation name
- #459
- web page is required on the responsible party
- #494
- References: An offline reference should notl require a URL
- #579
- vocabulary for "coupling" input types
- #699
- bug in adding modelmods
- #731
- export xml not working
- #780
- Model names in Questionnaire
notes
Here is a blurb about WP1.
Wiki Index
- WP1: Wiki Index
- WP1/SoftwareManagement: Live Deliverables
- WP2: the starting point for WP2: The CIM
- 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
- 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/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/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/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
- 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/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/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/92: Outstanding CIM Prototype Human GUI Issues