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.
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 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:
Description: Free-text description of the association between the collection and the target metadata record. Providing a description is optional but can be important for identifying a specific related resource such as a document, citation or piece of data in the target metadata record (recommended for SCIENCE ASSOCIATED, DEPENDENT, INPUT, RELATED and LARGER CITATION WORKS association types).
Examples:
EntryId: "AST_L1A"
Version: "4"
Type: "INPUT"
Description: "Raw sensor counts that were converted to radiometric values found in this collection."
EntryId: "Polarimetric_CT_1602"
Version: "1"
Type: "RELATED"
Description: "This related dataset contains forest vertical structure and associated uncertainty products over the same study area derived by applying multi-baseline Polarimetric Interferometric Synthetic Aperture Radar (PolInSAR) and Polarimetric Coherence Tomographic SAR (PCT or PC-TomoSAR)."
Providing the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | MetadataAssociations/EntryId | String | 1 - 80 characters | Yes, if applicable | 1 |
UMM-C | MetadataAssociations/Version | String | 1 - 80 characters | No | 0..1 |
UMM-C | MetadataAssociations/Type | Enumeration | SCIENCE ASSOCIATED DEPENDENT INPUT PARENT CHILD RELATED LARGER CITATION WORKS | No | 0..1 |
UMM-C | MetadataAssociations/Description | String | 1 - 4000 characters | No | 0..1 |
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.
|
|
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
DIF 10Providing the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.
Enumeration Mapping
|
ECHO 10Providing the Collection Association element is optional (Cardinality: 0..*). Multiple Collection Associations may provided, if necessary.
|
ISO 19115-2 MENDSProviding the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.
|
ISO 19115-2 SMAPThere is currently no mapping between UMM-C and ISO 19115- for Metadata Association.
|
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|---|---|
Future Mappings
|
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | No changes were made for Metadata Association during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for Metadata Association during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Metadata Association during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Metadata Association during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Metadata Association during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Metadata Association during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Metadata Association during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for Metadata Association during the transition from version 1.12.0 to 1.13.0 |
1.12.0 | 01/22/2019 | No changes were made for Metadata Association during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No changes were made for Metadata Association during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 05/02/2018 | No changes were made for Metadata Association during the transition from version 1.9.0 to 1.10.0. |
1.9.0 |
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 02/01/2018 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |