Projects (Granule)

• Element Description
• Best Practices
• Element Specification
• Metadata Validation and QA/QC
• History
  • UMM Versioning
  • ARC Documentation

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. 

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

Providing a Project is optional, however, it is highly recommended that a Project be provided in the metadata if possible. If a dataset is associated with more than one Project, then multiple Projects may be listed. Project also includes the 'Campaign' sub-element in order to support multiple sub-campaigns under the same Project. The following sub-elements are used to describe Project:

ShortName: If the Project element is provided, then the Short Name field is required. The Project Short Name must be selected from the 'Short_Name' column in the GCMD Project Keyword list. Project names are controlled to ensure ensure consistency when searching for data using keywords or via the Project faceted search.

Campaigns: Providing a Campaign name is optional, however, it is encouraged that a value be provided if one exists in the GCMD Project Keyword list. Providing a Campaign is encouraged If a Project Short Name is associated with one of more Campaigns. Campaign names should be selected from the Project GCMD keyword list. 

Examples:
ShortName: ISLSCP II

ShortName: MEaSUREs
Campaigns: NVAP-M 

UMM-G Example:
"Projects": [
         {
          "ShortName": "ISLSCP II"
          }
]

"Projects": [
        {
         "ShortName": "MEaSUREs",
         "Campaigns": ["NVAP-M"]
         }
]

Element Specification

Providing the Projects element is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)

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. 

Please see the expandable sections below for flowchart details.

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

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

UMM Versioning