Page History
Table of Contents | ||
---|---|---|
|
Element Description
The Data Metadata Dates element is used to identify dates when the data or resource itself changed metadata changed in some way. This element is made of two sub-elements, Type and Date. The Type describes what the date represents: a future review, when the resource metadata was created, last updated, or planned for deletion. The Date describes when the resource metadata had or will have the action performed on it as described by the Type element.
Best Practices
Each Data Metadata Date is accompanied by a Type. The Type must be selected from a controlled vocabulary list. There are four options available for Type:
- CREATE: The date the resource metadata was created. This should be the date the data set metadata was published in the database/ entered into the data archive system.
- UPDATE: The date the resource metadata was last updated. This includes any changes made to the data itself, such as a change in processing or a change in the file naming convention.
- REVIEW: The date of a planned future review of the resourcemetadata.
- DELETE: The date the resource metadata record will be deleted.
At least one Data Date must be providedProviding a Metadata Date is optional. Multiple Data Metadata Dates are allowed, however, the same date type should not be repeated more than once in the same record (for example, a CREATE and an UPDATE time can be provided, but two CREATE times cannot be provided in the same record). All dates should comply with the ISO 8601 Standard.
Examples:
Type = CREATE Date: 2010-02-01
Type = UPDATE Date: 2018-02-01
Type = REVIEW Date: 2019-02-01
Element Specification
Data Metadata Date is an optional field. Multiple Data Metadata Dates may be provided, if necessary (Cardinality 0..*)
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-C | DataDateMetadataDate/Type | Enumeration | CREATE UPDATE REVIEW DELETE | n/a | No | 0..* | The same Type should not be used more than once in the same record. |
UMM-C | DataDateMetadataDate/Date | dateTime | n/a | n/a | No | 0..* | The actual date that the event associated with the data metadata occurred/ will occur goes in this field. |
Metadata Validation and QA/QC
All metadata entering the CMR goes through the below process to ensure metadata quality requirements are met. All records undergo CMR validation before entering the system. The process of QA/QC is slightly different for NASA and non-NASA data providers. Non-NASA providers include interagency and international data providers and are referred to as the International Directory Network (IDN).
Lucidchart rich-viewer false autofit true name Copy of Wiki Page Metadata Evaluation Workflow-1939-51df84 width 1102 pages-to-display id 98e5dc28-3252-4209-953f-66f1378e1cf4 align Left height 299
Please see the expandable sections below for flowchart details.
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
<> |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Rules
|
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10Data Date is an optional field. Multiple Data Providing a Metadata_Creation date and Metadata_Last_Revision date is required in DIF 10. The Metadata_Future_Review and Metadata_Delete fields are optional. Multiple types of Metadata Dates may be provided, if necessary (Cardinality 01..*)
Value needed for translations: Not provided - The value of 'Not provided' might appear in the Metadata_Dates/DataMetadata_Creation and/or the Metadata_Dates/DataMetadata_Last_Revision fields as a result of software used to convert older versions of DIF to DIF version newer versions of DIF (such as 10.2 or 10.3). Required fields that are left empty in older versions a DIF record are automatically populated with 'Not provided' when being converted to a new version, and both Metadata_Dates/DataMetadata_Creation and Metadata_Dates/DataMetadata_Last_Revision are required in the latest version of DIF version 10.2. Both Data_Creation and /Data_Last_Revision were changed from required to optional in DIF version 10.3. Therefore, no DIF 10.3 records should have 'Not provided' as a value in the Data_Creation or Data_Last_Revision fields. This value should not be used by metadata providers. Example Mapping . This value should not be used by metadata providers. Example Mapping
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Insert Time and Last Update are required Providing a Revision Date is optional in ECHO 10 (Cardinality: 1). Delete Time is optional. Only 1 Delete Time may be provided (Cardinality: 0..1).
| 1 | The most recent update which occurred on the data provider's database. The date provided in the LastUpdate field will be labeled with the DataDate/Type of 'UPDATE' when translated to UMM. | Example Mapping
Section | |||
---|---|---|---|
|
The date the collection is planned to be deleted from the data provider's database.
The date provided in the DeleteTime field will be labeled with the DataDate/Type of 'DELETE' when translated to UMM.
| ||||||||||||||
|
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
ISO 19115-2 MENDSData Metadata Date is an optional field. Multiple Data Metadata Dates may be provided, if necessary (Cardinality 0..*)
Enumeration/Code List Mapping | ||||||||||||||
ISO MENDS | Translation Direction | UMM | ||||||||||||
creation | ↔ | CREATE | publication | ↔ | ||||||||||
revision | ↔ | UPDATE |
"Date" <- this isn't a codelist value?? with /gmi:MI_Metadata/gmd:metadataExtensionInfo/gmd:MD_MetadataExtensionInformation/gmd:extendedElementInformation/ gmd:MD_ExtendedElementInformation/gmd:domainValue/gco:CharacterString= {the actual date} with /gmi:MI_Metadata/gmd:metadataExtensionInfo/gmd:MD_MetadataExtensionInformation/gmd:extendedElementInformation/ gmd:MD_ExtendedElementInformation/gmd:parentEntity gco:nilReason="inapplicable" with /gmi:MI_Metadata/gmd:metadataExtensionInfo/gmd:MD_MetadataExtensionInformation/gmd:extendedElementInformation/ gmd:MD_ExtendedElementInformation/gmd:rule gco:nilReason="inapplicable" with /gmi:MI_Metadata/gmd:metadataExtensionInfo/gmd:MD_MetadataExtensionInformation/gmd:extendedElementInformation/ gmd:MD_ExtendedElementInformation/gmd:source gco:nilReason="inapplicable" | The actual date should be provided in the gmd:domainValue/gco:CharacterString field. A codelist value (gmd:CI_DateTypeCode) should be provided with the date in order to identify the date Type. These fields can be repeated as many times as necessary - however, note that the same DateTypeCode should not be used more than once in the same record. If the same DateTypeCode is used more than once, only the first occurrence will be translated to UMM. |
Enumeration/Code List Mapping
ISO MENDS | Translation Direction | UMM |
---|---|---|
creation | ↔ | CREATE |
publication | ↔ | |
revision | ↔ | UPDATE |
Example Mapping
Section | |||||||
---|---|---|---|---|---|---|---|
|
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
ISO 19115-2 SMAP
Data Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)
|
with
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/ gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue=
dateTime
codelist
The actual date should be provided in the gco:DateTime field.
A codelist value (gmd:CI_DateTypeCode) should be provided with the date in order to identify the date Type. These fields can be repeated as many times as necessary - however, note that the same DateTypeCode should not be used more than once in the same record. If the same DateTypeCode is used more than once, only the first occurrence will be translated to UMM.
Enumeration/Code List Mapping
|
Expand | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||
ISO 19115-2 SMAPMetadata Date is an optional field. Multiple Metadata Dates may be provided, if necessary (Cardinality 0..*)
Example Mapping Section | Column | | |||||||||||||||||||||
| |||||||||||||||||||||||
No Format |
xml#MD_ |
DatatypeCode" |
codeListValue=" |
Date" <- this isn't a codelist value?? with /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:metadataExtensionInfo/gmd:MD_MetadataExtensionInformation/ gmd:extendedElementInformation/gmd:MD_ExtendedElementInformation/gmd:domainValue/gco:CharacterString= {the actual date} | dateTime codelist | The actual date should be provided in the gmd:domainValue/gco:CharacterString field. A codelist value (gmd:CI_DateTypeCode) should be provided with the date in order to identify the date Type. These fields can be repeated as many times as necessary - however, note that the same DateTypeCode should not be used more than once in the same record. If the same DateTypeCode is used more than once, only the first occurrence will be translated to UMM. |
Enumeration/Code List Mapping
ISO MENDS | Translation Direction | UMM |
---|---|---|
creation | ↔ | CREATE |
publication | ↔ | |
revision | ↔ | UPDATE |
Example Mapping
Section | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UMM Migration
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|---|---|
Future Mappings
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
ISO 19115-1Metadata Date is an optional field. Multiple Metadata Dates may be provided, if necessary (Cardinality 0..*)
|
UMM Migration
Future Mappings
Expand | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||
ISO 19115-1Data Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)
Enumeration/Code List Mapping
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | 5/2/2018 | No changes were made for Data Metadata Dates during the transition from version 1.9.0 to 1.10.0 |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 1011/166/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |