/api/pids GET is broken as of v6.2
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Looks like the /api/pids GET call is broken because it does a lookup of JvmSettings that, as of the change to multiple pid providers in 6.2, require specifying which provider to use. See https://github.com/IQSS/dataverse/blob/c6ccf8719d70664367bd6e65f6418017fdaaabfc/src/main/java/edu/harvard/iq/dataverse/api/Pids.java#L57-L59.
FWIW: There's a note to update to support more than just DataCite - my guess is a fix would start in that direction - parsing the incoming PID to find the provider is needed and one might then call methods in the correct provider to get the info.
What steps does it take to reproduce the issue?
Use the api
-
When does this issue occur?
-
Which page(s) does it occurs on?
-
What happens?
-
To whom does it occur (all users, curators, superusers)?
-
What did you expect to happen?
Which version of Dataverse are you using?
6.2+
Any related open or closed issues to this bug report?
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?
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
Start in src/main/java/edu/harvard/iq/dataverse/api/Pids.java around lines 57-59, where the /api/pids GET handler looks up JvmSettings. Read the multiple-PID-provider change and the provider methods it affects, then verify the endpoint can identify the provider from an incoming PID and return the expected information for configured providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100