Paleo Temporal Coverage

Element Description

Note: This page is a draft/ work in progress

The Paleo Temporal Coverage element defines the time period in which geologic and/or paleoclimate data collection occurred. The element is predominantly used for data collection that occurred 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 to simply classify 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 is suggested that Paleo Temporal Coverage tags are as specific as possible to aid in data discovery. 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: "560 ka"

PaleoTemporalCoverage/PaleoEndDate: "60 ka"

PaleoTemporalCoverage/PaleoEon: "PHANEROZOIC"

PaleoTemporalCoverage/PaleoEra: "CENOZOIC"

PaleoTemporalCoverage/PaleoPeriod: "QUATERNARY"

PaleoTemporalCoverage/PaleoEpoch: "PLEISTOCENE"

PaleoTemporalCoverage/PaleoStage: "LATE"

PaleoTemporalCoverage/DetailedClassification:

PaleoTemporalCoverage/PaleoStartDate: "175 myr"

PaleoTemporalCoverage/PaleoEndDate: "160 myr"

PaleoTemporalCoverage/PaleoEon: "PHANEROZOIC"

PaleoTemporalCoverage/PaleoEra: "MESOZOIC"

PaleoTemporalCoverage/PaleoPeriod: "JURASSIC"

PaleoTemporalCoverage/PaleoStartDate: "100 ka"

PaleoTemporalCoverage/PaleoEndDate: "20 ka"

PaleoTemporalCoverage/PaleoEon: "PHANEROZOIC"

Element Specification

Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality
UMM-C	PaleoTemporalCoverage/PaleoStartDate	String	Paleo Temporal Coverage Paleo Start Date Terms	KMS controlled	No	0..1
UMM-C	PaleoTemporalCoverage/PaleoEndDate	String	Paleo Temporal Coverage Paleo End Date Terms	KMS controlled	No	0..1
UMM-C	PaleoTemporalCoverage/ChronostratigraphicUnit	String	Paleo Temporal Coverage Chronostratigraphic_Unit Terms	KMS controlled	No	0..*
UMM-C	PaleoTemporalCoverage/ChronostratigraphicUnit/Eon	String	Paleo Temporal Coverage Chronostratigraphic_Unit_Eon Terms	KMS controlled	Yes	1
UMM-C	PaleoTemporalCoverage/ChronostratigraphicUnit/Era	String	Paleo Temporal Coverage Chronostratigraphic_Unit_Era Terms	KMS controlled	No	0..1
UMM-C	PaleoTemporalCoverage/ChronostratigraphicUnit/Period	String	Paleo Temporal Coverage Chronostratigraphic_Unit_Period Terms	KMS controlled	No	0..1
UMM-C	PaleoTemporalCoverage/ChronostratigraphicUnit/Epoch	String	Paleo Temporal Coverage Chronostratigraphic_Unit_Epoch Terms	KMS controlled	No	0..1
UMM-C	PaleoTemporalCoverage/ChronostratigraphicUnit/Stage	String	Paleo Temporal Coverage Chronostratigraphic_Unit_Stage Terms	KMS controlled	No	0..1
UMM-C	PaleoTemporalCoverage/ChronostratigraphicUnit/Detailed_Classification	String	Paleo Temporal Coverage Detailed_Classification Terms	1 - 80 characters (Uncontrolled/Free-Text)	No	0..1

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

ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: The element is not included at all (for relevant collections). The element is included but is empty. The paleo temporal coverage term does not align with the KMS. The paleo temporal coverage term does not exist in 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 term is not appropriate for the dataset.
	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 term in the metadata (i.e. to extend a keyword hierarchy down to a more detailed keyword).
	Not Applicable
	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 is provided, return is "np"
- If a value is provided, return is "OK"

CMR Validation

<>

Dialect Mappings

DIF 9

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

DIF 10

If provided, Paleo Temporal Coverage Terms are required at the Eon level.

Specification	Path	Type	Constraints	Required in DIF 10?	Cardinality
DIF 10	/DIF/Paleo_Date_Time/Paleo_Start_Date	String	KMS controlled	No	0..1
DIF 10	/DIF/Paleo_Date_Time/Paleo_End_Date	String	KMS controlled	No	0..1
DIF 10	/DIF/Paleo_Date_Time/Chronostratigraphic_Unit	String	KMS controlled	No	0..1
DIF 10	/DIF/Paleo_Date_Time/Eon	String	KMS controlled	Yes	1
DIF 10	/DIF/Paleo_Date_Time/Era	String	KMS controlled	No	0..1
DIF 10	/DIF/Paleo_Date_Time/Period	String	KMS controlled	No	0..1
DIF 10	/DIF/Paleo_Date_Time/Epoch	String	KMS controlled	No	0..1
DIF 10	/DIF/Paleo_Date_Time/Stage	String	KMS controlled	No	0..1

Example Mapping

DIF 10

<Paleo_Temporal_Coverage>
  <Paleo_Start_Date>560 ka</Paleo_Start_Date>
  <Paleo_End_Date>60 ka</Paleo_End_Date>
  <Chronostratigraphic_Unit></Chronostratigraphic_Unit>
  <Eon>PHANEROZOIC</Eon>
  <Era>CENOZOIC</Era>
  <Period>QUATERNARY</Period>
  <Epoch>PLEISTOCENE</Epoch>
  <Stage>LATE</Stage>
</Paleo_Temporal_Coverage>
<Paleo_Temporal_Coverage>
  <Paleo_Start_Date>100 ka</Paleo_Start_Date>
  <Paleo_End_Date>20 ka</Paleo_End_Date>
  <Eon>PHANEROZOIC</Eon>
</Paleo_Temporal_Coverage>

UMM

PaleoTemporalCoverage: [
  {
    Start Date: "560 ka",
    End Date: "60 ka",
    Eon: "PHANEROZOIC",
    Era: "CENOZOIC",
	Period: "QUATERNARY",
	Epoch: "PLEISTOCENE",
	Stage: "LATE",
  },
  {
    Start Date: "100 ka",
    End Date: "20 ka",
    Eon: "PHANEROZOIC",
  }
],

ECHO 10

Location Keywords at the Category Level are required.

Specification	Path	Type	Constraints	Required in ECHO10?	Cardinality
ECHO 10	/Collection/LocationKeywords/LocationKeyword/CategoryKeyword	String	KMS controlled	Yes	1
ECHO 10	/Collection/LocationKeywords/LocationKeyword/TypeKeyword	String	KMS controlled	No	0..1
ECHO 10	/Collection/LocationKeywords/LocationKeyword/Subregion1Keyword/Value	String	KMS controlled	No	0..1
ECHO 10	/Collection/LocationKeywords/LocationKeyword/Subregion2Keyword/Value	String	KMS controlled	No	0..1
ECHO 10	/Collection/LocationKeywords/LocationKeyword/Subregion3Keyword/Value	String	KMS controlled	No	0..1
ECHO 10	/Collection/ScienceKeywords/LocationKeyword/DetailedLocationKeyword	String	Uncontrolled (Free-Text)	No	0..1

Example Mapping

ECHO 10

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

UMM

PaleoTemporalCoverage: [
  {
    Start Date: "560 ka",
    End Date: "60 ka",
    Eon: "PHANEROZOIC",
    Era: "CENOZOIC",
	Period: "QUATERNARY",
	Epoch: "PLEISTOCENE",
	Stage: "LATE",
  },
  {
    Start Date: "100ka",
    End Date: "20ka",
    Eon: "PHANEROZOIC",
  }
],

ISO 19115-2 MENDS

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

Specification

Path

Type

Notes

ISO 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 > )

String

KMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by ">". 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

ISO 19115-2 MENDS

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

UMM

PaleoTemporalCoverage: [
  {
    Start Date: "560 ka",
    End Date: "60 ka",
    Eon: "PHANEROZOIC",
    Era: "CENOZOIC",
	Period: "QUATERNARY",
	Epoch: "PLEISTOCENE",
	Stage: "LATE",
  },
  {
    Start Date: "100ka",
    End Date: "20ka",
    Eon: "PHANEROZOIC",
  }
],

ISO 19115-2 SMAP

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

Specification

Path

Type

Notes

ISO 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 > )

String

KMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by ">". 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

ISO 19115-2 SMAP

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

UMM

PaleoTemporalCoverage: [
  {
    Start Date: "560 ka",
    End Date: "60 ka",
    Eon: "PHANEROZOIC",
    Era: "CENOZOIC",
	Period: "QUATERNARY",
	Epoch: "PLEISTOCENE",
	Stage: "LATE",
  },
  {
    Start Date: "100ka",
    End Date: "20ka",
    Eon: "PHANEROZOIC",
  }
],

UMM Migration

None

Future Mappings

ISO 19115-1

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

Specification

Path

Type

Notes

ISO 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 > )

String

KMS controlled. This is where the entire keyword hierarchy should be listed. Each keyword in the hierarchy must be separated by ">". 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.

ISO 19115-1

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

UMM

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

Version	Date	What Changed
1.10.0	5/2/2018	No changes were made to Paleo Temporal Coverage in the transition from UMM Version 1.9.0 to 1.10.0
1.9.0

ARC Documentation

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

Page tree

Paleo Temporal Coverage

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

DIF 10

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 SMAP

UMM Migration

ISO 19115-1

History

UMM Versioning

ARC Documentation