You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


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, scientific programs, etc. This element may also cover a long term project that continuously creates new data sets. 

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 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/static/kms/projects/projects.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 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 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 in 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 completely 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 completely optional.

Examples:

ShortName: ISLSCP II

LongName: International Satellite Land Surface Climatology Project II

Campaign: Carbon

Campaign: BOREAS

StartDate: 


Element Specification

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

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CommonProject/ShortNameStringProject Short_Name Keywords

1 - 40 characters

KMS controlled

Yes, if applicable1Providing a Project is optional. If provided, the Short Name is required.
UMM-CommonProject/LongNameStringProject Long_Name Keywords

1 - 300 characters

KMS controlled

No0..1
UMM-CommonProject/CampaignsStringn/a1 - 80 charactersNo0..*Multiple Campaigns may be listed under each Project.
UMM-CommonProject/StartDatedateTimen/an/aNo0..1
UMM-CommonProject/EndDatedateTimen/an/aNo0..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.




ARC Priority Matrix

Priority CategorizationJustification

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

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.

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 also 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

DIF 9

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


DIF 10

SpecificationPathTypeConstraintsRequired in DIF 10?CardinalityNotes
DIF 10/DIF/Temporal_Coverage/Time_TypeString
No0..1


DIF 10/DIF/Temporal_Coverage/Date_TypeString
No0..1
DIF 10/DIF/Temporal_Coverage/Temporal_Range_TypeString
No0..1
DIF 10/DIF/Temporal_Coverage/Precision_Of_SecondsInteger
No0..1The precision (position in number of places to right of decimal point) of seconds used in measurement.
DIF 10/DIF/Temporal_Coverage/Ends_At_Present_FlagBoolean
No0..1Recommend providing a value of "true" for active data sets.

Choice of:

(1) Single_DateTime

If Single_DateTime is selected, the cardinality is 1..*

ModelElementTypeUsable Valid ValuesRequired?CardinalityNotes
DIF 10/DIF/Temporal_Coverage/Single_DateTime

Date

dateTime

Enumeration

unknown

present

unbounded

future

Not provided

Yes, if applicable1

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.

(2) Range_DateTime

If Range_DateTime is selected, the cardinality is 1..*

ModelElementTypeUsable Valid ValuesRequired?CardinalityNotes
DIF 10/DIF/Temporal_Coverage/Range_DateTime/Beginning_Date_Time

Date

dateTime

Enumeration

unknown

present

unbounded

future

Not provided

Yes, if applicable1

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

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

(3) Periodic_DateTime

If Periodic_DateTime is selected, the cardinality is 1..*

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/NameStringn/a
Yes, if applicable1Dates 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 applicable1

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 applicable1

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_UnitEnumeration

DAY

MONTH

YEAR


Yes, if applicable1
DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/Duration_ValueIntegern/a
Yes, if applicable1
DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/Period_Cycle_Duration_UnitEnumeration

DAY

MONTH

YEAR


Yes, if applicable1
DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/Period_Cycle_Duration_ValueIntegern/a
Yes, if applicable1

Value needed for translations:

The following value is used to translate older versions of DIF (e.g. DIF 9, DIF 10.1) to the most current version of DIF (DIF10.3) if no valid value is provided in the older version of the record.

Not provided - This value is auto-populated to any DateTime fields if no valid value is provided in the DateTime field at time of conversion to DIF 10.3. This value should not be used by metadata providers.


Enumeration Mapping

DIF 10

Translation

Direction

UMM
DAY↔DAY
MONTH↔MONTH
YEAR↔YEAR
unknown→
present

unbounded

future

Not provided

Example Mapping

DIF 10

<Temporal_Coverage>
  <Single_DateTime>2018-08-20T14:13:22Z</Single_DateTime>
</Temporal_Coverage>


<Temporal_Coverage>
  <Ends_At_Present_Flag>true</Ends_At_Present_Flag>
  <Range_DateTime>
    <Beginning_Date_Time>1980-01-01</Beginning_Date_Time>
  </Range_DateTime>
</Temporal_Coverage>


<Temporal_Coverage>
  <Range_DateTime>
    <Beginning_Date_Time>1980-01-01T00:00:00Z</Beginning_Date_Time>
    <Ending_Date_Time>2010-12-31T23:59:59Z</Ending_Date_Time>
  </Range_DateTime>
</Temporal_Coverage>


<Temporal_Coverage>
  <Periodic_DateTime>
    <Name>Winter_FieldCampaign</Name>
    <Start_Date>2013-12-01T00:00:00Z</Start_Date>
    <End_Date>2017-02-28T23:59:59Z</End_Date>
    <Duration_Unit>MONTH</Duration_Unit>
    <Duration_Value>3</Duration_Value>
    <Period_Cycle_Duration_Unit>YEAR</Period_Cycle_Duration_Unit>
    <Period_Cycle_Duration_Value>1</Period_Cycle_Duration_Value>
  </Periodic_DateTime>
</Temporal_Coverage>

UMM

TemporalExtents: [
  {
    SingleDateTimes: [
      {
        SingleDateTime: "2018-08-20T14:13:22Z"
      }
    ]
  }
]


TemporalExtents: [
  {
    EndsAtPresentFlag: true,
    RangeDateTimes: [
      {
        BeginningDateTime: "1980-01-01",
      }
    ]
  }
]


TemporalExtents: [
  {
    RangeDateTimes: [
      {
        BeginningDateTime: "1980-01-01T00:00:00Z",
        EndingDateTime: "2010-12-31T23:59:59Z"
      }
    ]
  }
]


TemporalExtents: [
  {
    PeriodicDateTimes: [
      {
        Name: "Winter_FieldCampaign",
        StartDate: "2013-12-01T00:00:00Z",
        EndDate: "2017-02-28T23:59:59Z",
        DurationUnit: "MONTH",
        DurationValue: "3",
        PeriodCycleDurationUnit: "YEAR",
        PeriodCycleDurationValue: "1"
      }
    ]
  }
]

ECHO 10

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10/Collection/Temporal/TimeTypeString1 - 80 charactersNo0..1

The time system which the values found in temporal subclasses. For example:

ECHO 10/Collection/Temporal/DateTypeString1 - 80 charactersNo0..1

The type of date represented by the value in the date attributes of the temporal subclasses. For example:

ECHO 10/Collection/Temporal/TemporalRangeTypeString1 - 80 charactersNo0..1

Tells the system how temporal coverage is
specified for the collection. For example: SingleDateTime, RangeDateTime, PeriodicDateTime

ECHO 10/Collection/Temporal/PrecisionOfSecondsIntegern/aNo0..1

The precision (position in number of
places to right of decimal point) of seconds used in measurement.

ECHO 10/Collection/Temporal/EndsAtPresentFlagBooleann/aNo0..1It is recommended that a value of "true" be provided for active data sets.

Choice of:

(1) SingleDateTime

If SingleDateTime is selected, the cardinality is 1..*

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10/Collection/Temporal/SingleDateTimedateTimen/aYes, if applicable0..1

(2) RangeDateTime

If RangeDateTime is selected, the cardinality is 1..*

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10/Collection/Temporal/RangeDateTime/BeginningDateTimedateTimen/aYes, if applicable1
ECHO 10/Collection/Temporal/RangeDateTime/EndingDateTimedateTimen/aNo0..1An EndingDateTime must be provided if the collection is complete. No EndingDateTime is necessary if the collection is active.

(3) PeriodicDateTime

If PeriodicDateTime is selected, the cardinality is 1..*

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10/Collection/Temporal/PeriodicDateTime/NameStringn/a1 - 30 charactersYes, if applicable1
ECHO 10/Collection/Temporal/PeriodicDateTime/StartDatedateTimen/an/aYes, if applicable1
ECHO 10/Collection/Temporal/PeriodicDateTime/EndDatedateTimen/an/aYes, if applicable1
ECHO 10/Collection/Temporal/PeriodicDateTime/DurationUnitEnumeration

DAY

MONTH

YEAR

n/aYes, if applicable1
ECHO 10/Collection/Temporal/PeriodicDateTime/DurationValueIntegern/an/aYes, if applicable1
ECHO 10/Collection/Temporal/PeriodicDateTime/PeriodCycleDurationUnitEnumeration

DAY

MONTH

YEAR

n/aYes, if applicable1
ECHO 10/Collection/Temporal/PeriodicDateTime/PeriodCycleDurationValueIntegern/an/aYes, if applicable1

Enumeration Mapping

ECHO 10

Translation

Direction

UMM
DAY↔DAY
MONTH↔MONTH
YEAR↔YEAR

Example Mapping

ECHO 10

<Temporal>
  <SingleDateTime>2018-08-20T14:13:22Z</SingleDateTime>
</Temporal>


<Temporal>
  <EndsAtPresentFlag>true</EndsAtPresentFlag>
  <RangeDateTime>
    <BeginningDateTime>1980-01-01</BeginningDateTime>
  </RangeDateTime>
</Temporal>


<Temporal>
  <RangeDateTime>
    <BeginningDateTime>1980-01-01T00:00:00Z</BeginningDateTime>
    <EndingDateTime>2010-12-31T23:59:59Z</EndingDateTime>
  </RangeDateTime>>
</Temporal>


<Temporal>
  <PeriodicDateTime>
    <Name>Winter_FieldCampaign</Name>
    <StartDate>2013-12-01T00:00:00Z</StartDate>
    <EndDate>2017-02-28T23:59:59Z</EndDate>
    <DurationUnit>MONTH</DurationUnit>
    <DurationValue>3</DurationValue>
    <PeriodCycleDurationUnit>YEAR</PeriodCycleDurationUnit>
    <PeriodCycleDurationValue>1</PeriodCycleDurationValue>
  </PeriodicDateTime>
</Temporal>

UMM

TemporalExtents: [
  {
    SingleDateTimes: [
      {
        SingleDateTime: "2018-08-20T14:13:22Z"
      }
    ]
  }
]


TemporalExtents: [
  {
    EndsAtPresentFlag: true,
    RangeDateTimes: [
      {
        BeginningDateTime: "1980-01-01",
      }
    ]
  }
]


TemporalExtents: [
  {
    RangeDateTimes: [
      {
        BeginningDateTime: "1980-01-01T00:00:00Z",
        EndingDateTime: "2010-12-31T23:59:59Z"
      }
    ]
  }
]


TemporalExtents: [
  {
    PeriodicDateTimes: [
      {
        Name: "Winter_FieldCampaign",
        StartDate: "2013-12-01T00:00:00Z",
        EndDate: "2017-02-28T23:59:59Z",
        DurationUnit: "MONTH",
        DurationValue: "3",
        PeriodCycleDurationUnit: "YEAR",
        PeriodCycleDurationValue: "1"
      }
    ]
  }
]



ISO 19115-2 MENDS

SpecificationPathTypeNotes
ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:status/gmd:MD_ProgressCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_ProgressCode" codeListValue=StringProgressCode has code values of completed, historicalArchive, obsolete, onGoing, planned, required, underDevelopment. gmd:status is not required. Any string can be substituted as well. Since ISO supports multiple statuses for a collection/series, the CMR translates only the first one to UMM.

Enumeration/Code List Mapping

ISO MENDS

Translation

Direction

UMM
planned↔PLANNED
underDevelopment→PLANNED
onGoing↔ACTIVE
completed↔COMPLETE
historicalArchive→COMPLETE
obsolete→COMPLETE

NOT APPLICABLE

a string is used instead

of the defined codes.

The codeList=”” and

codeListValue = “”

↔NOT APPLICABLE
Blank or doesn’t exist→NOT PROVIDED
Any other value→NOT PROVIDED
Don’t translate←NOT PROVIDED

Example Mapping

ISO 19115-2 MENDS

<gmd:status>
    <gmd:MD_ProgressCode codeList=
        "https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_ProgressCode"
        codeListValue="completed">completed</gmd:MD_ProgressCode>
</gmd:status>

UMM

"CollectionProgress" : "COMPLETE",



ISO 19115-2 SMAP

SpecificationPathTypeNotes
ISO 19115-2 SMAP/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:status/gmd:MD_ProgressCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_ProgressCode" codeListValue=StringProgressCode has code values of completed, historicalArchive, obsolete, onGoing, planned, required, underDevelopment. gmd:status is not required. Any string can be substituted as well. Since ISO supports multiple statuses for a collection/series, the CMR translates only the first one to UMM.

Enumeration/Code List Mapping

ISO SMAP

Translation

Direction

UMM
planned↔PLANNED
underDevelopment→PLANNED
onGoing↔ACTIVE
completed↔COMPLETE
historicalArchive→COMPLETE
obsolete→COMPLETE

NOT APPLICABLE

a string is used instead

of the defined codes.

The codeList=”” and

codeListValue = “”

↔NOT APPLICABLE
Blank or doesn’t exist→NOT PROVIDED
Any other value→NOT PROVIDED
Don’t translate←NOT PROVIDED

Example Mapping

ISO 19115-2 SMAP

<gmd:status>
    <gmd:MD_ProgressCode codeList=
         "https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_ProgressCode"
         codeListValue="completed">completed</gmd:MD_ProgressCode>
</gmd:status>

UMM

"CollectionProgress" : "COMPLETE",



UMM Migration


UMM Version 1.9.0

Translation

Direction

UMM Version 1.10.0
PLANNED↔PLANNED
IN WORK↔ACTIVE
COMPLETE↔COMPLETE
NOT APPLICABLE↔NOT APPLICABLE
NOT PROVIDED↔NOT PROVIDED
Any other value→NOT PROVIDED

Future Mappings

ISO 19115-1

SpecificationPathTypeNotes
ISO 19115-1

/mdb:MI_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:status/mri:MD_ProgressCode

with codeList and codeListValue attributes

StringProgressCode has code values of completed, historicalArchive, obsolete, onGoing, planned, required, underDevelopment. gmd:status is not required. Any string can be substituted as well. Since ISO supports multiple statuses for a collection/series, the CMR translates only the first one to UMM.

ISO 19115-1

<mri:MD_DataIdentification>
  <mri:citation>
    ...
    <mri:status>
      <mri:MD_ProgressCode codeList="{codeListLocation}#MD_ProgressCode"
        codeListValue="onGoing">onGoing</mri:MD_ProgressCode>
    </mri:status>
    ...
  </mri:citation>
</mri:MD_DataIdentification>

UMM

"CollectionProgress" : "ACTIVE",


History

UMM Versioning

VersionDateWhat Changed
1.10.0
Changes would be tracked here
1.9.0

ARC Documentation

VersionDateWhat ChangedAuthor
1.08/17/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space
Kaylin Bugbee



  • No labels