Page History

Table of Contents

style	circle

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 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	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).

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	GCMD Metadata QA/QC

Manual Review
Automated Review

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: 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.
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	DIF 9

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

Expand

title	DIF 10

DIF 10

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

UMM-C Element	DIF 10 Path	Type	Usable Valid Values	Constraints	Required in DIF 10?	Cardinality	Notes
ContactPerson/Roles	Personnel/Role	Enumeration	INVESTIGATOR INVESTIGATOR, TECHNICAL CONTACT METADATA AUTHOR METADATA AUTHOR, TECHNICAL CONTACT TECHNICAL CONTACT	n/a	Yes, if applicable	1..*
ContactPerson/FirstName	Personnel/Contact_Person/First_Name	String	n/a		No	0..1
ContactPerson/MiddleName	Personnel/Contact_Person/Middle_Name	String	n/a		No	0..1
ContactPerson/LastName	Personnel/Contact_Person/Last_Name	String	n/a		Yes, if applicable	1	If Personnel information is provided, a Last_Name is required.
ContactPerson/Uuid	Personnel/Contact_Person/uuid	String	n/a		No	0..1
ContactPerson/ContactInformation/ContactMechanism/Type	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).
ContactPerson/ContactInformation/ContactMechanism/Value	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.
ContactPerson/ContactInformation/ContactMechanism/Value	Personnel/Contact_Person/Email	String			No	0..*
ContactPerson/ContactInformation/Address/StreetAddresses	Personnel/Contact_Person/Address/Street_Address	String			No	0..*	Multiple Street Address fields may be provided to indicate multiple lines in a street address
ContactPerson/ContactInformation/Address/City	Personnel/Contact_Person/Address/City	String			No	0..1
ContactPerson/ContactInformation/Address/StateProvince	Personnel/Contact_Person/Address/State_Province	String			No	0..1
ContactPerson/ContactInformation/Address/PostalCode	Personnel/Contact_Person/Address/Postal_Code	String			No	0..1
ContactPerson/ContactInformation/Address/Country	Personnel/Contact_Person/Address/Country	String			No	0..1

Enumeration/Code List Mapping

DIF 10	Translation Direction	UMM
INVESTIGATOR	↔
INVESTIGATOR, TECHNICAL CONTACT	→
METADATA AUTHOR	↔
METADATA AUTHOR, TECHNICAL CONTACT	↔
TECHNICAL CONTACT	→

Example Mapping

Section

Column

width	50%

DIF 10

No Format

<Personnel>
  <Role>INVESTIGATOR</Role>
  <Contact_Person>
    <First_Name>R.</First_Name>
    <Last_Name>Ramachandran</Last_Name>
    <Address>
      <Street_Address>Laser Remote Sensing Laboratory, Code 694</Street_Address>
      <Street_Address>NASA Goddard Space Flight Center</Street_Address>
      <City>Greenbelt</City>
      <State_Province>MD</State_Province>
      <Postal_Code>20771</Postal_Code>
      <Country>USA</Country>
    </Address>    
    <Phone>
      <Type>Telephone</Type>
      <Number>123-777-7777</Number>
    </Phone>
    <Email>email@email.com</Email>
  </Contact_Person>
</Personnel>

Column

width	50%

UMM

No Format

"ContactPersons":[
  {
    "Roles":[
       "Investigator"
    ],
    "ContactInformation":{
      "ContactMechanisms":[
        {
          "Type": "Telephone",
          "Value": "123-777-7777"
        },            
        {
          "Type": "Email",
          "Value": "email@email.com"
        }
      ],
      "Addresses":[
        {
          "StreetAddresses":[
            "Laser Remote Sensing Laboratory, Code 694",
            "NASA Goddard Space Flight Center"
          ],
          "City": "Greenbelt",
          "StateProvince": "MD",
          "Country": "USA",
          "PostalCode": "20771"
        }
      ]
    },
    "FirstName": "R.",
    "LastName": "Ramachandran"
  }
]

Expand

title	ECHO 10

ECHO 10

Providing Contact Persons is optional. An unlimited number of Contact Persons may be listed (Cardinality: 0..*)

UMMC-Element	ECHO 10 Path	Type	Constraints	Required in ECHO 10?	Cardinality	Notes
ContactPerson/FirstName	Contacts/Contact/ContactPersons/ContactPerson/FirstName	String	1 - 255 characters	Yes, if applicable	1	If a Contact Person is provided, a First Name is required
ContactPerson/MiddleName	Contacts/Contact/ContactPersons/ContactPerson/MiddleName	String	1 - 255 characters	No	0..1
ContactPerson/LastName	Contacts/Contact/ContactPersons/ContactPerson/LastName	String	1 - 255 characters	Yes, if applicable	1	If a Contact Person is provided, a Last Name is required
ContactPerson/Roles	Contacts/Contact/ContactPersons/ContactPerson/JobPosition	String	1 - 255 characters	No	0..1	While this field is not controlled in ECHO 10, it is highly recommended that one of the enumeration values for ContactPerson/Role be selected to populate this field (Data Center Contact, Technical Contact, Science Contact, Investigator, Metadata Author, User Services, Science Software Development) When translating from ECHO 10 to UMM, the CMR will attempt to map the value provided in this field to one of the UMM Roles. Therefore, providing one of the UMM Role enumeration values will prevent translation errors from occurring & will ensure that the Contact Person Role is displayed appropriately in the Earthdata Search Client.

Example Mapping

Section

Column

width	50%

ECHO 10

No Format

<Contacts>
  <Contact>
    <ContactPersons>
      <ContactPerson>
        <FirstName>R.</FirstName>
        <LastName>Ramachandran</LastName>
        <JobPosition>Investigator</JobPosition>
      </ContactPerson>
    </ContactPersons>
  </Contact>
</Contacts>

Column

width	50%

UMM

No Format
"ContactPersons":[ { "Roles":[ "Investigator" ], "FirstName": "R.", "LastName": "Ramachandran" } ]

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

Providing a Contact Person is optional. An unlimited number of Contact Persons may be listed (Cardinality: 0..*)

UMMC-Element	ISO 19115-2 MENDS Path	Type	Notes
ContactPerson/Roles	For all roles except Metadata Author: /gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_RoleCode For Metadata Author: /gmi:MI_Metadata/gmd:contact/gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode role code value???	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
ContactPerson/NonDataCenterAffiliation	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:positionName/gco:CharacterString = NonDataCenterAffiliation:	String
ContactPerson/FirstName	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = FirstName:	String
ContactPerson/MiddleName	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = MiddleName:	String
ContactPerson/LastName	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = LastName:	String
ContactPerson/ContactInformation/ServiceHours	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:hoursOfService/gco:CharacterString	String
ContactPerson/ContactInformation/ContactInstructions	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:contactInstructions/gco:CharacterString	String
ContactPerson/ContactInformation/ContactMechanism/Value	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>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)		Use '[==> gmd:voice/gco:CharacterString' to provide a phone number When translating from UMM to ISO, if the ContactMechanism/Type = Direct Line, Mobile, Primary, TDD/TTY Phone, Telephone, U.S. toll free or Other then the number will be provided in this field Use '[==> gmd:facsimile/gco:CharacterString' to provide a fax number When translating from UMM to ISO, if the ContactMechanism/Type = Fax then the number will be provided in this field
ContactPerson/ContactInformation/ContactMechanism/Type & ContactPerson/ContactInformation/ContactMechanism/Value	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:electronicMailAddress/gco:CharacterString	String	Corresponds to the UMM fields "ContactPerson/ContactInformation/ContactMechanism/Type" = Email & "ContactPerson/ContactInformation/ContactMechanism/Value"
ContactPerson/ContactInformation/Address/StreetAddresses	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:deliveryPoint/gco:CharacterString	String
ContactPerson/ContactInformation/Address/City	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:city/gco:CharacterString	String
ContactPerson/ContactInformation/Address/StateProvince	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:administrativeArea/gco:CharacterString	String
ContactPerson/ContactInformation/Address/PostalCode	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:postalCode/gco:CharacterString	String
ContactPerson/ContactInformation/Address/Country	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:country/gco:CharacterString	String
ContactPerson/ContactInformation/RelatedUrls/URL	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL	String
ContactPerson/ContactInformation/RelatedUrls/Description	/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact/[=> [=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description	String

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

Section

Column

width	50%

ISO 19115-2 MENDS

No Format

<gmi:MI_Metadata>
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:pointOfContact>
        <gmd:CI_ResponsibleParty>
          <gmd:role>
            <gmd:CI_RoleCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="Investigator">Investigator</gmd:CI_RoleCode>
          </gmd:role>
          <gmd:positionName>
            <gco:CharacterString>NonDataCenterAffiliation:UMD Laser Remote Sensing Laboratory</gco:CharacterString>
          </gmd:positionName
          <gmd:individualName>
            <gco:CharacterString>FirstName:R. LastName:Ramachandran</gco:CharacterString>
          </gmd:individualName>
          <gmd:contactInfo>
            <gmd:CI_Contact>
              <gmd:phone>
                <gmd:CI_Telephone>
                  <gmd:voice>
                    <gco:CharacterString>123-777-7777</gco:CharacterString>
                  </gmd:voice>
                </gmd:CI_Telephone>
              </gmd:phone>
              <gmd:address>
                <gmd:CI_Address>
                  <gmd:electronicMailAddress>
                    <gco:CharacterString>email@email.com</gco:CharacterString>
                  </gmd:electronicMailAddress>
                  <gmd:deliveryPoint>
                    <gco:CharacterString>Laser Remote Sensing Laboratory, Code 694</gco:CharacterString>
                  </gmd:deliveryPoint>
                  <gmd:deliveryPoint>
                    <gco:CharacterString>NASA Goddard Space Flight Center</gco:CharacterString>
                  </gmd:deliveryPoint>
                  <gmd:city>
                    <gco:CharacterString>Greenbelt</gco:CharacterString>
                  </gmd:city>
                  <gmd:administrativeArea>
                    <gco:CharacterString>MD</gco:CharacterString>
                  </gmd:administrativeArea>
                  <gmd:country>
                    <gco:CharacterString>USA</gco:CharacterString>
                  </gmd:country>
                  <gmd:postalCode>
                    <gco:CharacterString>20771</gco:CharacterString>
                  </gmd:postalCode>
                </gmd:CI_Address>
              </gmd:address>
            </gmd:CI_Contact>
          </gmd:contactInfo>
        </gmd:CI_ResponsibleParty>
      </gmd:pointOfContact>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>

Column

width	50%

UMM

No Format

"ContactPersons":[
  {
    "Roles":[
       "Investigator"
    ],
    "NonDataCenterAffiliation": "UMD Laser Remote Sensing Laboratory",
    "ContactInformation":{
      "ContactMechanisms":[
        {
          "Type": "Telephone",
          "Value": "123-777-7777"
        },            
        {
          "Type": "Email",
          "Value": "email@email.com"
        }
      ],
      "Addresses":[
        {
          "StreetAddresses":[
            "Laser Remote Sensing Laboratory, Code 694",
            "NASA Goddard Space Flight Center"
          ],
          "City": "Greenbelt",
          "StateProvince": "MD",
          "Country": "USA",
          "PostalCode": "20771"
        }
      ]
    },
    "FirstName": "R.",
    "LastName": "Ramachandran"
  }
]

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

Providing a Contact Person is optional. An unlimited number of Contact Persons may be listed (Cardinality: 0..*)

UMM-C Element	ISO 19115-2 SMAP Path	Type	Notes
ContactPerson/Roles	For all roles except Metadata Author: /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:role/gmd:CI_RoleCode https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_RoleCode For Metadata Author: /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:contact/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
ContactPerson/NonDataCenterAffiliation	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:positionName/gco:CharacterString = NonDataCenterAffiliation:	String
ContactPerson/FirstName	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = FirstName:	String
ContactPerson/MiddleName	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = MiddleName:	String
ContactPerson/LastName	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = LastName:	String
ContactPerson/ContactInformation/ServiceHours	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:hoursOfService/gco:CharacterString	String
ContactPerson/ContactInformation/ContactInstructions	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:contactInstructions/gco:CharacterString	String
ContactPerson/ContactInformation/ContactMechanism/Type	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>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)		Use '[==> gmd:voice/gco:CharacterString' to provide a phone number When translating from UMM to ISO, if the ContactMechanism/Type = Direct Line, Mobile, Primary, TDD/TTY Phone, Telephone, U.S. toll free or Other then the number will be provided in this field Use '[==> gmd:facsimile/gco:CharacterString' to provide a fax number When translating from UMM to ISO, if the ContactMechanism/Type = Fax then the number will be provided in this field
ContactPerson/ContactInformation/ContactMechanism/Type & ContactPerson/ContactInformation/ContactMechanism/Value	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:electronicMailAddress/gco:CharacterString	String	Corresponds to the UMM fields "ContactPerson/ContactInformation/ContactMechanism/Type" = Email & "ContactPerson/ContactInformation/ContactMechanism/Value"
ContactPerson/ContactInformation/Address/StreetAddresses	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:deliveryPoint/gco:CharacterString	String
ContactPerson/ContactInformation/Address/City	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:city/gco:CharacterString	String
ContactPerson/ContactInformation/Address/StateProvince	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:administrativeArea/gco:CharacterString	String
ContactPerson/ContactInformation/Address/PostalCode	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:postalCode/gco:CharacterString	String
ContactPerson/ContactInformation/Address/Country	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:country/gco:CharacterString	String
ContactPerson/ContactInformation/RelatedUrls/URL	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URL	String
ContactPerson/ContactInformation/RelatedUrls/Description	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:pointOfContact[=> [=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:description	String

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

Section

Column

width	50%

ISO 19115-2 SMAP

No Format

<gmd:DS_Series>
<gmd:seriesMetadata>
<gmi:MI_Metadata>
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:pointOfContact>
        <gmd:CI_ResponsibleParty>
          <gmd:role>
            <gmd:CI_RoleCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="Investigator">Investigator</gmd:CI_RoleCode>
          </gmd:role>
          <gmd:positionName>
            <gco:CharacterString>NonDataCenterAffiliation:UMD Laser Remote Sensing Laboratory</gco:CharacterString>
          </gmd:positionName
          <gmd:individualName>
            <gco:CharacterString>FirstName:R. LastName:Ramachandran</gco:CharacterString>
          </gmd:individualName>
          <gmd:contactInfo>
            <gmd:CI_Contact>
              <gmd:phone>
                <gmd:CI_Telephone>
                  <gmd:voice>
                    <gco:CharacterString>123-777-7777</gco:CharacterString>
                  </gmd:voice>
                </gmd:CI_Telephone>
              </gmd:phone>
              <gmd:address>
                <gmd:CI_Address>
                  <gmd:electronicMailAddress>
                    <gco:CharacterString>email@email.com</gco:CharacterString>
                  </gmd:electronicMailAddress>
                  <gmd:deliveryPoint>
                    <gco:CharacterString>Laser Remote Sensing Laboratory, Code 694</gco:CharacterString>
                  </gmd:deliveryPoint>
                  <gmd:deliveryPoint>
                    <gco:CharacterString>NASA Goddard Space Flight Center</gco:CharacterString>
                  </gmd:deliveryPoint>
                  <gmd:city>
                    <gco:CharacterString>Greenbelt</gco:CharacterString>
                  </gmd:city>
                  <gmd:administrativeArea>
                    <gco:CharacterString>MD</gco:CharacterString>
                  </gmd:administrativeArea>
                  <gmd:country>
                    <gco:CharacterString>USA</gco:CharacterString>
                  </gmd:country>
                  <gmd:postalCode>
                    <gco:CharacterString>20771</gco:CharacterString>
                  </gmd:postalCode>
                </gmd:CI_Address>
              </gmd:address>
            </gmd:CI_Contact>
          </gmd:contactInfo>
        </gmd:CI_ResponsibleParty>
      </gmd:pointOfContact>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>
</gmd:seriesMetadata>  
</gmd:DS_Series>

Column

width	50%

UMM

No Format

"ContactPersons":[
  {
    "Roles":[
       "Investigator"
    ],
    "NonDataCenterAffiliation": "UMD Laser Remote Sensing Laboratory",
    "ContactInformation":{
      "ContactMechanisms":[
        {
          "Type": "Telephone",
          "Value": "123-777-7777"
        },            
        {
          "Type": "Email",
          "Value": "email@email.com"
        }
      ],
      "Addresses":[
        {
          "StreetAddresses":[
            "Laser Remote Sensing Laboratory, Code 694",
            "NASA Goddard Space Flight Center"
          ],
          "City": "Greenbelt",
          "StateProvince": "MD",
          "Country": "USA",
          "PostalCode": "20771"
        }
      ]
    },
    "FirstName": "R.",
    "LastName": "Ramachandran"
  }
]

UMM Migration

None

Excerpt

hidden	true

Future Mappings

Expand

title	ISO 19115-1

ISO 19115-1

There is currently no mapping between UMM-C and ISO 19115-1 for Contact person.

Specification	Path	Type	Notes
ISO 19115-1	N/A	N/A	There is currently no mapping between UMM-C and ISO 19115-1 for Contact Person.

Enumeration/Code List Mapping

N/A

Example Mapping

Section

Column

width	50%

ISO 19115-1

No Format
N/A

Column

width	50%

UMM

No Format
N/A

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

Page tree

Versions Compared

Old Version 29

New Version 30

Key

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

DIF 10

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 MENDS Path

ISO 19115-2 SMAP

ISO 19115-2 SMAP Path

UMM Migration

Future Mappings

ISO 19115-1

History

UMM Versioning

ARC Documentation