Page History
Table of Contents | ||
---|---|---|
|
Element Description
Note: This wiki page is a draft/ work in progress
Data Dates is comprised of dates for 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 Type and dateDate. The type Type describes what the date represents: a future review, when the resource was created, last updated, or planned for deletion. The date Date describes when the resource had an or will have the action performed on it or when the action will occur as described by the type Type element.
Best Practices
The Creation, Last Revision, Future Review, and Planned Deletion dates exist in various places in the different standards.
All data dates have been consolidated under this element. They will be typed and will all be represented by the ISO 8601 date and time conventions as part of the reconciliation process.
Examples:
Type=CREATE Date: 2010-02-01
Type=UPDATE: Date: 2018-02-01
Type=REVIEW: Date: 2019-02-01
Element Specification
CREATE
UPDATE
DELETE
REVIEW
n/a
n/a
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.
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
<> |
title | ARC Metadata QA/QC |
---|
This element is categorized as highest priority when:
- n/a
This element is categorized as medium priority when:
- n/a
This element is categorized as low priority when:
- n/a
ARC Automated Rules
If novalue is provided, return is "np"Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
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).
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 Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
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 Dates may be provided, if necessary (Cardinality 0..*)
| ||||||||||||||||||||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||
Specification | Path | Type | Constraints | Required in DIF 10? | Cardinality | Notes | DIF 10 | Metadata_Dates/Data_Creation | n/a | No | 0..1 | In DIF 10 both the metadata and data dates are located under the DIF/Metadata_Dates element. The difference is that the sub-elements of Metadata_Creation, Metadata_Last_Revision, Metadata_Future_Review, and Metadata_Delete describe the metadata dates and the sub-elements of Data_Creation, Data_Last_Revision, Data_Future_Review, Data_Delete describe the resource dates. | DIF 10 | Metadata_Dates/Data_Last_Revision | Date or Time or EnumType | n/a | No | 0..1 | DIF 10 | Metadata_Dates/Data_Future_Review | Date or Time or EnumType | n/a | No | 0..1 | DIF 10 | Metadata_Dates/Data_Delete | Date or Time or EnumType | n/a | No | 0..1 | Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ECHO 10 |
---|
ECHO 10
Specification | Path | Type | Constraints | Required in ECHO10? | Cardinality | Notes |
---|---|---|---|---|---|---|
ECHO 10 | InsertTime | dateTime | n/a | Yes | 1 | The insert date/time the collection entered data provider's database. This date is provided by the data provider |
ECHO 10 | LastUpdate | dateTime | n/a | Yes | 1 | The most recent update occurred on the data provider's database. This date is provided by the data provider. |
ECHO 10 | DeleteTime | dateTime | n/a | No | 0..1 | The date the collection is or is planned to be deleted from the data provider's database.This date is provided by the data provider. If this date is in the past, the collection will be deleted during the next automated cleanup. |
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 MENDS |
---|
ISO 19115-2 MENDS
Dates provided in the Data_Last_Revision field will be labeled with the DataDate/Type of 'UPDATE' when translated to UMM. If any of the enumeration values are provided (unknown, present, unbounded, future, Not provided) the date will automatically default to 1970-01-01T00:00:00Z when being translated to UMM. This is because UMM does not currently support any enumeration values in date fields. | |||||||
DataDate/Type = REVIEW DataDate/Date | Metadata_Dates/Data_Future_Review | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Data_Future_Review field will be labeled with the DataDate/Type of 'REVIEW' when translated to UMM. If any of the enumeration values are provided (unknown, present, unbounded, future, Not provided) the date will automatically default to 1970-01-01T00:00:00Z when being translated to UMM. This is because UMM does not currently support any enumeration values in date fields. |
DataDate/Type = DELETE DataDate/Date | Metadata_Dates/Data_Delete | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Data_Delete field will be labeled with the DataDate/Type of 'DELETE' when translated to UMM. If any of the enumeration values are provided (unknown, present, unbounded, future, Not provided) the date will automatically default to 1970-01-01T00:00:00Z when being translated to UMM. This is because UMM does not currently support any enumeration values in date fields. |
Value needed for translations:
Not provided - The value of 'Not provided' might appear in the Metadata_Dates/Data_Creation and/or the Metadata_Dates/Data_Last_Revision fields as a result of software used to convert older versions of DIF to DIF version 10.2. 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/Data_Creation and Metadata_Dates/Data_Last_Revision are required in 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
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Insert Time and Last Update are required in ECHO 10 (Cardinality: 1). Delete Time is optional. Only 1 Delete Time may be provided (Cardinality: 0..1).
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSData Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)
| ||||||||||||||||||||||||||||||||||||||||||||
Specification | Path | Type | Constraints | Required in ISO 19115-2 MENDS? | Cardinality | ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime with /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode codeListValue varies. | Yes, only one is required | 1..* | ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime with /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode codeListValue varies. | No | 0..* | ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime with /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode codeListValue varies. | No | 0..* | ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime with /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode codeListValue varies. | No | 0..* | ISO 19115-2 MENDS | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime with /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:dateType/gmd:CI_DateTypeCode codeListValue varies. | No | 0..* | Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
ISO 19115-2 SMAP
Specification | Path | Type | Constraints | Required in ISO 19115-2 SMAP? | Cardinality | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/ gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd: | dateTypeISO 19115-2 SMAP | /gmd:DS_Series/gmd:seriesMetadatadate/ | gmd:CI_DateTypeCode codeListValue varies.Yes, only one date is required | 0..1 | gco:DateTime with | /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/ gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd: | date/gco:DateTimedateType/ 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 codeListValue varies.No | 0..* | ISO 19115-2 SMAP | /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime 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 codeListValue varies. | No | 0..* | ISO 19115-2 SMAP | /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime 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 codeListValue varies. | No | 0..* | ISO 19115-2 SMAP | /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:date/gmd:CI_Date/gmd:date/gco:DateTime 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 codeListValue varies. | No | 0..* |
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UMM Migration
Future Mappings
title | ISO 19115-1 |
---|
ISO 19115-1
with
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:dateType/cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode" codeListValue varies.
with
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:dateType/cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode" codeListValue varies.
with
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:dateType/cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode" codeListValue varies.
with
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:dateType/cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode" codeListValue varies.
with
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:dateType/cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode" codeListValue varies.
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Enumeration/Code List Mapping
|
Expand | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||
ISO 19115-2 SMAPData Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)
Enumeration/Code List Mapping
Example Mapping
|
UMM Migration
None
Excerpt | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||
Future Mappings
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | No changes were made for Data Dates during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for Data Dates during the transition from version 1.15.3 to 1.15.4 |
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. |
History
UMM Versioning
No changes were made for Purpose during the transition from version 1.9.0 to 1.10.0
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 10/516/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |