| Element | Definition | Required |
|---|---|---|
| Short Name | This element describes the data set short name | Yes |
| Version | This element describes the data set version. | Yes |
| Version Description | This element describes the the version of the data set. | |
| Entry Title | This element describes the title of the resource described by the metadata. | Yes |
| DOI | This element stores the DOI (Digital Object Identifier) that identifies the data set. | |
| Abstract | This element provides a brief description of the resource the metadata represents. | Yes |
| Purpose | ||
| Science Keywords | This element enables specification of Earth Science keywords. | Yes |
| Platform | This element describes the relevant platforms used to acquire the data. | Yes |
| Instrument | This element is used to register the device that measured or recorded the data, including direct human observation. | Yes |
| Related URL | This element describes any resource-related URLs that include project home pages, resource information pages, services, related data, archives/servers, metadata extensions, direct links to online software packages, web mapping services, links to images, documents, or other data. | |
| Data Language | ||
| Data Dates | ||
| Data Center | Yes | |
| Contact Group | ||
| Contact Person | ||
| Collection Data Type | ||
| Processing Level | Yes | |
| Collection Citations | ||
| Collection Progress | Describes the production status of the data set. There are three choices: PLANNED refers to data sets to be collected in the future and are thus unavailable at the present time. For Example: The Hydro spacecraft has not been launched, but information on planned data sets may be available. ACTIVE refers to data sets currently in production or data that is continuously being collected or updated. For Example: data from the AIRS instrument on Aqua is being collected continuously. COMPLETE refers to data sets in which no updates or further data collection will be made. For Example: Nimbus-7 SMMR data collection has been completed. NOT APPLICABLE refers to data sets where collection progress doesn't make sense. For example a calibration collection record. NOT PROVIDED - It is necessary for this value to exist so that the CMR can translate older non UMM compliant records into the latest UMM specification where CollectionProgress is required. | Yes |
| Quality | Free text description of the quality of the collection data. Description may include:
| |
| Use Constraints | Designed to protect privacy and/or intellectual property by allowing the author to specify how the collection may or may not be used after access is granted. This includes any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the item. Providers may request acknowledgement of the item from users and claim no responsibility for quality and completeness. Note: Use Constraints describe how the item may be used once access has been granted; and is distinct from Access Constraints, which refers to any constraints in accessing the item. | |
| Access Constraints | ||
| Metadata Language | The language used in the metadata record. | ... |
| Metadata Dates | Dates related to activities involving the metadata record itself. For example, Future Review date is the date that the metadata record is scheduled to be reviewed. | |
| Directory Names | Formerly called Internal Directory Name (IDN) Node (IDN_Node). This element has been used historically by the GCMD internally to identify association, responsibility and/or ownership of the dataset, service or supplemental information. Note: This field only occurs in the DIF. When a DIF record is retrieved in the ECHO10 or ISO 19115 formats, this element will not be translated. |
Overview
Content Tools