Data Dates

Element Description

Note: This wiki page is a draft/ work in progress

Data Dates is comprised of dates for 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 an action performed on it or when the action will occur as described by the 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

Model

Element

Type

Usable Valid Values

Constraints

Required?

Cardinality

Notes

UMM-C

DataDate/Type

Enumeration

CREATE

UPDATE

DELETE

REVIEW

n/a

No

At least 1 is required

Dates related to activities involving the collection data. For example, Creation date is the date that the collection data first entered the data archive system.

UMM-C

DataDate/Date

date-time

n/a

No

At least 1 is required

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.

GCMD Metadata QA/QC

Manual Review
- Check that the date is accurate for the data set
Automated Review
- Check that the field has been populated
- Checks for correct format
- Check that the field length is not greater than 1000 characters

CMR Validation

<>

ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	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
	The element is provided, and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

If no value is provided, return is "np"
Otherwise, return is "OK"

Dialect Mappings

DIF 9

DIF 9 ^{(Note: DIF-9 is being phased out and will no longer be supported after 2018)}

DIF 10

DIF 10

Specification	Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
DIF 10	Metadata_Dates/Data_Creation	Date or Time or EnumType	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

DIF 10

<Metadata_Dates>
  <Metadata_Creation>2012-12-12</Metadata_Creation>
  <Metadata_Last_Revision>2018-10-03</Metadata_Last_Revision>
  <Data_Creation>2000-01-01</Data_Creation>
  <Data_Last_Revision>2000-01-01</Data_Last_Revision>
</Metadata_Dates>

UMM

DataDates: [
    {
        Date: "2007-06-14T00:00:00.000Z",
        Type: "CREATE"
    },
    {
        Date: "2015-07-07T00:00:00.000Z",
        Type: "UPDATE"
    }
]

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.

Example Mapping

ECHO 10

<InsertTime>2008-12-02T00:00:00.000Z</InsertTime>
<LastUpdate>2008-12-02T00:00:00.000Z</LastUpdate>

UMM

DataDates: [
    {
        Date: "2007-06-14T00:00:00.000Z",
        Type: "CREATE"
    },
    {
        Date: "2015-07-07T00:00:00.000Z",
        Type: "UPDATE"
    }
]

ISO 19115-2 MENDS

ISO 19115-2 MENDS

Specification	Path	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

ISO 19115-2 MENDS

<gmi:MI_Metadata>
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:purpose>
        <gco:CharacterString>To provide VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats.</gco:CharacterString>
      </gmd:purpose>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>

UMM

DataDates: [
    {
        Date: "2007-06-14T00:00:00.000Z",
        Type: "CREATE"
    },
    {
        Date: "2015-07-07T00:00:00.000Z",
        Type: "UPDATE"
    }
]

ISO 19115-2 SMAP

ISO 19115-2 SMAP

Specification	Path	Required in ISO 19115-2 SMAP?	Cardinality
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.	Yes, only one date is required	0..1
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..*
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

ISO 19115-2 SMAP

<gmd:date>
<gmd:CI_Date>
   <gmd:date>
     <gco:DateTime>2008-06-03T00:00:00.000Z</gco:DateTime>
   </gmd:date>
   <gmd:dateType>
     <gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision">revision</gmd:CI_DateTypeCode>
   </gmd:dateType>
</gmd:CI_Date>
</gmd:date>
<gmd:date>
<gmd:CI_Date>
   <gmd:date>
     <gco:DateTime>2005-06-01T00:00:00.000Z</gco:DateTime>
   </gmd:date>
   <gmd:dateType>
     <gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="creation">creation</gmd:CI_DateTypeCode>
   </gmd:dateType>
</gmd:CI_Date>
</gmd:date>

UMM

DataDates: [
    {
        Date: "2007-06-14T00:00:00.000Z",
        Type: "CREATE"
    },
    {
        Date: "2015-07-07T00:00:00.000Z",
        Type: "UPDATE"
    }
]

UMM Migration

UMM Version 1.9.0	Translation Direction	UMM Version 1.10.0

Future Mappings

ISO 19115-1

ISO 19115-1

Specification	Path	Required in ISO 19115-1?	Cardinality
ISO 19115-1	/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:date/gco:DateTime 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.	No	0..*
ISO 19115-1	/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:date/gco:DateTime 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.	No	0..*
ISO 19115-1	/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:date/gco:DateTime 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.	No	0..*
ISO 19115-1	/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:date/gco:DateTime 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.	No	0..*
ISO 19115-1	/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:date/cit:CI_Date/cit:date/gco:DateTime 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.	No	0..*

Example Mapping

ISO 19115-1

<mdb:MD_Metadata>
  <mdb:identificationInfo>
    <mri:MD_DataIdentification>
      <mri:purpose>
        <gco:CharacterString>To provide VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats.</gco:CharacterString>
      </mri:purpose>
    </mri:MD_DataIdentification>
  </mdb:identificationInfo>
</mdb:MD_Metadata>

UMM

DataDates: [
    {
        Date: "2007-06-14T00:00:00.000Z",
        Type: "CREATE"
    },
    {
        Date: "2015-07-07T00:00:00.000Z",
        Type: "UPDATE"
    }
]

History

UMM Versioning

Version	Date	What Changed
1.10.0	5/2/2018	No changes were made for Purpose during the transition from version 1.9.0 to 1.10.0
1.9.0

ARC Documentation

Version	Date	What Changed	Author
1.0	10/5/18	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Jeanne' le Roux

Page tree

Data Dates

Element Description

Note: This wiki page is a draft/ work in progress

Best Practices

Element Specification

Metadata Validation and QA/QC

UMM Migration

History

UMM Versioning

ARC Documentation