Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
stylecircle

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

Examples:

Type=CREATE: 2010-02-01

Type=UPDATE: 2018-02-01

Type=REVIEW: 2019-02-01

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 dataset 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. 

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..*)

Element Specification

ModelElementType
ModelElementTypeUsable Valid Values
ConstraintsRequired?CardinalityNotes
UMM-CDataDate/Type
=
Enumeration

CREATE

UPDATE

String

REVIEW

DELETE

n/a

No
At least 1 is requiredDates related to activities involving the collection data. For example, Creation date is the date that the collection data first entered the data archive system.
0..*

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

UMM-CDataDate/
Type=UPDATE
Date
String
dateTime
n/a
NoAt least 1 is requiredUMM-CDataDate/Type=REVIEWString

n/a

NoAt least 1 is required

n/a

No0..*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-viewerfalse
autofittrue
nameCopy of Wiki Page Metadata Evaluation Workflow-1939-51df84
width1102
pages-to-display
id98e5dc28-3252-4209-953f-66f1378e1cf4
alignLeft
height299

Please see the expandable sections below for flowchart details.


Expand
titleGCMD Metadata QA/QC
  • Manual Review
    • Check that the date is accurate for the data setdataset.
  • Automated Review
    • Check that the field has been populated.
    • Check that the date format is correct.Checks for correct format
    • Check that the field length is not greater than 1000 1,000 characters.
Expand
titleCMR Validation
  • The CMR makes sure the date values are in the correct order and range where CREATE date needs to be earlier or equal to the UPDATE date and both dates need to be in the past. The REVIEW date needs to be before the DELETE date and both dates need to be in the future.
  • The Date needs to comply with the ISO 8601 Standard.
<>
Expand
titleARC Metadata QA/QC

ARC Priority Matrix

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

n/a
  • The DataDate/Type does not match one of the date type enumeration values (CREATE, UPDATE, REVIEW, DELETE).
  • The DataDate/Date provided does comply with the ISO 8601 Standard.

Yellow = Medium Priority Finding

This element is categorized as medium priority when:

  • n/a
  • 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.

Blue = Low Priority Finding

This element is This element is categorized as low priority when:

  • n/a
  • The default value of "1970-01-01T00:00:00.000Z" is provided. 

Green = No Findings/Issues

The element is provided The element is provided, and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

If novalue is provided, return is "np"
  • Otherwise, return is "OK"
  • Checks

    ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information.  

    Dialect Mappings

    Expand
    titleDIF 9

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

    Expand
    titleDIF 10

    DIF 10

    Data Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)

    DIF 10Yes
    UMM-C ElementPathTypeUsable Valid ValuesConstraintsSpecificationPathTypeConstraintsRequired in DIF 10?CardinalityNotes

    DataDate/Type = CREATE

    DataDate/Date

    Metadata_Dates/Data_Creation

    Date

    dateTime

    Enumeration

    1Granular data was inserted (Changed to optional in DIF 10.3)

    unknown

    present

    unbounded

    future

    Not provided

    n/aDIF 10Metadata_Dates/Data_Last_RevisionYes1Granular data was updated  DIF 10Metadata_Dates/Data_Future_ReviewNo0..1Granular data is to be updatedDIF 10Metadata_Dates/Data_DeleteNo0..1Granular data removed 
    Example Mapping
    Section
    Column
    width50%

    DIF 10

    No Format
    <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>
    Column
    width50%

    UMM

    No Format
    INSERT EXAMPLE
    Expand
    titleECHO 10

    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.

    DataDate/Type = UPDATE

    DataDate/Date

    Metadata_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.

    DataDate/Type = REVIEW

    DataDate/Date

    Metadata_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.

    DataDate/Type = DELETE

    DataDate/Date

    Metadata_Dates/Data_Delete

    Date

    dateTime

    Enumeration

    unknown

    present

    unbounded

    future

    Not provided

    n/a

    ECHO 10

    SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
    ECHO 10InsertTimeYes1

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

    ECHO 10LastUpdateYes1

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

    ECHO 10DeleteTimeNo0..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
    Section
    Column
    width50%

    ECHO 10

    No Format
    <InsertTime>2008-12-02T00:00:00.000Z</InsertTime>
    <LastUpdate>2008-12-02T00:00:00.000Z</LastUpdate>
    Column
    width50%

    UMM

    No Format
    INSERT EXAMPLE

    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
    Column
    width50%

    DIF 10

    No Format
    <Metadata_Dates>
      <Data_Creation>2012-12-12</Data_Creation>
      <Data_Last_Revision>2018-10-03</Data_Last_Revision>
      <Data_Future_Review>2100-01-01</Data_Future_Review>
    </Metadata_Dates>
    Column
    width50%

    UMM

    No Format
    DataDates: [
        {
            Date: "2012-12-12T00:00:00.000Z",
            Type: "CREATE"
        },
        {
            Date: "2018-10-03T00:00:00.000Z",
            Type: "UPDATE"
        },
        {
            Date: "2100-01-01T00:00:00.000Z",
            Type: "REVIEW"
        },
    ]

    Example Mapping

    Expand
    titleECHO 10

    ECHO 10

    Insert 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).

    UMM-C ElementPathTypeConstraintsRequired in ECHO10?CardinalityNotes

    DataDate/Type = CREATE

    DataDate/Date

    InsertTimedateTime

    n/a

    Yes1

    The insert date/time the collection entered data provider's database.

    The date provided in the InsertTime field will be labeled with the DataDate/Type of 'CREATE' when translated to UMM.

    DataDate/Type = UPDATE

    DataDate/Date

    LastUpdatedateTimen/aYes1

    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.

    DataDate/Type = DELETE

    DataDate/Date

    DeleteTimedateTimen/aNo0..1

    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.


    Example

    Expand
    titleISO 19115-2 MENDS

    ISO 19115-2 MENDS

    SpecificationPathTypeConstraintsRequired in ISO 19115-2 MENDS?Cardinality
    ISO 19115-2 MENDS/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.
    No0..*ISO 19115-2 MENDS/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.
    No0..*ISO 19115-2 MENDS/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.
    No0..*ISO 19115-2 MENDS/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.
    No0..*ISO 19115-2 MENDS/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.
    No0..*
    Section
    Column
    width50%

    ISO 19115-2 MENDSECHO 10

    No Format
    <InsertTime>2012-12-12T00:00:00.000Z</InsertTime>
    <LastUpdate>2018-10-03T00:00:00.000Z</LastUpdate>
    Column
    width50%

    UMM

    No Format
    DataDates: [
        {
     <gmi:MI_Metadata>
      <gmd:identificationInfo>
        <gmd:MD_DataIdentification>
          <gmd:purpose> Date: "2012-12-12T00:00:00.000Z",
            <gcoType:CharacterString>To provide"CREATE"
     VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats.</gco:CharacterString>},
        {
            Date: "2018-10-03T00:00:00.000Z",
          </gmd:purpose>  Type: "UPDATE"
        </gmd:MD_DataIdentification>
      </gmd:identificationInfo>
    </gmi:MI_Metadata>
    Column
    width50%

    UMM

    No Format
    INSERT EXAMPLE
    Expand
    }
    ]
    Expand
    titleISO 19115-2 MENDStitleISO 19115-2 SMAP

    ISO 19115-2

    SMAP

    MENDS

    Data Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)

    UMM-C Element
    SpecificationISO 19115-2 SMAP
    /gmd:DS_Series/gmd:seriesMetadata/ /gmd:DS_Series/gmd:seriesMetadataDateTypeCode   codeListValue varies.
    PathTypeConstraintsRequired in ISO 19115-2 SMAP?CardinalityNotes

    DataDate/Type

    DataDate/Date

    /

    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_

    Yes, only one date is required0..1ISO 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.
    No0..*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.

    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

    ISO MENDSTranslation DirectionUMM
    creationCREATE
    revisionUPDATE
    lastRevisionFUTURE
    unavailableDELETE


    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 MENDS

    No Format
    <gmi:MI_Metadata>
      ...
      <gmd:identificationInfo>
        <gmd:MD_DataIdentification>
          ...
          <gmd:citation>
            <gmd:CI_Citation>
              ...
              <gmd:date>
                <gmd:CI_Date>
                  <gmd:date>
                    <gco:DateTime>2012-12-12T00:00:00.000Z</gco:DateTime>
                  </gmd:date>
                  <gmd:dateType>
                    <gmd:CI_DateTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="creation">creation</gmd:CI_DateTypeCode>
                  </gmd:dateType>
                  <gmd:date>
                    <gco:DateTime>2018-10-03T00:00:00.000Z</gco:DateTime>
                  </gmd:date>
                  <gmd:dateType>
                    <gmd:CI_DateTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision">revision</gmd:CI_DateTypeCode>
                  </gmd:dateType>
                </gmd:CI_Date>
              </gmd:date>
              ...
            </gmd:CI_Citation>
          </gmd:citation>
          ...
        </gmd:MD_DataIdentification>
      </gmd:identificationInfo>
      ...
    </gmi:MI_Metadata>
    Column
    width50%

    UMM

    No Format
    DataDates: [
        {
            Date: "2012-12-12T00:00:00.000Z",
            Type: "CREATE"
        },
        {
            Date: "2018-10-03T00:00:00.000Z",
            Type: "UPDATE"
        }
    ]
    Expand
    titleISO 19115-2 SMAP

    ISO 19115-2 SMAP

    Data Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)

    UMM-C ElementPathTypeNotes

    DataDate/Type

    DataDate/Date

    /gmd:DS_Series/gmd:seriesMetadata/gmi:MI

    No0..*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.
    No0..*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.
    No0..*

    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 SMAP

    No Format
    <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>
    Column
    width50%

    UMM

    No Format
    INSERT EXAMPLE

    UMM Migration

    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

    ISO MENDSTranslation DirectionUMM
    creationCREATE
    revisionUPDATE
    lastRevisionFUTURE
    unavailableDELETE

    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 SMAP

    No Format
    <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>2012-12-12T00:00:00.000Z</gco:DateTime>
                  </gmd:date>
                  <gmd:dateType>
                    <gmd:CI_DateTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="creation">creation</gmd:CI_DateTypeCode>
                  </gmd:dateType>
                  <gmd:date>
                    <gco:DateTime>2018-10-03T00:00:00.000Z</gco:DateTime>
                  </gmd:date>
                  <gmd:dateType>
                    <gmd:CI_DateTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision">revision</gmd:CI_DateTypeCode>
                  </gmd:dateType>
                </gmd:CI_Date>
              </gmd:date>
              ...
            </gmd:CI_Citation>
          </gmd:citation>
          ...
        </gmd:MD_DataIdentification>
      </gmd:identificationInfo>
      ...
    </gmi:MI_Metadata>
    </gmd:seriesMetadata>
    </gmd:DS_Series>
    Column
    width50%

    UMM

    No Format
    DataDates: [
        {
            Date: "2012-12-12T00:00:00.000Z",
            Type: "CREATE"
        },
        {
            Date: "2018-10-03T00:00:00.000Z",
            Type: "UPDATE"
        }
    ]

    UMM Migration

    None

    Excerpt
    hiddentrue

    Future Mappings

    Expand
    titleISO 19115-1

    ISO 19115-1

    Data Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)

    UMM-C ElementPathTypeNotes

    DataDate/Type

    DataDate/Date

    /mdb:

    UMM Version 1.9.0Translation DirectionUMM Version 1.10.0

    Future Mappings

    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:
    Expand
    titleISO 19115-1

    ISO 19115-1

    SpecificationPathTypeConstraintsRequired in ISO 19115-1?Cardinality
    /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.
    No0..*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.
    No0..*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.
    No0..*ISO 19115-1

    MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/

    cit:CI_Citation/cit:date/cit:CI_Date/cit:

    dateTypeNo0..*ISO 19115-1

    date/

    cit:CI_DateTypeCode codeList="codeListLocation#CI_DateTypeCode"  codeListValue varies.

    gco:DateTime

    with

    /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/

    cit:CI_Citation/cit:date/cit:CI_Date/cit:

    date

    dateType/

    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.

    cit:CI_DateTypeCode codeList = "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

    ISO MENDSTranslation DirectionUMM
    creationCREATE
    revisionUPDATE
    lastRevisionFUTURE
    unavailableDELETE


    Example Mapping

    Section
    No0..*Example Mapping
    Section
    Column
    width50%

    ISO 19115-1

    Column
    width50%

    ISO 19115-1

    No Format
    <mdb:MD_Metadata>
      ...
      <mdb:identificationInfo>
        <mri:MD_DataIdentification>
          <mri:
    purpose>
    citation>
            
    <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>
    Column
    width50%

    UMM

    No Format
    INSERT EXAMPLE
    <cit:CI_Citation>
              ...
              <cit:date>
                <cit:CI_Date>
                  <cit:date>
                    <gco:DateTime>2012-12-12T00:00:00.000Z</gco:DateTime>
                  </cit:date>
                  <cit:dateType>
                    <cit:CI_DateTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="creation">creation</gmd:CI_DateTypeCode>
                  </cit:dateType>
                  <cit:date>
                    <gco:DateTime>2018-10-03T00:00:00.000Z</gco:DateTime>
                  </cit:date>
                  <cit:dateType>
                    <cit:CI_DateTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision">revision</gmd:CI_DateTypeCode>
                  </cit:dateType>
                </cit:CI_Date>
              </cit:date>
              ...
            </cit:CI_Citation>
          </mri:citation>
          ...
        </mri:MD_DataIdentification>
      </mdb:identificationInfo>
      ...
    </mdb:MD_Metadata>
    Column
    width50%

    UMM

    No Format
    DataDates: [
        {
            Date: "2012-12-12T00:00:00.000Z",
            Type: "CREATE"
        },
        {
            Date: "2018-10-03T00:00:00.000Z",
            Type: "UPDATE"
        }
    ]

    History

    UMM Versioning

    VersionDateWhat Changed
    1.15.512/3/2020No changes were made for Data Dates during the transition from version 1.15.4 to 1.15.5
    1.15.49/18/2020No changes were made for Data Dates during the transition from version 1.15.3 to 1.15.4
    1.15.37/1/2020No changes were made for Data Dates during the transition from version 1.15.2 to 1.15.3
    1.15.25/20/2020No changes were made for Data Dates during the transition from version 1.15.1 to 1.15.2
    1.15.13/25/2020No changes were made for Data Dates during the transition from version 1.15.0 to 1.15.1
    1.15.02/26/2020No changes were made for Data Dates during the transition from version 1.14.0 to 1.15.0
    1.14.010/21/2019No changes were made for Data Dates during the transition from version 1.13.0 to 1.14.0
    1.13.004/11/2019No changes were made for Data Dates during the transition from version 1.12.0 to 1.13.0.
    1.12.001/22/2019No changes were made for Data Dates during the transition from version 1.11.0 to 1.12.0.
    1.11.011/28/2018No changes were made for Data Dates during the transition from version 1.10.0 to 1.11.0.
    1.10.005/02

    History

    UMM Versioning

    VersionDateWhat Changed1.10.05/2
    /2018

    No changes were made for

    Purpose

    Data Dates during the transition from version 1.9.0 to 1.10.0

    1.9

    .

    0

    ARC Documentation

    VersionDateWhat ChangedAuthor
    1.010/516/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space