metadata export API exports metadata from harvested datasets, caches locally
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
I noticed this on v5.9 but reproduced the behavior on v5.13 this morning.
When an anonymous user calls the /api/datasets/export API endpoint using the DOI of a harvested dataset, Dataverse writes out the export_format.cached file in a directory structure appropriate to the originating instance, then returns the file.
I asked in Slack because Dataverse reports the parent collection (root dataverse) as the publisher.
Proposed corrections included preventing Dataverse from exporting harvested metadata, or redirecting (via 301 or text response) to the primary Dataverse instance, as would happen in the GUI.
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 /api/datasets/export endpoint and trace how DOI requests for harvested datasets are handled, including creation of export_format.cached. Compare this path with the GUI behavior for harvested metadata. Done means an agreed behavior is implemented: prevent the export or redirect the requester to the primary Dataverse instance.
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
- 35/100