Page History

Table of Contents

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 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, of if necessary.

Model	Element	Type	Constraints	Required?	Cardinality
UMM-C	MetadataAssociationMetadataAssociations/EntryId	String	1 - 80 characters	Yes, if applicable	1
UMM-C	MetadataAssociationMetadataAssociations/Version	String	1 - 80 characters	No	0..1
UMM-C	MetadataAssociationMetadataAssociations/Type	Enumeration	SCIENCE ASSOCIATED DEPENDENT INPUT PARENT CHILD RELATED LARGER CITATION WORKS	No	0..1
UMM-C	MetadataAssociationMetadataAssociations/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

title	GCMD Metadata QA/QC

Manual Review
- Identify errors, discrepancies or omissions.
- Proof all content for conciseness and readability.
Automated Review

Expand

title	CMR Validation

<>

- Check the Type field to make sure it matches a Type keyword in the enumeration list.
- Check that the Description field length is not greater than 4,000 characters
- Check that the Short_Name, Version, and Type field lengths are not greater than 80 characters

Expand

title	CMR Validation

Check the Type field to make sure it matches a Type keyword in the enumeration list.
Check that the Description field length is not greater than 4,000 characters
Check that the Short_Name, Version, and Type field lengths are not greater than 80 characters

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
Red = High Priority Finding	This element is categorized

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
This element is categorized as highest priority when: A Metadata Association is provided but the Entry Id is missing (Entry Id is required). An incorrect enumeration value is provided for the MetadataAssociationMetadata Association/Type fieldThe MetadataAssociation/Description includes spelling errors.
Yellow = Medium Priority Finding	This element is categorized as medium priority when: The Metadata Association points to an outdated collection (i.e. a collection that no longer exists). The Metadata Association/Description includes spelling or grammatical errors.
Blue = Low Priority Finding	This element is categorized as low priority when: Suggestions are made to change the information provided in the Metadata Association for clarity. Suggestions are made to provide additional information in the Metadata Association for clarity.
Green = No Findings/Issues	The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

If novalue is provided, return is "np."Otherwise, return is "OK."

Checks

ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information.

Dialect Mappings

Expand

title	DIF 9

DIF 9 ^{(Note: DIF-9 is being phased out and will no longer be supported after 2018)}

MetadataAssociation

Expand

title	DIF 10

DIF 10

Providing the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.

UMM-C Element	DIF 10 Path	Type	Constraints	Required in DIF 10?	Cardinality

Notes

MetadataAssociations/EntryId

Metadata_Association/Entry_ID/Short_Name

String

Yes

1

MetadataAssociation

MetadataAssociations/Version

Metadata_Association/Entry_ID/Version

String

Yes

1

MetadataAssociation

MetadataAssociations/Type

Metadata_Association/Type

Enumeration

Parent

Child

Input

Science Associated

Yes

1

Metadata

Association

Associations/Description

Metadata_Association/Description

String

No

0..1

Enumeration Mapping

DIF 10	Translation Direction	UMM
Parent	↔	PARENT
Child	↔	CHILD
Related	↔	RELATED
Dependent	↔	DEPENDENT
Input	↔	INPUT
Science Associated	↔	SCIENCE ASSOCIATED
	←	LARGER CITATION WORKS

Example Mapping

Section

Column

width	50%

DIF 10

No Format

<Metadata_Association>
  <Entry_ID>
    <Short_Name>AST_L1A</Short_Name>
    <Version>004</Version>
  </Entry_ID>
  <Type>Input</Type>
  <Description>Raw sensor counts that were converted to radiometric values found in this collection.</Description>
</Metadata_Association>

Column

width	50%

UMM

No Format
MetadataAssociations: [ - { Type: "INPUT", Description: "Raw sensor counts that were converted to radiometric values found in this collection.", EntryId: "AST_L1A" Version: "4" } ],

Expand

title	ECHO 10

ECHO 10

Providing the Collection Association element is optional (Cardinality: 0..*). Multiple Collection Associations may provided, if necessary.

UMM-C Element	ECHO 10 Path	Type	Constraints	Required in ECHO10?	Cardinality	Note
MetadataAssociationMetadataAssociations/EntryId	CollectionAssociations/CollectionAssociation/ShortName	String	1 - 80 characters	Yes, if applicable	1	The short name of an input collection and/or a dependent collection that is somehow associated with this collection.
MetadataAssociationMetadataAssociations/Version	CollectionAssociations/CollectionAssociation/VersionId	String	1 - 80 characters	Yes, if applicable	1	The version of an input collection and/or a dependent collection that is somehow associated with this collection.
MetadataAssociationMetadataAssociations/Type	CollectionAssociations/CollectionAssociation/CollectionType	String	1 - 80 characters	Yes, if applicable	1	The type of the association whether an input type, or dependent type etc. This field is not controlled in ECHO10, but is controlled in the UMM. Therefore, strongly recommend utilizing one of the UMM enumeration types in this field in order to prevent errors when translating from ECHO10 to other metadata formats. UMM controlled vocabulary options for this field include: SCIENCE ASSOCIATED, DEPENDENT, INPUT, PARENT, CHILD, RELATED, LARGER CITATION WORKS
Metadata AssociationMetadataAssociations/Description	CollectionAssociations/CollectionAssociation/CollectionUse	String	1 - 4000 characters	No	0..1	Explanation of how the associated collection is used for this collection.

Enumeration Mapping

ECHO 10	Translation Direction	UMM
SCIENCE ASSOCIATED	←	SCIENCE ASSOCIATED
DEPENDENT	←	DEPENDENT
INPUT	←	INPUT
PARENT	←	PARENT
CHILD	←	CHILD
RELATED	←	RELATED
LARGER CITATION WORKS	←	LARGER CITATION WORKS	→	???

Example Mapping

Section

Column

width	50%

ECHO 10

No Format

<CollectionAssociations>
  <ShortName>AST_L1A</ShortName> 
  <VersionId>4</VersionId>
  <CollectionType>Input</CollectionType>
  <CollectionUse>Raw sensor counts that were converted to radiometric values found in this collection.</CollectionUse>
</CollectionAssociations>

Column

width	50%

UMM

No Format
MetadataAssociations: [ - { Type: "INPUT", Description: "Raw sensor counts that were converted to radiometric values found in this collection.", EntryId: "AST_L1A" Version: "4" } ],

ISO 19115-2 SMAP

There is currently no mapping between UMM-C and ISO 19115-1 for Metadata Association.

Enumeration/Code List MappingExample Mapping

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

Providing the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.

UMM-C Element

ISO 19115-2 MENDS Path

Type

MetadataAssociationMetadataAssociations

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetName/gmd:CI_Citation

Metadata Associations:
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:associationType/gmd:DS_AssociationTypeCode codeListValue="Science Associated"

Parent Associations:
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:associationType/gmd:DS_AssociationTypeCode codeListValue="largerWorkCitation"

String

Enumeration/Code List Mapping

ISO MENDS

Translation

Direction

UMM

↔

Example Mapping

Section

Column

width	50%

ISO 19115-2 MENDS

No Format
ADD EXAMPLE (need 2 examples - 1 for metadata association & 1 for parent association)

Column

width	50%

UMM

No Format

MetadataAssociations: [
  - {Metadata Association Sample:

<gmd:dataQualityInfo>
                <gmd:DQ_DataQuality>
       Type: "INPUT",
       Description: "Raw sensor counts that were<gmd:lineage>
 converted to radiometric values found in this collection.",
       EntryId: "AST_L1A"
       Version: "4" <gmd:LI_Lineage>
    }
],

Expand

title	ISO 19115-2 SMAP

UMM-C Element

ISO 19115-2 SMAP Path

Type

Notes

MetadataAssociation

N/A

ISO SMAP

Translation

Direction

UMM

↔

Section

Column

width	50%

ISO 19115-2 SMAP

No Format
N/A

Column

width	50%

UMM

No Format
N/A

UMM Migration

UMM Version 1.9.0Translation DirectionUMM Version 1.10.0

Future Mappings

Expand

title	ISO 19115-1

ISO 19115-1

Providing the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.

UMM-C ElementPathTypeMetadataAssociation

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:associatedResource/mri:MD_AssociatedResource/mri:name

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"

StringEnumeration/Code List MappingISO MENDS

Translation

Direction

UMM↔Example Mapping

Section

Column

width	50%

ISO 19115-1

No Format
ADD EXAMPLE (need 2 examples - 1 for metadata association & 1 for parent association)

Column

width	50%

UMM

No Format
MetadataAssociations: [ - { Type: "INPUT", Description: "Raw sensor counts to be converted to radiometric values", EntryId: "AST_L1A" Version: "4" } ],

                        <gmd:source>
                                <gmd:LI_Source>
                                    <gmd:description>
                                        <gco:CharacterString>Raw sensor counts that were converted to radiometric values found in this collection.</gco:CharacterString>
                                    </gmd:description>
                                    <gmd:sourceCitation>
                                        <gmd:CI_Citation>
                                            <gmd:title>
                                                <gco:CharacterString>AST_L1A</gco:CharacterString>
                                            </gmd:title>
                                            <gmd:date gco:nilReason="unknown"></gmd:date>
                                            <gmd:edition>
                                                <gco:CharacterString>4</gco:CharacterString>
                                            </gmd:edition>
                                        </gmd:CI_Citation>
                                    </gmd:sourceCitation>
                                </gmd:LI_Source>
                            </gmd:source>
                        </gmd:LI_Lineage>
                    </gmd:lineage>
                </gmd:DQ_DataQuality>
            </gmd:dataQualityInfo>


Parent Association Example:

 <gmd:identificationInfo>
                <gmd:MD_DataIdentification>
                    <gmd:aggregationInfo>
                        <gmd:MD_AggregateInformation>
                            <gmd:aggregateDataSetName>
                                <gmd:CI_Citation>
                                    <gmd:title>
                                        <gco:CharacterString>MYD02SSH</gco:CharacterString>
                                    </gmd:title>
                                    <gmd:date gco:nilReason="unknown"></gmd:date>
                                    <gmd:edition>
                                        <gco:CharacterString>6.1NRT</gco:CharacterString>
                                    </gmd:edition>
                                    <gmd:otherCitationDetails>
                                        <gco:CharacterString>Parent collection for child product MYD021KM.</gco:CharacterString>
                                    </gmd:otherCitationDetails>
                                </gmd:CI_Citation>
                            </gmd:aggregateDataSetName>
                            </gmd:MD_AggregateInformation>
                            </gmd:aggregationInfo>
                </gmd:MD_DataIdentification>
            </gmd:identificationInfo>

Column

width	50%

UMM

No Format
MetadataAssociations: [ - { Type: "INPUT", Description: "Raw sensor counts that were converted to radiometric values found in this collection.", EntryId: "AST_L1A" Version: "4" } ],

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

There is currently no mapping between UMM-C and ISO 19115- for Metadata Association.

UMM-C Element	ISO 19115-2 SMAP Path	Type	Notes
MetadataAssociations	N/A	N/A	N/A

Enumeration/Code List Mapping

ISO SMAP

Translation

Direction

UMM

↔

UMM Migration

UMM Version 1.9.0	Translation Direction	UMM Version 1.10.0

Excerpt

hidden	true

Future Mappings

Expand

title	ISO 19115-1

ISO 19115-1

Providing the Metadata Association element is optional (Cardinality: 0..*). Multiple Metadata Associations may provided, if necessary.

UMM-C Element

ISO 19115-1 Path

Type

MetadataAssociations

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:associatedResource/mri:MD_AssociatedResource/mri:name

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"

String

Enumeration/Code List Mapping

ISO MENDS

Translation

Direction

UMM

↔

Example Mapping

Section

Column

width	50%

ISO 19115-1

No Format
ADD EXAMPLE (need 2 examples - one for metadata association & one for parent association)

Column

width	50%

UMM

No Format
MetadataAssociations: [ - { Type: "INPUT", Description: "Raw sensor counts to be converted to radiometric values", EntryId: "AST_L1A" Version: "4" } ],

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

History

UMM Versioning

What Changed

Version	Date
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

ARC Documentation

Version	Date	What Changed	Author
1.0	202/101/182018	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Jeanne' le Roux Ingrid Garcia-Solera

Page tree

Versions Compared

Old Version 14

New Version Current

Key

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

DIF 10

ECHO 10

ISO 19115-2 SMAP

ISO 19115-2 MENDS

UMM Migration

Future Mappings

ISO 19115-1

ISO 19115-2 SMAP

UMM Migration

Future Mappings

ISO 19115-1

History

UMM Versioning

History

UMM Versioning

ARC Documentation