Page History
Table of Contents | ||
---|---|---|
|
Element Description
Note: This page is a draft/ work in progress
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, field experimentsscientific programs, etc. Project and campaign names provided in CMR metadata must be chosen from a controlled keyword hierarchy maintained in the . This element may also cover a long term project that continuously creates new datasets.
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). A list of valid project keywords 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://gcmdservicesgcmd.gsfcearthdata.nasa.gov/statickms/kmsconcepts/projectsconcept_scheme/projects.csv?ed_wiki_keywords_page
Best Practices
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 Project and/or campaign names are important for data search and discovery. In order to provide a consistent search experience, project and campaign names are controlled by GCMD vocabulary maintained in the Keyword Management System (KMS). This is especially important when conducting a faceted search by project name in the Earthdata Search Client. The following sub-elements are used to describe Project:
ShortName: Providing a project short name is required in CMR. The project short name 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 in optionalProject 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 Project Long Name is encouraged because the associated project short name Project Short Name may be comprised of acronyms. Project long names 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..*)
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-Common | Project/ShortName | String | 1 - 40 characters | Yes, if applicable | 1 | Providing a Project is optional. If provided, the Short Name is required |
Element Specification
Providing a Project is optional. Multiple Project may be provided if necessary (Cardinality 0..*)
1 - 40 characters
KMS controlled
1 - 300 characters
KMS controlled
. | |
UMM-Common | Project/ |
LongName |
String | 1 - 300 characters | No | 0..1 | |||
UMM-Common | Project/Campaigns | String | 1 - 80 characters | No | 0..* | Multiple Campaigns may be listed under each Project. |
UMM-Common | Project/StartDate | dateTime | n/a | No | 0..1 |
Value needed for translations:
N/AUMM-Common | Project/EndDate | dateTime | 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 | ||
---|---|---|
| ||
Expand | ||
| ||
Expand | ||
| ||
Priority Categorization | Justification | This element is categorized as highest priority when:
| This element is categorized as medium priority when:
| 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 set. |
Dialect Mappings
|
Expand | ||
---|---|---|
| ||
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10Providing a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)
|
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Providing a Campaign is optional. Multiple Campaigns may be provided if necessary (Cardinality 0..*)
|
Expand | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSProviding a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)
| |||||||||||||||||||||||||||||||||
Expand | |||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||
Expand | |||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||
Specification | Path | Type | Constraints | Required in DIF 10? | Cardinality | Notes | DIF 10 | /DIF/Temporal_Coverage/Time_Type | String | No | 0..1 | DIF 10 | /DIF/Temporal_Coverage/Date_Type | String | No | 0..1 | DIF 10 | /DIF/Temporal_Coverage/Temporal_Range_Type | String | No | 0..1 | DIF 10 | /DIF/Temporal_Coverage/Precision_Of_Seconds | Integer | No | 0..1 | The precision (position in number of places to right of decimal point) of seconds used in measurement. | DIF 10 | /DIF/Temporal_Coverage/Ends_At_Present_Flag | Boolean | No | 0..1 | Recommend providing a value of "true" for active data sets. |
Model | Element | Type | Usable Valid Values | Required? | Cardinality | Notes | |||||||||||||||||||||||||||
DIF 10 | /DIF/Temporal_Coverage/Single_DateTime | Date dateTime Enumeration | unknown present unbounded future Not provided | Yes, if applicable | 1 | DateTime fields must be in date (YYY-MM-DD) or Date-Time (YYYY-MM-DDTHH:MM:SS) format. It is preferred that a date or dateTime be provided if known, rather than one of the enumeration values. For definitions of the enumeration values, please see the DIF schema. The enumeration "Not provided" should not be used by metadata providers. This value is used by translation software (to DIF 10) for required fields. | |||||||||||||||||||||||||||
Model | Element | Type | Usable Valid Values | Required? | Cardinality | Notes | |||||||||||||||||||||||||||
DIF 10 | /DIF/Temporal_Coverage/Range_DateTime/Beginning_Date_Time | Date dateTime Enumeration | unknown present unbounded future Not provided | Yes, if applicable | 1 | DateTime fields must be in date (YYY-MM-DD) or Date-Time (YYYY-MM-DDTHH:MM:SS) format. It is preferred that a date or dateTime be provided if known, rather than one of the enumeration values. For definitions of the enumeration values, please see the DIF schema. The enumeration "Not provided" should not be used by metadata providers. This value is used by translation software (to DIF 10) for required fields. | |||||||||||||||||||||||||||
DIF 10 | /DIF/Temporal_Coverage/Range_DateTime/Ending_Date_Time | Date dateTime Enumeration | unknown present unbounded future Not provided | No | 0..1 | DateTime fields must be in date (YYY-MM-DD) or Date-Time (YYYY-MM-DDTHH:MM:SS) format. It is preferred that a date or dateTime be provided if known, rather than one of the enumeration values. For definitions of the enumeration values, please see the DIF schema. The enumeration "Not provided" should not be used by metadata providers. This value is used by translation software (to DIF 10) for required fields. | |||||||||||||||||||||||||||
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes | DIF 10 | /DIF/Temporal_Coverage/Periodic_DateTime/Name | String | n/a | Yes, if applicable | 1 | Dates must comply with the ISO 8601 Standard. | DIF 10 | /DIF/Temporal_Coverage/Periodic_DateTime/Start_Date | Date dateTime Enumeration | unknown present unbounded future Not provided | Yes, if applicable | 1 | DateTime fields must be in date (YYY-MM-DD) or Date-Time (YYYY-MM-DDTHH:MM:SS) format. It is preferred that a date or dateTime be provided if known, rather than one of the enumeration values. For definitions of the enumeration values, please see the DIF schema. The enumeration "Not provided" should not be used by metadata providers. This value is used by translation software (to DIF 10) for required fields. | DIF 10 | /DIF/Temporal_Coverage/Periodic_DateTime/End_Date | Date dateTime Enumeration | unknown present unbounded future Not provided | Yes, if applicable | 1 | DateTime fields must be in date (YYY-MM-DD) or Date-Time (YYYY-MM-DDTHH:MM:SS) format. It is preferred that a date or dateTime be provided if known, rather than one of the enumeration values. For definitions of the enumeration values, please see the DIF schema. The enumeration "Not provided" should not be used by metadata providers. This value is used by translation software (to DIF 10) for required fields. | DIF 10 | /DIF/Temporal_Coverage/Periodic_DateTime/Duration_Unit | Enumeration | DAY MONTH YEAR | Yes, if applicable | 1 | DIF 10 | /DIF/Temporal_Coverage/Periodic_DateTime/Duration_Value | Integer | n/a | Yes, if applicable | 1 | DIF 10 | /DIF/Temporal_Coverage/Periodic_DateTime/Period_Cycle_Duration_Unit | Enumeration | DAY MONTH YEAR | Yes, if applicable | 1 | DIF 10 | /DIF/Temporal_Coverage/Periodic_DateTime/Period_Cycle_Duration_Value | Integer | n/a | Yes, if applicable | 1 |
DIF 10 | Translation Direction | UMM | |||||||||||||||||||||||||||||||
DAY | ↔ | DAY | |||||||||||||||||||||||||||||||
MONTH | ↔ | MONTH | |||||||||||||||||||||||||||||||
YEAR | ↔ | YEAR | unknown | → | present | unbounded | future | Not provided |
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ECHO 10 |
---|
ECHO 10
The time system which the values found in temporal subclasses. For example:
The type of date represented by the value in the date attributes of the temporal subclasses. For example:
Tells the system how temporal coverage is
specified for the collection. For example: SingleDateTime, RangeDateTime, PeriodicDateTime
The precision (position in number of
places to right of decimal point) of seconds used in measurement.
Choice of:
(1) SingleDateTime
If SingleDateTime is selected, the cardinality is 1..*
(2) RangeDateTime
If RangeDateTime is selected, the cardinality is 1..*
(3) PeriodicDateTime
If PeriodicDateTime is selected, the cardinality is 1..*
DAY
MONTH
YEAR
DAY
MONTH
YEAR
Enumeration Mapping
Translation
Direction
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 MENDS |
---|
ISO 19115-2 MENDS
Enumeration/Code List Mapping
Translation
Direction
NOT APPLICABLE
a string is used instead
of the defined codes.
The codeList=”” and
codeListValue = “”
Expand | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||
ISO 19115-2 SMAPProviding a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*) |
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
ISO 19115-2 SMAP
UMM-C Element | ISO 19115-2 SMAP Path | Type | Notes |
---|---|---|---|
Project/ShortName | /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. |
Project/LongName | /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. |
Project/Campaign | /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. |
Project/StartDate | /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. |
Project/EndDate |
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/ |
gmi: |
acquisitionInformation/ |
gmi: |
MI_ |
AcquisitionInformation/ |
gmi: |
operation/ |
gmi: |
Enumeration/Code List Mapping
Translation
Direction
NOT APPLICABLE
a string is used instead
of the defined codes.
The codeList=”” and
codeListValue = “”
Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UMM Migration
Translation
Direction
Future Mappings
title | ISO 19115-1 |
---|
ISO 19115-1
|
UMM Migration
None
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||
Future Mappings
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | The description of this element now includes text about the controlled vocabulary for project names coming from KMS. |
1.15.4 | 9/18/2020 | No changes were made for Project during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Project during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Project during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Project during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Project during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Project during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | 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. |
/mdb:MI_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:status/mri:MD_ProgressCode
with codeList and codeListValue attributes
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | Changes would be tracked here | 1.9.0
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 808/1724/182018 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |