support RORs at the account level #12803

Open
pdurbin opened 1:36pm on October 7, 2026 wants to merge 587 Ξ” into iqss/dataverse develop from
12620-account-rors

Overview of the Feature Request Dataverse's backend needs to be able to record RORs for the affiliations 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 https://github.com/IQSS/dataverse-frontend/issues/1022 to let a user add an affiliation to their built-in account in a way that lets Dataverse record the ROR of that affiliation.

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

Any open or closed issues related to this feature request? - https://github.com/IQSS/dataverse-pm/issues/473 - https://github.com/IQSS/dataverse-frontend/issues/1022

Diff Delta:
587
About 37 Diff Delta/hour
Classified as:  Feature Add

pdurbin's Description of Work #12620 Feature Request: Change Dataverse so that for built-in user accounts, Dataverse can record RORs of organizations that users enter in the affiliation field

What this PR does / why we need it:

Which issue(s) this PR closes:


  • Closes #12620

Special notes for your reviewer:

Suggestions on how to test this:

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

https://dataverse-guide--12803.org.readthedocs.build/en/12803/api/native-api.html#manage-a-user-s-rors

11 total changed files
(2 files ignored)
Loading changes...
Loading changes...
Loading changes...
Loading changes...
Loading changes...
Loading changes...
That’s the last hunk
The diff well is dry.