Element Description

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. 

The Data Product Development Guide for Data Producers offers the following guidance for naming a data product. The term "long name" in the excerpt below is synonymous with the "Entry Title" metadata element:

"The name of a data product is critical to its discovery in Earthdata Search and tools developed by
DAACs. DAACs have rules for naming data products, so selection of long and short names should be
a joint effort between producer and DAAC. DAAC involvement in naming also helps in making the
data products discoverable and EOSDIS-unique. Data products must be assigned both a long name,
which is meant to be human readable (and comprehensible), and a short name, which aids precise
searching by keyword. The data product long name and short name are considered global attributes
in that they are not associated with any particular variable but are related to the data product as a
whole.


Data producers should seek a name that will be understandable to the target user community but
also unique within EOSDIS. A reasonable data product name may already be in use (e.g., beginning
with “MODIS/Aqua” or MODIS/Terra”), and care should be taken to avoid naming conflicts by
consultation with the relevant data producers. Also consider interoperability when choosing names
[26].


There is no universal file-naming convention for NASA Earth Science data products, apart from the
DIWG recommendations regarding the components of file names provided in [26] (Rec. 3.8-3.11).
However, filenames should be unique and human-readable and contain information that is
descriptive of the contents.

The data product long name (not to be confused with the CF long_name attribute for individual
variables) is a scientific definition of the product. It should be as brief (but as complete) as possible,
as it expands on the sometimes-cryptic corresponding short name. Specifically, the long name
should be a character string from 45-90 characters to prevent wrapping and enhance readability
and scannability in interfaces (such as Earthdata Search) [49]. The attribute LongName is
synonymous with the attribute title used in netCDF documentation (see Appendix D.1).

The product long name should be included in the file as the global attribute LongName.

The recommended naming convention for data products includes the following information:

• The data source, usually the acronym/abbreviation for the project responsible for producing
the data, but can also be the instrument (e.g., HIRDLS, the High Resolution Dynamics Limb
Sounder), satellite (e.g., TRMM, the Tropical Rainfall Measuring Mission), or program (e.g.,
MEaSUREs, Making Earth System Data Records for Use in Research Environments); include
both the instrument and satellite names to eliminate ambiguity (e.g., MODIS/Aqua).

• Science content (e.g., Aerosol, Precipitation).

• The general spatial distribution of the data (e.g., gridded, swath, orbit, in situ).

• For gridded data, the temporal resolution (e.g., daily, monthly).

• Processing level (e.g., L2 or Level 2).

• Spatial resolution (e.g., 3 km; if there are multiple resolutions in the product, then the
highest resolution is stated)."


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

ModelElementTypeConstraintsRequired?Cardinality
UMM-CEntryTitleString1030 maximum charactersYes1


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 required
  • Must contain at least 1 character and be no longer than 1,030 characters in length
  • The Entry Title must be unique per data provider

ARC Priority Matrix

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

  • No Entry Title is provided.
  • The Entry Title is identical to the Short Name.
  • The Entry Title is in an abbreviated format (similar, but not necessarily identical to, the Short Name).
  • The Entry Title contains a spelling error.
  • The Entry Title includes incorrect information about the dataset (e.g. mismatch between data set landing page and the Entry Title).
  • The Entry Title contains the wrong version number. 
Yellow = Medium Priority Finding

Not applicable

Blue = Low Priority Finding

This element is categorized as low priority when:

  • A mixed-case capitalization scheme is not used.

Green = No Findings/Issues

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

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

Dialect Mappings

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

DIF 10

UMM-C ElementDIF 10 PathTypeConstraintsRequired in DIF 10?CardinalityNotes
EntryTitle/DIF/Entry_TitleString1030 maximum charactersYes1

DIF 10 Entry_Title is a string. The Entry_Title 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

UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?CardinalityNotes
EntryTitle/Collection/DataSetIdString1 - 1030 charactersYes1The 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",



ISO 19115-2 MENDS

UMM-C Element

ISO 19115-2 MENDS Path

TypeNotes
EntryTitle

/gmi:MI_Metadata/gmd:fileIdentifier/gco:CharacterString

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString

String

The first path specified to the left is optional in ISO. The CMR does not read this value, but when it generates ISO 19115-2 MENDS records it will write the title to this location.

The second path specified to the left is required in ISO.

Enumeration/Code List Mapping

N/A

Example Mapping

ISO 19115-2 MENDS

<gmi:MI_Metadata>
  ...
  <gmd:fileIdentifier>
    <gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
  </gmd:fileIdentifier>
  ...
</gmi:MI_Metadata>

<gmi:MI_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
	  <gmd:citation>
	    <gmd:CI_Citation>
		  <gmd:title>
			<gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
    	  </gmd:title>
          ...
		</gmd:CI_Citation>
	  </gmd:citation>
      ...
	</gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmi:MI_Metadata>

UMM

"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",



ISO 19115-2 SMAP

UMM-C Element

ISO 19115-2 SMAP Path

TypeNotes
EntryTitle

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetIdentifier/gmd:MD_Identifier/ gmd:code/gco:CharacterString

with

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString='DataSetId'

String

Adding gco:CharacterString='DataSetId' helps CMR identify the identifier provided within the aggregate information section as the Entry Title.

Enumeration/Code List Mapping

N/A

Example Mapping

ISO 19115-2 SMAP

<gmd:DS_Series>
 <gmd:seriesMetadata>
  <gmi:MI_Metadata>
    ...
	<gmd:identificationInfo>
		<gmd:MD_DataIdentification>
			<gmd:citation>
				<gmd:CI_Citation>
					<gmd:title>
						<gco:CharacterString>DataSetId</gco:CharacterString>
    				</gmd:title>
                    ...
				</gmd:CI_Citation>
			</gmd:citation>
            ...
			<gmd:aggregationInfo>
				<gmd:MD_AggregateInformation>
                    ...
					<gmd:aggregateDataSetIdentifier>
						<gmd:MD_Identifier>
							<gmd:code>
								<gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
							</gmd:code>
                            ...
						</gmd:MD_Identifier>
                        ...
					</gmd:aggregateDataSetIdentifier>
                    ...
				</gmd:MD_AggregateInformation>
			</gmd:aggregationInfo>
            ...
		</gmd:MD_DataIdentification>
	</gmd:identificationInfo>
    ...
  </gmi:MI_Metadata>
 </gmd:seriesMetadata>
</gmd:DS_Series>

UMM

"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",



UMM Migration

N/A

Future Mappings

ISO 19115-1

UMM-C Element

ISO 19115-1 Path

TypeNotes
EntryTitle

/mdb:MD_Metadata/mdb:metadataIdentifier/mcc:MD_Identifier/mcc:code/gco:CharacterString

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:title/gco:CharacterString

String

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.

Example Mapping

<mdb:MD_Metadata>
  ...
  <mdb:metadataIdentifier>
    <mcc:MD_Identifier>
      <mcc:code>
        <gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
      </mcc:code>
    </mcc:MD_Identifier>
  </mdb:metadataIdentifier>
  ...
</mdb:MD_Metadata>



<mdb:MD_Metadata>
  ...
  <mdb:identificationInfo>
    <mri:MD_DataIdentification>
      <mri:citation>
        <cit:CI_Citation>  
          ... 
          <cit:title>
            <gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
          </cit:edition>
          ...
        </cit:CI_Citation>
      </mri:citation>
      ...
    </mri:MD_DataIdentification>
  </mdb:identificationInfo>
  ...
</mdb:MD_Metadata>
"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",

History

UMM Versioning

VersionDateWhat Changed
1.15.512/3/2020No changes were made for Entry Title during the transition from version 1.15.4 to 1.15.5
1.15.49/18/2020No changes were made for Entry Title during the transition from version 1.15.3 to 1.15.4
1.15.37/1/2020No changes were made for Entry Title during the transition from version 1.15.2 to 1.15.3
1.15.25/20/2020No changes were made for Entry Title during the transition from version 1.15.1 to 1.15.2
1.15.13/25/2020No changes were made for Entry Title during the transition from version 1.15.0 to 1.15.1
1.15.02/26/2020No changes were made for Entry Title during the transition from version 1.14.0 to 1.15.0
1.14.010/21/2019No changes were made for Entry Title during the transition from version 1.13.0 to 1.14.0
1.13.004/11/2019No changes were made for Entry Title during the transition from version 1.12.0 to 1.13.0
1.12.001/22/2019No changes were made for Entry Title during the transition from version 1.11.0 to 1.12.0.
1.11.011/28/2018No changes were made for Entry Title during the transition from version 1.10.0 to 1.11.0.
1.10.005/02/2018No changes were made for Entry Title during the transition from version 1.9.0 to 1.10.0.

ARC Documentation

VersionDateWhat ChangedAuthor
1.004/06/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space
Kaylin Bugbee