Element Description
The Contact Person metadata element is used to provide contact information for an individual associated with the dataset.
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 4 (Contact Person).
Note that the Contact Person element can also be nested under the Data Center element. As a rule of thumb, if an individual is affiliated with a Data Center, then it is recommended that their contact info be provided under DataCenter/ContactPerson. If the individual is not affiliated with a particular Data Center, then their contact information can be provided here.
Best Practices
Each Contact Person listed in the metadata must be affiliated with a Role. Providing a Role for the Contact Person is required and must be selected from a controlled vocabulary list. Multiple Roles may be assigned to the same person, if necessary. There are seven options for Role:
- DATA CENTER CONTACT: an individual affiliated with the dataset. If the individual is affiliated with a Data Center, then it is recommended that their contact information be provided under DataCenter/ContactPerson.
- TECHNICAL CONTACT: an individual with technical (expert) knowledge about the data product.
- SCIENCE CONTACT: an individual with technical (expert) knowledge about the science principals involved in deriving the data product.
- INVESTIGATOR: a person involved in the creation of the data product. For instance, this might be the principal investigator (PI) or co-PI of the project responsible for creating the data product.
- METADATA AUTHOR: a person responsible for creating and/or maintaining the collection level and/or granule level metadata records associated with the data product.
- USER SERVICES: an individual representative of the user services office at the organization responsible for archiving, distributing, originating or processing the data. If the individual is affiliated with a Data Center, then it is recommended that their contact information be provided under DataCenter/ContactPerson.
- SCIENCE SOFTWARE DEVELOPMENT: a person with knowledge of software specifically developed for the data product.
Other Contact Person metadata fields include:
Non Data Center Affiliation: This field can be used to specify the name of the organization the Contact Person is affiliated with. Providing a Non Data Center Affiliation is optional, however, is it recommended that this information be provided.
First Name: The first name of the contact person. Providing a first name is optional.
Middle Name: The middle name of the contact person. Providing a middle name is optional.
Last Name: The last name of the contact person. Providing a last name is required.
Contact Information: Any relevant contact information for the contact person. 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.
Examples:
Role: TECHNICAL CONTACT
Non Data Center Affiliation: University of Alabama in Huntsville Earth System Science Center
FirstName: Bob
LastName: Smith
ContactInformation/ContactMechanism/Type: Email
ContactInformation/ContactMechanism/Value: email@email.com
Role: TECHNICAL CONTACT
Non Data Center Affiliation: UMD Laser Remote Sensing Laboratory
FirstName: J.
LastName: Blair
ContactInformation/ContactMechanism/Type: Email
ContactInformation/ContactMechanism/Value: email@email.com
ContactInformation/ContactMechanism/Type: Telephone
ContactInformation/ContactMechanism/Value: 301-444-4444
ContactInformation/ContactMechanism/Type: Fax
ContactInformation/ContactMechanism/Value: 301-555-5555
ContactInformation/Address/StreetAddresses: Laser Remote Sensing Laboratory, Code 694
ContactInformation/Address/StreetAddresses: NASA Goddard Space Flight Center
ContactInformation/Address/City: Greenbelt
ContactInformation/Address/StateProvince: MD
ContactInformation/Address/Country: USA
ContactInformation/Address/PostalCode: 20771
Element Specification
Providing a Contact Person is optional. An unlimited number of Contact Persons may be listed (Cardinality: 0..*)
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | ContactPerson/Roles | Enumeration | Data Center Contact Technical Contact Science Contact Investigator Metadata Author User Services Science Software Development | n/a | Yes, if applicable | 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.12/umm-cmn-json-schema.json#1440 |
UMM-Common | ContactPerson/NonDataCenterAffiliation | String | n/a | 1 - 1024 characters | No | 0..1 | |
UMM-Common | ContactPerson/FirstName | String | n/a | 1 - 255 characters | No | 0..1 | |
UMM-Common | ContactPerson/MiddleName | String | n/a | 1 - 255 characters | No | 0..1 | |
UMM-Common | ContactPerson/LastName | String | n/a | 1 - 255 characters | Yes, if applicable | 1 | If Contact Person information is provided, a Last Name is required. |
UMM-Common | ContactPerson/ContactInformation/ServiceHours | String | n/a | 1 - 1024 characters | No | 0..1 | The time zone should be specified. |
UMM-Common | ContactPerson/ContactInformation/ContactInstructions | String | n/a | 1 - 2048 characters | No | 0..1 | Supplemental/ special instructions on how or when to contact the contact person. |
UMM-Common | ContactPerson/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 | ContactPerson/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 | ContactPerson/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 | ContactPerson/ContactInformation/Address/City | String | n/a | 1 - 100 characters | No | 0..1 | |
UMM-Common | ContactPerson/ContactInformation/Address/StateProvince | String | n/a | 1 - 100 characters | No | 0..1 | |
UMM-Common | ContactPerson/ContactInformation/Address/PostalCode | String | n/a | 1 - 20 characters | No | 0..1 | |
UMM-Common | ContactPerson/ContactInformation/Address/Country | String | n/a | 1 - 100 characters | No | 0..1 | |
UMM-Common | ContactPerson/ContactInformation/RelatedURLs/Url | String | n/a | 1 - 1024 characters | Yes, if applicable | 1 | Providing a URL for a contact person is completely optional. If information is provided in any of the 'RelatedURLs' metadata fields, then the URL must be provided. |
UMM-Common | ContactPerson/ContactInformation/RelatedURLs/UrlContentType | Enumeration | DataContactURL | 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 Contact Person Related URLs is "DataContactURL" |
UMM-Common | ContactPerson/ContactInformation/RelatedURLs/Type | String | KMS controlled | HOME PAGE | 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 Contact Person Related URL is "HOME PAGE" |
UMM-Common | ContactPerson/ContactInformation/RelatedURLs/Description | String | n/a | 1 - 4000 characters | No | 0..1 | It is strongly recommended that a description be provided for each URL. |
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
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | No changes were made for Contact Person during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for Contact Person during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Contact Person during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Contact Person during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Contact Person during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Contact Person during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Contact Person during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for Contact Person during the transition from version 1.12.0 to 1.13.0 |
1.12.0 | 01/22/2019 | No changes were made for Contact Person during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No changes were made for Contact Person during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 05/02/2018 | No changes were made for Contact Person during the transition from version 1.9.0 to 1.10.0. |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 02/12/19 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |