Add support for organization information

[briri]

We are in the process of adding organization identifiers to the DMPRoadmap codebase, specifically ROR and FundRef. It would be useful to somehow incorporate these into the Common Standard schema.

Perhaps something like:

"affiliation": {
  "name": "University of Virginia",
  "abbreviation": "UVA",
  "url": "https://www.virginia.edu",
  "affiliation_id":  {
     "type": "ror", 
     "identifier": "https://ror.org/0153tk833" 
  }
}

This could then:

• be added to the contact and contributors as affiliation
• replace the current name and funder_id on the funding object as funder

[rduyme]

Hi, feedback as part of OSTrails.

warn on integration of “affiliation” and “ROR”

example of possible implementation issue : https://community.crossref.org/t/ror-affiliation-raw-affiliation-in-american-physical-society-aps-publisher-publications/12450/9

[briri]

Thanks @rduyme!

I have a PR, #71 , open that has an example of an affiliation portion of the record.

For the proposed schema addition, both the affiliation name and organizational identifiers are optional fields, allowing systems to use them as separate assertions. I think this should avoid potential issues like the one cited, where affiliation strings are replaced with the names in ROR records or ROR IDs (and other organizational identifiers) are used exclusively in place of affiliations.

ROR is just one type of identifier that can be included. We have allowed for url as another catch-all type in that enum. We can expand on that further in the future with more specific identifier types.

The schema definition for the affiliation identifier reads:

  "title": "The affiliation ID",
  "description": "Recommend using Research Organization Registry (https://ror.org)"
  "examples": ["https://ror.org/05dc6w374", "https://rd-alliance.org"]
  "enum": ["ror", "url"],

The schema definition for the affiliation name is:

  "title": "Name of the instituion/organization",
  "description": "Official institution/organization name",
  "examples": ["Example University"]

Perhaps we can reword those 2 to make it clear that the identifier should not be used to convey a human readable name for the affiliation, but rather a unique and persistent identifier.

[rduyme]

Hi Brian,

Suggestion to simplify affiliation (this is "label" approach we decided to take for SKG-IF, to cover every possible need of a user)

  "label": "Name of the institution/organization or full address",
  "examples": ["University  of California", "California Digital Library, University  of California, CA, US", "California Digital Library, University of California Office of the President, Oakland, CA", "California Digital Library, CA, US", "California Digital Library, California, USA"]

An affiliation is just a free label. from this label you can have a one or more ROR, this can be done at any stage by a human or an IA model ( ex: see authors ROR institutions derived from label raw affiliation by OpenAlex model in https://api.openalex.org/works/doi:10.1890/120103 )

My opinion is that it is very important to just give the freedom to a user to express a full affiliation with many details (lab, department, sub department, sub sub sub department, school of university university, city state, country etc...) => And not even try to model this structure that is different for every country in the world... :-)

ROR is just categorisation, a ROR can even not exists at the time you create the DMP, ( or can even be created 2 years later ;-) )