Versions Compared

Key

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

...

This wiki resource provides best practices documentation for all collection and granule metadata concepts supported by the Common Metadata Repository (CMR). It is intended to support metadata authors as well as provide general guidance to those seeking information about CMR supported metadata concepts

The wiki is organized by metadata concept as specified in the Unified Metadata Model (UMM) and includes information such as: required metadata fields, definitions for each metadata concept, best practices for populating each metadata field, guidance on how to use controlled vocabularies, and the revision history of the UMM metadata schema. Also included are a detailed mapping/crosswalk between each UMM metadata field and the corresponding field in each CMR supported metadata standard. Supported standards currently include ECHO 10, DIF 10, ISO 19115-2 (in NASA specific MENDS and SMAP "flavors"), and ISO 19115-1.   

...

Currently, this wiki resource provides documentation for elements found in the UMM-C, UMM-G and UMM-Common models. 

Other UMM models not documented covered here include UMM-S (Services) and UMM-Var (Variables). 

...

Each wiki page has the following outline:

Element Description

  • Provides a high level definition on the metadata concept

Best Practices

  • Provides best practices for the metadata concept as well as sample values

Element Specification

  • A table detailing each unique metadata element within the concept. For each metadata element the table specifies:
    • The UMM model it is from (UMM-Common

...

    • , C or G)
    • The element name, exactly as it appears in the UMM schema
    • The element Type (string, enumeration, boolean, etc.)
    • Constraints (e.g. character length restrictions, controlled vocabularies, etc.)
    • The cardinality, which specifies how many times the element may be repeated. Please see the following for a more in depth explanation of cardinality: 
    • Notes: any additional information which may be useful about the element

Metadata Validation and QA/QC

  • There are various systems in place to ensure a certain standard of metadata quality is maintained in the CMR. The Metadata Validation and QA/QC section of the wiki page provides documentation regarding these efforts and systems:
    • GCMD Metadata QA/QC: The GCMD team is responsible for stewardship of metadata records in the CMR provided by any of CMR's International Directory Network (IDN) partners. This section details both the automated and manual checks the GCMD team performs on the IDN records to help maintain a certain standard of quality.
    • CMR Validation: The CMR system itself has certain requirements. This section details any baseline CMR requirements for the metadata concept in question.
    • ARC Metadata QA/QC: The ARC team is responsible for performing quality assessments of NASA metadata records in the CMR. This section specifies what the ARC team looks for (both manually and in an automated fashion) to ensure NASA's metadata records in the CMR maintain a certain standard of quality. 

   Dialect Mappings

  • The Dialect Mapping section provides detailed element-element mappings between the UMM and each CMR supported metadata standard. Current CMR supported metadata standards include:
    • DIF 10 
    • ECHO 10
    • ISO 19115-2 MENDS
    • ISO 19115-2 SMAP
  • Provided for each supported standard:
    • An element specification table which includes the direct crosswalk between the UMM element path and the corresponding element path in the supported standard. This table will also indicate if an element in a supported standard does not map to the UMM, or if there are any caveats in the manner that the information gets translated.
    • An enumeration mapping table (if applicable) - sometimes there are differences in enumeration values used in a supported standard VS the UMM.
    • An example mapping showing how a snippet of metadata in the supported standard will appear in the UMM format. This might illustrate examples of how certain information can get dropped or only partially translated between the supported standard and the UMM.  

UMM Migration

  • If a metadata concept undergoes significant changes between UMM version updates, this section will illustrate how the information provided in the older version of UMM will be translated over to the newer version.

Future Mapping

  • Occasionally, the CMR will consider supporting a new metadata standard. For instance, work is currently under way to support the ISO 19115-1 standard in order to support a large influx of records from NOAA. ((no idea if this is true - need to confirm)). If the CMR is in the process of building support for a new metadata standard, known documentation for that standard will be provided in the 'Future Mapping' section.

History

  • Provides a version history for the metadata element in question

Documentation Directory

There is a separate wiki page for each high level metadata concept in the UMM. The drop down sections below link directly to the documentation, and are categorized by UMM model:

The table below illustrates which elements in UMM-Common are shared between both Collections and Granules and their description. You will also see that while the elements are identical, some standards will include less information or different information based on the specific granule, such as that granules temporal extent. It is important to note that this is just a subset of what is in UMM-Common and the full list of elements found in UMM-Common can be from other objects (such as services and visualizations). 

...

ElementDefinitionRequired
Spatial ExtentThis element describes the geographic coverage of the data.No
Temporal Extent

This element describes when data were acquired or collected.

No
PlatformThis element describes the relevant platforms used to acquire the data.Yes
InstrumentThis element is used to register the device that measured or recorded the data, including direct human observation.Yes
ProjectThis element describes the scientific endeavor(s) with which the collection is associated.No
Related URLThis element describes any resource-related URLs that include project home pages, resource information pages, services, related data, archives/servers, metadata extensions, direct links to online software packages, web mapping services, links to images, documents, or other data.Yes
Data DatesThis element is used to identify dates when the data or resource itself changed in some way. No
Use Constraints

This element defines how data may or may not be used to assure the protection of privacy or intellectual property. This includes license information, or any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the dataset.

No
Access ConstraintsThis element describes any restrictions imposed on data access. Access Constraints can be described in a free text field with the option to provide an access control list (ACL) value. No
Metadata LanguageThis element specifies the language used in the metadata record (i.e. English, French, Chinese, etc.).No
Metadata DatesThis element is used to identify dates when the metadata changed in some way. This element is made of two sub-elements, Type and Date.No
Tiling Identification SystemThis element defines a named two-dimensional tiling system related to the collection. No
Additional AttributesThis element stores the data's distinctive attributes (i.e. attributes used to describe the unique characteristics of the resource which extend beyond those defined in this mapping).No
Language********The language used in the dataset (i.e. English, French, Chinese, etc.). Note: This is different from the language of the metadata.

EXAMPLE HEADER FOR NEXT SECTION

While the information in the table above depicts shared elements in UMM-Common, the table below illustrates what the actual information looks like in the metadata. These examples will show how the information looks in both collections and granules as well as how the different metadata standards display their information that UMM then interprets and maps.

Examples of UMM-Common Metadata InformationUMM-CUMM-GElementInformationStandardElementInformationStandardTemporal Extent

<Temporal>

    <TimeType>Universal Time</TimeType>

    <DateType>Eastern Daylight</DateType>

    <TemporalRangeType>Long Range</TemporalRangeType>

    <PrecisionOfSeconds>1</PrecisionOfSeconds>

    <EndsAtPresentFlag>true</EndsAtPresentFlag>

    <RangeDateTime>

       <BeginningDateTime>1990-01-01T00:00:00Z</BeginningDateTime> 

       <EndingDateTime>2003-12-31T00:00:00Z</EndingDateTime> 

    </RangeDateTime>

</Temporal>

ECHO 10Temporal Extent

<RangeDateTime>

  <BeginningDateTime>2006-01-15T00:00:00.000Z</BeginningDateTime>

  <EndingDateTime>2006-01-23T00:00:00.000Z</EndingDateTime>

</RangeDateTime>

**For single date/time***

<SingleDateTime>2002-02-27T23:49:24.0000000Z</SingleDateTime>

ECHO 10 (Different options available within ECHO 10 for granules, such as point, orbit, etc.)Platform

 <Platform>
    <Type>Earth Observation Satellites</Type>
    <Short_Name>AQUA</Short_Name>
    <Long_Name>Earth Observing System, AQUA</Long_Name>
    <Characteristics>
      <Name>EquatorCrossingTime</Name>
      <Description>Local time of the equator crossing and direction (ascending or descending </Description>
      <DataType>Time/direction (ascending)</DataType>
      <Unit>Local Mean Time</Unit>
      <Value>3:30, ascending</Value>
    </Characteristics>
    <Instrument>
      <Short_Name>MODIS</Short_Name>
      <Long_Name>Moderate-Resolution Imaging Spectroradiometer</Long_Name>
      <Technique>Imaging Spectroradiometry</Technique>
      <Sensor>
        <Short_Name>MODIS</Short_Name>
        <Long_Name>Cross-track Scanning Radiometer</Long_Name>
        <Technique>Radiometry</Technique>
      </Sensor>
    </Instrument>
  </Platform>

DIF 10Platform

 <Platform>
    <Type>Earth Observation Satellites</Type>
    <Short_Name>AQUA</Short_Name>
    <Long_Name>Earth Observing System, AQUA</Long_Name>
    <Characteristics>
      <Name>EquatorCrossingTime</Name>
      <Description>Local time of the equator crossing and direction (ascending or descending </Description>
      <DataType>Time/direction (ascending)</DataType>
      <Unit>Local Mean Time</Unit>
      <Value>3:30, ascending</Value>
    </Characteristics>
    <Instrument>
      <Short_Name>MODIS</Short_Name>
      <Long_Name>Moderate-Resolution Imaging Spectroradiometer</Long_Name>
      <Technique>Imaging Spectroradiometry</Technique>
      <Sensor>
        <Short_Name>MODIS</Short_Name>
        <Long_Name>Cross-track Scanning Radiometer</Long_Name>
        <Technique>Radiometry</Technique>
      </Sensor>
    </Instrument>
  </Platform>

DIF 10Related URL

<OnlineAccessURLs>

   <OnlineAccessURL>

      <URL>http://sedac.ciesin.columbia.edu/data/set/ulandsat-cities-from-space/data-download</URL>

      <URLDescription>data download page</URLDescription>

   </OnlineAccessURL>

</OnlineAccessURLs>

<OnlineResources>

   <OnlineResource>

      <URL>http://dx.doi.org/10.7927/H4SQ8XB1</URL>

      <Description>data set DOI and homepage</Description> 

      <Type>DOI URL</Type>

   </OnlineResource>

</OnlineResources>

<AssociatedBrowseImageUrls>

    <ProviderBrowseUrl>

        <URL>http://sedac.ciesin.columbia.edu/data/set/ulandsat-cities-from-space/maps</URL>

    </ProviderBrowseUrl>

</AssociatedBrowseImageUrls>

ECHO 10Related URL

<OnlineAccessURLs>
        <OnlineAccessURL>
          <URL>https://datapool.asf.alaska.edu/GEOTIFF/SS/SS_00107_STD_F0373_tif.zip</URL>
        </OnlineAccessURL>
    </OnlineAccessURLs>
        <Orderable>true</Orderable>
        <Visible>true</Visible>
  <AssociatedBrowseImageUrls>
      <ProviderBrowseUrl>
      <URL>https://datapool.asf.alaska.edu/BROWSE/SS/SS_00107_STD_F0373_BROWSE.jpg</URL>
      </ProviderBrowseUrl>
  </AssociatedBrowseImageUrls>

ECHO 10Metadata Dates

<gmd:dateStamp>

  <gco:DateTime>2008-12-02T00:00:00Z</gco:DateTime>

</gmd:dateStamp>

...

<gmd:date>

  <gmd:CI_Date>

    <gmd:date>

      <gco:DateTime>2008-12-02T00: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>2008-12-02T00: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>

ISO 19115-2Metadata Dates

<gmd:dateStamp>

  <gco:DateTime>2008-12-02T00:00:00Z</gco:DateTime>

</gmd:dateStamp>

...

<gmd:date>

  <gmd:CI_Date>

    <gmd:date>

      <gco:DateTime>2008-12-02T00: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>2008-12-02T00: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>

ISO 19115-2


Related Resources, Information, and Documentation

...