Page History

Table of Contents

style	circle

Element Description

The Project element describes the scientific endeavor(s) with which the collection is associated. Scientific endeavors include field campaigns, flight campaigns, projects, interdisciplinary science investigations, missions, scientific programs, etc. This element may also cover a long term project that continuously creates new data setsdatasets.

Best Practices

Project 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://gcmdservices.gsfc.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 data set 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.

LongName: Providing a Project Long Name is optional, however, it is encouraged that a long name be provided if one exists in the GCMD Project Keyword list. Providing a Project Long Name is encouraged because the associated Project Short Name may be comprised of acronyms. Project Long Names should be selected from the Long_Name column in the keyword list.

Campaign: The Campaign sub-element can be used to list the names of smaller projects/campaigns which fall within the scope of the Project listed. If necessary, multiple Campaigns may be associated with a single Project.

StartDate: The Start Date should indicate the date that the Project began. Providing the Start Date is optional.

EndDate: The End Date should indicate the date that the Project ended/ will end. For Projects that are still underway, the End Date may be in the future. Providing the End Date for the Project is optional.

Examples:

ShortName: ISLSCP II

LongName: International Satellite Land Surface Climatology Project II

StartDate: 1986-01-01

EndDate: 1995-12-31

ShortName: MEaSUREs

LongName: Making Earth System Data Records for Use in Research Environments

Campaign: NVAP-M

Element Specification

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

Usable Valid Values

Model	Element	Type		Constraints	Required?	Cardinality	Notes
UMM-Common	Project/ShortName	String	1 - 40 characters Project Short_Name Keywords	1 - 40 characters KMS controlled	Yes, if applicable	1	Providing a Project is optional. If provided, the Short Name is required.
UMM-Common	Project/LongName	String	Project Long_Name Keywords	1 - 300 charactersKMS controlledProject Long_Name Keyword	No	0..1
UMM-Common	Project/Campaigns	String	n/a	1 - 80 characters	No	0..*	Multiple Campaigns may be listed under each Project.
UMM-Common	Project/StartDate	dateTime	n/a	n/a	No	0..1
UMM-Common	Project/EndDate	dateTime	n/a	n/a	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).

Lucidchart

rich-viewer	true

autofit	true
name	Copy of Wiki Page Metadata Evaluation Workflow-1939-672ea43a
width	1102
id	98e5dc28-3252-4209-953f-66f1378e1cf4
align	Left
height	299

Please see the expandable sections below for flowchart details.

Expand

title	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 field length is not greater than the maximum characters allowed for each sub-element.
- Check that the Date format is valid.

Expand

title	CMR Validation

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: The Project Short Name and/or Long Name keyword does not comply with the KMS. The Project Short Name and /or Long Name keyword does not exist in the KMS. A keyword(s) is placed in the incorrect position of the hierarchy (e.g. the Project Short Name is placed in the Long Name field). Keywords from two different KMS hierarchies are listed in the same hierarchy in the metadata (i.e. hierarchies cannot be mixed and matched). The Project and/or Campaign listed is incorrect for the data setdataset. The Start Date and/or End Date are incorrect for the Project.
	This element is categorized as medium priority when: There is no Project provided. While not required, providing a Project is highly recommended. A recommendation is made to add a Project Long Name when a long name exists in the KMS. Project and/or Campaign names are provided in an inconsistent manner across related data setsdatasets.
	This element is categorized as low priority when:
	The element is provided, a correct valid value is used, and the valid value matches the status of the data setdataset.

ARC Automated Checks

Short Name
- If a value is not provided, return is: "It is highly recommended that a Project Short Name be provided. Project Short Names are GCMD controlled and should be chosen from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/projects/projects.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."
Long Name
- If a value is not provided, return is: "np."
- If a short name is absent as well as long name, return is: "In addition to adding a Project Short Name, recommend adding a Project Long Name (if applicable)."
- 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."

Dialect Mappings

Expand

title	DIF 9

DIF 9

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

Expand

title	DIF 10

DIF 10

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

Usable Valid Values

UMM-C Element	DIF 10	Specification	Path	Type		Constraints	Required in DIF 10?	Cardinality
Project/ShortName	DIF 10	/DIF/Project/Short_Name	String	Project Short_Name Keywords	KMS controlled	Yes, if applicable	1	Providing a Project is optional. If provided, the Short Name is required.
Project/LongName	DIF 10	/DIF/Project/Long_Name	String	Project Long_Name Keywords	KMS controlled	No	0..1
Project/Campaigns	DIF 10	/DIF/Project/Campaign	Stringn/a		No	0..*	Multiple Campaigns may be listed under each Project.
Project/StartDate	DIF 10	/DIF/Project/Start_Date	Date	n/a		No	0..1	DIF 10
Project/EndDate	/DIF/Project/End_Date	Daten/a		No	0..1

Example Mapping

Section

Column

width	50%

DIF 10

No Format
<Project> <Short_Name>GCPEx</Short_Name> <Long_Name>GPM Cold Season Precipitation Experiment</Long_Name> </Project>

Column

width	50%

UMM

No Format
Projects: [ { ShortName: "GCPEx", LongName: "GPM Cold Season Precipitation Experiment" } ]

Expand

title	ECHO 10

ECHO 10

Providing a Campaign is optional. Multiple Campaigns may be provided if necessary (Cardinality 0..*)

UMM-C Element	ECHO 10

Specification

Path	Type

Usable Valid Values

	Constraints	Required in ECHO10?	Cardinality	Notes

ECHO 10/Collection/

Project/ShortName

Campaigns/Campaign/ShortName

String

1 - 40 characters

Project Short_Name Keywords

1 - 40 characters

KMS controlled

Yes, if applicable

1

Providing a Campaign is optional. If provided, the Short Name is required.

ECHO 10/Collection/

Project/LongName

Campaigns/Campaign/LongName

String

1 - 1024 characters

Project Long_Name Keywords

1 - 1024 characters

KMS controlled

No

0..1

ECHO 10/Collection/


Project/StartDate	Campaigns/Campaign/StartDate	dateTime	n/a

n/a

No

0..1

ECHO 10/Collection/


Project/EndDate	Campaigns/Campaign/EndDate	dateTime

n/a

No

0..1

Example Mapping

Section

Column

width	50%

ECHO 10

No Format
<Campaigns> <Campaign> <ShortName>GCPEx</ShortName> <LongName>GPM Cold Season Precipitation Experiment</LongName> </Campaign> </Campaigns>

Column

width	50%

UMM

No Format
Projects: [ { ShortName: "GCPEx", LongName: "GPM Cold Season Precipitation Experiment" } ]

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

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

Specification	Path	Type	Notes
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.projectshortname	String	Maps to the UMM element Project/ShortName. A list of valid project short names can be found in the KMS. For each project listed, a short name is required by CMR. The short name value goes in the gmd:code field. The value of "gov.nasa.esdis.umm.projectshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the project short name from the ISO metadata.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString	String	Maps to the UMM element Project/LongName. A list of valid project long names can be found in the KMS. Providing a project long name is optional, but is highly recommended.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/ gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.campaignshortname	String	Maps to the UMM element Project/Campaign. The campaign value goes in the gmd:code field. Multiple Campaigns can be provided if necessary. The value of "gov.nasa.esdis.umm.campaignshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the campaign name from the ISO metadata.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:description/gco:CharacterString = StartDate:	String	Maps to the UMM element Project/StartDate. The string "StartDate: " must be provided as part of the character string in order for CMR to properly parse out the project start date from the ISO metadata.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:description/gco:CharacterString = EndDate:	String	Maps to the UMM element Project/EndDate. The string "EndDate: " must be provided as part of the character string in order for CMR to properly parse out the project end date from the ISO metadata.

Example Mapping

Section

Column

width	50%

ISO 19115-2 MENDS

No Format

<gmi:MI_Metadata>
...
  <gmi:acquisitionInformation>
    <gmi:MI_AcquisitionInformation>
      <gmi:operation>
        <gmi:MI_Operation>
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>GCPEx</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>GPM Cold Season Precipitation Experiment</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
        </gmi:MI_Operation>
      </gmi:operation>
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
...
</gmi:MI_Metadata>

Column

width	50%

UMM

No Format
Projects: [ { ShortName: "GCPEx", LongName: "GPM Cold Season Precipitation Experiment" } ]

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

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

Specification	Path	Type	Notes
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.projectshortname	String	Maps to the UMM element Project/ShortName. A list of valid project short names can be found in the KMS. For each project listed, a short name is required by CMR. The short name value goes in the gmd:code field. The value of "gov.nasa.esdis.umm.projectshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the project short name from the ISO metadata.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString	String	Maps to the UMM element Project/LongName. A list of valid project long names can be found in the KMS. Providing a project long name is optional, but is highly recommended.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/ gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.campaignshortname	String	Maps to the UMM element Project/Campaign. The campaign value goes in the gmd:code field. Multiple Campaigns can be provided if necessary. The value of "gov.nasa.esdis.umm.campaignshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the campaign name from the ISO metadata.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:description/gco:CharacterString = StartDate:	String	Maps to the UMM element Project/StartDate. The string "StartDate: " must be provided as part of the character string in order for CMR to properly parse out the project start date from the ISO metadata.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:description/gco:CharacterString = EndDate:	String	Maps to the UMM element Project/EndDate. The string "EndDate: " must be provided as part of the character string in order for CMR to properly parse out the project end date from the ISO metadata.

Example Mapping

Section

Column

width	50%

ISO 19115-2 SMAP

No Format

<gmd:DS_Series>
<gmd:seriesMetadata>
<gmi:MI_Metadata>
...
  <gmi:acquisitionInformation>
    <gmi:MI_AcquisitionInformation>
      <gmi:operation>
        <gmi:MI_Operation>
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>GCPEx</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>GPM Cold Season Precipitation Experiment</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
        </gmi:MI_Operation>
      </gmi:operation>
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
...
</gmi:MI_Metadata>
</gmd:seriesMetadata>
</gmd:DS_Series>

Column

width	50%

UMM

No Format
Projects: [ { ShortName: "GCPEx", LongName: "GPM Cold Season Precipitation Experiment" } ]

UMM Migration

None

Future Mappings

Expand

title	ISO 19115-1

ISO 19115-1

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

Specification	Path	Type	Notes

Section

Column

width	50%

ISO 19115-1

No Format

Column

width	50%

UMM

No Format
Projects: [ { ShortName: "GCPEx", LongName: "GPM Cold Season Precipitation Experiment" } ]

History

UMM Versioning

Version	Date	What Changed
1.13.0	Future	No changes were made for Project during the transition from version 1.12.0 to 1.13.0
1.12.0	01/22/2019	No changes were made for Project during the transition from version 1.11.0 to 1.12.0.
1.11.0	11/28/2018	No changes were made for Project during the transition from version 1.10.0 to 1.11.0.
1.10.0	05/02/2018	No changes were made for Project during the transition from version 1.9.0 to 1.10.0.
1.9.0

ARC Documentation

Version	Date	What Changed	Author
1.0	8/24/18	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Kaylin Bugbee

Page tree

Versions Compared

Old Version 27

New Version 28

Key

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

DIF 10

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 SMAP

UMM Migration

ISO 19115-1

History

UMM Versioning

ARC Documentation