Versions Compared

Old Version 7

changes.mady.by.user Michael Morahan

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (em.koontz)

Saved on

Key

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

Element Description

The Projects element describes the scientific endeavor(s) with which the collection is associated. Scientific endeavors include field campaigns, flight campaigns, projects, campaigns, interdisciplinary science investigations, missions, scientific programs, etc. This element may also cover a long term project that continuously creates new datasets. A reference to a project in the parent collection that is associated with the acquisition of the granule. The project must exist in the parent collection. Campaigns are a part of a project and must also be defined in the parent collection.

Best Practices

Projects names are important for data search and discovery. In order to provide a consistent search experience, Project names are controlled by GCMD vocabulary maintained in the Keyword Management System (KMS). This is especially important for faceted searches by Project name in the Earthdata Search Client. A list of valid Project keywords can be found here: https://gcmd.earthdata.nasa.gov/kms/concepts/concept_scheme/projects?format=csv

...

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

HTML
<div style="width: 960px; height: 504px; margin: 10px; position: relative;"><iframe allowfullscreen frameborder="0" style="width:960px; height:504px" src="https://lucid.app/documents/embedded/98e5dc28-3252-4209-953f-66f1378e1cf4" id="aOKsQ0i2SArm"></iframe></div>


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 field length is not greater than the maximum characters allowed for each sub-element.
    • Check that the Date format is valid.
Expand
titleCMR Validation
  • If a granule has a project short name in it, it must match to one that is defined in the collection.
  • If removing a project from a collection, none of its granules can reference that project's short name.
Expand
titleARC Metadata QA/QC

ARC Priority Matrix


Priority CategorizationJustification
Red = Hight Priority Finding

This element is categorized as highest priority when:

  • The Project Short Name does not comply with or exist within the KMS.
  • The Project/Campaign listed is incorrect for the dataset
Yellow = Medium Priority FindingNot Applicable
Blue = Low Priority Finding

This element is provided as lowest priority when:

  • There is no Project/Campaign listed. While not required, providing a Project is highly recommended.
Green = No Findings/IssuesThe element is provided and follows all applicable criteria specified in the best practices section above.


UMM Versioning

VersionDateWhat Changed
1.6.6

 

Initial version for WIKI entry.