Guidelines for metadata required as a means of ensuring consistency in science data products.
The ESD Base Metadata Requirements document serves as the ESD-approved implementation guidelines for metadata required in science data products. The metadata requirements in this memo are a means of assuring the consistency of metadata requirements across subsystems, and supporting the standardization necessary for system interoperability. The International Organization for Standardization (ISO) Geographic Information – Metadata standard 19115 (and related standards) shall be used to describe science data products. This standard includes two parts, 19115 and 19115-2. Part 2 and revisions to 19115 that became an International Standard during April, 2014 (19115-1), include elements that are critical for NASA collections and products. In addition, the data quality elements of 19115 have been extracted into another standard (ISO 19157). Complete descriptions of NASA collections and products will require elements from all of these standards.
These requirements are currently under review by the ESDIS Standards Office (ESO), so the requirements listed below may change pending the results of that review.
Please send comments on this document to Andrew.E.Mitchell @ nasa.gov
The following three concepts are used to describe the metadata in this document. Although individual mission/instruments may utilize different terms for these concepts, the corresponding descriptions should all be addressed. (Note that the use of term “dataset” in NASA Earth Science Data Systems (ESDS) metadata conflicts with ISO terminology. In ISO, “dataset” means “granule”. In NASA ESDS, “dataset” means “collection”.)
A series may contain zero or more datasets, however datasets/granules cannot exist without being associated with a series. Browse images may be associated or included within either series or datasets.
Series Metadata shall provide all fields listed in the table below.
This element specifies a name for the series/collection.
This element specifies a unique identifier for the series/collection.
This element specifies the version identifier of the data series/collection
This element identifies the purpose and provides a description of the content of the series/collection.
This element provides a summary of the intentions with which the data were developed
This entity describes the platforms associated with the acquisition of the series/collection or dataset/granule, instrument/sensor used to measure or record data and acquisition plan. Acquisition information that applies to all datasets in the series is contained in this entity.
This entity describes the physical parameters being measured or calculated.
This entity allows for the specification of Earth science keywords that are representative of the series/collection. Notably, the Platform/Instrument and Science Keyword lists are managed by the Global Change Master Directory (GCMD).
This entity contains attributes describing the scientific endeavor(s) to which the series/collection is associated. Scientific endeavors include campaigns, projects, interdisciplinary science investigations, missions, field experiments, etc.
This element contains elements for describing people or organizations that are related to the data and their roles.
This entity describes the spatial representation.
Datasets shall inherit all fields listed in the series table in addition to the elements listed below.
This element is a unique reference which identifies the metadata file.
This element holds information about series/collections that a dataset/granule is part of.
This entity records the data series/collection generation in detail sufficient to allow reproducibility.
This entity records the information about the quality of the data or any quality assurance procedures followed in producing the data.
When available, list of browse images associated with the series/collection.
This entity describes the spatial and temporal extent of the data
In addition to the required elements previously identified in this document, there are other elements of ISO 19115 that may also be required by conditional requirements. For example, the LI_Source “description” is mandatory if “sourceExtent” is not documented. There are two cases where an element can be considered to have conditional requirements: