Changes between Version 7 and Version 8 of Projects/IS-ENES2/Metadata


Ignore:
Timestamp:
05/06/13 13:56:32 (7 years ago)
Author:
lawrence
Comment:

Legend:

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

    v7 v8  
    6060 
    6161 0. Telco to discuss finalisation of CMIP5 CIM content -- Bryan -- [5-8 weeks], depends on 
    62    0. Resource at Reading - short or long term. 
     62   * Resource at Reading - short or long term. 
    6363 0. Implementation of CIM questionnaire for SPECS   with additional vocabularies[ tbd] 
    6464 
    65 ==== Relevant IS-ENES2 DoW Milestones and Deliverables ==== 
     65== Relevant IS-ENES2 DoW Milestones and Deliverables == 
     66 
     67NA4 states that: 
     68 * The scientific coordination and development of CIM and CV extension will be done in NA4 whereas the technical support for the resulting governance activities will be covered in SA2. NA4 will further organise the community evaluation of CIM generation software, developed both in JRA3 as well as in other projects. A gap and duplication analysis as well as a sharing of best practice and experience with various experimental generation of CIM content will be performed. 
     69 
     70This suggests that CMS should *not* be doing the metadata scientific leadership, as it is not funded in the NA4 work package. However, if we do take on the leadership, this might give us an opportunity to suggest that one of the NA4 partners takes on some aspect of the technical work. 
     71 
     72==== JRA3====  
     73 
     74JRA3 will ''enhance the existing data archives services of SA2 by delivering enhancements on four key service packages '', one of which is the : 
     75 *  '''Metadata Services Package''' The metadata infrastructure necessary for managing petascale climate model archives includes a range of components – many of which are encapsulated in the specifications of the METAFOR Common Information Model (CIM). Software components delivered by the FP7 METAFOR and IS-ENES1 projects will need further development and enhancements to meet ongoing ENES requirements – particularly those captured and delivered in, respectively, the NA4 and SA2 work packages of this project. There will be two major activities:  
     76   0. improving and extending existing tools for metadata capture, and  
     77   0. refactoring and extending tools to provide metadata services (including the repository and services to be deployed in SA2). 
     78 
     79This is being delivered in Task 2.1 (with a small contribution from the UKMO): 
     80 *  '''Tools for metadata capture and generation'''. The primary tool used thus far for meta-data creation (in the context of IS-ENES support for CMIP5) has been the METAFOR questionnaire. This tool consists of a graphical user interface handling answering hundreds of questions about model capability and configuration. The existing tools are heavily customised for CMIP5, and need re-factoring to improve flexibility for alternative users. As CIM capability is extended within NA4, the new tool will be modified accordingly, and deployed in support of SA2. The MetO internal tool for meta-data will also be modified to directly generate CIM content so that alternative approaches to meta-data entry can be compared. 
     81 * This task is associated with: 
     82   * Deliverable D11.4: Report on meta-data services, due in month 39, itself associated with: 
     83     * Milestone: MS113: Revised Generic Questionnaire software package available.  
     84     * Milestone: MS116: MetO Metadata Entry Tool Evaluation, due in month 21.  
     85 
     86==== NA4 ==== 
     87 
     88CMS does not have a formal engagement in NA4, but clearly JRA3 is related to NA4, and the proposal that CMS has leadership for Metadata, means that the relevant information about NA4 is included here: 
     89 
     90Task 2:  
     91 * '''Meta-data, interoperability and standardisation (37 pm)''' (Engaging, STFC, CERFACS, CSAG, MF-CNRM, UNIMAN, CSAG in collaboration with ESA. 
     92 * This task focuses on extending the FP7 METAFOR “Common Information Model” (CIM) to support new data and activities, better experiment description, more utility in quality control – and coordinate generation of new content. CIM extensions and new controlled vocabulary will need to be coordinated on a global scale, and notably in direct coordination with the US-led CURATOR and National Unified Operational Prediction Capability (NUOPC) consortiums. 
     93 * This task will establish and manage a community process for identifying and delivering CIM upgrades to improve and extend support for global climate model documentation, including better descriptions of coupling and frameworks, and statistical downscaling methodologies. New support for regional climate models and re-analyses data will also be initiated. This will lead to new CIM controlled vocabularies (CV) to be handed to SA2 for community governance. Working groups will be established for each theme, and these will, in the first 6 months, identify and establish contact with the key community projects (in Europe and elsewhere) in each area.  
     94 * Liaison with similar projects working on remote sensing and ground based observations will be important – particularly in the context of GMES and WMO Climate Service Information System. 
     95  * The DoW then implies that Task 2 itself (rather than one of the data activities) will also   
     96    *  (Deliver close collaboration) with ESA to foster the exploitation of European satellite data archive and the new generation of missions (Earth Explorers & Sentinels) and products (in particular from ESA Climate Change Initiative (CCI) when available). More precisely, given the direct involvement of ESA within IS-ENES2, we will ensure interoperability of the ESA CCI database repositories. 
     97       * (This is obviously nothing to do with Metadata, but perhaps the DoW means "interoperatiblity of methods for getting to such metadata in these repositories". More realistically, this should probably now read "Work closely with CHARMe on these issues". 
     98   * The standardisation efforts will be extended to the CORDEX programme statistical downscaling component, with specifications of the experiment design and data format. 
     99 
     100The relevant deliverable is: 
     101 * Deliverable D5.4: '''Report on metadata controlled vocabulary extensions''' (Month 45): The report will be based on the identification and the delivery of CIM upgrades to improve and extend support for global climate model documentation, including better descriptions of coupling and frameworks, and statistical downscaling methodologies. New draft support for regional climate models and re-analyses data will also be described. This will lead to new CIM controlled vocabularies (CV) that will be described in details in this report. Results will be handed to SA2 for community governance. Itself associated with: 
     102   * Milestone MS54: Synthesis report on metadata requirements regarding relevant data archives, due at month 42, and the responsibility of STFC. 
     103 
     104 
     105 
     106 
     107