as a data provider, I'd like to look up a dataset's available upload mechanisms
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Currently, the wonderful DV-Uploader has no way to determine whether the storage driver housing a given dataset is capable of direct uploads, and so defaults to normal uploads unless instructed to use direct.
Soon, Dataverse will add HttpOverlay store- and Globus support, so this is a placeholder issue for an API endpoint which might allow such a look up externally.
In the particular case of direct-to-S3, this could allow DV-Uploader and other clients to default to direct unless told not to, which would save Dataverse application nodes some serious wear and tear caused by users who may not know the difference.
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 by reviewing how DV-Uploader determines upload behavior and how Dataverse storage drivers expose direct-upload capability. Clarify the endpoint contract, including support for direct-to-S3, HttpOverlay, and Globus, before identifying the implementation and tests. Done means external clients can reliably look up the available upload mechanisms for a dataset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100