• Created by Unknown User (em.koontz), last updated on Aug 01, 2025 2 minute read

Element Description

The Additional Attributes element is used to describe unique characteristics of the resource which extends beyond those defined in other metadata fields.

Best Practices

The Additional Attributes metadata concept can be used to describe unique characteristics of a dataset beyond what is covered in the existing metadata model. For example: cloud cover, tile number, or acquisition mode could fall into this category since there is no existing field for these characteristics within the Unified Metadata Model (UMM). All Additional Attributes must be defined in the collection level metadata, and should also be provided in the granule level metadata. If an additional attribute is defined in the granule level metadata and has not been defined in the parent collection, then validation errors may occur. 

There are three sub-elements that comprise Additional Attributes at the granule level:

Name: The name / label for the additional attribute. Providing a name is required.

Value: The value of the additional attribute. This value should only be provided at the collection level if it is the same for all granules within the collection. If the value varies by granule, it should be provided for each granule.

Parameter Units of Measurement: The standard unit of measurement for the additional attribute. For example: meters, hertz, microns. Providing a parameter unit of measurement is optional, but highly recommended if the additional attribute value has an associated unit. Use of SI Base Units are recommended.

Element Specification

ModelElementTypeConstraintsRequired?CardinalityNotes
UMM-GAdditonalAttribute/NameString1-50 CharactersYes, if applicable1
UMM-GAdditionalAttribute/ValueString1-500 CharacterNo0..1
UMM-GAdditionalAttribute/ParameterUnitsOfMeasureString1-80 CharactersNo0..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.

Checks to determine if string falls within maximum field lengths.

ARC Priority Matrix
Priority CategorizationJustification
Red= High Priority Finding

This element is categorized as highest priority when:

  • Any Additional Attribute element contains a major spelling or grammatical error.
  • An Additional Attribute is provided at the granule level that is not defined at the collection level.

Yellow = Medium Priority Finding

Not Applicable
Blue = Low Priority Finding

This element is categorized as low priority when:

  • Any minor miscellaneous suggestion
Green = No Findings/IssuesThe element is provided and follows all applicable criteria specified in the best practices section above

ARC Automated Checks

The pyQuARC library is used for automated metadata checks. Please see the pyQuARC GitHub for more information. 

 
  • No labels