Element Description
The Data Dates element is used to identify dates when the data or resource itself 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 was created, last updated, or planned for deletion. The Date describes when the resource had or will have the action performed on it as described by the Type element.
Best Practices
Each Data 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 was created. This should be the date the dataset was published in the database/ entered into the data archive system.
- UPDATE: The date the resource 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 resource.
- DELETE: The date the resource will be deleted.
Providing a Data Date is optional. Multiple Data 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 Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-C | DataDate/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 | DataDate/Date | dateTime | n/a | n/a | No | 0..* | The actual date that the event associated with the data 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).
Please see the expandable sections below for flowchart details.
Dialect Mappings
UMM Migration
None
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.15.3 | 7/1/2020 | No changes were made for Data Dates during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Data Dates during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Data Dates during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Data Dates during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Data Dates during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for Data Dates during the transition from version 1.12.0 to 1.13.0. |
1.12.0 | 01/22/2019 | No changes were made for Data Dates during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No changes were made for Data Dates during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 05/02/2018 | No changes were made for Data Dates during the transition from version 1.9.0 to 1.10.0. |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 10/16/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |