Changes between Version 10 and Version 11 of Projects/IS-ENES2/Metadata


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

Legend:

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

    v10 v11  
    55Amongst other things, it is intended to help the briefing of CMS staff working on IS-ENES2. 
    66 
    7 Total metadata resource at CMS (not including NA2): 21pm, all associated with task 2.1 of JRA2. 
     7Total metadata resource at CMS (not including NA2, which adds another 6-9pm): 21pm, all associated with task 2.1 of JRA2. 
    88 
    99==== Background ==== 
     
    7474In what follows we cover the metadata aspects of the data packages first, then the metadata aspects of the model packages. 
    7575 
     76[[span(style=color: #FF0000 NOT ALL DELIVERABLES AND MILESTONES ARE LISTED YET)]] 
     77 
    7678==== JRA3====  
    7779 
     
    127129     * Elsewhere a firmer statement is that WDCC/DKRZ will operate the CIM model and experiment repository and provide services for climate model data quality control. I expect this means CNRS-IPSL are maintaining the code for the operational service. 
    128130 
     131=== Metadata in the "Model" Packages === 
     132 
     133==== NA2 ==== 
     134 
     135(Future Models) 
     136 
     137The relevant part of NA2 is Task 2.1 
     138 * Task 2.1: '''Model Structure and Code Evaluation'''. The key aim of this sub-task is to prepare the ground for subsequent community discussion of the different approaches in use in Europe. The first activity will be to establish a consistent methodology for documenting key model components, the exchanges between them, and their scaling properties - across all the major European models. This methodology will exploit the model metadata work in other work packages, and the service documentation activities. It is likely that the resources available will only allow the initial analysis of two models, but this will then feed into a workshop to establish the efficacy for more wide usage of the methodology by model groups. 
     139  * Post DoW Technical Detail: It is proposed that we begin with whatever codes are available from JRA1 (high resolution) and JRA2 (benchmarking). The idea is that we will exploit code-parsing to produce a CIM description of the software, which would then be compared and analysed by a human. Rupert Ford (UMAN) will use some of his time in NA4 to help with producing a CIM outputting code-parser, which may need to make use of CIM2.x. 
     140 * This is due in year one of the project!  
     141 
     142==== NA5 ==== 
     143 
     144(Workflow environments)  
     145 
     146The relevant part of NA5 is Task 3: 
     147 * Task 3: '''Metadata creation and usage '''. Significant experience has been gained in CMIP5 and related exercises in providing meta-data to describe ESM experiment sets. A number of sites are recognising the need to build meta-data capture into the heart of the ESM experiment process and to drive data provision exercises; this needs to be supported by both software and processes. This networking activity will promote the sharing of experiences and designs in this emerging area through two workshops organised by DKRZ. The aim will be to encourage investment in software and working processes that will allow more comprehensive meta-data to be collected more efficiently. Further, the development of workflow and diagnostic solutions will be influenced by the meta-data requirements. To support the workshop, the Met Office and DKRZ will develop documents that identify key interfaces between the meta-data and the experiment definition and modelling processes, and explore design solutions. 
    129148 
    130149 
    131150 
     151 
     152 
     153 
     154