Export Failed (403) when following directApiCall URL from OAI-PMH dataverse_json record
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?
- GET /oai?verb=GetRecord&metadataPrefix=dataverse_json&identifier=
- Read the directApiCall attribute from the element. It contains:
.../api/datasets/export?exporter=dataverse_json&persistentId= - Follow that URL exactly as returned.
-
When does this issue occur?
When you follow the directApiCall URL as published by the OAI-PMH
server -
Which page(s) does it occurs on?
/api/datasets/export -
What happens?
You got a "Export Failed" message -
To whom does it occur (all users, curators, superusers)?
all users -
What did you expect to happen?
The dataset JSON.
Which version of Dataverse are you using?
6.11
Any related open or closed issues to this bug report?
Screenshots:
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 at the OAI-PMH GetRecord endpoint and trace how its dataverse_json metadata builds the directApiCall URL, then inspect /api/datasets/export handling. Reproduce the exact published URL, including its escaped query separator, and verify that it returns dataset JSON rather than Export Failed (403).
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100