Additional Attributes

Element Description

The Addition Attribute element is used to describe unique characteristics of the resource which extend 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. Example attributes include values for cloud cover, MODIS Tile grid coordinates, and elevation information. All Additional Attributes must be defined in the collection metadata. These attributes can then be provided in the granule level metadata to facilitate search. An Additional Attribute that has not been defined in the collection level metadata record may not be provided in the granule metadata. There are two possible scenarios:

1. The additional attribute has a value that is the same for all of the granules in the collection. In this case, the additional attribute 'Value' may be provided in the collection level metadata. The value should be provided in the granule level metadata as well, so that the attribute is searchable at the granule level.
2. The additional attribute has a value that varies from granule to granule. In this case, the 'Value' field must be left blank in the collection level metadata. The 'Value' field should only be populated in granule level metadata. 

If the additional attribute type is known it can be mapped to the correct section of ISO.  Currently additional attributes are mapped to several sections within ISO depending if the attribute is geographical, describes coverage, describes data quality, describes acquisition, or maps to a keyword.

There are fourteen sub-elements that comprise Additional Attributes:

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

Description: A free-text description of the additional attribute. Providing a description is required.

Value: The actual value of the additional attribute. Provide the value in the collection level record if it is the same for all granules across the collection. If the value of the additional attribute differs by granule, then leave value blank at the collection level.

DataType: The data type of the additional attribute value. Providing a data type is required. This is a controlled vocabulary field in UMM-Common with the following options: STRING, FLOAT, INT, BOOLEAN, DATE, TIME, DATETIME, DATE_STRING, TIME_STRING, DATETIME_STRING

Measurement Resolution: The smallest unit increment to which the additional attribute value is measured. Providing a measurement resolution is optional.

Parameter Range Begin: The minimum value of the additional attribute over the whole collection. This only applies to attributes that are continuous in nature. Providing a parameter range begin is optional.

Parameter Range End: The maximum value of the additional attribute over the whole collection. This only applies to attributes that are continuous in nature. Providing a parameter range begin is optional.

Parameter Units Of Measure: The standard unit of measurement for the additional attribute. For example: meters, hertz. Providing a parameter unit of measure is optional.

Parameter Value Accuracy: An estimate of the accuracy of the values of the additional attribute. For example, for AVHRR: Measurement error or precision-measurement error or precision of a data product parameter. The accuracy must be specified as a percentage or the unit with which the parameter is measured. Providing a parameter value accuracy is optional.

Value Accuracy Explanation: Describes the method used for determining the parameter value accuracy that is given for this additional attribute. Providing a value accuracy explanation is optional.

Group: Identifies a namespace for the additional attribute name. Providing a group is optional. 

Update Date: The date this additional attribute information was updated. Providing an update date is optional. 

Examples: 

Group: "gov.nasa.gsfc.gcmd"

Value: "42a420d8-04bd-4b2f-ad2a-8adc138faa04"

Name: "metadata.uuid"

Description: "Not provided"

DataType: "STRING"

note: add table example where the attribute is the same for all granules, and one where it is different

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

Future Mappings

ADD EXAMPLE

-AdditionalAttributes: [
   - {
         Group: "gov.nasa.gsfc.disc",
         Value: "1 month",
         Name: "Data Granularity",
         Description: "The time coverage of individual data granules.",
         DataType: "STRING"
     },

History

UMM Versioning

ARC Documentation