You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Element Description

The Contact Person metadata element is used to provide contact information for an individual associated with the data set. 

There are 5 options for providing contact information in the UMM:

  1. Data Center
  2. Data Center/ Contact Person
  3. Data Center/Contact Group
  4. Contact Person
  5. Contact Group

Details for each of these options is 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 field. 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. There are seven options for Role:

  1. DATA CENTER CONTACT: an individual affiliated with a data center. This will typically be the same data center listed in the required 'Data Center' element.   
  2. TECHNICAL CONTACT: an individual with technical (expert) knowledge about the data product. 
  3. SCIENCE CONTACT: an individual with technical (expert) knowledge about the science principals involved in deriving the data product.
  4. 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.   
  5. 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.
  6. USER SERVICES: an individual representative of the user services office at the data center responsible for archiving, distributing, originating or processing the data.
  7. 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 are sub-fields of the Data Center metadata fields. 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.

Uuid: ??

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 amount of Contact Persons may be listed (Cardinality: 0..*)

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CommonDataCenters/ContactPerson/Roles Enumeration

Data Center Contact

Technical Contact

Science Contact

Investigator

Metadata Author

User Services

Science Software Development

n/aYes, if applicable1..*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-CommonDataCenters/ContactPerson/NonDataCenterAffiliationStringn/a1 - 1024 charactersNo0..1
UMM-CommonDataCenters/ContactPerson/FirstName Stringn/a1 - 255 charactersNo0..1
UMM-CommonDataCenters/ContactPerson/MiddleNameNumbern/a1 - 255 charactersNo0..1
UMM-CommonDataCenters/ContactPerson/LastName
Stringn/a1 - 255 charactersYes, if applicable1If Contact Person information is provided, a Last Name is required.
UMM-CommonDataCenters/ContactPerson/Uuid
Stringn/a?No0..1
UMM-CommonDataCenters/ContactPerson/ContactInformation/ServiceHours
Stringn/a1 - 1024 charactersNo0..1The time zone should be specified.
UMM-CommonDataCenters/ContactPerson/ContactInformation/ContactInstructions
Stringn/a1 - 2048 charactersNo0..1Supplemental/ special instructions on how or when to contact the contact person.
UMM-CommonDataCenters/ContactPerson/ContactInformation/ContactMechanism/Type Enumeration

Direct Line

Email

Facebook

Fax

Mobile

Modem

Primary

TDD/TTY Phone

Telephone

Twitter

U.S. toll free

Other

n/aYes, if applicable1

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-CommonDataCenters/ContactPerson/ContactInformation/ContactMechanism/ValueStringn/a1 - 1024 charactersYes, if applicable1

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-CommonDataCenters/ContactPerson/ContactInformation/Address/StreetAddresses String

n/a

1 - 1024 charactersNo0..*

Multiple Street Addresses may be provided to indicate multiple lines in a street address


UMM-CommonDataCenters/ContactPerson/ContactInformation/Address/City Stringn/a1 - 100 charactersNo0..1


UMM-CommonDataCenters/ContactPerson/ContactInformation/Address/StateProvinceStringn/a1 - 100 charactersNo0..1
UMM-CommonDataCenters/ContactPerson/ContactInformation/Address/PostalCode Stringn/a1 - 20 charactersNo0..1
UMM-CommonDataCenters/ContactPerson/ContactInformation/Address/Country Stringn/a1 - 100 charactersNo0..1
UMM-CommonDataCenters/ContactPerson/ContactInformation/RelatedURLs/Url Stringn/a1 - 1024 charactersYes, if applicable1Providing 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-CommonDataCenters/ContactPerson/ContactInformation/RelatedURLs/UrlContentTypeEnumerationDataContactURLn/aYes, if applicable1

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-CommonDataCenters/ContactPerson/ContactInformation/RelatedURLs/Type = HOME PAGEStringKMS controlledHOME PAGEYes, if applicable1

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-CommonDataCenters/ContactPerson/ContactInformation/RelatedURLs/DescriptionStringn/a1 - 4000 charactersNo0..1It 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.


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

<>

ARC Priority Matrix

Priority CategorizationJustification

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.

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 or Data Center/Contact Group metadata elements.

This element is categorized as low priority when: The Contact Person Related URL is provided via http when https is available.


The element is provided, and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

  • Role
    • If no value is provided, return is: "The Data Center Role has been left blank - this field must be provided to accompany any Data Center contact information."
    • If the provided value is not valid, return is: "Invalid value for Data Center Role: <provided value>. Choose a valid value from the following list: <schema listed here>."
    • Otherwise, return is "OK."
  • UUID, Non Data Center Affiliation, First Name, Middle Name, Last Name, Service Hours, Contact Instructions, Contact Mechanism/Value, Street Address, City, State Province, Postal Code, Country
    • If no value is provided, return is "np."
    • Otherwise, return is "OK."
  • Related Urls/ URL Content Type
    • If no value is provided, return is "URL Content Type is required for each link. Recommend providing a valid value from the following options: <schema listed here>."
    • If an invalid value is provided, return is "Invalid value for URL Content Type: <provided value>. Recommend providing valid value."
    • Otherwise, return is "OK."
  • Related Urls/ Type
  • Related Urls/ Description
    • If no value is provided, return is "One (or more) URLs appear to be missing a description. Recommend providing descriptions for each URL."
    • If a repeated description value is provided, return is "Descriptions should be unique to each URL. The following descriptions are repeated in this record: <repeated descriptions> Recommend changing descriptions to more accurately and uniquely describe the URL."
    • Otherwise, return is "OK."





Dialect Mappings

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 amount of Personnel may be listed (Cardinality: 0..*)

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in DIF 10?CardinalityNotes
DIF 10Organization/Personnel/Role
EnumerationDATA CENTER CONTACTn/aYes, if applicable1..*'DATA CENTER CONTACT' is the only valid option for this field in DIF 10.
DIF 10Organization/Personnel/Contact_Person/First_Name
Stringn/a
No0..1
DIF 10Organization/Personnel/Contact_Person/Middle_NameStringn/a
No0..1
DIF 10Organization/Personnel/Contact_Person/Last_NameStringn/a
Yes, if applicable1If Personnel information is provided, a Last_Name is required.
DIF 10Organization/Personnel/Contact_Person/uuidStringn/a
No0,.1
DIF 10Organization/Personnel/Contact_Person/Phone/Type
Enumeration

Direct Line

Primary

Telephone

Fax

Mobile

Modem

TDD/TTY Phone

U.S. toll free

Other

n/aYes, if applicable1

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

DIF 10Organization/Personnel/Contact_Person/Phone/Number
Stringn/a
Yes, if applicable1

Providing a phone number is optional.

If provided, the Number must be provided in this element.

DIF 10Organization/Personnel/Contact_Person/Email
String

No0..*
DIF 10Organization/Personnel/Contact_Person/Address/Street_Address
String

No0..*Multiple Street Address fields may be provided to indicate multiple lines in a street address
DIF 10Organization/Personnel/Contact_Person/Address/CityString

No0..1
DIF 10Organization/Personnel/Contact_Person/Address/State_Province
String

No0..1
DIF 10Organization/Personnel/Contact_Person/Address/Postal_CodeString

No0..1
DIF 10Organization/Personnel/Contact_Person/Address/CountryString

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

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in ECHO 10?CardinalityNotes
ECHO 10N/AN/AN/AN/AN/AN/ADataCenter/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

Example Mapping

ECHO 10

N/A

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 MENDS

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

SpecificationPathTypeNotes
ISO 19115-2 MENDS

<=]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)

ISO 19115-2 MENDS

<=]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


ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:positionName/gco:CharacterString = NonDataCenterAffiliation:String

Corresponds to the UMM field

DataCenters/ContactPerson/NonDataCenterAffiliation

ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = FirstName:String

Corresponds to the UMM field

DataCenters/ContactPerson/FirstName

ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = MiddleName:String

Corresponds to the UMM field

DataCenters/ContactPerson/MiddleName

ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = LastName:String

Corresponds to the UMM field

DataCenters/ContactPerson/LastName

ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:hoursOfService/gco:CharacterStringString

Corresponds to the UMM field

DataCenters/ContactPerson/ContactInformation/ServiceHours

ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:contactInstructions/gco:CharacterStringString

Corresponds to the UMM field

DataCenters/ContactPerson/ContactInformation/ContactInstructions

ISO 19115-2 MENDS

[=>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)



ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:electronicMailAddress/gco:CharacterStringString

Corresponds to the UMM fields

DataCenters/ContactPerson/ContactInformation/ContactMechanism/Type = Email

&

DataCenters/ContactPerson/ContactInformation/ContactMechanism/Value

ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:deliveryPoint/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StreetAddresses
ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:city/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/City
ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:administrativeArea/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StateProvince
ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:postalCode/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/PostalCode
ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:country/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/Country
ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URLStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/RelatedUrls/URL
ISO 19115-2 MENDS[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:descriptionStringCorresponds 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

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 amount of Contact Persons may be listed (Cardinality: 0..*)

SpecificationPathTypeNotes
ISO 19115-2 SMAP

<=]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)

ISO 19115-2 SMAP

<=]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

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:positionName/gco:CharacterString = NonDataCenterAffiliation:String

Corresponds to the UMM field

DataCenters/ContactPerson/NonDataCenterAffiliation

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = FirstName:String

Corresponds to the UMM field

DataCenters/ContactPerson/FirstName

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = MiddleName:String

Corresponds to the UMM field

DataCenters/ContactPerson/MiddleName

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:individualName/gco:CharacterString = LastName:String

Corresponds to the UMM field

DataCenters/ContactPerson/LastName

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:hoursOfService/gco:CharacterStringString

Corresponds to the UMM field

DataCenters/ContactPerson/ContactInformation/ServiceHours

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:contactInstructions/gco:CharacterStringString

Corresponds to the UMM field

DataCenters/ContactPerson/ContactInformation/ContactInstructions

ISO 19115-2 SMAP[=>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)

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:electronicMailAddress/gco:CharacterStringString

Corresponds to the UMM fields

DataCenters/ContactPerson/ContactInformation/ContactMechanism/Type = Email

&

DataCenters/ContactPerson/ContactInformation/ContactMechanism/Value

ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:deliveryPoint/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StreetAddresses
ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:city/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/City
ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:administrativeArea/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/StateProvince
ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:postalCode/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/PostalCode
ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:contactInfo/gmd:CI_Contact/gmd:address/gmd:CI_Address/ gmd:country/gco:CharacterStringStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/Address/Country
ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:linkage/gmd:URLStringCorresponds to the UMM field DataCenters/ContactPerson/ContactInformation/RelatedUrls/URL
ISO 19115-2 SMAP[=>gmd:CI_ResponsibleParty/gmd:onlineResource/gmd:CI_OnlineResource/gmd:descriptionStringCorresponds 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

<gmd:DS_Series>
<gmd:seriesMetadata>
<gmi:MI_Metadata>
...
...
</gmi:MI_Metadata> 
</gmd:seriesMetadata>  
</gmd:DS_Series>

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


Future Mappings

ISO 19115-1

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

SpecificationPathTypeNotes
ISO 19115-1





Enumeration/Code List Mapping

N/A

Example Mapping

ISO 19115-1

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"
      }
    ]

History

UMM Versioning

VersionDateWhat Changed
1.12.001/22/2019No changes were made for Data Centers-Contact Person during the transition from version 1.11.0 to 1.12.0.
1.11.011/28/2018No changes were made for Data Centers-Contact Person during the transition from version 1.10.0 to 1.11.0.
1.10.005/02/2018No 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

VersionDateWhat ChangedAuthor
1.09/12/18Recommendations/priority matrix transferred from internal ARC documentation to wiki spaceJeanne' le Roux



  • No labels