Feature Request: Change Dataverse so that it can record RORs of built-in user accounts

[jggautier]

Overview of the Feature Request
Dataverse's backend needs to be able to record a ROR for the organizational name and affiliation of users' built-in accounts

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Developer, Sysadmin?

What inspired the request?
Efforts described and being tracked in IQSS/dataverse-frontend#1021 and IQSS/dataverse-frontend#1022 to let a user add an organizational name and affiliation to their built-in account in a way that lets Dataverse record the ROR of that organizational name and affiliation.

What existing behavior do you want changed?
The backend has a way to record the ROR of the organizational name and affiliation that a user added to their built-in account

Any open or closed issues related to this feature request?

• Continue evaluation of account page and deposit form redesigns for increasing ORCIDs and other ORCID-related recommendations in GREI Metadata Recommendations V2 dataverse-pm#473
• Feature Request: Let a user add an ORCID or ROR to indicate who owns the account during creation of the built-in account dataverse-frontend#1021
• Feature Request: Let a user add a ROR to describe their affiliation during account creation dataverse-frontend#1022

[jggautier]

In the related issue at IQSS/dataverse-frontend#1021, @pdurbin wrote:

the backend has been built to store two required fields: firstname and lastname in the authenticateduser database table. All the code dealing with users is oriented around those two fields. If we were to allow organizations to be users, how would we change the database and its constraints? What implications would it have on all the backend code?

I looked for a design doc that captured the decisions we made during the 4.0 rewrite but came up empty.