The Entry Title element states the title of the dataset.
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.
Examples:
"The San Joaquin Valley Air Quality Study (SJVAQS) Atmospheric Signatures, Predictions, and Experiments (AUSPEX) Database"
"Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0"
"The Next Generation Weather Radar (NEXRAD) Level II, III, and IV Data Products"
Element Specification
Model
Element
Type
Constraints
Required?
Cardinality
UMM-C
EntryTitle
String
1030 maximum characters
Yes
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.
Manual Review
Identify errors, discrepancies or omissions.
Proof all content for conciseness and readability.
Automated Review
Check that the field has been populated.
Check that the field length is not greater than 1,030 characters.
Check that the field value does not match the Entry ID.
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).
ARC Automated Checks
Checks if a value is provided. If not, return is: "Recommending a "*data set ID/entry title*" for this data set, as this is a required field."
If a value is provided, return is "OK."
Dialect Mappings
DIF 9(Note: DIF-9 is being phased out and will no longer be supported after 2018)
DIF 10
Specification
Path
Type
Constraints
Required in DIF 10?
Cardinality
Notes
DIF 10
/DIF/Entry_Title
String
1030 maximum characters
Yes
1
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
DIF 10
<Entry_Title>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</Entry_Title>
UMM
"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",
ECHO 10
Specification
Path
Type
Constraints
Required in ECHO10?
Cardinality
Notes
ECHO 10
/Collection/DataSetId
String
Yes
1
The DataSetId element and the LongName element may be identical in ECHO 10.
Enumeration Mapping
N/A
Example Mapping
ECHO 10
<DataSetId>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</DataSetId>
UMM
"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",
The first path specified to the left is optional in ISO. The CMR will write the value into this path for export to ISO, but it will not read the value from this path.
The second path specified to the left is required in ISO. The CMR will read and write the value in this path.
History
UMM Versioning
Version
Date
What Changed
1.10.0
No changes were made for Entry Title during the transition from version 1.9.0 to 1.10.0
1.9.0
ARC Documentation
Version
Date
What Changed
Author
1.0
4/6/18
Recommendations/priority matrix transferred from internal ARC documentation to wiki space