Versions Compared

Old Version 9

changes.mady.by.user Patrick Staton

Saved on

compared with

New Version Current

changes.mady.by.user Jenny Wood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents
stylecircle

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


Best Practices

Project names are important for data search and discovery. In order to provide a consistent search experience, project Project names are controlled by GCMD vocabulary maintained in the Keyword Management System (KMS). This is especially important for faceted searches by project Project name in the Earthdata Search Client. A list of valid project Project keywords can be found here: https://gcmdservicesgcmd.gsfcearthdata.nasa.gov/statickms/kmsconcepts/projectsconcept_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 projectProject. 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 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 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: 1986-01-01

EndDate: 1995-12-31


ShortName: MEaSUREs

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

Campaign: NVAP-M StartDate: 


Element Specification

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

ModelElementType
Usable Valid Values
ConstraintsRequired?CardinalityNotes
UMM-CommonProject/ShortNameString

1 - 40 characters

Project Short_Name Keywords

1 - 40 characters

KMS controlled

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

1 - 300 characters

KMS controlled

Project Long_Name Keyword

No0..1
UMM-CommonProject/CampaignsString
n/a
1 - 80 charactersNo0..*Multiple Campaigns may be listed under each Project.
UMM-CommonProject/StartDatedateTime
n/a
n/aNo0..1
UMM-CommonProject/EndDatedateTimen/a
n/a
No0..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-viewertrue
autofittrue
nameCopy of Wiki Page Metadata Evaluation Workflow-1939-672ea43a
width1102
id98e5dc28-3252-4209-953f-66f1378e1cf4
alignLeft
height299

Please see the expandable sections below for flowchart details.


Expand
titleGCMD Metadata QA/QC
Expand
titleCMR Validation
  • 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
titleCMR Validation
  • The specific project must be unique within the collection.
  • The project short name must match with what is in the KMS.
  • 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.

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

    Expand
    titleARC Metadata QA/QC

    ARC Priority Matrix

    Priority CategorizationJustification

    Red = High Priority Finding

    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 (hierarchies cannot be mixed and matched).
    • The Project and/or Campaign listed is incorrect for the dataset.
    • The Start Date and/or End Date are incorrect for the Project.

    Yellow = Medium Priority Finding

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

    Blue = Low Priority Finding

    Not Applicable

    Green = No Findings/Issues

    The element is provided and follows all applicable criteria specified in the best practices section above.

    ARC Automated Checks

    ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. 

    Expand
    titleARC Metadata QA/QC

    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.

    Dialect Mappings

    Expand
    titleDIF 9

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


    Expand
    titleDIF 10

    DIF 10

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

    UMM-C ElementDIF 10
    		Specification
    PathTypeConstraintsRequired in DIF 10?CardinalityNotes
    DIF 10
    Project/ShortNameProject/
    DIF/Temporal_Coverage/Time_Type
    Short_NameString
    No0..1DIF 10/DIF/Temporal_Coverage/Date_TypeString
    Project Short_Name KeywordsYes, if applicable1

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

    Project/LongName
    		Project/Long_NameStringProject Long_Name KeywordsNo0..1
    DIF 10

    Project/Campaigns
    /DIF/Temporal_Coverage/Temporal_Range_Type
    Project/CampaignString
    		No0..
    1DIF 10/DIF/Temporal_Coverage/Precision_Of_SecondsInteger
    *Multiple Campaigns may be listed under each Project.
    Project/StartDate
    		Project/Start_DateDate
    		No0..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_FlagBoolean

    Project/EndDate
    		Project/End_DateDate
    		No0..1
    Recommend 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?CardinalityNotesDIF 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?CardinalityNotesDIF 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?CardinalityNotesDIF 10/DIF/Temporal_Coverage/Periodic_DateTime/NameStringn/aYes, 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.



    Example Mapping

    Section
    Column
    width50%

    DIF 10

    No Format
    <Project>
  <Short_Name>OIB</Short_Name>
  <Long_Name>Operation Ice Bridge</Long_Name>
  <Campaign>2009_AN_NASA</Campaign>
  <Campaign>2009_GR_NASA</Campaign>
  <Campaign>2010_AN_NASA</Campaign>
  <Campaign>2010_GR_NASA</Campaign>
  <Start_Date>2009-01-01</Start_Date>
  <End_Date>2011-01-01</End_Date>
</Project>
    Column
    width50%

    UMM

    No Format
    "Projects": [
  {
    "ShortName": "OIB",
    "LongName": "Operation Ice Bridge",
    "Campaigns": ["2009_AN_NASA", "2009_GR_NASA", "2010_AN_NASA", "2010_GR_NASA"],
    "StartDate": "2009-01-01T00:00:00Z",
    "EndDate": "2011-01-01T00:00:00Z"  
  }
]
    Expand
    titleECHO 10

    ECHO 10

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

    UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?CardinalityNotes
    Project/ShortNameCampaigns/Campaign/ShortNameString

    1 - 40 characters

    Project Short_Name Keywords

    		Yes, if applicable1

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

    Project/LongName
    		Campaigns/Campaign/LongNameString

    1 - 1024 characters

    Project Long_Name Keywords

    		No0..1


    Project/StartDate
    		Campaigns/Campaign/StartDatedateTimen/aNo0..1


    Project/EndDate
    		Campaigns/Campaign/EndDatedateTimen/aNo0..1



    Example     Mapping

    Section
    Column
    width50%

    ECHO 10

    No Format
    <Campaigns>
  <Campaign>
    <ShortName>OIB</ShortName>
    <LongName>Operation Ice Bridge</LongName>
    <StartDate>2009-01-01T00:00:00.000Z</StartDate>
    <EndDate>2011-01-01T00:00:00.000Z</EndDate>
  </Campaign>
</Campaigns>
    Column
    width50%

    UMM

    No Format
    "Projects": [
  {
    "ShortName": "OIB",
    "LongName": "Operation Ice Bridge",
    "StartDate": "2009-01-01T00:00:00Z",
    "EndDate": "2011-01-01T00:00:00Z"  
  }
]

    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

    Not provided
    Expand
    titleISO 19115-2 MENDS

    ISO 19115-2 MENDS

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

    UMM-C Element

    ISO 19115-2 MENDS Path

    		TypeNotes
    Project/ShortName

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

    Project/LongName

    /gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/

    gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString

    		StringMaps 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

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

    Project/StartDate

    /gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/

    gmi:description/gco:CharacterString = StartDate:

    		StringMaps 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

    /gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/

    gmi:description/gco:CharacterString = EndDate:

    		StringMaps 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.
    		DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/Duration_UnitEnumeration

    DAY

    MONTH

    YEAR

    		Yes, if applicable1DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/Duration_ValueIntegern/aYes, if applicable1DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/Period_Cycle_Duration_UnitEnumeration

    DAY

    MONTH

    YEAR

    		Yes, if applicable1DIF 10/DIF/Temporal_Coverage/Periodic_DateTime/Period_Cycle_Duration_ValueIntegern/aYes, if applicable1
    DIF 10

    Translation

    Direction

    		UMM
    DAY↔DAY
    MONTH↔MONTH
    YEAR↔YEAR
    unknown→presentunboundedfuture


    Example Mapping

    Section
    Column
    width50%

    DIF 10ISO 19115-2 MENDS

    No Format
    <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><gmi:MI_Metadata>
...
  <gmi:acquisitionInformation>
    <gmi:MI_AcquisitionInformation>
    <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>
    Column
    width50%

    UMM

    No Format
    TemporalExtents: [
  {
    SingleDateTimes: [
      {  ...
      <gmi:operation>
        <gmi:MI_Operation>
          <gmi:description>
            </gco:CharacterString>StartDate: 2009-01-01T00:00:00Z  EndDate: 2011-01-01T00:00:00Z</gco:CharacterString>
          </gmi:description>
          ...
          <gmi:identifier>
            <gmd:MD_Identifier>
        SingleDateTime: "2018-08-20T14:13:22Z"
     <gmd:code>
 }
    ]
  }
]


TemporalExtents: [
  {
    EndsAtPresentFlag: true,
    RangeDateTimes: [ <gco:CharacterString>OIB</gco:CharacterString>
      {
        BeginningDateTime: "1980-01-01",
</gmd:code>
        }
    ]
  }
]


TemporalExtents: [<gmd:codeSpace>
  {
    RangeDateTimes: [
      {
   <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
     BeginningDateTime: "1980-01-01T00:00:00Z",
        EndingDateTime: "2010-12-31T23:59:59Z"</gmd:codeSpace>
      }
    ]
  }
]


TemporalExtents: [
  {<gmd:description>
    PeriodicDateTimes: [
      {
     <gco:CharacterString>Operation Ice  Name: "Winter_FieldCampaign",Bridge</gco:CharacterString>
        StartDate: "2013-12-01T00:00:00Z",
     </gmd:description>
   EndDate: "2017-02-28T23:59:59Z",
        DurationUnit: "MONTH",
</gmd:MD_Identifier>
          </gmi:identifier>
         DurationValue <gmi: "3",
childOperation>
            <gmi:MI_Operation>
            PeriodCycleDurationUnit  <gmi:identifier>
 "YEAR",
        PeriodCycleDurationValue: "1"
      }
<gmd:MD_Identifier>
      ]
  }
]
    Expand
    titleECHO 10

    ECHO 10

                <gmd:code>
                    <gco:CharacterString>2009_AN_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>
            </gmi:MI_Operation>
          </gmi:childOperation>
          <gmi:childOperation>
            <gmi:MI_Operation>
              <gmi:identifier>
                <gmd:MD_Identifier>
                  <gmd:code>
                    <gco:CharacterString>2009_GR_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>
            </gmi:MI_Operation>
          </gmi:childOperation>
          <gmi:childOperation>
            <gmi:MI_Operation>
              <gmi:identifier>
                <gmd:MD_Identifier>
                  <gmd:code>
                    <gco:CharacterString>2010_AN_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>
            </gmi:MI_Operation>
          </gmi:childOperation>
          <gmi:childOperation>
            <gmi:MI_Operation>
              <gmi:identifier>
                <gmd:MD_Identifier>
                  <gmd:code>
                    <gco:CharacterString>2010_GR_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>
            </gmi:MI_Operation>
          </gmi:childOperation>
        </gmi:MI_Operation>
      </gmi:operation>
      ...
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
...
</gmi:MI_Metadata>
    Column
    width50%

    UMM

    No Format
    "Projects": [
  {
    "ShortName": "OIB",
    "LongName": "Operation Ice Bridge",
    "Campaigns": ["2009_AN_NASA", "2009_GR_NASA", "2010_AN_NASA", "2010_GR_NASA"],
    "StartDate": "2009-01-01T00:00:00Z",
    "EndDate": "2011-01-01T00:00:00Z"  
  }
]

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

    Enumeration Mapping

    Example Mapping

    Expand
    titleISO 19115-2 SMAP

    ISO 19115-2 SMAP

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

    UMM-C Element

    ISO 19115-2 SMAP Path

    		TypeNotes
    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

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

    		StringMaps 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
    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.
    SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
    ECHO 10/Collection/Temporal/SingleDateTimedateTimen/aYes, if applicable0..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.
    SpecificationPathTypeUsable Valid ValuesConstraintsRequired in ECHO10?CardinalityNotes
    ECHO 10/Collection/Temporal/PeriodicDateTime/NameStringn/a1 - 30 charactersYes, if applicable1ECHO 10/Collection/Temporal/PeriodicDateTime/StartDatedateTimen/an/aYes, if applicable1ECHO 10/Collection/Temporal/PeriodicDateTime/EndDatedateTimen/an/aYes, if applicable1ECHO 10/Collection/Temporal/PeriodicDateTime/DurationUnitEnumeration

    DAY

    MONTH

    YEAR

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

    DAY

    MONTH

    YEAR

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

    Translation

    Direction

    		UMM
    DAY↔DAY
    MONTH↔MONTH
    YEAR↔YEAR
    Section
    Column
    width50%

    ECHO 10

    No Format
    <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>
    Column
    width50%

    UMM

    No Format
    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"
      }
    ]
  }
]
    Expand
    titleISO 19115-2 MENDS

    ISO 19115-2 MENDS

    SpecificationPathTypeNotesISO 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

    UMMplanned↔PLANNEDunderDevelopment→PLANNEDonGoing↔ACTIVEcompleted↔COMPLETEhistoricalArchive→COMPLETEobsolete→COMPLETE

    NOT APPLICABLE

    a string is used instead

    of the defined codes.

    The codeList=”” and

    codeListValue = “”

    ↔NOT APPLICABLEBlank or doesn’t exist→NOT PROVIDEDAny other value→NOT PROVIDEDDon’t translate←NOT PROVIDED

    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 MENDS

    No Format
    <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>
    Column
    width50%

    UMM

    No Format
    "CollectionProgress" : "COMPLETE",
    Expand
    titleISO 19115-2 SMAP

    ISO 19115-2 SMAP

    SpecificationPathTypeNotesISO 19115-2 SMAP

    /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/

    gmd

    gmi:

    identificationInfo

    acquisitionInformation/

    gmd

    gmi:

    MD

    MI_

    DataIdentification

    AcquisitionInformation/

    gmd

    gmi:

    status

    operation/

    gmd

    gmi:

    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

    UMMplanned↔PLANNEDunderDevelopment→PLANNEDonGoing↔ACTIVEcompleted↔COMPLETEhistoricalArchive→COMPLETEobsolete→COMPLETE

    NOT APPLICABLE

    a string is used instead

    of the defined codes.

    The codeList=”” and

    codeListValue = “”

    ↔NOT APPLICABLEBlank or doesn’t exist→NOT PROVIDEDAny other value→NOT PROVIDEDDon’t translate←NOT PROVIDED

    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 SMAP

    No Format
    <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>
    Column
    width50%

    UMM

    No Format
    "CollectionProgress" : "COMPLETE",

    UMM Migration

    UMM Version 1.9.0

    Translation

    Direction

    UMM Version 1.10.0PLANNED↔PLANNEDIN WORK↔ACTIVECOMPLETE↔COMPLETENOT APPLICABLE↔NOT APPLICABLENOT PROVIDED↔NOT PROVIDEDAny other value→NOT PROVIDED

    Future Mappings

    Expand
    titleISO 19115-1

    ISO 19115-1

    SpecificationPathTypeNotesISO 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.
    Section
    Column
    width50%

    ISO 19115-1

    No Format
    <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>
    Column
    width50%

    UMM

    No Format
    "CollectionProgress" : "ACTIVE",

    MI_Operation/gmi:description/gco:CharacterString = EndDate:

    		StringMaps 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
    width50%

    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:description>
            </gco:CharacterString>StartDate: 2009-01-01T00:00:00Z  EndDate: 2011-01-01T00:00:00Z</gco:CharacterString>
          </gmi:description>
          ...
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>OIB</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>Operation Ice Bridge</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
          <gmi:childOperation>
            <gmi:MI_Operation>
              <gmi:identifier>
                <gmd:MD_Identifier>
                  <gmd:code>
                    <gco:CharacterString>2009_AN_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>

            </gmi:MI_Operation>
          </gmi:childOperation>
          <gmi:childOperation>
            <gmi:MI_Operation>
              <gmi:identifier>
                <gmd:MD_Identifier>
                  <gmd:code>
                    <gco:CharacterString>2009_GR_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>
            </gmi:MI_Operation>
          </gmi:childOperation>
          <gmi:childOperation>
            <gmi:MI_Operation>
              <gmi:identifier>
                <gmd:MD_Identifier>
                  <gmd:code>
                    <gco:CharacterString>2010_AN_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>
            </gmi:MI_Operation>
          </gmi:childOperation>
          <gmi:childOperation>
            <gmi:MI_Operation>
              <gmi:identifier>
                <gmd:MD_Identifier>
                  <gmd:code>
                    <gco:CharacterString>2010_GR_NASA</gco:CharacterString>
                  </gmd:code>
                  <gmd:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.campaignshortname</gco:CharacterString>
                  </gmd:codeSpace>
                </gmd:MD_Identifier>
              </gmi:identifier>
            </gmi:MI_Operation>
          </gmi:childOperation>
        </gmi:MI_Operation>
      </gmi:operation>
      ...
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
...
</gmi:MI_Metadata>
</gmd:seriesMetadata>
</gmd:DS_Series>
    Column
    width50%

    UMM

    No Format
    "Projects": [
  {
    "ShortName": "OIB",
    "LongName": "Operation Ice Bridge",
    "Campaigns": ["2009_AN_NASA", "2009_GR_NASA", "2010_AN_NASA", "2010_GR_NASA"],
    "StartDate": "2009-01-01T00:00:00Z",
    "EndDate": "2011-01-01T00:00:00Z"  
  }
]

    UMM Migration

    None

    Excerpt
    hiddentrue

    Future Mappings

    Expand
    titleISO 19115-1

    ISO 19115-1

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

    UMM-C Element

    ISO 19115-1 Path

    		TypeNotes
    Project/ShortName

    /mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/

    mac:operation/mac:MI_Operation/mac:identifier/mcc:MD_Identifier/mcc:code/gco:CharacterString

    and

    /mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/

    mac:identifier/mcc:MD_Identifier/mcc:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.projectshortname

    and (CMR write only)
    /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/

    mri:MD_Keywords/mri:keyword/gco:CharacterString
    with
    /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:descriptiveKeywords/

    mri:MD_Keywords/mri:keyword/mri:type/mri:MD_KeywordTypeCode codeList = "http://www.ngdc.noaa.gov/metadata/published/xsd/schema/resources/Codelist/gmxCodelists.xml#MD_KeywordTypeCode" codeListValue = "project"

    		String

    A list of valid campaign 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

    /mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/

    mac:operation/mac:MI_Operation/mac:identifier/mcc:MD_Identifier/mcc:description/gco:CharacterString

    		StringA 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

    /mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/

    mac:operation/mac:MI_Operation/mac:childOperation/mac:MI_Operation/mac:identifier/

    mcc:MD_Identifier/mcc:code/gco:CharacterString

    with

    /mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/

    mac:operation/mac:MI_Operation/mac:childOperation/mac:MI_Operation/mac:identifier/

    mcc:MD_Identifier/mcc:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.campaignshortname

    		String

    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

    /mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/

    mac:operation/mac:MI_Operation/mac:description/gco:CharacterString StartDate:

    		StringThe 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

    /mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/

    mac:operation/mac:MI_Operation/mac:description/gco:CharacterString EndDate:

    		StringThe 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.
    Section
    Column
    width50%

    ISO 19115-1

    No Format
    <mdb:MD_Metadata>
  ...
  <mdb:acquisitionInformation>
    <mac:MI_AcquisitionInformation>
      ...
      <mac:operation>
        <mac:MI_Operation>
          <mac:description>
            <gco:CharacterString>StartDate: 2009-01-01T00:00:00Z EndDate: 2011-01-01T00:00:00Z</gco:CharacterString>
          </mac:description>
          <mac:identifier>
            <mcc:MD_Identifier>
              <mcc:code>
                <gco:CharacterString>GCPEx</gco:CharacterString>
              </mcc:code>
              <mcc:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
              </mcc:codeSpace>
              <mcc:description>
                <gco:CharacterString>GPM Cold Season Precipitation Experiment</gco:CharacterString>
              </mcc:description>
            </mcc:MD_Identifier>
          </mac:identifier>
          <mac:childOperation>
            <mac:MI_Operation>
              <mac:identifier>
                <mcc:MD_Identifier>
                  <mcc:code>
                    <gco:CharacterString>2009_AN_NASA</gco:CharacterString>
                  </mcc:code>
                  <mcc:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
                  </mcc:codeSpace>
                </mcc:MD_Identifier>
              </mac:identifier>
            </mac:MI_Operation>
          </mac:childOperation>
          <mac:childOperation>
            <mac:MI_Operation>
              <mac:identifier>
                <mcc:MD_Identifier>
                  <mcc:code>
                    <gco:CharacterString>2009_GR_NASA</gco:CharacterString>
                  </mcc:code>
                  <mcc:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
                  </mcc:codeSpace>
                </mcc:MD_Identifier>
              </mac:identifier>
            </mac:MI_Operation>
          </mac:childOperation>
          <mac:childOperation>
            <mac:MI_Operation>
              <mac:identifier>
                <mcc:MD_Identifier>
                  <mcc:code>
                    <gco:CharacterString>2010_AN_NASA</gco:CharacterString>
                  </mcc:code>
                  <mcc:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
                  </mcc:codeSpace>
                </mcc:MD_Identifier>
              </mac:identifier>
            </mac:MI_Operation>
          </mac:childOperation>
          <mac:childOperation>
            <mac:MI_Operation>
              <mac:identifier>
                <mcc:MD_Identifier>
                  <mcc:code>
                    <gco:CharacterString>2010_GR_NASA</gco:CharacterString>
                  </mcc:code>
                  <mcc:codeSpace>
                    <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
                  </mcc:codeSpace>
                </mcc:MD_Identifier>
              </mac:identifier>
            </mac:MI_Operation>
          </mac:childOperation>
        </mac:MI_Operation>
      </mac:operation>
    </mac:MI_AcquisitionInformation>
  </mdb:acquisitionInformation>
</mdb:MD_Metadata>
    Column
    width50%

    UMM

    No Format
    "Projects": [
  {
    "ShortName": "OIB",
    "LongName": "Operation Ice Bridge",
    "Campaigns": ["2009_AN_NASA", "2009_GR_NASA", "2010_AN_NASA", "2010_GR_NASA"],
    "StartDate": "2009-01-01T00:00:00Z",
    "EndDate": "2011-01-01T00:00:00Z"  
  }
]

    History

    UMM Versioning

    VersionDateWhat Changed
    1.15.512/3/2020The description of this element now includes text about the controlled vocabulary for project names coming from KMS.
    1.15.49/18/2020No changes were made for Project during the transition from version 1.15.3 to 1.15.4
    1.15.37/1/2020No changes were made for Project during the transition from version 1.15.2 to 1.15.3
    1.15.25/20/2020No changes were made for Project during the transition from version 1.15.1 to 1.15.2
    1.15.13/25/2020No changes were made for Project during the transition from version 1.15.0 to 1.15.1
    1.15.02/26/2020No changes were made for Project during the transition from version 1.14.0 to 1.15.0
    1.14.010/21/2019No changes were made for Project during the transition from version 1.13.0 to 1.14.0
    1.13.004/11/2019No changes were made for Project during the transition from version 1.12.0 to 1.13.0
    1.12.001/22/2019No changes were made for Project during the transition from version 1.11.0 to 1.12.0.
    1.11.011/28/2018No 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.

    History

    UMM Versioning

    1.9.0
    VersionDateWhat Changed
    1.10.0Changes would be tracked here

    ARC Documentation

    VersionDateWhat ChangedAuthor
    1.0808/1724/182018Recommendations/priority matrix transferred from internal ARC documentation to wiki space

    Kaylin Bugbee