Page History
Table of Contents | ||
---|---|---|
|
Element Description
The Data Center metadata element is used to identify and provide contact information for the organization responsible for originating, processing, archiving, and/or distributing the dataset being described in the metadata.
Contact information for an individual or a group affiliated with the data center can also be provided. Information about an individual should be provided in the DataCenter/ContactPerson sub-fields. Information about a group should be provided in the DataCenter/ContactGroup sub-fields.
There are 5 options for providing contact information in the UMM:
Details for each of these options are provided on a separate wiki page. This wiki page describes details for option 1 (Data Center).
Best Practices
Each Data Center listed in the metadata must be affiliated with a Role. Providing a Role for the Data Center is required and must be selected from a controlled vocabulary list. There are four options for Role:
- ARCHIVER: the organization responsible for storing the data. This role should be selected when listing the name of a NASA Distributed Active Archive Center (DAAC).
- DISTRIBUTOR: the organization responsible for distributing the data. The archiver and distributor will often be the same organization. In this case, both 'ARCHIVER' and 'DISTRIBUTOR' can be specified for the same data center.
- ORIGINATOR: the organization responsible for producing the data.
- PROCESSOR: the organization responsible for processing the data. Not all data is necessarily processed. Examples of processing include: converting raw data into level 1 data; re-gridding or re-projecting data to make a higher level product; combining multiple data products to derive a model output.
The same data center may be responsible for multiple roles. In this case, multiple roles may be assigned to the same data center.
Other Data Center metadata fields include:
Short Name: The name of the Data Center (abbreviated version). Providing a Data Center Short Name is required. The Data Center Short Name must be selected from a controlled vocabulary maintained in the Keyword Management System (KMS). A list of valid Data Center keywords can be found here: https://gcmd.earthdata.nasa.gov/kms/concepts/concept_scheme/providers?format=csv Note that the Short Name should be selected from the "Short_Name" column in the keyword list.
Long Name: The name of the Data Center. Providing a Data Center Long Name is optional, however, it is recommended that a long name be provided if one exists in the keyword list since short names are often comprised of acronyms. A list of valid Data Center keywords can be found here: https://gcmd.earthdata.nasa.gov/kms/concepts/concept_scheme/providers?format=csv Note that the Long Name should be selected from the "Long_Name" column in the keyword list.
Uuid: The uuid is the unique identifier associated with the Data Center name in the controlled vocabulary keyword list. Providing the uuid is completely optional. The uuid can be found in the Data Centers keyword list in the "UUID" column.
Contact Information: Any relevant contact information for the data center can be provided in the Contact Information fields. Providing contact information is optional, however, it is recommended that at least one piece of contact information (such as a link, email or phone number) be provided. Some examples of contact information include: phone number, email, fax, related links, service hours, and contact instructions. See the element specification table below for full details.
Example:
Role: ARCHIVER, DISTRIBUTOR
ShortName: NASA/MSFC/GHRC
LongName: Global Hydrology Resource Center, Marshall Space Flight Center, NASA
ContactInformation/RelatedURL/Url: https://ghrc.nsstc.nasa.gov/home/
ContactInformation/RelatedURLs/UrlContentType: DataCenterURL
ContactInformation/RelatedURLs/Type: HOME PAGE
ContactInformation/RelatedURLs/Description: The Global Hydrology Resource Center (GHRC) website's home page
ContactInformation/ServiceHours: 8 AM to 5 PM Central Time
ContactInformation/ContactMechanism/Type: Email
ContactInformation/ContactMechanism/Value: support-ghrc@earthdata.nasa.gov
ContactInformation/ContactMechanism/Type: Phone
ContactInformation/ContactMechanism/Value: 256-961-7932
Element Specification
Data Centers is a required element. At least 1 Data Center must be provided. Multiple Data Centers may also be provided, if necessary (Cardinality: 1..*).
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | DataCenters/Roles | Enumeration | DISTRIBUTOR ORIGINATOR ARCHIVER PROCESSOR | n/a | Yes | 1..* | Location of the enumeration list in the UMM-Common schema: https://git.earthdata.nasa.gov/projects/EMFD/repos/unified-metadata-model/browse/collection/v1.10/umm-cmn-json-schema.json#1435 Note: enumerations are case sensitive. This means that the Role must be provided in all caps to pass validation. |
UMM-Common | DataCenter/ShortName | String | Data Center Short Name Keywords | KMS controlled | Yes | 1 | |
UMM-Common | DataCenter/LongName | String | Data Center Long Name Keywords | KMS controlled | No | 0..1 | It is highly recommended that a Data Center Long Name be provided if one exists in the keyword list. |
UMM-Common | DataCenter/Uuid | Number | Data Center UUID | KMS controlled | No | 0..1 | |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Url | String | n/a | n/a | Yes, if applicable | 1..* | Providing a URL is optional. If information is provided in any of the 'RelatedURLs' metadata fields, then the URL must be provided. This URL should link to the home page of the Data Center's website. |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/UrlContentType | Enumeration | DataCenterURL | n/a | Yes, if applicable | 1 | This field is only required if a URL is provided. URL Content Types are controlled as an enumeration list in the UMM-Common schema. The only valid option for Data Center Related URLs is "DataCenterURL". |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Type | String | HOME PAGE | KMS controlled | Yes, if applicable | 1 | This field is only required if a URL is provided. Related URL Types are controlled by GCMD vocabulary (URL Content Types). The only valid keyword option for a Data Center Related URL is "HOME PAGE". |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Description | String | n/a | 1 - 1024 characters | No | 0..1 | It is strongly recommended that a description be provided for each URL. |
UMM-Common | DataCenters/ContactInformation/ServiceHours | String | n/a | 1 - 1024 characters | No | 0..1 | The time zone should be specified. |
UMM-Common | DataCenters/ContactInformation/ContactInstructions | String | n/a | 1 - 2048 characters | No | 0..1 | Supplemental/ special instructions on how or when to contact the data center. |
UMM-Common | DataCenters/ContactInformation/ContactMechanism/Type | Enumeration | Direct Line Fax Mobile Modem Primary TDD/TTY Phone Telephone U.S. toll free Other | n/a | Yes, if applicable | 1 | Providing a contact mechanism is optional. If provided, the Type is required and must be selected from the ContactMechanismType enumeration list found in the UMM-Common schema. The actual value (e.g. the phone number or email) should be provided in the Value field (see below). Multiple contact mechanisms can be provided for each data center (Cardinality 0..*). |
UMM-Common | DataCenters/ContactInformation/ContactMechanism/Value | String | n/a | 1 - 1024 characters | Yes, if applicable | 1 | Providing a contact mechanism is optional. If provided, a Value is required (e.g. if the contact mechanism type is 'Email' then the actual email would go in this field). Multiple contact mechanisms can be provided for each data center (Cardinality 0..*). |
UMM-Common | DataCenters/ContactInformation/Address/StreetAddresses | String | n/a | 1 - 1024 characters | No | 0..* | Multiple Street Addresses may be provided to indicate multiple lines in a street address. |
UMM-Common | DataCenters/ContactInformation/Address/City | String | n/a | 1 - 100 characters | No | 0..1 | |
UMM-Common | DataCenter/ContactInformation/Address/StateProvince | String | n/a | 1 - 100 characters | No | 0..1 | |
UMM-Common | DataCenter/ContactInformation/Address/PostalCode | String | n/a | 1 - 20 characters | No | 0..1 | |
UMM-Common | DataCenter/ContactInformation/Address/Country | String | n/a | 1 - 100 characters | No | 0..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).
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 | ||
---|---|---|
| ||
<> |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10Data Centers is a required element. At least 1 Data Center must be provided. Multiple Data Centers may also be provided, if necessary (Cardinality: 1..*).
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10In ECHO 10, it is required that either Processing Center OR Archive Center be provided. It is not necessary to provide both. If a data center name is provided in the 'Contacts' section (with an appropriate GCMD Data Center Short Name and 'Type' value) then it will be mapped to the UMM 'Data Centers' element.
The ECHO10 "Contacts/Contact/Role" field is not enumeration controlled, however, the equivalent field in the UMM is enumeration controlled. The below table summarizes how values provided in the ECHO10 field "Contacts/Contact/Role" are converted to the UMM field "DataCenters/Roles". Note that the value provided in the ECHO10 field "Contacts/Contact/Role" will automatically be converted to all lower case and then mapped accordingly. If the ECHO10 value does not match any of the options provided below, then it will automatically be mapped to "ARCHIVER" by the UMM.
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDSData Centers is a not a required element in ISO 19115-2 MENDS. Multiple Data Centers may also be provided, if necessary.
N/A Example Mapping
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 SMAPData Centers is a not a required element in ISO 19115-2 SMAP. Multiple Data Centers may also be provided, if necessary.
N/A Example Mapping
|
UMM Migration
None
Excerpt | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
Future Mappings
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | No changes were made for Data Centers during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for Data Centers during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Data Centers during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Data Centers during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Data Centers during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Data Centers during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Data Centers during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for Data Centers during the transition from version 1.12.0 to 1.13.0 |
1.12.0 | 01/22/2019 | No changes were made for Data Centers during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No changes were made for Data Centers during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 05/02/2018 | No changes were made for Data Centers during the transition from version 1.9.0 to 1.10.0. |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 09/07/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |