Repository navigation
Feature Request: Change Dataverse so that for built-in user accounts, Dataverse can record RORs of organizations that users enter in the affiliation field #12620
Description
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 IQSS/dataverse-frontend#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?
- 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 a ROR to describe their affiliation during creation of a built-in account dataverse-frontend#1022
Metadata
Metadata
Type
Projects
- Status
Activity
[-]Feature Request:[/-][+]Feature Request: Backend changes to record RORs of built-in accounts[/+][-]Feature Request: Backend changes to record RORs of built-in accounts[/-][+]Feature Request: Change Dataverse so that it can record RORs of built-in user accounts[/+]jggautier commentedon Aug 19, 2026
In the related issue at IQSS/dataverse-frontend#1021, @pdurbin wrote:
jggautier commentedon Sep 28, 2026
In meetings this month we discussed concern that when users enter organizations in the name fields of built-in accounts, letting Dataverse record those RORs can signal support of organizational Dataverse accounts and of account password sharing.
I'm adjusting the titles and first comments of this and connected GitHub issues to remove plans for making Dataverse record the RORs of organizations that users enter in the name fields of built-in accounts. Instead this issue will track work that supports having Dataverse record RORs of organizations that users enter in the affiliation field when they create and edit built-in accounts.
[-]Feature Request: Change Dataverse so that it can record RORs of built-in user accounts[/-][+]Feature Request: Change Dataverse so that for built-in user accounts, Dataverse can record RORs of organizations users enter in the affiliation field[/+][-]Feature Request: Change Dataverse so that for built-in user accounts, Dataverse can record RORs of organizations users enter in the affiliation field[/-][+]Feature Request: Change Dataverse so that for built-in user accounts, Dataverse can record RORs of organizations that users enter in the affiliation field[/+]cmbz commentedon Oct 1, 2026
2026-10-01: During the GREI meeting, we decided on the following next steps
pdurbin commentedon Oct 1, 2026
I threw some thoughts in a google doc. Let's discuss! 😄
jggautier commentedon Oct 5, 2026
@pdurbin I left some comments, edits and questions on the doc.
pdurbin commentedon Oct 8, 2026
Fruitful design meeting today. Some notes: https://docs.google.com/document/d/1VJvp9qOHQLi6Vvqj0u79ktLu9sF_7mTbna5MaD95IME/edit?usp=sharing
jggautier commentedon Oct 19, 2026
@pdurbin and I discussed on Slack the following day (Oct. 9) and since then have been discussing in Slack and leaving more updates in the "ROR for accounts" Google Doc.
I drafted an outline that organizes the options we've talked about so far for redesigning parts of Dataverse so that it can record the ROR of the affiliation of a user's account, and so that ROR can be added to the datasets that the user creates. And in relevant parts of the outline I added the questions we have so far.
I'm trying to help answer those questions, and at IQSS/dataverse-frontend#1022 (comment) I also asked a larger question about scope.