Feature Request: Change Dataverse so that it can record RORs of built-in user accounts
@jggautier is already working on this.
Since Aug 20, 2026.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
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 https://github.com/IQSS/dataverse-frontend/issues/1021 and https://github.com/IQSS/dataverse-frontend/issues/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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.