Ingest Modularity/Improvements
Open
Nobody has claimed this yet.
Feature: File Upload & Handling
Type: Suggestion
User Role: Depositor
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Related to ingest, I'm interested in
- allowing installations to ingest larger files ( handled in IQSS/dataverse.harvard.edu#111)
- not experiencing system instability due to aforementioned large file ingests, or many ingests ( handled in IQSS/dataverse.harvard.edu#111)
- allowing for external developers to more easily utilize the ingest code (I'm thinking TRSAs that want to generate and deposit metadata to a Dataverse installation ex. https://github.com/akio-sone/dataverse-ingest)
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
The issue names no files, tests, or entry points; start by reading IQSS/dataverse.harvard.edu#111 and the dataverse-ingest project to clarify which ingest goals remain. Done is not defined beyond larger-file stability and easier external use, so acceptance criteria need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100