You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »



ElementDefinitionRequired
Short Name
Yes
Version
Yes
MetadataLanguageThe language used in the metadata record....
MetadataDatesDates related to activities involving the metadata record itself.  For example, Future Review date is the date that the metadata record is scheduled to be reviewed.
DirectoryNames

Formerly called Internal Directory Name (IDN) Node (IDN_Node). This element has been used historically by the GCMD internally to identify association, responsibility and/or ownership of the dataset, service or supplemental information. Note: This field only occurs in the DIF. When a DIF record is retrieved in the ECHO10 or ISO 19115 formats, this element will not be translated.


EntryTitle
Yes
DOI

Abstract
Yes
Purpose

Science Keywords
Yes
DataLanguage

DataDates

DataCenters

ContactGroups

ContactPersons

CollectionDataType

ProcessingLevel

CollectionCitations

Collection Progress

Describes the production status of the data set. There are three choices:

PLANNED refers to data sets to be collected in the future and are thus unavailable at the present time. For Example: The Hydro spacecraft has not been launched, but information on planned data sets may be available.

ACTIVE refers to data sets currently in production or data that is continuously being collected or updated. For Example: data from the AIRS instrument on Aqua is being collected continuously.

COMPLETE refers to data sets in which no updates or further data collection will be made. For Example: Nimbus-7 SMMR data collection has been completed.

NOT APPLICABLE refers to data sets where collection progress doesn't make sense.  For example a calibration collection record.

NOT PROVIDED - It is necessary for this value to exist so that the CMR can translate older non UMM compliant records into the latest UMM specification where CollectionProgress is required. 

Yes

Quality

Free text description of the quality of the collection data.  Description may include:

  1. succinct description of the quality of data in the collection;
  2. Any quality assurance procedures followed in producing the data in the collection;
  3. indicators of collection quality or quality flags - both validated or invalidated;
  4. recognized or potential problems with quality;
  5. established quality control mechanisms; and
  6. established quantitative quality measurements.

UseConstraintsDesigned to protect privacy and/or intellectual property by allowing the author to specify how the collection may or may not be used after access is granted. This includes any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the item. Providers may request acknowledgement of the item from users and claim no responsibility for quality and completeness. Note: Use Constraints describe how the item may be used once access has been granted; and is distinct from Access Constraints, which refers to any constraints in accessing the item.
AccessConstraints




TilingIdentificationSystems

still in progress

Defines a named two-dimensional tiling system.
  • No labels