Access Constraints

Element Description

Note: this page is a draft/ work in progress

Best Practices

Examples:

Element Specification

Providing Access Constraints is optional. (Cardinality 0..1*)

Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality	Notes
UMM-Common	Access_Constraints	String	n/a	1 - 4000 characters	Yes, if provided	1
UMM-Common	AccessConstraints/Value	Integer	n/a	1 - 255 characters	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).

[]

Please see the expandable sections below for flowchart details.

GCMD Metadata QA/QC

CMR Validation

ARC Metadata QA/QC

ARC Priority Matrix

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.

ARC Automated Checks

Description
- If a value is not provided, return is: "np"
- If the provided value is
Value
- If a value is not provided, return is: "np"

Dialect Mappings

DIF 9

DIF 9

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

DIF 10

DIF 10

Providing Access Constraints is optional. (Cardinality 0..1*)

Specification	Path	Type	Usable Valid Values	Constraints	Required in DIF 10?	Cardinality
DIF 10	AccessConstraints/Description	String	n/a	1 - 4000 characters	No	1
DIF 10	AccessConstraints/Access_Control	Integer	n/a	0 - 255 characters	Yes, if provided	0..1
DIF 10	AccessConstraints/Access_Control_Description	String	n/a	1 - 4000 characters	No	0..1

Example Mapping

DIF 10

<Access_Constraints> None </Access_Constraints>

UMM

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

ECHO 10

ECHO 10

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

Specification

Path

Type

Usable Valid Values

Constraints

Required in ECHO10?

Cardinality

Notes

ECHO 10

/Collection/Campaigns/Campaign/ShortName

String

Project Short_Name Keywords

1 - 40 characters

KMS controlled

Yes, if applicable

1

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

Example Mapping

ECHO 10

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

UMM

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

ISO 19115-2 MENDS

ISO 19115-2 MENDS

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

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

Example Mapping

ISO 19115-2 MENDS

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

UMM

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

ISO 19115-2 SMAP

ISO 19115-2 SMAP

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

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

Example Mapping

ISO 19115-2 SMAP

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

UMM

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

UMM Migration

UMM Version 1.9.0

Translation

Direction

UMM Version 1.10.0

Future Mappings

ISO 19115-1

ISO 19115-1

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

Specification	Path	Type	Notes

ISO 19115-1

UMM

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

History

UMM Versioning

Version	Date	What Changed
1.10.0	02 May 2018
1.9.0

ARC Documentation

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

Element Description

Note: this page is a draft/ work in progress

Best Practices

Examples:

Element Specification

Providing Access Constraints is optional. (Cardinality

0..1

*)

Model

Element

Type

Usable Valid Values

Constraints

Required?

Cardinality

Notes

UMM-Common

Access_Constraints

String

Project Short_Name Keywords

1 - 40 characters

KMS controlled

Yes, if applicable

0..1

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

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.

GCMD Metadata QA/QC

CMR Validation

ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: The Project Short Name and/or Long Name keyword does not comply with the KMS. The Project Short Name and /or Long Name keyword does not exist in the KMS. A keyword(s) is placed in the incorrect position of the hierarchy (e.g. the Project Short Name is placed in the Long Name field). Keywords from two different KMS hierarchies are listed in the same hierarchy in the metadata (i.e. hierarchies cannot be mixed and matched). The Project and/or Campaign listed is incorrect for the data 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

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

DIF 10

DIF 10

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

Specification	Path	Type	Usable Valid Values	Constraints	Required in DIF 10?	Cardinality	Notes
DIF 10	/DIF/Project/Short_Name	String	Project Short_Name Keywords	KMS controlled	Yes, if applicable	1	Providing a Project is optional. If provided, the Short Name is required.
DIF 10	/DIF/Project/Long_Name	String	Project Long_Name Keywords	KMS controlled	No	0..1
DIF 10	/DIF/Project/Campaign	String	n/a		No	0..*	Multiple Campaigns may be listed under each Project.
DIF 10	/DIF/Project/Start_Date	Date	n/a		No	0..1
DIF 10	/DIF/Project/End_Date	Date	n/a		No	0..1

Example Mapping

DIF 10

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

UMM

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

ECHO 10

ECHO 10

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

Specification	Path	Type	Usable Valid Values	Constraints	Required in ECHO10?	Cardinality	Notes
ECHO 10	/Collection/Campaigns/Campaign/ShortName	String	Project Short_Name Keywords	1 - 40 characters KMS controlled	Yes, if applicable	1	Providing a Campaign is optional. If provided, the Short Name is required.
ECHO 10	/Collection/Campaigns/Campaign/LongName	String	Project Long_Name Keywords	1 - 1024 characters KMS controlled	No	0..1
ECHO 10	/Collection/Campaigns/Campaign/StartDate	dateTime	n/a	n/a	No	0..1
ECHO 10	/Collection/Campaigns/Campaign/EndDate	dateTime	n/a	n/a	No	0..1

Example Mapping

ECHO 10

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

UMM

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

ISO 19115-2 MENDS

ISO 19115-2 MENDS

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

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

Example Mapping

ISO 19115-2 MENDS

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

UMM

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

ISO 19115-2 SMAP

ISO 19115-2 SMAP

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

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

Example Mapping

ISO 19115-2 SMAP

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

UMM

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

UMM Migration

UMM Version 1.9.0

Translation

Direction

UMM Version 1.10.0

Future Mappings

ISO 19115-1

ISO 19115-1

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

Specification	Path	Type	Notes

ISO 19115-1

UMM

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

History

UMM Versioning

Version	Date	What Changed
1.10.0	02 May 2018
1.9.0

ARC Documentation

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

Page tree

Access Constraints

Element Description

Note: this page is a draft/ work in progress

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

UMM Migration

Future Mappings

History

UMM Versioning

ARC Documentation

Element Description

Note: this page is a draft/ work in progress

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

UMM Migration

Future Mappings

History

UMM Versioning

ARC Documentation