Page History
Table of Contents |
---|
Element Description
This The Metadata Association element is used to identify other services, collections, visualizations, granules, and other metadata types and resources that are associated with or 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
This element is also used 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'.
There are four sub-elements that comprise Metadata Association:
Entry ID: Short-name of the target metadata record that is associated with this collection record.
Version: The version of the target metadata record that is associated with this collection record.
Type: The type of association between this collection metadata record and the target metadata record. Choose type from the drop-down list.
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..*)
1 - 80 characters
1 - 80 characters
SCIENCE ASSOCIATED
DEPENDENT
INPUT
PARENT
CHILD
RELATED
LARGER CITATION WORKS
1 - 4000 characters
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.
title | GCMD Metadata QA/QC |
---|
Expand | ||
---|---|---|
| ||
<> |
title | ARC Metadata QA/QC |
---|
This element is categorized as highest priority when:
- The information provided is not related to the element.
- The Collection Citation described are inaccurate for the data set.
- The Collection Citation description includes spelling or grammatical errors.
This element is categorized as medium priority when:
- The
This element is categorized as low priority when:
- The
ARC Automated Rules
If novalue is provided, return is "np."Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
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:
- SCIENCE ASSOCIATED: There is an associated science resource (such as a document or data) in the target metadata record.
- DEPENDENT: The collection is somehow dependent on the target record.
- INPUT: The target record is an input to the collection. For example, the target record could be a lower level data product that was input to an algorithm and processed to create the collection.
- PARENT: The target record is a parent of the collection. This means the collection is a subset or 'child' of a larger parent collection.
- CHILD: The target record is a child of the collection. This means the collection is a parent record with a number of associated 'child' records.
- RELATED: The target record is somehow related to the collection.
- LARGER CITATION WORKS: There is a document cited in the target record that is related to the collection.
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)."
Element Specification
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 |
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).
Lucidchart rich-viewer false autofit true name Copy of Wiki Page Metadata Evaluation Workflow-1939-51df84 width 1102 pages-to-display id 98e5dc28-3252-4209-953f-66f1378e1cf4 align Left height 299
Please see the expandable sections below for flowchart details.
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10Providing the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.
Enumeration Mapping
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Specification | Path | Type | Constraints | Required in DIF 10? | Cardinality | Notes | DIF 10 | Metadata_Association/Entry_ID/Short_Name | String | Yes | 1 | DIF 10 | Metadata_Association/Entry_ID/Version | String | Yes | 1 | DIF 10 | Metadata_Association/Type | Enumeration | Parent Child Related Dependent Input Science Associated | Yes | 1 | DIF 10 | Metadata_Association/Description | String | No | 0..1 | Example Mapping
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ECHO 10 |
---|
ECHO 10
Providing the Metadata Association element is optional (Cardinality: 0..*)
The type of the association whether an input type, or dependent type etc.
Example Mapping
Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Providing the Collection Association element is optional (Cardinality: 0..*). Multiple Collection Associations may provided, if necessary.
|
Expand | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
ISO 19115-2 MENDSProviding the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.
|
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
ISO 19115-2 SMAPThere is currently no mapping between UMM-C and ISO 19115- for Metadata Association.
|
UMM Migration
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|---|---|
Excerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Future Mappings
| 2 MENDS
| Specification | Path | Type | Notes
0..*). Multiple Metadata Associations may provided, if necessary.
|
Metadata Associations:
/gmi:MI_Metadata/gmd:identificationInfo/gmd
|
|
|
|
|
Parent
|
|
|
|
|
|
|
|
|
|
|
|
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
title | ISO 19115-2 SMAP |
---|
|
ISO 19115-2 SMAP
Providing the Metadata Association element is ? (Cardinality: ?)
|
UMM Migration
Future Mappings
title | ISO 19115-1 |
---|
ISO 19115-1
Providing the Metadata Association element is ? (Cardinality: ?)
Metadata Associations:
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:associatedResource/mri:MD_AssociatedResource/mri:associationType/mri:DS_AssociationTypeCode codeList="codeListLocation#DS_AssociationTypeCode"codeListValue="Science Associated"
Parent Associations:
/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:associatedResource/mri:MD_AssociatedResource/mri:associationType/mri:DS_AssociationTypeCode codeList="codeListLocation#DS_AssociationTypeCode"codeListValue="largerWorkCitation"
Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
History
UMM Versioning
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 |
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | 5/2/2018 | No changes were made for Collection Data Type Metadata Association during the transition from version 1.9.0 to 1.10.0. |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 1102/1601/182018 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |