Feature Request/Idea: add _double-zip on the fly_ as an _opt-in widget_ on the UI for data upload
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Add double-zip on the fly as an opt-in widget on UI so it happens on the fly. To the right of the Select files to add widget for example.
Adding a link to documentation on how to do double-zip programmatically would also be useful imho.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Plenty. See https://github.com/IQSS/dataverse/pull/5396 https://github.com/IQSS/dataverse/issues/3439 https://github.com/IQSS/dataverse/issues/2107
What inspired the request?
Unzipping is very inconvenient for what we are trying to do in JuliaEO.
What existing behavior do you want changed?
To quote from @mankoff in one of the previously closed issues:
Perfect FAIR-ness and not supporting ZIP files will make some users use other solutions. I think the correct behavior is to allow ZIP files, but discourage it. Make us jump through some hoops to do it, but allow it. Archives of some type is a requirement for certain types of data.
For the hoop, an opt-in widget on the UI to trigger double-zip on the fly seems simple enough for user to jump through.
Also, embedding a link to a code snippet showing how to do it programmatically would help folks like myself.
Any brand new behavior do you want to add to Dataverse?
Any related open or closed issues to this feature request?
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 tracing the UI around the “Select files to add” widget and review the linked issues and pull request for existing double-zip behavior. Determine the opt-in interaction, upload flow, and programmatic documentation needed; done means the behavior is specified, implemented, and documented with appropriate UI coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100