Versions Compared

Old Version 7

changes.mady.by.user Camille Woods

Saved on

compared with

New Version Current

changes.mady.by.user Jenny Wood

Saved on

Key

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

Table of Contents
stylecircle

Element Description

Note: This page is a draft/ work in progress

The Paleo Temporal Coverage element defines the time period in which for geologic and/or paleoclimate data collection occurred. The element is predominantly used for data collection samples that occurred originated prior to 01-01-0001. As a result, it is not an element that is commonly used. 

Best Practices

Paleo Temporal Coverage tags identify time periods where geologic and paleoclimate data collection occurred. The time period tags can be chosen used to simply classify identify the start and end dates for data collection or they can more specifically identify the era, eon and stage, just to name a few tags, for the data collection time period. However, it . There is also the option to provide the names of the eon, era, period, epoch and stage associated with the data collection. It is suggested that Paleo Temporal Coverage tags are as specific as possible to aid in data discovery. The names of eons, eras, periods, epochs and stages must be selected from a controlled vocabulary list managed by the Keyword Management System (KMS). Because the tags are KMS controlled, if a specific tag is not already included in the KMS, a request to have it added can be made through the GCMD Keywords Community Forum.

Examples:

PaleoTemporalCoverage/PaleoStartDate:

It is important to note that even if Paleo Temporal Coverage metadata is provided, it is still required that a Temporal Extent be provided in addition. Please see the Temporal Extent wiki page for details.  

Examples:

PaleoTemporalCoverage/StartDate: "560 ka"

PaleoTemporalCoverage/

PaleoEndDate

EndDate: "60 ka"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoEon

Eon: "PHANEROZOIC"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoEra

Era: "CENOZOIC"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoPeriod

Period: "QUATERNARY"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoEpoch

Epoch: "PLEISTOCENE"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoStage

Stage: "LATE"


PaleoTemporalCoverage/

DetailedClassification: PaleoTemporalCoverage/PaleoStartDate:

StartDate: "175 myr"

PaleoTemporalCoverage/

PaleoEndDate

EndDate: "160 myr"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoEon

Eon: "PHANEROZOIC"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoEra

Era: "MESOZOIC"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoPeriod

Period: "JURASSIC"


PaleoTemporalCoverage/

PaleoStartDate

StartDate: "100 ka"

PaleoTemporalCoverage/

PaleoEndDate

EndDate: "20 ka"

PaleoTemporalCoverage/ChronostratigraphicUnit/

PaleoEon

Eon: "PHANEROZOIC"


Element Specification

Paleo Temporal Coverage is an optional metadata element, and should only be provided if it is applicable to the dataset. The Paleo Temporal Coverage element may not be repeated (Cardinality: 0..1).

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityUMM-CPaleoTemporalCoverage/PaleoStartDateStringPaleo Temporal Coverage Paleo Start Date TermsKMS controlled
No0..1
UMM-CPaleoTemporalCoverage/
PaleoEndDate
PaleoStartDateString
Paleo Temporal Coverage Paleo End Date Terms
n/a1 - 80 characters
KMS controlled
No0..1Provide a date unit for the start and end date (e.g. myr, ka, mya, B.C., etc.).
UMM-CPaleoTemporalCoverage/
ChronostratigraphicUnit
PaleoEndDateString
Paleo Temporal Coverage Chronostratigraphic_Unit Terms
n/a1 - 80 characters
KMS controlled
No0..
*
1Provide a date unit for the start and end date (e.g. myr, ka, mya, B.C., etc.)
UMM-
UMM-
CPaleoTemporalCoverage/
ChronostratigraphicUnit
ChronostratigraphicUnits/EonString
Paleo Temporal Coverage

GCMD Chronostratigraphic

_

Unit

_

Eon

Terms

Keywords

KMS controlledYes, if applicable1Providing Chronostratigraphic Units are optional. If included, the Eon must be provided at a minimum.
UMM-CPaleoTemporalCoverage/
ChronostratigraphicUnit
ChronostratigraphicUnits/EraString
Paleo Temporal Coverage

GCMD Chronostratigraphic

_

Unit

_

Era

Terms

Keywords

KMS controlledNo0..1
UMM-CPaleoTemporalCoverage/
ChronostratigraphicUnit
ChronostratigraphicUnits/PeriodString
Paleo Temporal Coverage

GCMD Chronostratigraphic

_

Unit

_

Period

Terms

Keywords

KMS controlledNo0..1
UMM-CPaleoTemporalCoverage/
ChronostratigraphicUnit
ChronostratigraphicUnits/EpochString
Paleo Temporal Coverage

GCMD Chronostratigraphic

_

Unit

_

Epoch

Terms

Keywords

KMS controlledNo0..1
UMM-CPaleoTemporalCoverage/
ChronostratigraphicUnit
ChronostratigraphicUnits/StageString
Paleo Temporal Coverage

GCMD Chronostratigraphic

_

Unit

_

Stage

Terms

Keywords

KMS controlledNo0..1
UMM-CPaleoTemporalCoverage/
ChronostratigraphicUnit
ChronostratigraphicUnits/Detailed_ClassificationString
Paleo Temporal Coverage Detailed_Classification Terms1 - 80 characters (Uncontrolled/Free-Text)No0..1
n/a
No

Metadata Validation 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-viewertrue
autofittrue
nameCopy of Wiki Page Metadata Evaluation Workflow-1939-12404ac7
width1102
id98e5dc28-3252-4209-953f-66f1378e1cf4
alignLeft
height299

Please see the expandable sections below for flowchart details.


Expand
titleGCMD Metadata QA/QC

Manual Review

  • Identify errors, discrepancies or omissions.
  • Verify that all pertinent keywords have been applied.
  • Verify that existing facets and other controlled keyword values are consistent and suitable for the data.
    • Automated Review
  • Check that the field has been populated.
  • Check that the field is populated with a valid value from KMS.
  • Check that the field value is not a duplicate.
    • Check that the 'Detailed_Variable' field length is not greater than 80 characters.
  • Proof all content for conciseness and readability.
Expand
titleCMR Validation

XML Schema Validation Only

Expand
titleARC Metadata QA/QC

ARC Priority Matrix

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

  • The element is not included at all No Paleo Temporal Coverage is provided (for relevant collections).
  • The element is included but is empty.
  • Paleo Temporal Coverage is provided but it is not applicable for the dataset (i.e. data were collected after 0001-01-01).
  • The Paleo Temporal Coverage The paleo temporal coverage term does not align with the KMS.
    • The paleo temporal coverage Paleo Temporal Coverage term does not exist in the KMS.
    • A term(s) is missing from the hierarchy.
    • A term(s) is placed in the incorrect position of the hierarchy (e.g. an Eon term is placed in the Epoch field).
  • The paleo temporal coverage Paleo Temporal Coverage term is not appropriate for the dataset.

Yellow = Medium Priority Finding

This element is categorized as medium priority when:

A recommendation is made to add a relevant paleo temporal coverage term to the metadata.

  • A recommendation is made to add to an existing Paleo Temporal Coverage term in the metadata (i.e. to extend a keyword hierarchy down to a more detailed keyword).
Not Applicable

Blue = Low Priority Finding

Not Applicable

Green = No Findings/Issues

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

ARC Automated Checks

  • Category
    • If no value is provided, return is: "This is a required field. Recommend providing at least one science keyword hierarchy relevant to this data set. This field should contain the Category keyword as specified in the hierarchy (EARTH SCIENCE). Science keywords are GCMD controlled and should be chosen from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/sciencekeywords/sciencekeywords.csv?ed_wiki_keywords_page"
    • If the provided value is in the incorrect position of the hierarchy, return is: "<provided value> is in the incorrect position of the project keyword hierarchy."
    • If the provided value does not conform to GCMD, return is: "<provided value> does not conform to GCMD."
  • Topic
    • If no value is provided, return is: "This is a required field. Recommend providing at least one science keyword hierarchy relevant to this data set. This field should contain the Topic keyword as specified in the hierarchy. Science keywords are GCMD controlled and should be chosen from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/sciencekeywords/sciencekeywords.csv?ed_wiki_keywords_page"
    • If the provided value is in the incorrect position of the hierarchy, return is: "<provided value> is in the incorrect position of the project keyword hierarchy."
    • If the provided value does not conform to GCMD, return is: "<provided value> does not conform to GCMD."
  • Term
    • If no value is provided, return is: "This is a required field. Recommend providing at least one science keyword hierarchy relevant to this data set. This field should contain the Term keyword as specified in the hierarchy. Science keywords are GCMD controlled and should be chosen from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/sciencekeywords/sciencekeywords.csv?ed_wiki_keywords_page"
    • If the provided value is in the incorrect position of the hierarchy, return is: "<provided value> is in the incorrect position of the project keyword hierarchy."
    • If the provided value does not conform to GCMD, return is: "<provided value> does not conform to GCMD."
  • Variable Level 1 - Variable Level 3
    • If no value is provided, return is "np"
    • If the provided value is in the incorrect position of the hierarchy, return is: "<provided value> is in the incorrect position of the project keyword hierarchy."
    • If the provided value does not conform to GCMD, return is: "<provided value> does not conform to GCMD."
    • Detailed Variable
    If no value isprovided, return is "np"
  • If a value is provided, return is "OK"
    • Expand
    titleCMR Validation

    <>

    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

    Science_Keywords are required. An unlimited amount of Science Keywords may be provided (Cardinality: 1..*)

    SpecificationPathTypeConstraintsRequired in DIF 10?CardinalityNotesDIF 10

    /DIF/Location_Keywords/Category

    String

    KMS controlled

    Yes

    1DIF 10/DIF/Location_Keywords/Type
    String

    KMS controlled

    No0..1DIF 10/DIF/Science_Keywords/Subregion_1String

    KMS controlled

    No0..1DIF 10/DIF/Science_Keywords/Subregion_2StringKMS controlledNo0..1DIF 10/DIF/Science_Keywords/Subregion_3StringKMS controlledNo0..1DIF 10/DIF/Science_Keywords/Detailed_LocationString1 - 80 characters (Uncontrolled/Free-Text)No0..1Example Mapping
    Section
    Column
    width50%

    DIF 10

    No Format
    <Paleo_Temporal_Coverage>
  <Location_Category>CONTINENT</Location_Category>
  <Location_Type>NORTH AMERICA</Location_Type>
  <Location_Subregion1>UNITED STATES</Location_Subregion1>
  <Location_Subregion2>ALBAMA</Location_Subregion2>
  <Location_Subregion3>HUNTSVILLE</Location_Subregion3>
  <Detailed_Location>THE UNIVERSITY OF ALABAMA IN HUNTSVILLE</Detailed_Location>
</Location_Keywords>
<Location_Keywords>
  <Location_Category>CONTINENT</Location_Category>
  <Location_Type>NORTH AMERICA</Location_Type>
  <Location_Subregion1>CANADA</Location_Subregion1>
  <Location_Subregion2>ONTARIO</Location_Subregion2>
</Location_Keywords>
    Column
    width50%

    UMM

    No Format
    LocationKeywords: [
  {
    Start Date: "560 ka",
    End Date: "60 ka",
    Eon: "PHANEROZOIC",
    Era: "CENOZOIC",
	Period: "QUATERNARY",
	Epoch: "PLEISTOCENE",
	Stage: "LATE",
    DetailedClassification: ""
  },
  {
    Start Date: "100ka",
    End Date: "20ka",
    Eon: "PHANEROZOIC",
  }
],
    Expand
    titleECHO 10

    ECHO 10

    Location Keywords at the Category Level are required.

    SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotesECHO 10/Collection/LocationKeywords/LocationKeyword/CategoryKeywordString

    KMS controlled

    Yes1ECHO 10/Collection/LocationKeywords/LocationKeyword/TypeKeywordString

    KMS controlled

    No0..1ECHO 10/Collection/LocationKeywords/LocationKeyword/Subregion1Keyword/ValueStringKMS controlledNo0..1ECHO 10/Collection/LocationKeywords/LocationKeyword/Subregion2Keyword/ValueStringKMS controlledNo0..1ECHO 10/Collection/LocationKeywords/LocationKeyword/Subregion3Keyword/ValueStringKMS controlledNo0..1ECHO 10/Collection/ScienceKeywords/LocationKeyword/DetailedLocationKeywordStringUncontrolled (Free-Text)No0..1Example Mapping
    Section
    Column
    width50%

    ECHO 10

    No Format
    <LocationKeyword>
  <CategoryKeyword>CONTINENT</CategoryKeyword> 
  <TypeKeyword>NORTH AMERICA</TypeKeyword> 
  <Subregion1Keyword>
  <Value>UNITED STATES</Value> 
    <Subregion2Keyword>
     <Value>ALABAMA</Value>
      <Subregion3Keyword>
        <Value>HUNTSVILLE</Value>
      	  </Subregion3Keyword>
	   </Subregion2Keyword>
    </Subregion1Keyword>
  <DetailedLocationKeyword>THE UNIVERSITY OF ALABAMA IN HUNTSVILLE</DetailedLocationKeyword>
</LocationKeyword>
<LocationKeyword>
  <CategoryKeyword>CONTINENT</CategoryKeyword> 
  <TypeKeyword>NORTH AMERICA</TypeKeyword> 
  <Subregion1Keyword>VEGETATION</Subregion1Keyword> 
</LocationKeyword>
    Column
    width50%

    UMM

    No Format
    ScienceKeywords: [
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "UNITED STATES",
    Subregion2: "ALABAMA"
    Subregion3: "HUNTSVILLE"
    DetailedLocation: "THE UNIVERSITY OF ALABAMA IN HUNTSVILLE"
  },
  {
    Category: "CONTINENT",
    Type: "NORTH AMERICA",
    Subregion1: "UNITED STATES",
    Subregion2: "HUNTSVILLE"
  }
],
    Expand
    titleISO 19115-2 MENDS

    ISO 19115-2 MENDS

    Science Keywords are required. An unlimited amount of Science Keywords may be provided (Cardinality: 1..*)

    SpecificationPathTypeNotesISO 19115-2 MENDS

    /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/ gmd:keyword/gco:CharacterString  (list each value of the keyword hierarchy delimited by &gt; )

    String

    KMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by "&gt;". If any keyword is missing and there exists a keyword later in the hierarchy (such as DetailedLocation), use NONE to fill in the values in between. The CMR will not translate the NONE values they are only used to place each keyword in its correct space in the hierarchy.

    /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/ gmd:keyword/gmd:type/MD_KeywordTypeCode[@codeListValue="theme"]
    Codelist

    codeList=https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode

    Select the value "theme" from the codelist. This codelist value does not directly map to a UMM element; choosing "theme" indicates to CMR that the Science Keywords should be mapped.

    Example Mapping
    Section
    Column
    width50%

    ISO 19115-2 MENDS

    No Format
    ...
<gmd:identificationInfo>
  <gmd:MD_DataIdentification>
    <gmd:descriptiveKeywords>
      <gmd:MD_Keywords>
        <gmd:keyword>
          <gco:CharacterString>EARTH SCIENCE&gt;BIOSPHERE&gt;VEGETATION&gt;VEGETATION INDEX&gt;NORMALIZED DIFFERENCE VEGETATION INDEX (NDVI)&gt;NONE&gt;0.9 DENSITY</CharacterString>
        </gmd:keyword>
        <gmd:keyword>
          <gco:CharacterString>EARTH SCIENCE&gt;BIOSPHERE&gt;VEGETATION&gt;EVERGREEN VEGETATION</CharacterString>
        </gmd:keyword>
        <gmd:type>
          <gmd:MD_KeywordTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="theme">theme</gmd:MD_KeywordTypeCode>
        </gmd:type>
      </gmd:MD_Keywords> 
    </gmd:descriptiveKeywords>
  </gmd:MD_DataIdentification>
</gmd:identificationInfo>
...
    Column
    width50%

    UMM

    No Format
    ScienceKeywords: [
  {
    Category: "EARTH SCIENCE",
    Topic: "BIOSPHERE",
    Term: "VEGETATION",
    VariableLevel1: "VEGETATION INDEX"
    VariableLevel2: "NORMALIZED DIFFERENCE VEGETATION INDEX (NDVI)"
    DetailedVariable: "0.9 DENSITY"
  },
  {
    Category: "EARTH SCIENCE",
    Topic: "BIOSPHERE",
    Term: "VEGETATION",
    VariableLevel1: "EVERGREEN VEGETATION"
  }
],

    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

    Paleo_Date_Time is an optional element, and should only be provided if it is applicable to the dataset. The Paleo_Date_Time element may not be repeated (Cardinality: 0..1). Please note: This element falls under Temporal_Coverage in DIF 10. 

    UMM-C ElementDIF 10 PathTypeUsable Valid ValuesConstraintsRequired in DIF 10?CardinalityNotes
    PaleoTemporalCoverage/PaleoStartDate

    Temporal_Coverage/Paleo_DateTime/Paleo_Start_Date

    String



    No

    		0..1


    PaleoTemporalCoverage/PaleoEndDateTemporal_Coverage/Paleo_DateTime/Paleo_Stop_Date
    		String


    		No0..1
    PaleoTemporalCoverage/ChronostratigraphicUnit/EonTemporal_Coverage/Paleo_DateTime/Chronostratigraphic_Unit/EonStringGCMD Chronostratigraphic Unit Eon KeywordsKMS controlledYes, if applicable1Providing Chronostratigraphic Units are optional. If included, the Eon must be provided at a minimum.
    PaleoTemporalCoverage/ChronostratigraphicUnit/EraTemporal_Coverage/Paleo_DateTime/Chronostratigraphic_Unit/EraStringGCMD Chronostratigraphic Unit Era KeywordsKMS controlledNo0..1
    PaleoTemporalCoverage/ChronostratigraphicUnit/PeriodTemporal_Coverage/Paleo_DateTime/Chronostratigraphic_Unit/PeriodStringGCMD Chronostratigraphic Unit Period KeywordsKMS controlledNo0..1
    PaleoTemporalCoverage/ChronostratigraphicUnit/EpochTemporal_Coverage/Paleo_DateTime/Chronostratigraphic_Unit/EpochStringGCMD Chronostratigraphic Unit Epoch KeywordsKMS controlledNo0..1
    PaleoTemporalCoverage/ChronostratigraphicUnit/StageTemporal_Coverage/Paleo_DateTime/Chronostratigraphic_Unit/StageStringGCMD Chronostratigraphic Unit Stage KeywordsKMS controlledNo0..1
    PaleoTemporalCoverage/ChronostratigraphicUnit/Detailed_ClassificationTemporal_Coverage/Paleo_DateTime/Chronostratigraphic_Unit/Detailed_ClassificationString

    		No0..1


    Example Mapping

    Section
    Column
    width50%

    DIF 10

    No Format
    <Temporal_Coverage>
  <Paleo_DateTime>
    <Paleo_Start_Date>340 mya</Paleo_Start_Date>
    <Paleo_Stop_Date>338 mya</Paleo_Stop_Date>
    <Chronostratigraphic_Unit>
      <Eon>PHANEROZOIC</Eon>
      <Era>PALEOZOIC</Era>
      <Period>CARBONIFEROUS</Period>
      <Epoch>MISSISSIPPIAN</Epoch>
    </Chronostratigraphic_Unit>
  </Paleo_DateTime>
</Temporal_Coverage>
    Column
    width50%

    UMM

    No Format
    PaleoTemporalCoverage: [
  {
    Start Date: "340 mya",
    End Date: "338 mya",
    Chronostratigraphic Unit: [
      {	
        Eon: "PHANEROZOIC",
        Era: "PALEOZOIC",
	    Period: "CARBONIFEROUS",
	    Epoch: "MISSISSIPPIAN"
      }
    ]
  }
],
    Expand
    titleECHO 10

    ECHO 10

    Paleo Temporal Coverage does not map to ECHO 10.

    UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?CardinalityNotes
    Paleo Temporal Coverage N/AN/A

    N/A

    		N/AN/APaleo Temporal Coverage does not map to ECHO10.
    Expand
    titleISO 19115-2 MENDS

    ISO 19115-2 MENDS

    Paleo Temporal Coverage currently does not map to ISO 19115-2 MENDS.

    UMM-C Element

    ISO 19115-2 MENDS Path

    		TypeNotes
    Paleo Temporal Coverage 

    N/A

    N/A


    N/A


    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 MENDS

    No Format
    N/A
    Column
    width50%

    UMM

    No Format
    N/A



    Expand
    titleISO 19115-2 SMAP

    ISO 19115-2 SMAP

    Paleo Temporal Coverage currently does not map to ISO 19115-2 SMAP.

    UMM-C Element

    ISO 19115-2 SMAP Path

    		TypeNotes
    Paleo Temporal Coverage 

    N/A

    		N/AN/A


    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 SMAP

    No Format
    N/A
    Column
    width50%

    UMM

    No Format
    N/A



    UMM Migration

    None

    Excerpt
    hiddentrue

    Future Mappings

    Expand
    titleISO 19115-1

    ISO 19115-1

    Paleo Temporal Coverage may one day map to ISO 19115-1.

    SpecificationPathTypeNotes
    ISO 19115-1

    N/A

    		N/AN/A
    Section
    Column
    width50%

    ISO 19115-1

    No Format
    N/A
    Column
    width50%

    UMM

    No Format
    N/A

    History

    UMM Versioning

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

    ISO 19115-2 SMAP

    Science Keywords are required. An unlimited amount of Science Keywords may be provided (Cardinality: 1..*)

    SpecificationPathTypeNotesISO 19115-2 SMAP

    /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/ gmd:MD_Keywords/gmd:keyword/gco:CharacterString  (list each value of the keyword hierarchy delimited by &gt; )

    StringKMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by "&gt;". If any keyword is missing and there exists a keyword later in the hierarchy (such as DetailedLocation), use NONE to fill in the values in between. The CMR will not translate the NONE values they are only used to place each keyword in its correct space in the hierarchy.ISO 19115-2 SMAP/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:descriptiveKeywords/gmd:MD_Keywords/gmd:keyword/ gmd:type/MD_KeywordTypeCode[@codeListValue="theme"]Codelist

    codeList=https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode

    Select the value "theme" from the codelist. This codelist value does not directly map to a UMM element; choosing "theme" indicates to CMR that the Science Keywords should be mapped.

    Example Mapping
    Section
    Column
    width50%

    ISO 19115-2 SMAP

    No Format
    ...
<gmd:identificationInfo>
  <gmd:MD_DataIdentification>
    <gmd:descriptiveKeywords>
      <gmd:MD_Keywords>
        <gmd:keyword>
          <gco:CharacterString>EARTH SCIENCE&gt;BIOSPHERE&gt;VEGETATION&gt;VEGETATION INDEX&gt;NORMALIZED DIFFERENCE VEGETATION INDEX (NDVI)&gt;NONE&gt;0.9 DENSITY</CharacterString>
        </gmd:keyword>
        <gmd:keyword>
          <gco:CharacterString>EARTH SCIENCE&gt;BIOSPHERE&gt;VEGETATION&gt;EVERGREEN VEGETATION</CharacterString>
        </gmd:keyword>
        <gmd:type>
          <gmd:MD_KeywordTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="theme">theme</gmd:MD_KeywordTypeCode>
        </gmd:type>
      </gmd:MD_Keywords> 
    </gmd:descriptiveKeywords>
  </gmd:MD_DataIdentification>
</gmd:identificationInfo>
...
    Column
    width50%

    UMM

    No Format
    ScienceKeywords: [
  {
    Category: "EARTH SCIENCE",
    Topic: "BIOSPHERE",
    Term: "VEGETATION",
    VariableLevel1: "VEGETATION INDEX"
    VariableLevel2: "NORMALIZED DIFFERENCE VEGETATION INDEX (NDVI)"
    DetailedVariable: "0.9 DENSITY"
  },
  {
    Category: "EARTH SCIENCE",
    Topic: "BIOSPHERE",
    Term: "VEGETATION",
    VariableLevel1: "EVERGREEN VEGETATION"
  }
],

    UMM Migration

    None

    Future Mappings

    Expand
    titleISO 19115-1

    ISO 19115-1

    Science Keywords are required. An unlimited amount of Science Keywords may be provided (Cardinality: 1..*)

    SpecificationPathTypeNotesISO 19115-1

    /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/

    mri:MD_Keywords/mri:keyword/gco:CharacterString

    (list each value of the keyword hierarchy delimited by &gt; )

    StringKMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by "&gt;". If any keyword is missing and there exists a keyword later in the hierarchy (such as DetailedLocation), use NONE to fill in the values in between. The CMR will not translate the NONE values they are only used to place each keyword in its correct space in the hierarchy.ISO 19115-1

    /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/

    mri:MD_Keywords/mri:keyword/mri:type/mri:MD_KeywordTypeCode[@codeListValue="theme"]

    Codelist

    codeList=http://standards.iso.org/iso/19115/resources/Codelist/cat/codelists.xml#MD_KeywordTypeCode

    Select the value "theme" from the codelist. This codelist value does not directly map to a UMM element; choosing "theme" indicates to CMR that the Science Keywords should be mapped.

    Section
    Column
    width50%

    ISO 19115-1

    No Format
    ...    
    <mdb:identificationInfo>
        <mri:MD_DataIdentification>

            <mri:descriptiveKeywords>
                <mri:MD_Keywords>
                    <mri:keyword>
                        <gco:CharacterString>EARTH SCIENCE&gt;BIOSPHERE&gt;VEGETATION&gt;VEGETATION INDEX&gt;NORMALIZED DIFFERENCE VEGETATION INDEX (NDVI)&gt;NONE&gt;0.9 DENSITY</gco:CharacterString>
                    </mri:keyword>
                    <mri:keyword>
                        <gco:CharacterString>EARTH SCIENCE&gt;BIOSPHERE&gt;VEGETATION&gt;EVERGREEN VEGETATION</gco:CharacterString>
                    </mri:keyword>
                    <mri:type>
                        <mri:MD_KeywordTypeCode
                            codeList="http://standards.iso.org/iso/19115/resources/Codelist/cat/codelists.xml#MD_KeywordTypeCode"
                            codeListValue="MD_KeywordTypeCode_theme">theme</mri:MD_KeywordTypeCode>
                    </mri:type>
                </mri:MD_Keywords>
            </mri:descriptiveKeywords>
         </mri:MD_DataIdentification>
    </mdb:identificationInfo>       
...
    Column
    width50%

    UMM

    No Format
    ScienceKeywords: [
  {
    Category: "EARTH SCIENCE",
    Topic: "BIOSPHERE",
    Term: "VEGETATION",
    VariableLevel1: "VEGETATION INDEX"
    VariableLevel2: "NORMALIZED DIFFERENCE VEGETATION INDEX (NDVI)"
    DetailedVariable: "0.9 DENSITY"
  },
  {
    Category: "EARTH SCIENCE",
    Topic: "BIOSPHERE",
    Term: "VEGETATION",
    VariableLevel1: "EVERGREEN VEGETATION"
  }
],

    History

    UMM Versioning

    VersionDateWhat Changed
    1.10.05/2/2018No changes were made to Location Keywords in the transition from UMM Version 1.9.0 to 1.10.0.
    1.9.0

    ARC Documentation

    VersionDateWhat ChangedAuthor
    1.0505/404/182018Recommendations/priority matrix transferred from internal ARC documentation to wiki spaceJeanne' le Roux