You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Element Description

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

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/ 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:

  1. CREATE: The date the resource was created. This should be the date the data set was published in the database/ entered into the data archive system. 
  2. 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.  
  3. REVIEW: The date of a planned future review of the resource. 
  4. DELETE: The date the resource will be deleted. 

At least one Data Date must be provided. 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

At least 1 Data Date must be provided. Multiple Data Dates may be provided, if necessary (Cardinality 1..*)

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CDataDate/TypeEnumeration

CREATE

UPDATE

REVIEW

DELETE

n/a

Yes1..*

Type is chosen from a pick-list.

The same Type should not be used more than once in the same record.

UMM-CDataDate/DatedateTime
n/a

n/a

Yes1..*The actual date that the event associated with the data occurred/ will occur.

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.


  • 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

<>

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • The DataDate/Type does not match one of the date type enumeration values (CREATE, UPDATE, REVIEW, DELETE)
  • No DataDate is provided (at least 1 Data Date must be provided)
  • The DataDate/Date provided does comply with the ISO 8601 Standard

This element is categorized as medium priority when:

  • A REVIEW or DELETE date is in the past
  • The CREATE or UPDATE date is in the future
  • A translation error between a native metadata format (ISO, DIF 10, ECHO 10) and UMM is present for the date and/or the date type

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 (Note: DIF-9 is being phased out and will no longer be supported after 2018)

DIF 10

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in DIF 10?CardinalityNotes
DIF 10Metadata_Dates/Data_Creation

Date

dateTime

Enumeration

unknown

present

unbounded

future

Not provided

n/aNo0..1

Dates provided in the Data_Creation field will be labeled with the DataDate/Type of 'CREATE' 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.

DIF 10Metadata_Dates/Data_Last_Revision

Date

dateTime

Enumeration

unknown

present

unbounded

future

Not provided

n/aNo0..1

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.

DIF 10Metadata_Dates/Data_Future_Review

Date

dateTime

Enumeration

unknown

present

unbounded

future

Not provided

n/aNo0..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.

DIF 10Metadata_Dates/Data_Delete

Date

dateTime

Enumeration

unknown

present

unbounded

future

Not provided

n/aNo0..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 were required in DIF version 10.2. Both Metadata_Dates/Data_Creation and Metadata_Dates/Data_Last_Revision were changed from required to optional in DIF version 10.3 so 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

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

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10InsertTimedateTime

n/a

Yes1

The insert date/time the collection entered data provider's database. This date is provided by the data provider

ECHO 10LastUpdatedateTimen/aYes1

The most recent update occurred on the data provider's database. This date is provided by the data provider.

ECHO 10DeleteTimedateTimen/aNo0..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

SpecificationPathTypeNotes
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.		String
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.		String
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.		String
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.		String
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.		String


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

SpecificationPathTypeNotes
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.		String
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.		String
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.		String
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.		String
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.		String


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.0Translation DirectionUMM Version 1.10.0



Future Mappings

ISO 19115-1

SpecificationPathTypeRequired in ISO 19115-1?CardinalityNotes
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.		StringNo0..*
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.		StringNo0..*
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.		StringNo0..*
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.		StringNo0..*
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.		StringNo0..*


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

VersionDateWhat Changed
1.10.05/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

VersionDateWhat ChangedAuthor
1.010/5/18Recommendations/priority matrix transferred from internal ARC documentation to wiki spaceJeanne' le Roux



  • No labels