Element Description
Note: This wiki page is a draft/ still in progress
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 data set being described in the metadata.
Contact information about an individual or a group affiliated with the data can also be provided. Information about an individual should be provided in the DataCenter/ContactPerson sub-fields. Please see the DataCenter/ContactPerson wiki page for details on the Contact Person metadata elements. Information about a group should be provided in the DataCenter/ContactGroup sub-fields. Please see the DataCenter/ContactGroup wiki page for details on the Contact Group metadata elements. Note that each contact person or group must be affiliated with a 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. The following is a (completely theoretical) example where a different Data Center is responsible for each role: A team from the University of Maryland is responsible for collecting raw data from an airborne sensor (ORIGINATOR). The raw data is sent to colleagues at Goddard Space Flight Center to be processed to level 1 data (PROCESSOR). It is ultimately decided that the NSIDC DAAC is the best place to archive the data (ARCHIVER). The USGS decides to harvest the data from the NSIDC DAAC and distribute it through their own data portal (DISTRIBUTOR).
Examples:
Element Specification
An unlimited amount of Data Centers may be listed (Cardinality: 1..*)
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | DataCenter/Roles | Enumeration | DISTRIBUTOR ORIGINATOR ARCHIVER | Yes | 1..* | ||
UMM-Common | DataCenter/ShortName | String | n/a | Yes | 1 | ||
UMM-Common | DataCenter/LongName | String | n/a | No | 0..1 | ||
UMM-Common | DataCenter/Uuid | Number | n/a | No | 0..1 | ||
UMM-Common | DataCenter/ContactInformation/RelatedURL | String | n/a | No | 0..1 | ||
UMM-Common | DataCenter/ContactInformation/ServiceHours | String | 1 - 1024 characters | No | 0..1 | ||
UMM-Common | DataCenters/ContactInformation/ContactInstructions | String | 1 - 2048 characters | No | 0..1 | ||
UMM-Common | DataCenter/ContactInformation/ContactMechanism | String | n/a | No | 0..* | ||
UMM-Common | DataCenter/ContactInformation/ContactMechanism/Type | Enumeration | PHONE | n/a | Yes | 1 | |
UMM-Common | DataCenter/ContactInformation/ContactMechanism/Value | String | 1 - 1024 characters | Yes | 1 | ||
UMM-Common | DataCenter/ContactInformation/Address/StreetAddresses | String | 1 - 1024 characters | No | 0..* | ||
UMM-Common | DataCenter/ContactInformation/Address/City | String | 1 - 100 characters | No | 0..1 | ||
UMM-Common | DataCenter/ContactInformation/Address/StateProvince | String | 1 - 100 characters | No | 0..1 | ||
UMM-Common | DataCenter/ContactInformation/Address/PostalCode | String | 1 - 20 characters | No | 0..1 | ||
UMM-Common | DataCenter/ContactInformation/Address/Country | String | 1 - 100 characters | No | 0..1 | ||
UMM-Common | DataCenters/ContactInformation/RelatedURLs/UrlContentType = DataCenterURL | String | 1 - 4000 characters | Yes | 1 | ||
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Type = HOME PAGE | String | URL Content Types | KMS controlled | Yes | 1 | |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/SubType | String | URL Content Types | KMS controlled | No | 0..1 | |
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Description | String | 1 - 1024 characters | No | 0..1 | ||
UMM-Common | DataCenters/ContactInformation/RelatedURLs/Url | String | n/a | Yes | 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).
Please see the expandable sections below for flowchart details.
Dialect Mappings
UMM Migration
None
Future Mappings
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | 5/2/2018 | <> |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 7/25/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |