You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Element Description
The Entry Title element describes the title of the dataset. It is a required element in UMM-C.
Best Practices
The Entry Title should be a descriptive, formal title of the dataset. The Entry Title should not be the same as the Short Name element. It is recommended that the Entry Title follow a mixed case capitalization scheme and that the use of special characters (such as underscores) and acronyms be kept to a minimum, if possible. In order to make titles descriptive, important elements about the data may be included, such as: parameters measured, geographic location, instrument, project, temporal coverage, etc.
Element Specification
| Model | Element | Type | Constraints | Required? | Cardinality |
|---|
| UMM-C | EntryTitle | String | N/A | Yes | 1 |
Value needed for translations:
N/A
ARC Priority Matrix
| Priority Categorization | Justification |
|---|
| This element is categorized as highest priority when: - The element is not included at all.
- The element is included but is empty.
- The value in the element is identical to the Short Name.
- The value in the element is in an abbreviated format (similar, but not necessarily identical to, the short name).
- The value in the element contains a spelling error.
- The value in the element includes incorrect information about the dataset.
|
| Not applicable |
| Not applicable |
| The element is provided, and is a formal title for the dataset (i.e. it is not the same as the short name and is free of grammatical and content errors). |
DIF 9
DIF 9
| Specification | Path | Type | Required in DIF9? | Notes |
|---|
| DIF 9 | /DIF/Entry_Title | String
| Yes | DIF 9 Entry_Title is a string. |
Enumeration Mapping
N/A
Example Mapping
DIF 10
DIF 10
| Specification | Path | Type | Required in DIF 10? | Notes |
|---|
| DIF 10 | /DIF/Entry_Title | String | Yes | DIF 10 Entry_Title is a string. The Entry_Title and Version Id must be unique for a provider. |
Enumeration Mapping
N/A
Example Mapping
ECHO 10
ECHO 10
| Specification | Path | Type | Required in ECHO10? | Notes |
|---|
| ECHO 10 | /Collection/DataSetId | String | Yes | The DataSetId element and the LongName element may be identical in ECHO 10. |
Enumeration Mapping
N/A
Example Mapping
ISO 19115-2 MENDS
ISO 19115-2 MENDS
| Specification | Path | Type | Notes |
|---|
| 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= | String | ProgressCode 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 SMAP
ISO 19115-2 SMAP
| Specification | Path | Type | Notes |
|---|
| 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= | String | ProgressCode 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
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
| Specification | Path | Type | Notes |
|---|
| ISO 19115-1 | /mdb:MI_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:status/mri:MD_ProgressCode with codeList and codeListValue attributes | String | ProgressCode 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. |
History
UMM Versioning
| Version | Date | What Changed |
|---|
| 1.10.0 |
| Changes would be tracked here |
| 1.9.0 |
|
|
ARC Documentation
| Version | Date | What Changed | Author |
|---|
| 1.0 | 2/19/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | |
