Page History

Table of Contents

style	circle

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 required that the format value 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 required that the format value 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	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/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

title	CMR Validation

<>

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
Red = High Priority Finding	This element is categorized as highest priority when: Any of the information provided is incorrect for the granule. An invalid mime type is provided. The Data Format provided for the granule is incorrect. Required sub-fields are left blank (in this case, the only required sub-field is 'Name'). The Data Format provided is correct, however, it does not exactly match its entry in the GCMD Granule Data Format vocabulary list. E.g. providing 'netcdf4' versus 'netCDF-4' E.g. providing 'geo-tiff' versus 'GeoTIFF' The checksum algorithm provided does not align with a value in the enumeration list (Adler-32, BSD checksum, Fletcher-32, Fletcher-64, MD5, POSIX, SHA-1, SHA-2, SHA-256, SHA-384, SHA-512, SM3, SYSV).
Yellow = Medium Priority Finding	This element is categorized as medium priority when: None of the files contained in a packaged file are described or only some (but not all) of the files contained within a file package are described. No Data Format is provided. The Format provided is correct, but could be more specific. E.g. Providing 'ASCII' when the format should be 'CSV'
Blue = Low Priority Finding	This element is categorized as low priority when: The mime type field is left blank for service URLs.
Green = No Findings/Issues	The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Checks

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

Dialect Mappings

Expand

title	ECHO 10

ECHO 10

Only a couple of the Archive And Distribution Information fields map to ECHO 10. Both of these fields are optional (Cardinality: 0..1)

UMM-G Element	ECHO 10 Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
DataGranule/ArchiveAndDistributionInformation/SizeInBytes	DataGranule/DataGranuleSizeInBytes	Double	N/A	No	0..1	Note that the size unit is assumed to be in Bytes
DataGranule/ArchiveAndDistributionInformation/Size	DataGranule/SizeMBDataGranule	Double	N/A	No	0..1	Note that the size unit is assumed to be in MB
DataGranule/ArchiveAndDistributionInformation/Checksum/Value	DataGranule/Checksum/Value	String	1-128 characters	Yes if Checksum is used.	1
DataGranule/ArchiveAndDistributionInformation/Checksum/Algorithm	DataGranule/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
DataGranule/ArchiveAndDistributionInformation/Format	DataFormat	String	1 - 80 characters	No	0..1	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.

Example Mapping

Section

Column

width	50%

ECHO 10

No Format

<DataGranule>
  <DataGranuleSizeInBytes>10000</DataGranuleSizeInBytes>
  <SizeMBDataGranule>10</SizeMBDataGranule>
  <Checksum>
    <Value>E51569BF48DD0FD0640C6503A46D4753</Value>
    <Algorithm>MD5</Algorithm>
  </Checksum>
</DataGranule>
...
<DataFormat>NETCDF-4</DataFormat>
...

Column

width	50%

UMM

No Format

"DataGranule": {
  "ArchiveAndDistributionInformation": [{
    "Name": "Not provided",
    "SizeInBytes": 10000000,
    "Size": 10,
    "SizeUnit": "MB",
    "Format": "NETCDF-4",
    "Checksum": {
      "Value": "E51569BF48DD0FD0640C6503A46D4753",
      "Algorithm": "MD5"
    }
  }]
}

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

Archive And Distribution Information is optional in ISO-19115-2 (Cardinality: 0..*)

ISO Path	Type	Notes
/gmi:MI_Metadata/gmd:describes/gmx:MX_DataSet [=> [=> /gmd:has/ [=> /gmx:dataFile/gmx:MX_DataFile id= {the actual package file name} Only use the id attribute if the file is a package file. [=> /gmx:dataFile xlink:href="#{the actual package file name this file belongs to."}/gmx:MX_DataFile [==> Only use the xlink:href="#..." attribute if the file belongs to a package file. [==>/gmx:fileName/gmx:FileName {the actual package file name}	String	Maps to the UMM-G element "Name"
[==> /gmx:fileDescription/gco:CharacterString = "Size: " {the actual size}	String	Maps to the UMM-G element "Size"
[==> /gmx:fileDescription/gco:CharacterString = "SizeUnit: " {the actual size unit}	String	Maps to the UMM-G element "SizeUnit"
[==> /gmx:fileFormat/gmd:MD_Format/gmd:name/gco:CharacterString {the actual format} [==> /gmx:fileFormat/gmd:MD_Format/gmd:version gco:nilReason="unknown"	String	Maps to the UMM-G element "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.
[==> /gmx:fileType/gmx:MimeFileType type="{actual MimeType}" {actual MimeType}	String	Maps to the UMM-G element "MimeType"
[==> /gmx:fileDescription/gco:CharacterString = "ChecksumValue: " {the actual checksum}	String	Maps to the UMM-G element "ChecksumValue"
[==> /gmx:fileDescription/gco:CharacterString = "ChecksumAlgorithm: " {the actual algorithm}	String	Maps to the UMM-G element "ChecksumAlgorithm"
[==>/gmx:fileName/gmx:FileName {the actual package file name}	String	Maps to the UMM-G element "Files/Name"
[==> /gmx:fileDescription/gco:CharacterString = "Size: " {the actual size}	String	Maps to the UMM-G element "Files/Size"
[==> /gmx:fileDescription/gco:CharacterString = "SizeUnit: " {the actual size unit}	String	Maps to the UMM-G element "Files/SizeUnit"
[==> /gmx:fileFormat/gmd:MD_Format/gmd:name/gco:CharacterString {the actual format} [==> /gmx:fileFormat/gmd:MD_Format/gmd:version gco:nilReason="unknown"	String	Maps to the UMM-G element "Files/Format"
[==> /gmx:fileType/gmx:MimeFileType type="{actual MimeType}" {actual MimeType}	String	Maps to the UMM-G element "Files/MimeType"
[==> /gmx:fileDescription/gco:CharacterString = "ChecksumValue: " {the actual checksum}	String	Maps to the UMM-G element "Files/ChecksumValue"
[==> /gmx:fileDescription/gco:CharacterString = "ChecksumAlgorithm: " {the actual algorithm}	String	Maps to the UMM-G element "Files/ChecksumAlgorithm"
[==> /gmx:fileDescription/gco:CharacterString = "FormatType: " {the actual format type}	String	Maps to the UMM-G element "Files/FormatType"

Example Mapping

Section

Column

width	50%

ISO 19115-2 MENDS

No Format

   <!-- This section describes the UMM-G DataGranule ArchiveAndDistributionInformation section where the files are listed. -->
   <gmd:describes>
      <gmx:MX_DataSet>
         <gmd:has/>
         <!-- This file is a standalone file that happens to be a zip file. Use the id={package file name} to state that this file a package file so that the child files can be linked to it. If the id is not present then it is assumed that this is a regular file.-->
         <gmx:dataFile>
            <gmx:MX_DataFile id="GranuleZipFile">
               <gmx:fileName>
                  <gmx:FileName>GranuleZipFile</gmx:FileName>
               </gmx:fileName>
               <gmx:fileDescription>
                  <gco:CharacterString>SizeInBytes: 23000 Size: 23 SizeUnit: KB ChecksumValue: E51569BF48DD0FD0640C6503A46D4753 ChecksumAlgorithm: MD5 Description: Some wanted description</gco:CharacterString>
               </gmx:fileDescription>
               <gmx:fileType>
                  <gmx:MimeFileType type="application/zip">application/zip</gmx:MimeFileType>
               </gmx:fileType>
               <gmx:fileFormat>
                  <gmd:MD_Format>
                     <gmd:name>
                        <gco:CharacterString>ZIP</gco:CharacterString>
                     </gmd:name>
                     <gmd:version gco:nilReason="unknown"/>
                  </gmd:MD_Format>
               </gmx:fileFormat>
            </gmx:MX_DataFile>
         </gmx:dataFile>
         <!-- This file exists in the above defined ZIP file. Use the xlink:href="#{package file name}" to state that this file is in the zip file.
              If this isn't used then it is assumed that this file is standalone.-->
         <gmx:dataFile xlink:href="#GranuleZipFile">
            <gmx:MX_DataFile>
               <gmx:fileName>
                  <gmx:FileName>GranuleFileName1</gmx:FileName>
               </gmx:fileName>
               <gmx:fileDescription>
                  <gco:CharacterString>SizeInBytes: 10000 Size: 10 SizeUnit: KB ChecksumValue: E51569BF48DD0FD0640C6503A46D4754 ChecksumAlgorithm: MD5 FormatType: Native Description: Some file description</gco:CharacterString>
               </gmx:fileDescription>
               <gmx:fileType>
                  <gmx:MimeFileType type="application/x-netcdf">application/x-netcdf</gmx:MimeFileType>
               </gmx:fileType>
               <gmx:fileFormat>
                  <gmd:MD_Format>
                     <gmd:name>
                        <gco:CharacterString>NETCDF-4</gco:CharacterString>
                     </gmd:name>
                     <gmd:version gco:nilReason="unknown"/>
                  </gmd:MD_Format>
               </gmx:fileFormat>
            </gmx:MX_DataFile>
         </gmx:dataFile>
         <!-- This file exists in the above defined ZIP file. Use the xlink:href=#{id} to state that this file is in the zip file.
              If this isn't used then it is assumed that this file is standalone.-->
         <gmx:dataFile xlink:href="#GranuleZipFile">
            <gmx:MX_DataFile>
               <gmx:fileName>
                  <gmx:FileName>GranuleFileName2</gmx:FileName>
               </gmx:fileName>
               <gmx:fileDescription>
                  <gco:CharacterString>SizeInBytes 1000 Size: 1 SizeUnit: KB FormatType: NA</gco:CharacterString>
               </gmx:fileDescription>
               <gmx:fileType>
                  <gmx:MimeFileType type="text/plain">text/plain</gmx:MimeFileType>
               </gmx:fileType>
               <gmx:fileFormat>
                  <gmd:MD_Format>
                     <gmd:name>
                        <gco:CharacterString>ASCII</gco:CharacterString>
                     </gmd:name>
                     <gmd:version gco:nilReason="unknown"/>
                  </gmd:MD_Format>
               </gmx:fileFormat>
            </gmx:MX_DataFile>
         </gmx:dataFile>
         <!-- This file is a standalone file and not part of the zip file.-->
         <gmx:dataFile>
            <gmx:MX_DataFile>
               <gmx:fileName>
                  <gmx:FileName>SupportedGranuleFileNotInPackage</gmx:FileName>
               </gmx:fileName>
               <gmx:fileDescription>
                  <gco:CharacterString>SizeInBytes: 11000 Size: 11 SizeUnit: KB ChecksumValue: E51569BF48DD0FD0640C6503A46D4755 ChecksumAlgorithm: MD5 FormatType: Supported</gco:CharacterString>
               </gmx:fileDescription>
               <gmx:fileType>
                  <gmx:MimeFileType type="application/x-netcdf">application/x-netcdf</gmx:MimeFileType>
               </gmx:fileType>
               <gmx:fileFormat>
                  <gmd:MD_Format>
                     <gmd:name>
                        <gco:CharacterString>NETCDF-CF</gco:CharacterString>
                     </gmd:name>
                     <gmd:version gco:nilReason="unknown"/>
                  </gmd:MD_Format>
               </gmx:fileFormat>
            </gmx:MX_DataFile>
         </gmx:dataFile>
      </gmx:MX_DataSet>
   </gmd:describes>

Column

width	50%

UMM

No Format

  "DataGranule": {
    "ArchiveAndDistributionInformation": [{
      "Name": "GranuleZipFile",
      "SizeInBytes": 23000,
      "Size": 23,
      "SizeUnit": "KB",
      "Format": "ZIP",
      "MimeType": "application/zip",
      "Checksum": {
        "Value": "E51569BF48DD0FD0640C6503A46D4753",
        "Algorithm": "MD5"
      },
      "Files": [{
        "Name": "GranuleFileName1",
        "SizeInBytes": 10000,
        "Size": 10,
        "SizeUnit": "KB",
        "Format": "NETCDF-4",
        "MimeType": "application/x-netcdf",
        "FormatType": "Native",
        "Checksum": {
          "Value": "E51569BF48DD0FD0640C6503A46D4754",
          "Algorithm": "MD5"
        }
      }, {
        "Name": "GranuleFileName2",
        "SizeInBytes": 1000,
        "Size": 1,
        "SizeUnit": "KB",
        "Format": "ASCII",
        "MimeType": "text/plain",
        "FormatType": "NA"
      }]
    }, {
      "Name": "SupportedGranuleFileNotInPackage",
      "SizeInBytes": 11000,
      "Size": 11,
      "SizeUnit": "KB",
      "Format": "NETCDF-CF",
      "FormatType": "Supported",
      "MimeType": "application/x-netcdf",
      "Checksum": {
        "Value": "E51569BF48DD0FD0640C6503A46D4755",
        "Algorithm": "MD5"
      }
    }],

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

There is currently no mapping between UMM-G and ISO 19115-2 SMAP for Archive And Distribution Information.

Specification	Path	Type	Notes
ISO 19115-2 SMAP	N/A	N/A	There is currently no mapping between UMM-G and ISO 19115-2 SMAP for Archive And Distribution Information.

Example Mapping

Section

Column

width	50%

ISO 19115-2 SMAP

No Format
N/A

Column

width	50%

UMM

No Format
N/A

UMM Migration

None

Excerpt

hidden	true

Future Mappings

There are currently no future mappings planned for UMM-G.

History

UMM Versioning

Version	Date	What Changed
1.6.4	10/6/2021	Changed format definition to use KMS instead of enumerations.
1.6.3	5/3/2021	No changes were made for Archive And Distribution Information during the transition from version 1.6.2 to 1.6.3.
1.6.2	4/21/2021	No changes were made for Archive And Distribution Information during the transition from version 1.6.1 to 1.6.2.
1.6.1	6/5/2020	Added application/vnd.opendap.dap4.dmrpp+xml to the RelatedUrl Mime-Types and added dmrpp to the formats.
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	Ingrid Garcia-Solera

Page tree

Versions Compared

Old Version 37

New Version Current

Key

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 SMAP

UMM Migration

Future Mappings

History

UMM Versioning

ARC Documentation