...
| Attribute Name | Value | Examples | Comment | |||
|---|---|---|---|---|---|---|
| Conventions | CF convention string [Other convention] :... | "CF-1.6" "CF-1.6 C3S-0.1" | Multiple conventions may be included (separated by blank spaces) | |||
| title | A controlled vocabulary will be provided CF: Free text ACDD (highly recommended)C3S: A controlled vocabulary will be provided | "IPSL-CM5A-LR model output prepared for CMIP5 RCP4.5" | A short phrase or sentence describing the dataset. In many discovery systems, the title will be displayed in the results list from a search, and therefore should be human readable and reasonable to display in a list of such names | |||
| references | CF: Free text C3S: URIs (such as a URL or DOI) for papers or other references. A valid doi is recommended CF: Free text | "doi:10.5194/gmd-8-1509-2015" | references to more information Antonio S. Cofino Gonzalez: Published or web-based references that describe the data or methods used to produce it. This attribute is recommended in the CF conventions. Recommend values are URIs (such as a URL or DOI) for papers or other references.The validity of the doi values will be checked. Warnings will be raised for any other content.content. | |||
| source | A methodology to build this attribute will be provided |
| source | Free text |
| Where the data is fromAntonio S. Cofino Gonzalez: The method of production of the original data. If it was model-generated, source should name the model and its version. If it is observational, source should characterize it. This attribute is defined in the CF Conventions. Examples: 'temperature from CTD #1234'; 'world model v.0.1'.Francisco Doblas-Reyes I'm still missing information about the initialisation: what set of initial conditions was used, whether perturbations were used, etc Eduardo Penabad: Can you (Francisco Doblas-Reyes) suggest how to do this? |
| institution | CF: Free text C3S: A controlled vocabulary will be provided | "Met Office" Francisco Doblas-Reyes I'm not convinced "Met Office" is descriptive enough. Shouldn't it be something like "C3S"? Unknown User (brookshaw): "institution" is the origin of the data. Things like C3S will be specified elsewhere (e.g. project) | Who produced the data Antonio S. Cofino Gonzalez: The name of the institution principally responsible for originating this data. | |||
| contact | CF: Free text C3S: Copernicus User Support URI should be used
| "http://copernicus-support.ecmwf.int" | Antonio S. Cofino Gonzalez: The CMIP5/SPECS DRS define this attribute. The ACDD defines: creator_name, creator_email, creator_url, publisher_name, publisher_email, publisher_url | |||
| project | CF: Free text C3S: "C3S Seasonal Forecast" is required, additional project info (e.g. ITT details) is optional | "C3S Seasonal Forecast" | Antonio S. Cofino Gonzalez: The name of the project(s) principally responsible for originating this data. Multiple projects can be separated by commas, as described under Attribute Content Guidelines. Examples: 'PATMOS-X', 'Extended Continental Shelf Project'. | |||
| creation_date | SPECS: YYYY-MM-DDThh:mm:ss<zone> NOTE: This is ISO 8601:2004 extended format | "2011-06-24T02:53:46Z" | Antonio S. Cofino Gonzalez: The date on which this version of the data was created. (Modification of values implies a new version, hence this would be assigned the date of the most recent values modification.) Metadata changes are not considered when assigning the creation_date. The ISO 8601:2004 extended date format is recommended. The ACDD 1.3 names this attribute as | |||
| comment | Free text | "This 21th century simulation has been forced by prescribed concentration following the rcp 4.5 scenario." | Antonio S. Cofino Gonzalez: Miscellaneous information about the data, not captured elsewhere. This attribute is defined in the CF Conventions. | |||
| forecast_type | C3S: Controlled Vocabulary "forecast" or "hindcast" | "forecast" | To identify the type of data | |||
| history | Free Text |
| To record relevant information, such as the command history which led to this file being produced Francisco Doblas-Reyes I understand that the versioning of the software used to create the data can be included either here or in the commit attribute. Any idea how/when to make the decision?
| |||
commit, iso_lineage or lineage | Free text (ISO Lineage model 19115-2) | "Produced using CDS Toolbox v1.0" | trace of the tools/scripts used Antonio S. Cofino Gonzalez: We need a more implementtios examples on this. This could achiived in EQC WP where metadata is been part of their activities (i.e. WP4@QA4SEAS). ISO 19115-2 defines a linage model where this is been considered. TBD. | |||
| summary | ACDD (highly recommended): Text, defined phrase C3S: The content will be provided | A short paragraph describing the dataset | ||||
| keywords | ACDD (highly recommended) : text, controlled vocabulary C3S: The content will be provided | A comma separated list of key words and phrases. | ||||
| forecast_reference_time | SPECS: YYYY-MM-DDThh:mm:ssZ NOTE: This is ISO 8601:2004 extended format | "2011-06-01T00:00:00Z" | time of the analysis from which the forecast was made UTC zone is required |
...