Feature Request: Need ability to configure new institutions (dataverse.person-or-org.org-phrase-array)

[stevenwinship]

Overview of the Feature Request While testing #12248 it was found that the institution "Geological Survey of the Netherlands" was showing up as a person's name instead of an Institution. This request is to add functionality to improve on that.

Any brand new behavior do you want to add to Dataverse? ability to configure new institutions since the NameFinder data files are old

**Any open or closed issues related to this feature request?**#12248

[stevenwinship]

Per Dataverse docs:

dataverse.person-or-org.org-phrase-array
Please note that this setting is experimental.

The Schema.org metadata and OpenAIRE exports and the Schema.org metadata included in DatasetPages try to infer whether each entry in the various fields (e.g. Author, Contributor) is a Person or Organization. If you have examples where an organization name is being inferred to belong to a person, you can use this setting to force it to be recognized as an organization. The value is expected to be a comma-separated list of strings. Any name that contains one of the strings is assumed to be an organization. For example, “Project” is a word that is not otherwise associated with being an organization.

Can also be set via MicroProfile Config API sources, e.g. the environment variable DATAVERSE_PERSON_OR_ORG_ORG_PHRASE_ARRAY.

Note: This setting was previously called dataverse.personOrOrg.orgPhraseArray and expected a JsonArray of strings. Please update both the name and value format if using the old setting.

[jggautier]

This idea of letting repository managers add to a list of known person and organization names might work well for managers of some Dataverse repositories, but I don't think it's worked well for folks managing repositories like Harvard Dataverse, and maybe other repositories where there isn't enough staff to monitor the number of names included in datasets created every day.

Other ideas that I think might be more scalable, like letting depositors, at the time of deposit, indicate or verify that a name is a person or organization, have been postponed because we've generally put off those kinds of user-interface changes until we can make them for users using the Modern UI.

I'm writing this just to say, or maybe make more explicit, that the ability to configure new institutions in the "NameFinder data files" might not be a great long-term solution since folks managing Harvard Dataverse haven't had the resources to update that list of people and organizations, and this might be the case for managers of other Dataverse repositories.

[stevenwinship]

@jggautier Unfortunately we don't have the ability to add to the existing NameFinder data file. And creating a secondary file doesn't work either. We can hold off on this until we can have a discussion that allows for UI updates

[stevenwinship]

I like the idea of adding a type to the author. I think It will simplify things for the users

[qqmyers]

See gdcc/dataverse-external-vocab-support#58