Element Description
The Metadata Association element is used to identify other metadata resources that are dependent on or related to the data described by the metadata. Such metadata resources may include (but are not limited to): services, other collections, visualizations, variables, granules, documents, etc.
Best Practices
Metadata Association is an optional element. It can be used to identify resources stored in different metadata records that are related to the data, and can also be used to define relationships between collections. For instance, a metadata association can be used to identify a parent metadata record if it exists. This usage should be reserved for instances where a group of metadata records are subsets that can be better represented by one parent metadata record, which describes the entire set. In some instances, a 'child' metadata record may point to more than one 'parent'.
The association must be made to another collection level metadata record (via the Entry Id sub-element, which should contain the related collection's Short Name) and then the Type and Description fields can be used to further explain the relationship (whether it be the to the collection itself, or to a component provided in the other collection's metadata such as a service, document, visualization, etc.).
There are four sub-elements that comprise Metadata Association:
Entry ID: The Short Name of the target metadata record that is associated with the collection record. The Entry ID is required and should point to another collection level metadata record that includes the related information.
Version: The version of the target metadata record that is associated with the collection record. Providing a version is optional, but is recommended if the associated collection has multiple available versions.
Type: The type of association between the collection metadata record and the target metadata record. Providing a Type is optional, but recommended. This is a controlled vocabulary field and must be select from the following options:
SCIENCE ASSOCIATED:
Description: Free-text description of the association between this collection record and the target metadata record.
Examples:
Type: "INPUT"
Description: "Raw sensor counts to be converted to radiometric values"
EntryId: "AST_L1A"
Version: "4"
Element Specification
Providing the Metadata Association element is optional (Cardinality: 0..*)
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-C | MetadataAssociation/EntryId | String | 1 - 80 characters | Yes | 1 | |
UMM-C | MetadataAssociation/Version | String | 1 - 80 characters | No | 0..1 | |
UMM-C | MetadataAssociation/Type | Enumeration | SCIENCE ASSOCIATED DEPENDENT INPUT PARENT CHILD RELATED LARGER CITATION WORKS | No | 0..1 | |
UMM-C | Metadata Association/Description | String | 1 - 4000 characters | No | 0..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.
Dialect Mappings
UMM Migration
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|---|---|
Future Mappings
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | 5/2/2018 | No changes were made for Collection Data Type during the transition from version 1.9.0 to 1.10.0 |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 11/16/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |