reassessment of actors, their affiliations, and relations to research product (versions)

[lzehl]

This issue is based on issues #502, #500 with additional aspects.

research products (RPs); research product versions (RPVs)
category legalPerson: Person, Organisation, Consortium

@openMetadataInitiative/openminds-developers please review and discuss (terminology is still up for change, please provide better suggestions if you have them)

---

Current status (as reminder)

Current status for linkages between RP/PRV and actors:

• author (1-N) linked category: legalPerson (for some RP/RPV, e.g. dataset (version))
• custodian (1/0-N) linked category: legalPerson (for any RP/RPV; required only in dataset (version))
• developer (1-N) linked category: legalPerson (for some RP/RPV, e.g. software (version))
• otherContribution (0-N) linked type: Contribution (for any RPV)

Current Contribution:

• contributor (1) linked category: legalPerson
• type (1-N) linked type: ContributionType (controlled, e.g. coordination, data processing, etc.)

Current linkage to Affiliation:

• affiliation (0-N) linked type: Affiliation (for Person or Organisation)

Current Affiliation:

• endDate (0-1) string (date)
• memberOf (1) linked type: Consortium or Organisation
• startDate (0-1) string (date)

Current Organisation:

• affiliation (0-N) linked type: Affiliation
• digitalIdentifier (0-N) linked type: GRIDID, RORID, RRID
• fullName (1) string
• hasParent (0-N) linked type: Organisation
• homepage (0-1) string (iri)
• shortName (0-1) string

Current Consortium:

• fullName (1) string
• contactInformation (0-1) linked type ContactInformation (email)
• homepage (0-1) string (iri)
• shortName (0-1) string

---

SUGGESTIONS:

1. get rid of role specific actor linkages
2. make affiliation for a specific RP/RPV explicit
3. enforce real Organization (with RORID); decouple department, institute, etc. info
4. review Consortium (ID missing? affiliation missing?)
5. review Person (full name?)

---

RP/RPV

• replace "author", "developer", "otherContribution" with "contributor"
• contributor (1-N) embedded type Contributor

New Contributor:

• affiliation (1-N) linked type: Organization
• contribution (1-N) embedded type: Contribution
• legalPerson (1) linked category: legalPerson

New Contribution:

• role (1) linked type: ContributorType (or stick with ContributionType ?)
• order (0-1) number (will require conditions to be checked)

New Organization:

• address (1) embedded type: Location
• acronym (0-1) string
• alternateName (0-N) string
• digitalIdentifier (0-N) linked type: GRIDID, RORID, RRID, ISNI, LEI
• name (1) string
• hasParent (0-N) linked type: Organization
• homepage (0-1) string (iri)
• memberOf (0-N) embedded type: Membership ?
• type (1) linked type: LegalEntityType -> (new controlled terms)
  (Question: what are other types beyond legal entity type? e.g. patient associations?)

New Person:

• alternateName (0-N) string
• associatedAccount (0-N) linked type: AccountInformation
• contactInformation (1-N) linked type: ContactInformation
• digitalIdentifier (0-N) linked type: ORCID (others??)
• familyName (0-1) string
• fullName (1) string
• givenName (1) string
• memberOf (0-N) embedded type: Membership ?

New Membership:

• endDate (0-1) string (date)
• memberOf (1) linked type: Consortium or Organization
• startDate (0-1) string (date)

New ContactInformation

• address (0-1) embedded type: Location
• email (1) string

New Location:

• administrativeDivision (0-1)
• city (1)
• country (1)
• geoCoordinates (0-1) embedded type: GeoCoordinates
• postalAddress (0-1) embedded type: POBox | StreetAddress
• postalCode (1)

New GeoCoordinates

• elevation (0-1)
• latitude (1)
• longitude (1)

New POBox

• number (1)

New StreetAddress

• street (1)
• number (0-1)

New ISNI

• identifier (regex: ^https?://(www.)?isni.org/(isni/)?\d{15}[\dX]$)

New LEI

• identifier (regex: ^https://lei.global/LEI/[A-Z0-9]{18}\d{2}$)

[lzehl]

@openMetadataInitiative/openminds-developers this needs to be discussed for v5.0

[Raphael-Gazzotti]

New Contribution:

• role (1) linked type: ContributorType (or stick with ContributionType ?)

Roles like curator, developer, designer, writer, or data provider are straightforward. However for nuanced tasks such as data collection, optimization, data interpretation, or survey design, aren’t as easily categorized. In these cases, simply using "role" might not fully capture the contribution, and providing a detailed description (e.g., "task" or "taskDescription") could offer better clarity.

Affiliation Property (Contributor):
Some organizations require researchers/employees to be cited in a specific order when they have multiple affiliations. Including an order property could address this need.

New Organization:
homepage (0-1): Change type from string (iri) to (url).n

[lzehl]

@Raphael-Gazzotti

ContributorType: fully correct, we may want to go deeper. I checked again and I would like to follow the logic of DataCite (so ContributorType), but then as you suggest refine with the use cases.

Affiliation: you are fully correct. This would mean to separate an Affiliation schema with order similar to Contribution schema above.

Organization: we should discuss with the others. There was a reason why we decided for IRI for all web addresses (but I don't remember why).

Some other things @Raphael-Gazzotti and I discussed in person:

Alternative option to the restructuring above is organizing according to contribution role with ordered lists of persons. (Contribution schema, with role, contributors (ordered list of linked types) -> Contributor schema person, affiliation).

Questions around address: is it sufficient for international addresses? Is the lower administrative division (district, block, etc) needed besides the higher administrative division (state, province, region)?

Name(s) of organization: For legal registration the name is normally in the native language of the country the organization is located in. However for our purposes the English name would be more beneficial. We should register at least the name in native language as alternate name. Acronym however typically refers to the native name. Other alternate names are other abbreviations or transliterated names (native name without special characters or English for non roman letter languages). What do we want to capture?

LegalEntityType: are new controlled terms, with main name provided in English and then in synonyms in other languages (with Language code embedded in the string "XXX (EN)" or as "XXX @EN"? or as structured string embedded type: String:text"XXX",language"EN"?)

Organization connections: we have hasParent and memberOf, however there are also other relations between organizations (e.g. between a university and a university hospital).

Organization logos: do we want that?? linked type (File | WebResource) OR just iri to WikiData/WikiMedia?

Person: we may want to still have a currentAffiliation directly attached to display on the KG for persons. or could this be merged with memberOf / isPartOf? (allowing to state there any relation of a person to something consortium/organization?)

[apdavison]

Organisation needs to have shortName or acronym field, because full names are sometimes very long.

Example: "The College of the Holy and Undivided Trinity of Queen Elizabeth near Dublin", usually known as "Trinity College Dublin" (ROR) in English ("Coláiste na Tríonóide, Bhaile Átha Cliath" in Irish).

[apdavison]

Contact information should refer to just the current, preferred methods of contact.

[apdavison]

For scientific purposes, I think Location can be simplified to country (required), city (optional), administrativeDivision (optional).

[lzehl]

Alternative approach for the upper part

RP/RPV

replace "author", "developer", "otherContribution" with "contribution"
contribution (1-N) embedded type Contribution

New Contribution:

contributor (1-N) embedded type: Contributor (ordered list)
role (1) linked type: ContributionType

New Contributor:

legalPerson (1) linked category: legal person 
affiliation (1-N) linked type: Organization (ordered list)

[apdavison]

Yet another alternative approach for the upper part: flatten Contribution/Contributor:

RP/RPV

• replace "author", "developer", "otherContribution" with "contribution"
• contribution (1-N) embedded type Contribution

New Contribution:

• contributor (1) linked category: legal person
• role (1) linked type: ContributionType
• affiliation (1-N) linked type: Organization (ordered list)

(as above, the affiliations are understood to be those that applied at the time of the contribution).