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 Request/Idea : generated zip files naming dependent of dataset (no longer dataverse_files.zip) #9620

Open
DS-INRAE opened this issue May 26, 2023 · 3 comments
Labels
Feature: File Upload & Handling GREI 6 Connect Digital Objects Type: Suggestion an idea User Role: Guest Anyone using the system, even without an account

Comments

@DS-INRAE
Copy link
Member

Issue created by the "entrepot.recherche.data.gouv.fr" team (we use this to find them out)

Overview of the Feature Request
As a downloader of several/all files from several datasets, I want to be able to distinguish the various zip files from the different datasets.

What kind of user is the feature intended for?
All file downloaders via API or UI

What inspired the request?
Users and support team members downloading files from several datasets.

What existing behavior do you want changed?
Currently, for all datasets when a zip generated from datafiles it is always named "dataverse_files.zip". It would be nice to be able to identify by default the origin dataset if a user downloads several zips, whithout having the user changing it manually.
For Dataverse instances using DOIs the zip file name could be the suffix of the DOI :
image

@jggautier jggautier changed the title Feature Request/Idea : generated zip files naming dependent of dataset (nolonger dataverse_files.zip) Feature Request/Idea : generated zip files naming dependent of dataset (no longer dataverse_files.zip) May 26, 2023
@shlake
Copy link
Contributor

shlake commented May 26, 2023

Thanks for the reminder @pdurbin

Agree with this request - My thoughts on this issue:

....... the download file name for multiple file downloads be something other than "dataverse_files.zip". Because one could download from more than one dataset and they would all have the same filename, with "(n)" at the end to make the filename unique.

Maybe with some part (or all) of the DOI?

doi.10.7910_DVN_ZYVNLQ.zip
or ZYVNLQ.zip

And another suggestion (maybe a separate one, or a compromise) is to include the DOI in the manifest.txt file included in the "dataverse_files.zip"?

@DS-INRAE
Copy link
Member Author

I think the addition to the manifest is also a great idea, but indeed should be addressed in a separate issue for clarity

@pdurbin
Copy link
Member

pdurbin commented May 26, 2023

Credit to @shlake for posting this idea a while back: https://groups.google.com/g/dataverse-community/c/V-U1LsUNGxo/m/Me1LX0U9BAAJ

In terms of what to call the file, I'll note that BagIt export creates a file like this:

doi-10-5072-fk2-16erwxv1.1.zip

That's from doi:10.5072/FK2/16ERWX with a version of 1.1.

If people like this name for the zip file perhaps we could reuse it. The x and v are a little squished together though. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: File Upload & Handling GREI 6 Connect Digital Objects Type: Suggestion an idea User Role: Guest Anyone using the system, even without an account
Projects
Status: No status
Status: 🔍 Interest
Development

No branches or pull requests

4 participants