contact 2.0

[stansmith907]

Changes:

1. "contactId" is a required element of type string. It was added by ADIwg to support referencing contacts from elsewhere in the metadata record.
2. “isOrganization” is a required element of type Boolean. It was added by ADIwg to specify whether the contact is for an individual or organization. The default value is false.
3. “name” is a required element of type string. It replaces both “organizationName” and “individualName” in mdJson 1.0 since only one name is allowed for a contact now.
4. “positionName” will only be valid for individual contacts.
5. “memberOfOrganization” array was added to hold organization “contactId”s that this individual has some relationship to. Will only be valid for individual contacts.
6. “logoGraphic” array was added for organizations to provide their access to their logos. logoGraphic uses the BrowseGraphic object which has changed from previous ISO format. Will only be valid for organization contacts. Issue graphicOverview 2.0 #45.
7. “address” is now an array of addresses. Address format has not changed. Issue address 2.0 #115.
8. “onlineResource” does not include ISO attributes “applicationProfile” and “protocolRequest” for contact. Issue onlineResource 2.0 #50.
9. “phone” is the new name for “phonebook”. Issue phone 2.0 #114.
10. “hoursOfService” was added as an array of character strings. note: This field is also supported in FGDC.
11. “contactType” was added as a user defined contact type.
12. "electronicMailAddress" is an array of strings. It was moved to the base of 'contact' from 'address'.

{
   "contact": [
      {
         "contactId": "",
         "isOrganization": false,
         "name": "",
         "positionName": "",
         "memberOfOrganization": [
            "organization contact ID"
         ],
         "logoGraphic": [
            {
               "see": "graphic 2.0"
            }
         ],
         "phone": [
            {
               "see": "phone 2.0"
            }
         ],
         "address": [
            {
               "see": "address 2.0"
            }
         ],
         "electronicMailAddress": [""],
         "onlineResource": [
            {
               "see": "onlineResource 2.0"
            }
         ],
         "hoursOfService": [""],
         "contactInstructions": "",
         "contactType": ""
      }
   ]
}

No ISO XML example

[jlblcc]

Is there a way to add additional identifiers or aliases to the contact object? Possibly:

• add array of md_identifier
• use the onlineResource array

Add to onlineFunction codelist:

• orcid see: http://orcid.org/
• doi

[jlblcc]

Remove primaryRole.

[stansmith907]

primaryRole has been removed.

[jlblcc]

I think we need to be more nuanced in handling name and position. Often it is desirable to only list a position and not an individual's name in the metadata. The current schema will not allow this - name is required for both types of contact. I suggest adding the following rules:

• isOrganization=true and name is required
• isOrganization=false and (name or positionName) is required