Data Center - Contact Person

Element Description

The Data Center/ Contact Person metadata element is used to provide contact information for an individual associated with the dataset.

Note that the Contact Person metadata element being described on this wiki page is nested under the Data Center element. Contact Person information can also be provided separate from the Data Center element (i.e. for a person unaffiliated with a data center)—see the Contact Person wiki page for details.

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 2 (Data Center/Contact Person).

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. There are seven options for Role:

DATA CENTER CONTACT: an individual affiliated with a data center. This should be the same data center listed in the required 'Data Center' element.
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 record(s) associated with the data product.
USER SERVICES: an individual representative of the user services office at the data center responsible for archiving, distributing, originating or processing the data.
SCIENCE SOFTWARE DEVELOPMENT: a person with knowledge of software(s) specifically developed for the data product.

The same contact person may be responsible for multiple roles. In this case, multiple roles may be assigned to the same contact person.

Other Contact Person metadata fields include:

Non Data Center Affiliation: The Contact Person metadata elements described on this wiki page are sub-fields of the Data Center metadata element. Sometimes the Contact Person listed is not affiliated with the Data Center. This field can be used to specify the name of the organization the Contact Person is affiliated with if it differs from the Data Center. Providing a Non Data Center Affiliation is optional, however, is it recommended that this information be provided when the affiliation of the Contact Person differs from the Data Center they are listed under. Alternatively, if the individual is not affiliated with a particular Data Center, their contact information can be provided in the Contact Person metadata elements instead (these are not nested under a Data Center).

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: USER SERVICES

FirstName: Colleen

LastName: Schroeder

ContactInformation/ContactMechanism/Type: Email

ContactInformation/ContactMechanism/Value: podaac@podaac.jpl.nasa.gov

Role: METADATA AUTHOR

LastName: Ostrenga

ContactInformation/ContactMechanism/Type: Email

ContactInformation/ContactMechanism/Value: dana.ostrenga@nasa.gov

ContactInformation/ContactMechanism/Type: Telephone

ContactInformation/ContactMechanism/Value: 301-614-5475

ContactInformation/ContactMechanism/Type: Fax

ContactInformation/ContactMechanism/Value: 301-614-5268

ContactInformation/Address/StreetAddresses: Code 610.2 Bldg 32 Rm S151

ContactInformation/Address/StreetAddresses: NASA Goddard Space Flight Center

ContactInformation/Address/City: Greenbelt

ContactInformation/Address/StateProvince: MD

ContactInformation/Address/Country: USA

ContactInformation/Address/PostalCode: 21230

Element Specification

Providing a DataCenter/ContactPerson is optional. An unlimited number of Contact Persons may be listed under Data Center (Cardinality: 0..*)

Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality	Notes
UMM-Common	DataCenters/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.10/umm-cmn-json-schema.json#1440
UMM-Common	DataCenters/ContactPerson/NonDataCenterAffiliation	String	n/a	1 - 1024 characters	No	0..1
UMM-Common	DataCenters/ContactPerson/FirstName	String	n/a	1 - 255 characters	No	0..1
UMM-Common	DataCenters/ContactPerson/MiddleName	Number	n/a	1 - 255 characters	No	0..1
UMM-Common	DataCenters/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	DataCenters/ContactPerson/ContactInformation/ServiceHours	String	n/a	1 - 1024 characters	No	0..1	The time zone should be specified.
UMM-Common	DataCenters/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	DataCenters/ContactPerson/ContactInformation/ContactMechanism/Type	Enumeration	Direct Line Email Facebook Fax Mobile Modem Primary TDD/TTY Phone Telephone Twitter 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/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	DataCenters/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	DataCenters/ContactPerson/ContactInformation/Address/City	String	n/a	1 - 100 characters	No	0..1
UMM-Common	DataCenters/ContactPerson/ContactInformation/Address/StateProvince	String	n/a	1 - 100 characters	No	0..1
UMM-Common	DataCenters/ContactPerson/ContactInformation/Address/PostalCode	String	n/a	1 - 20 characters	No	0..1
UMM-Common	DataCenters/ContactPerson/ContactInformation/Address/Country	String	n/a	1 - 100 characters	No	0..1
UMM-Common	DataCenters/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	DataCenters/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	DataCenters/ContactPerson/ContactInformation/RelatedURLs/Type = HOME PAGE	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	DataCenters/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).

["https://wiki.earthdata.nasa.gov/download/attachments/118137966/Copy%20of%20Wiki%20Page%20Metadata%20Evaluation%20Workflow-1939-51df84-0.png?api=v2"]

Loading...

Please see the expandable sections below for flowchart details.

GCMD Metadata QA/QC

Manual Review
- Identify errors, discrepancies or omissions.
Automated Review
- Check that the field length is not greater than 255 characters (Personnel/Contact_Person/FirstName).
- Check that the field length is not greater than 255 characters (Personnel/Contact_Person/LastName).
- Check that the field length is not greater than 255 characters (Personnel/Contact_Person/MiddleName).
- Check that the field length is not greater than 1,024 characters (Personnel/Contact_Person/Address/Street_Address).
- Check that the field length is not greater than 100 characters (Personnel/Content_Person/Address/City).
- Check that the field length is not greater than 100 characters (Personnel/Contact_Person/Address/State_Province).
- Check that the field length is not greater than 100 characters (Personnel/Contact_Person/Address/Country).
- Check that the field length is not greater than 20 characters (Personnel/Contact_Person/Address/Postal_Code).
- Check that the field length is not greater than 100 characters (Personnel/Contact_Person/Email).
- Check that the field length is not greater than 1,024 characters (Personnel/Contact_Person/Phone/Number).
- Check that the field has been populated.
- Check that the field value is not a duplicate.
- Check that the field value (Phone Type) matches the enumeration value (Direct Line;Primary;Telephone;Fax;Mobile;Modem;TDD/TTY Phone;U.S. toll free;Other).
- Check that the field value (Personnel Role) matches the enumeration value (DATA CENTER CONTACT).
- Check that the email address is formatted correctly.
- Check that the phone number is formatted correctly.

CMR Validation

<>

ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
Red = High Priority Finding	This element is categorized as highest priority when: The Contact Person Related URL provided is broken. The URL Content Type does not match the enumeration value "DataContactURL". The URL Type provided does not match the keyword value "HOME PAGE". The Contact Person Role provided does not align with the UMM-Common enumeration values (Data Center Contact, Technical Contact, Science Contact, Investigator, Metadata Author, User Services, Science Software Development). The Contact Mechanism Type does not align with the UMM-Common enumeration values (Direct Line, Email, Facebook, Fax, Mobile, Modem, Primary, TDD/TTY Phone, Telephone, Twitter, U.S. toll free, Other). The Contact Information provided is incorrect.
Yellow = Medium Priority Finding	This element is categorized as medium priority when: The Contact Person Related URL 'Description' element is left blank. It is highly recommended that a description be provided for each URL. The Contact Person Related URL provided in the metadata redirects—it is recommended that the most current link always be provided. The information provided in the Contact Person elements is better suited for the Data Center, Data Center/Contact Person, Data Center/Contact Group or Contact Group metadata elements.
Blue = Low Priority Finding	This element is categorized as low priority when: The Contact Person Related URL is provided via "http" when "https" is available. The listed contact information does not match the information within the NASA directory. Duplicate Contact Person information is provided.
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

DIF 9

DIF 9 ^{(Note: DIF-9 is being phased out and will no longer be supported after 2018)}

DIF 10

Providing Organization/Personnel is optional. An unlimited number of Personnel may be listed under an Organization (Cardinality: 0..*)

DIF 10 Path	Type	Usable Valid Values	Constraints	Required in DIF 10?	Cardinality	Notes
Organization/Personnel/Role	Enumeration	DATA CENTER CONTACT	n/a	Yes, if applicable	1..*	'DATA CENTER CONTACT' is the only valid option for this field in DIF 10.
Organization/Personnel/Contact_Person/First_Name	String	n/a		No	0..1
Organization/Personnel/Contact_Person/Middle_Name	String	n/a		No	0..1
Organization/Personnel/Contact_Person/Last_Name	String	n/a		Yes, if applicable	1	If Personnel information is provided, a Last_Name is required.
Organization/Personnel/Contact_Person/uuid	String	n/a		No	0,.1
Organization/Personnel/Contact_Person/Phone/Type	Enumeration	Direct Line Primary Telephone Fax Mobile Modem TDD/TTY Phone U.S. toll free Other	n/a	Yes, if applicable	1	Providing a phone number is optional. Multiple phone numbers can be provided. (Cardinality 0..*) If provided, the Type is required and must be selected from the PhoneType enumeration list found in the DIF10 schema. The actual phone number should be provided in the Number field (see below).
Organization/Personnel/Contact_Person/Phone/Number	String	n/a		Yes, if applicable	1	Providing a phone number is optional. If provided, the Number must be provided in this element.
Organization/Personnel/Contact_Person/Email	String			No	0..*
Organization/Personnel/Contact_Person/Address/Street_Address	String			No	0..*	Multiple Street Address fields may be provided to indicate multiple lines in a street address
Organization/Personnel/Contact_Person/Address/City	String			No	0..1
Organization/Personnel/Contact_Person/Address/State_Province	String			No	0..1
Organization/Personnel/Contact_Person/Address/Postal_Code	String			No	0..1
Organization/Personnel/Contact_Person/Address/Country	String			No	0..1

Example Mapping

DIF 10

<Organization>
  <Organization_Type>ARCHIVER</Organization_Type>
  <Organization_Type>DISTRIBUTOR</Organization_Type>
  <Organization_Name>
    <Short_Name>NASA/GSFC/SED/ESD/GCDC/GESDISC</Short_Name>
    <Long_Name>Goddard Earth Sciences Data and Information Services Center, Global Change Data Center, Earth Sciences Division, Science and Exploration Directorate, Goddard Space Flight Center, NASA</Long_Name>
  </Organization_Name>
  <Organization_URL>https://disc.gsfc.nasa.gov/<Organization_URL>
---------------------------------------------------------------------#DataCenter/ContactPerson fields start here--------------------------
    <Personnel>
      <Role>INVESTIGATOR</Role>
        <Contact_Person>
          <First_Name>MICHAEL</First_Name>
          <Last_Name>BOSILOVICH</Last_Name>
          <Address>
             <Street_Address>NASA/Goddard Space Flight Center</Street_Address>
             <Street_Address>Global Modeling and Assimilation Office</Street_Address>
             <Street_Address>Code 610.1</Street_Address>
             <City>Greenbelt</City>
             <State_Province>MD</State_Province>
             <Postal_Code>20771</Postal_Code>
             <Country>USA</Country>
          <Email>Michael.Bosilovich@nasa.gov</Email>
        </Contact_Person>
    </Personnel>
 </Organization>

UMM

"DataCenters":[
  {
    "Roles":[
      "ARCHIVER",
      "DISTRIBUTOR"
    ],
    "ShortName": "NASA/GSFC/SED/ESD/GCDC/GESDISC",
    "LongName": "Goddard Earth Sciences Data and Information Services Center, Global Change Data Center, Earth Sciences Division, Science and Exploration Directorate, Goddard Space Flight Center, NASA",
------------------------------#DataCenter/ContactPerson fields start here---------------------------
    "ContactPersons":[
      {
        "Roles":[
          "Investigator"
        ],
        "ContactInformation":{
          "ContactMechanisms":[
            {
              "Type": "Email",
              "Value": "Michael.Bosilovich@nasa.gov"
            }
          ],
          "Addresses":[
            {
              "StreetAddresses":[
                "NASA/Goddard Space Flight Center",
                "Global Modeling and Assimilation Office",
                "Code 610.1"
              ],
              "City": "Greenbelt",
              "StateProvince": "MD",
              "Country": "USA",
              "PostalCode": "20771"
            }
          ]
        },
        "FirstName": "MICHAEL",
        "LastName": "BOSILOVICH"
      }
    ]

ECHO 10

DataCenter/ContactPerson does not map to ECHO 10. Contact information for an individual can be provided in the 'ContactPersons' ECHO 10 metadata elements. See the Contact Person wiki page for details on the 'ContactPersons' metadata elements.

UMM-C Element	ECHO 10 Path	Type	Usable Valid Values	Constraints	Required in ECHO 10?	Cardinality	Notes
DataCenters/ContactPerson	N/A	N/A	N/A	N/A	N/A	N/A	DataCenter/ContactPerson does not map to ECHO 10. Contact information for an individual can be provided in the 'ContactPersons' ECHO 10 metadata elements. See the Contact Person wiki page for details on the 'ContactPersons' metadata elements.

Enumeration Mapping

N/A

ISO 19115-2 MENDS

Providing a DataCenter/ContactPerson is optional. An unlimited number of Contact Persons may be listed under a Data Center (Cardinality: 0..*)

ISO 19115-2 MENDS Path	Type	Notes
<=]gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString	String	Provide Data Center Short Name and Long Name in this field. This tells CMR which Data Center to nest the Contact Person information under. *Should probably specify if there are differences in what gets read to CMR (ISO > UMM) vs what gets written to CMR (UMM > ISO)
<=]gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_RoleCode	Codelist	(For more than one role another pointOfContact must be created) Data Center Contact Technical Contact Science Contact Investigator Metadata Author User Services Science Software Development
[=>gmd:CI_ResponsibleParty/gmd:positionName/gco:CharacterString = NonDataCenterAffiliation:	String	Corresponds to the UMM field DataCenters/ContactPerson/NonDataCenterAffiliation
[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = FirstName:	String	Corresponds to the UMM field DataCenters/ContactPerson/FirstName
[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = MiddleName:	String	Corresponds to the UMM field DataCenters/ContactPerson/MiddleName
[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = LastName:	String	Corresponds to the UMM field DataCenters/ContactPerson/LastName
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:hoursOfService/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/ServiceHours
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:contactInstructions/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/ContactInstructions
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:phone/gmd:CI_Telephone/[==> [==>gmd:voice/gco:CharacterString (UMM Types=>ISO: Direct Line, Mobile, Primary, TDD/TTY Phone, Telephone, U.S. toll free, Other) (ISO=>UMM: Telephone) or gmd:facsimile/gco:CharacterString (Fax)
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:electronicMailAddress/gco:CharacterString	String	Corresponds to the UMM fields DataCenters/ContactPerson/ContactInformation/ContactMechanism/Type = Email & DataCenters/ContactPerson/ContactInformation/ContactMechanism/Value
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:deliveryPoint/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StreetAddresses
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:city/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/City
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:administrativeArea/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StateProvince
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:postalCode/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/PostalCode
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:country/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/Country
[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/RelatedUrls/URL
[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/RelatedUrls/Description

Enumeration/Code List Mapping

ISO MENDS	Translation Direction	UMM
	↔	Data Center Contact
	→	Technical Contact
	↔	Science Contact
	↔	Investigator
	→	Metadata Author
	→	User Services
	↔	Science Software Development

Example Mapping

ISO 19115-2 MENDS

ADD EXAMPLE

UMM

"DataCenters":[
  {
    "Roles":[
      "ARCHIVER",
      "DISTRIBUTOR"
    ],
    "ShortName": "NASA/GSFC/SED/ESD/GCDC/GESDISC",
    "LongName": "Goddard Earth Sciences Data and Information Services Center, Global Change Data Center, Earth Sciences Division, Science and Exploration Directorate, Goddard Space Flight Center, NASA",
------------------------------#DataCenter/ContactPerson fields start here---------------------------
    "ContactPersons":[
      {
        "Roles":[
          "Investigator"
        ],
        "ContactInformation":{
          "ContactMechanisms":[
            {
              "Type": "Email",
              "Value": "Michael.Bosilovich@nasa.gov"
            }
          ],
          "Addresses":[
            {
              "StreetAddresses":[
                "NASA/Goddard Space Flight Center",
                "Global Modeling and Assimilation Office",
                "Code 610.1"
              ],
              "City": "Greenbelt",
              "StateProvince": "MD",
              "Country": "USA",
              "PostalCode": "20771"
            }
          ]
        },
        "FirstName": "MICHAEL",
        "LastName": "BOSILOVICH"
      }
    ]

ISO 19115-2 SMAP

Providing a DataCenter/ContactPerson is optional. An unlimited number of Contact Persons may be listed under a Data Center (Cardinality: 0..*)

ISO 19115-2 SMAP Path	Type	Notes
<=]gmd:CI_ResponsibleParty/gmd:organisationName/gco:CharacterString	String	Provide Data Center Short Name and Long Name in this field. This tells CMR which Data Center to nest the Contact Person information under. *Should probably specify if there are differences in what gets read to CMR (ISO > UMM) vs what gets written to CMR (UMM > ISO)
<=]gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_RoleCode	Codelist	(For more than one role another pointOfContact must be created) Data Center Contact Technical Contact Science Contact Investigator Metadata Author User Services Science Software Development
[=>gmd:CI_ResponsibleParty/gmd:positionName/gco:CharacterString = NonDataCenterAffiliation:	String	Corresponds to the UMM field DataCenters/ContactPerson/NonDataCenterAffiliation
[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = FirstName:	String	Corresponds to the UMM field DataCenters/ContactPerson/FirstName
[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = MiddleName:	String	Corresponds to the UMM field DataCenters/ContactPerson/MiddleName
[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = LastName:	String	Corresponds to the UMM field DataCenters/ContactPerson/LastName
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:hoursOfService/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/ServiceHours
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:contactInstructions/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/ContactInstructions
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:phone/gmd:CI_Telephone/[==> [==>gmd:voice/gco:CharacterString (UMM Types=>ISO: Direct Line, Mobile, Primary, TDD/TTY Phone, Telephone, U.S. toll free, Other) (ISO=>UMM: Telephone) or gmd:facsimile/gco:CharacterString (Fax)
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:electronicMailAddress/gco:CharacterString	String	Corresponds to the UMM fields DataCenters/ContactPerson/ContactInformation/ContactMechanism/Type = Email & DataCenters/ContactPerson/ContactInformation/ContactMechanism/Value
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:deliveryPoint/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StreetAddresses
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:city/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/City
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:administrativeArea/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StateProvince
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:postalCode/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/PostalCode
[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:country/gco:CharacterString	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/Country
[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/RelatedUrls/URL
[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description	String	Corresponds to the UMM field DataCenters/ContactPerson/ContactInformation/RelatedUrls/Description

Enumeration/Code List Mapping

ISO SMAP	Translation Direction	UMM
	↔	Data Center Contact
	→	Technical Contact
	↔	Science Contact
	↔	Investigator
	→	Metadata Author
	→	User Services
	↔	Science Software Development

Example Mapping

ISO 19115-2 SMAP

ADD EXAMPLE

UMM

"DataCenters":[
  {
    "Roles":[
      "ARCHIVER",
      "DISTRIBUTOR"
    ],
    "ShortName": "NASA/GSFC/SED/ESD/GCDC/GESDISC",
    "LongName": "Goddard Earth Sciences Data and Information Services Center, Global Change Data Center, Earth Sciences Division, Science and Exploration Directorate, Goddard Space Flight Center, NASA",
------------------------------#DataCenter/ContactPerson fields start here---------------------------
    "ContactPersons":[
      {
        "Roles":[
          "Investigator"
        ],
        "ContactInformation":{
          "ContactMechanisms":[
            {
              "Type": "Email",
              "Value": "Michael.Bosilovich@nasa.gov"
            }
          ],
          "Addresses":[
            {
              "StreetAddresses":[
                "NASA/Goddard Space Flight Center",
                "Global Modeling and Assimilation Office",
                "Code 610.1"
              ],
              "City": "Greenbelt",
              "StateProvince": "MD",
              "Country": "USA",
              "PostalCode": "20771"
            }
          ]
        },
        "FirstName": "MICHAEL",
        "LastName": "BOSILOVICH"
      }
    ]

UMM Migration

None

History

UMM Versioning

Version	Date	What Changed
1.15.5	12/3/2020	No changes were made for Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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 Data Centers-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	09/12/18	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Jeanne' le Roux

Page tree

Data Center - Contact Person

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

DIF 10

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 SMAP

UMM Migration

History

UMM Versioning

ARC Documentation