Changes between Version 4 and Version 5 of Projects/IS-ENES2/Metadata


Ignore:
Timestamp:
05/06/13 09:14:15 (7 years ago)
Author:
lawrence
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Projects/IS-ENES2/Metadata

    v4 v5  
    1919==== Current Priorities ==== 
    2020 
     21(These are across the entire IS-ENES2, so CMS doesn't have to do all this, but we probably have to coordinate it.) 
     22 
    2123Generic: From an IS-ENES2 perspective: 
    2224 0. Establish the internal IS-ENES2 metadata organisation 
    2325   a. Need to make sure it is cross-cutting wrt IS-ENES2 work packages (JRA, NA etc). 
    2426   a. May take some advantage of es-doc cog, and/or telcos, as well as internal mechanisms.  
     27   a. Identify who is the relevant European community - funded within this project or not. 
    2528 0. Re-establish the European network to feed into es-edoc 
    2629 0. Establish and document priority actions for IS-ENES2 activities 
     
    3639 0. Communicate with modelling groups accordingly. 
    3740 
     41Technical Activities: 
     42 0. CIM: 
     43   a. Institute the governance body documented by Metafor 
     44   a. Establish any new requirements from the CMIP5 quality control exercise. 
     45   a. Establish any new requirements from new projects (s2d, obs4mips, CCI, Copernicus, Ermitage). 
     46   a. Revisit CIM 2.0 in the light of new requirements. 
     47 0. Controlled Vocab (CV): 
     48   a. Ensure that the CV is covered by the CIM governance body too (as proposed by Metafor). 
     49   a. Evaluate lessons from CMIP5 for global GCM CV. 
     50     * It has been suggested that some discrimination between core and tiers would be helpful, but consider whether this is an issue for the CV, or the tools (including creators and validators). 
     51   a. Consider how (or whether) to incorporate other CVs (e.g. downscaling, ERMITAGE, s2d, obs etc). 
     52 0. Tools (taking responsibility for technical work at CMS as appropriate): 
     53   a. Evaluate the future of "the questionnaire" vis-a-viz other possible tools. 
     54   a. Help guide the evolution of other tools (including viewers, comparators and validators) 
     55   a. Liaise with work on Annotation (CHARMe) 
     56   a. Scientific and Technical responsibility for repository. Who? Where? How? 
     57     * Who does and validates content migration? 
    3858 
    3959