The archive and distribution information main element allows data providers to provide users information of what is available for downloading when they initially looking at a collection. The end users get information such as the average downloadable file size, format, mime type, checksum, etc., an estimate of the collections entire downloadable file size, etc.
Examples:
Cardinality of Archive and Distribution Information:
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/ Format | String | 1 - 80 characters | Yes | 1 | ||
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/FormatType | String | Native Supported | n/a | No | 0..1 | |
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/ AverageFileSize | Decimal | Yes, if TotalCollectionFileSizeBeginDate is used. | 0..1 | |||
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/ AverageFileSizeUnit | String | KB MB GB TB PB NA | n/a | Yes, if AverageFileSize is used. | 0..1 | |
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSize | Decimal | No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | ||
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSizeUnit | Enumeration | KB MB GB TB PB NA | n/a | Yes, if TotalCollectionFileSize is used | 0..1 | |
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSizeBeginDate | Date | No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | ||
UMM-Common | ArchiveAndDistributionInformation/ FileArchiveInformation/ Description | String | n/a | 1 - 1024 characters | No | 0..1 | |
ArchiveAndDistributionInformation/ FileDistributionInformation/Format | String | 1 - 80 characters | Yes | 1 | |||
ArchiveAndDistributionInformation/ FileDistributionInformation/ FormatType | String | Native Supported | No | 0..1 | |||
UMM-Common | ArchiveAndDistributionInformation/ FileDistributionInformation/ Media | String | n/a | 1 - 80 characters | No | 0..1 | |
UMM-Common | ArchiveAndDistributionInformation/ FileDistributionInformation/ AverageFileSize | Decimal | n/a | n/a | Yes, if TotalCollectionFileSizeBeginDate is used. | 0..1 | |
UMM-Common | ArchiveAndDistributionInformation/ FileDistributionInformation/ AverageFileSizeUnit | Enumeration | KB MB GB TB PB NA | Yes, if AverageFileSize is used. | 0..1 | ||
UMM-Common | ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSize | Decimal | n/a | No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | |
UMM-Common | ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSizeUnit | Enumeration | KB MB GB TB PB NA | n/a | Yes, if TotalCollectionFileSize is used | 0..1 | |
UMM-Common | ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSizeBeginDate | Date | No | 0..1 | Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate | ||
UMM-Common | ArchiveAndDistributionInformation/ FileDistributionInformation/ Description | String | n/a | 1 - 1024 characters | No | 0..1 | |
UMM-Common | Fees | String | n/a | 1 - 255 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
|
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
DIF 10Instrument is a required metadata element. At least 1 Instrument Keyword must be provided under each Platform. Multiple Instruments may be listed if necessary (Cardinality: 1..*). Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
|
ECHO 10Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*). Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
|
ISO 19115-2 MENDSInstrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*). Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
|
ISO 19115-2 SMAPInstrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*). Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
|
None
Future Mappings
ISO 19115-1Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*). Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.
Example Mapping
|
Version | Date | What Changed |
---|---|---|
1.13.0 | Future | This element was added to the UMM-C specification. |
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 5/16/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |