ROR "label" field text displays in affiliation instead of "ROR display" field
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
-
When does this issue occur?
When filling out the affiliation using the ROR external vocabulary in a draft dataset -
Which page(s) does it occurs on?
It occurs within the citation metadata block. -
What happens?
I happened to try to enter "University of Oxford" in the affiliation field, but didn't see a ROR ID next to it (see image below). I then looked at the ROR site for the correct ID, which is 052gg0110. If you use that ID you get the Welsh translation of the University of Oxford. I then tried an Irish university thinking that because the government requires everything in both Irish and English, maybe something similar would happen. It did. I entered "Technological University Dublin", which is Ollscoil Teicneolaíochta Bhaile Atha Cliath, ROR id 04t0qbt32. Looking at the JSON, these are the "label" field. -
To whom does it occur (all users, curators, superusers)?
All users with the power to create a dataset. -
What did you expect to happen?
I expected the text from “ror display” to show instead of the text from “label”
Which version of Dataverse are you using?
6.7.1
Any related open or closed issues to this bug report?
None that I could find. But, I did reach out directly to ROR support December 17th. I've copied their response below
"Hi Betsy,
Thanks for flagging this. Ultimately, how any integrator chooses to makes use of our API and data is beyond our control, but we would generally not expect this behavior unless the user explicitly chose one of these labels, as opposed to the display name. We can reach out to our contacts on the Dataverse team about this issue, but would advise that you also create a support ticket with them to investigate."
Screenshots:
Are you thinking about creating a pull request for this issue?
At the moment, we do not have capacity to help :-(
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.
Research direction
Reproduce the issue in the citation metadata block while entering ROR affiliations in a draft dataset, using the University of Oxford or Technological University Dublin records described here. Compare the displayed affiliation text with the ROR API response and the expected “ror display” value. Done means the display value appears instead of the ROR “label” value for affected records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100