Element Description

The Purpose element contains suggested usage for the data and/or a description for why the resource exists. Any limitations on the resource (including, but not limited to, special restrictions, legal prerequisites, and terms and conditions) should be placed into the Use Constraints element and not into the Purpose element.

Best Practices

The Purpose element is optional. It can be leveraged to communicate to a user the broad applications the data is designed to be used for, and/or why the data were generated. 

Examples:

"To assess species composition, abundance, distribution and biomass of zooplankton within the Bering and Chukchi Seas, 1985-1989."

"To provide VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats."

"To serve a wide user community by providing composite Landsat images and raw data for urban areas that can be used in interdisciplinary studies of remote sensing and the environment."


Element Specification

ModelElementTypeConstraintsRequired?Cardinality
UMM-CPurpose String

1 - 10000 characters

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


  • Manual Review
    • Check that the purpose description is appropriate for the dataset.
  • Automated Review
    • Check that the field has been populated.
    • Check that the field length is not greater than 1000 characters.
  • If this element is used, it must contain at least 1 character and be no longer than 10000 characters in length

ARC Priority Matrix

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

  • The Purpose contains spelling or grammatical errors.
  • The Purpose is incorrect for the data (for example, a copy and paste error could result in the purpose for a different dataset to appear in this field).
  • A broken URL is provided in the Purpose element.

Yellow = Medium Priority Finding

This element is categorized as medium priority when:

  • The information provided in the Purpose element is better suited for a different metadata field (i.e. incorrect usage of the Purpose field).

Blue = Low Priority Finding

This element is categorized as low priority when:

  • A link provided in the Purpose element needs to be updated from 'http' to 'https'.

Green = No Findings/Issues

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

ARC Automated Checks

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

Dialect Mappings

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

DIF 10

Purpose is an optional element. Purpose can only be provided once (Cardinality: 0..1)

UMM-C ElementDIF 10 PathTypeConstraintsRequired in DIF 10?Cardinality
PurposeSummary/Purpose

String

1 - 10000 characters

No

0..1


Example Mapping

DIF 10

<Summary>
 <Purpose>To test the feasibility of creating a comparative index of national-level environmental sustainability.</Purpose>
</Summary>

UMM

"Purpose": "To test the feasibility of creating a comparative index of national-level environmental sustainability."

ECHO 10

Suggested Usage is an optional element. Suggested Usage can only be provided once (Cardinality: 0..1)

UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?CardinalityNotes
PurposeSuggestedUsageString

1 - 4000 characters

No0..1

The ECHO 10 schema definition for Suggested Usage: "This attribute describes how this collection or granule may be best used to support Earth science/global change research."


Example Mapping

ECHO 10

<SuggestedUsage>To serve a wide user community by providing composite Landsat images and raw data for urban areas that can be used in interdisciplinary studies of remote sensing and the environment.</SuggestedUsage>

UMM

"Purpose": "To serve a wide user community by providing composite Landsat images and raw data for urban areas that can be used in interdisciplinary studies of remote sensing and the environment."

ISO 19115-2 MENDS

Purpose is an optional element. Purpose can only be provided once in CMR (Cardinality: 0..1)

UMM-C Element

ISO 19115-2 MENDS Path

TypeNotes
Purpose/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:purpose/gco:CharacterString

String



Example Mapping

ISO 19115-2 MENDS

<gmi:MI_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      ...
      <gmd:purpose>
        <gco:CharacterString>To provide VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats.</gco:CharacterString>
      </gmd:purpose>
      ...
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmi:MI_Metadata>

UMM

"Purpose": "To provide VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats."

ISO 19115-2 SMAP

Purpose is an optional element. Purpose can only be provided once in CMR (Cardinality: 0..1)

UMM-C Element

ISO 19115-2 SMAP Path

TypeNotes
Purpose/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:purpose/gco:CharacterString

String



Example Mapping

ISO 19115-2 SMAP

<gmd:DS_Series>
  <gmd:seriesMetadata>
    <gmi:MI_Metadata>
      ...
      <gmd:identificationInfo>
        <gmd:MD_DataIdentification>
          ...        
          <gmd:purpose>
            <gco:CharacterString>To provide VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats.</gco:CharacterString>
          </gmd:purpose>
          ...
        </gmd:MD_DataIdentification>
      </gmd:identificationInfo>
      ...
    </gmi:MI_Metadata>
  </gmd:seriesMetadata>
</gmd:DS_Series>

UMM

"Purpose": "To provide VIIRS 375m resolution active fire locations in Near Real-Time in easy to use formats."

UMM Migration

None

History

UMM Versioning

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

No changes were made for Purpose during the transition from version 1.9.0 to 1.10.0.

ARC Documentation

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



  • No labels

1 Comment

  1. Samuel Ayers

    1. Recommend changing "for" to "of" in the following sentence:

    "The Purpose element contains suggested usage for the data and/or a description for why the resource exists."

    2. Recommend removing the space between 'and Chukchi Seas' and ', 1985-1989."'

    3. Appears that "1000" should be changed to "10000" in the following:

    "Check that the field length is not greater than 1000 characters"

    4. Note for DIF 9 is outdated