Page History
Table of Contents | ||
---|---|---|
|
Element Description
Archive and Distribution Information provides details about the file(s) or file package(s) that make up the granule. A file package refers to any file formatting used to store multiple files (e.g. zip files).
Best Practices
Archive And Distribution Information can be used to describe a file, whether it be a stand-alone file or a packaged file. Providing this information is optional but can be leveraged to document useful specs about the granule data.
Use the 'FileType' fields to describe a stand-alone file (i.e. any file that is not a packaged file).
- Name: The file name.
- SizeInBytes: The size in Bytes of the volume of data contained in the granule. Bytes are defined as eight bits. Please use this element in place of or inclusive with the Size element. The issue with the size element is that if CMR data providers use a unit other than Bytes, end users don't know how the granule size was calculated. For example, if the unit was MegaBytes, the size could be calculated by using 1000xE2 Bytes (MegaBytes) or 1024xE2 Bytes (mebibytes). Therefore, there is no systematic way to know the actual size of a granule by using the granule metadata record.
- Size: The size of the volume of data contained in the granule. Please use the SizeInBytes element either in place of this one or inclusive of this one. The issue with the size element is that if CMR data providers use a unit other than Bytes, end users don't know how the granule size was calculated. For example, if the unit was MegaBytes, the size could be calculated by using 1000xE2 Bytes (MegaBytes) or 1024xE2 Bytes (mebibytes) and therefore there is no systematic way to know the actual size of a granule by using the granule metadata record.
- Size Unit: The file size unit (must be selected from the following: KB, MB, GB, TB, PB, NA)
- Format: The file format. It is strongly recommended that the format be selected from the GCMD Granule Data Format vocabulary list in order to ensure consistent use of data formats across the CMR.
- Format Type: Allows the provider to state whether the file is in its native format or another supported format (must be selected from the following: Native, Supported, NA)
- Mime Type: The mime type of the resource. It is recommended that the mime type be selected from the KMS controlled list of mime types.
- Checksum Value: Allows the provider to provide the checksum value for the file.
- Checksum Algorithm: The name of the algorithm used to calculate the checksum. This allows the user to re-calculate the checksum to verify the integrity of the downloaded data. The checksum algorithm should be selected from a controlled list of algorithm names.
Use the 'FilePackageType' fields to describe a packaged file (e.g. a folder, a zipped file, etc.). These are identical to the 'FileType' fields with two exceptions:
- There is no option to provide the "Format Type" since this information is not applicable to a packaged file.
- There is a sub-field called "Files" - this refers back to the 'FileType' element which can be used to list the details of the individual files contained within the file package.
FilePackageType fields:
- Name: The file name of the package file.
- SizeInBytes: The size in Bytes of the volume of data contained in the granule. Bytes are defined as eight bits. Please use this element in place of or inclusive with the Size element. The issue with the size element is that if CMR data providers use a unit other than Bytes, end users don't know how the granule size was calculated. For example, if the unit was MegaBytes, the size could be calculated by using 1000xE2 Bytes (MegaBytes) or 1024xE2 Bytes (mebibytes) and therefore there is no systematic way to know the actual size of a granule by using the granule metadata record.
- Size: The size of the volume of data contained in the granule. Please use the SizeInBytes element either in place of this one or inclusive of this one. The issue with the size element is that if CMR data providers use a unit other than Bytes, end users don't know how the granule size was calculated. For example, if the unit was MegaBytes, the size could be calculated by using 1000xE2 Bytes (MegaBytes) or 1024xE2 Bytes (mebibytes) and therefore there is no systematic way to know the actual size of a granule by using the granule metadata record.
- Size Unit: The file size unit (must be selected from the following: KB, MB, GB, TB, PB, NA)
- Format: The file format. It is strongly recommended that the format be selected from the GCMD Granule Data Format vocabulary list in order to ensure consistent use of data formats across the CMR.
- Mime Type: The mime type of the resource. It is recommended that the mime type be selected from the KMS controlled list of mime types.
- Checksum Value: Allows the provider to provide the checksum value for the package file.
- Checksum Algorithm: The name of the algorithm used to calculate the checksum. This allows the user to re-calculate the checksum to verify the integrity of the downloaded data. The checksum algorithm should be selected from a controlled list of algorithm names.
- Files: List the information for all of the files contained in the file package using the 'FileType' fields (described above).
Examples:
Example 1: Single (unpackaged) file | Example 2: Package file containing 2 files |
---|---|
Name: Mongu_bulk_stable_isotope SizeInBytes: 2000 Size: 2 SizeUnit: KB Format: CSV FormatType: Native MimeType: text/csv ChecksumValue: 58b438495b4582d8483018bfb2f4677f ChecksumAlgorithm: MD5 | Name: modis_ba_500m_2000-09.zip SizeInBytes: 3331000 Size: 3331 SizeUnit: KB Format: zip MimeType: application/zip ChecksumValue: f3aa3adc ChecksumAlgorithm: Adler-32 Files: [ Name: modis_ba_500m_2000-09.dsr SizeInBytes: 3000 Size: 3 SizeUnit: KB Format: ASCII FormatType: Native MimeType: text/plain ChecksumValue: 3c7e8ae0 ChecksumAlgorithm: Adler-32 ____ Name: modis_ba_500m_2000-09 SizeInBytes: 147048000 Size: 147048 SizeUnit: KB Format: GeoTIFF FormatType: Native MimeType: image/tiff ChecksumValue: aaa123bc ChecksumAlgorithm: Adler-32 ] |
Element Specification
The Archive And Distribution Information element is optional for UMM-G (Cardinality: 0..*)
Model | Element | Type | Constraints | Required? | Cardinality | Notes | |
---|---|---|---|---|---|---|---|
Use the below 'FileType' fields to describe an individual file. This may be a stand-alone file or a file contained within a package file. To describe a packaged file, use the 'FilePackageType' fields specified in the next section - Cardinality: 0..* Note: if the 'FileType' elements are nested under the 'FilePackageType' - then "Files" will be added to the element path between 'ArchiveAndDistributionInformation' and the element name. E.g. DataGranule/ArchiveAndDistributionInformation/Name VS DataGranule/ArchiveAndDistributionInformation/Files/Name | |||||||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Name | String | 1 - 1024 characters | Yes, if applicable | 1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/SizeInBytes | Number | n/a | No | 0..1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Size | Number | n/a | No | 0..1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/SizeUnit | Enumeration | KB MB GB TB PB NA | No | 0..1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Format | String | 1 - 80 characters | No | 0..1 | It is required that the format be selected from the GCMD Granule Data Format vocabulary list (CSV) in order to ensure consistent use of data formats across the CMR. | |
UMM-G | DataGranule/ArchiveAndDistributionInformation/FormatType | Enumeration | Native Supported NA | No | 0..1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/MimeType | Enumeration | application/json application/xml application/x-netcdf application/x-hdfeos application/gml+xml application/vnd.google-earth.kml+xml application/vnd.opendap.dap4.dmrpp+xml image/gif image/tiff image/bmp text/csv text/xml application/pdf application/x-hd application/x-hdf5 application/octet-stream application/vnd.google-earth.kmz image/jpeg image/png image/vnd.collada+xml text/html text/plain application/zip application/gzip application/tar application/tar+gzip application/tar+zip Not provided | No | 0..1 | There is a mime type enumeration in the schema; however, a more comprehensive list is available in the KMS (JSON). | |
UMM-G | DataGranule/ArchiveAndDistributionInformation/Checksum/Value | String | 1 - 128 characters | Yes, if Checksum is used | 1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Checksum/Algorithm | Enumeration | Adler-32 BSD checksum Fletcher-32 Fletcher-64 MD5 POSIX SHA-1 SHA-2 SHA-256 SHA-384 SHA-512 SM3 SYSV | Yes, if Checksum is used | 1 | ||
Use the 'FilePackageType' fields to describe a packaged or zip file. Then use the 'FileType' elements (described above) to populate the last field (DataGranule/ArchiveAndDistributionInformation/Files) - Cardinality: 0..* | |||||||
UMM-G | DataGranule/ArchiveAndDistributionInformation//Name | String | 1 - 1024 characters | Yes, if applicable | 1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/SizeInBytes | Number | n/a | No | 0..1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Size | Number | n/a | No | 0..1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/SizeUnit | Enumeration | KB MB GB TB PB NA | No | 0..1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Format | Enumeration | ASCII BINARY BMP BUFR CSV DMRPP GEOTIFF GIF GEOTIFFINT16 GEOTIFFFLOAT32 GRIB GZIP HDF4 HDF5 HDF-EOS2 HDF-EOS5 HTML ICARTT JPEG JSON KML NETCDF-3 NETCDF-4 NETCDF-CF PNG PNG24 TAR TIFF XLSX XML ZIP Not provided | 1 - 80 characters | No | 0..1 | It is strongly recommended required that the format be selected from the GCMD Granule Data Format vocabulary list (CSV) in order to ensure consistent use of data formats across the CMR. (Note: there is a data format list in the schema, however, the GCMD keywords should be referenced as the authoritative list). |
UMM-G | DataGranule/ArchiveAndDistributionInformation/MimeType | Enumeration | application/json application/xml application/x-netcdf application/x-hdfeos application/gml+xml application/vnd.google-earth.kml+xml application/vnd.opendap.dap4.dmrpp+xml image/gif image/tiff image/bmp text/csv text/xml application/pdf application/x-hd application/x-hdf5 application/octet-stream application/vnd.google-earth.kmz image/jpeg image/png image/vnd.collada+xml text/html text/plain application/zip application/gzip application/tar application/tar+gzip application/tar+zip Not provided | No | 0..1 | There is a mime type enumeration in the schema, however, a more comprehensive list is available in the KMS. | |
UMM-G | DataGranule/ArchiveAndDistributionInformation/Checksum/Value | String | 1 - 128 characters | Yes if Checksum is used | 1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Checksum/Algorithm | Enumeration | Adler-32 BSD checksum Fletcher-32 Fletcher-64 MD5 POSIX SHA-1 SHA-2 SHA-256 SHA-384 SHA-512 SM3 SYSV | Yes if Checksum is used | 1 | ||
UMM-G | DataGranule/ArchiveAndDistributionInformation/Files | FileType | n/a | No | 0..* | Repeat the 'FileType' fields as many times as necessary to describe each file contained within the file package. |
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 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
Dialect Mappings
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10Only a couple of the Archive And Distribution Information fields map to ECHO 10. Both of these fields are optional (Cardinality: 0..1)
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSArchive And Distribution Information is optional in ISO-19115-2 (Cardinality: 0..*)
|
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
ISO 19115-2 SMAPThere is currently no mapping between UMM-G and ISO 19115-2 SMAP for Archive And Distribution Information.
|
UMM Migration
NoneExcerpt | ||
---|---|---|
| ||
Future MappingsThere are currently no future mappings planned for UMM-G. |
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.6.0 | 11/4/2019 | Added SizeInBytes so that a CMR data provider can add the size in Bytes so that there is no confusion of what the actual file size is. Increased the length of Name in FileType and FilePackageType elements to 1024. |
1.5.0 | 01/30/2019 | No changes were made for Archive And Distribution Information during the transition from version 1.4.0 to 1.5.0. |
1.4.0 | 08/01/2018 | No changes were made for Archive And Distribution Information from version 1.3.0 to 1.4.0. |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 03/13/2019 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |