Pull Request Overview

Opened on October 7, 2026
Status Open
Commit count 1 with first commit October 7, 2026

Total Delta

587 Total Diff Delta

Open Days

Open 20 weekdays

Test Delta

202 Diff Delta in Test Files

Breakdown by Phase

How long has this pull request spent in each phase of its lifecycle?

Fraction of total time	Business days	Phase
N/A	37.0 days	Issue creation to work beginning
	0.0 days	Authoring 1 commit before pull request opened for review
	0.0 days	Awaiting first review
	20.4 days	Revising work with 0 commits in response to 1 review that left 6 comments

Total time for pull request still awaiting merge (longer than repo's target): 20.4 business days

support RORs at the account level

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

This work implements Feature Request: Change Dataverse so that for built-in user accounts, Dataverse can record RORs of organizations that users enter in the affiliation field (open)

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

Comments Threads Pending Resolution

github-advanced-security[bot] reviewed on October 7, 2026

src/main/java/edu/harvard/iq/dataverse/api/Users.java

            user.setRors(rorIds);

            user = userSvc.save(user);

            return ok(JsonPrinter.jsonRors(user.getRors()));

        } catch (IllegalArgumentException ex) {

            return badRequest(ex.getMessage());