Page History

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

StartDate: 1986-01-01

EndDate: 1995-12-31

ShortName: MEaSUREs

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

Campaign:  NVAP-M 

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.

Dialect Mappings

(2) Range_DateTime

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

(3) Periodic_DateTime

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

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

Example Mapping

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

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

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

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

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

Enumeration/Code List Mapping

Translation

Direction

NOT APPLICABLE

a string is used instead

of the defined codes.

The codeList=”” and

codeListValue = “”

Example Mapping

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

"CollectionProgress" : "COMPLETE",

ISO 19115-2 SMAP

Enumeration/Code List Mapping

Translation

Direction

NOT APPLICABLE

a string is used instead

of the defined codes.

The codeList=”” and

codeListValue = “”

Example Mapping

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

"CollectionProgress" : "COMPLETE",

UMM Migration

Translation

Direction

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

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

UMM Migration

Future Mappings

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

Future Mappings

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

"CollectionProgress" : "ACTIVE",

History

UMM Versioning

ARC Documentation