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

Spike: investigate adding folder support to Primefaces upload component #6696

Closed
scolapasta opened this issue Feb 26, 2020 · 5 comments
Closed

Comments

@scolapasta
Copy link
Contributor

Currently when you drag a folder into the file upload component, the structure is flattened. There is a primefaces issue: primefaces/primefaces#2705 but no plan for them to work on it.

This issue is for us to investigate either adding the code to primefaces ourselves or finding some other workaround.

@djbrooke
Copy link
Contributor

@scolapasta is this a dupe and/or possible solution to #6692 ?

@pdurbin
Copy link
Member

pdurbin commented Sep 30, 2022

This may not be needed now that @qqmyers has created https://github.com/gdcc/dvwebloader ! 🚀 🎉

@jggautier
Copy link
Contributor

I'd have concerns about only adding dvwebloader in Dataverse repositories as a solution to letting depositors more easily upload files organized in folders without needing to first compress them in a zip file (and have Dataverse retain that structure so it can be displayed and re-created on download).

The dvwebloader option is displayed in the dataset page's "Access" dropdown menu. I don't think that depositors would know to look there in order to upload the folders that contain their data. And if they did, I don't think they know that the menu's dvwebloader option is what would let them upload folders.

Is dvwebloader added in a Dataverse repository now, and what do depositors think about how it works?

@qqmyers
Copy link
Member

qqmyers commented Nov 28, 2022

W.r.t. the Access menu, see #9095 / #9096.

@cmbz
Copy link

cmbz commented Aug 20, 2024

To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'.

If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment.

@cmbz cmbz closed this as completed Aug 20, 2024
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

7 participants