Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Allow zipped download of open access data #388

Open
Danny-dK opened this issue Mar 21, 2024 · 3 comments
Open

[FEATURE] Allow zipped download of open access data #388

Danny-dK opened this issue Mar 21, 2024 · 3 comments

Comments

@Danny-dK
Copy link

Danny-dK commented Mar 21, 2024

Is your feature request related to a problem? Please describe.

When data is openly published, there is no easy download feature to download data immediately (which is available in for example Zenodo, DANS, 4TU, Dataverse, etc).

Describe the solution you'd like

Be able to download as, for example, a zip file. SURF might be implementing it as a bagit file?

Describe alternatives you've considered

Connect to the publication address in your client of choice, but can be cumbersome for some researchers.

@peer35
Copy link

peer35 commented May 2, 2024

I agree, but we must consider what should happen if a dataset is very large (>100GB). In that case mounting with webdav is the better option.

@Danny-dK
Copy link
Author

Danny-dK commented May 2, 2024

True. Perhaps only up until a certain size (whatever size is acceptable). Whenever it is larger than 100GB, webdav is likely quite slow as well, I guess accessing it trough iRODS would then be better? Within the Yoda webportal at the bottom of each webpage there is the irods environment json configuration (if you click on the Yoda version). That type of configuration information could possible be shown on the public data package page? (I've actually never tried to use iCommands for a publicly available data package).

@jelletreep
Copy link
Member

By accident opened exactly the same feature request 😄 . I think this might be a real deal breaker for smaller projects (at least for the publication step). In our project we work with a substantial amount of smaller files, and for the moment we will probably go with Dataverse instead. A size limit of e.g. 10-100 GB seems logical

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants