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

Hovering mouse over Download button does not reveal the URL of the file and the URL does not contain the file name #2416

Closed
pdurbin opened this issue Jul 27, 2015 · 6 comments
Labels
Feature: File Upload & Handling Type: Suggestion an idea UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@pdurbin
Copy link
Member

pdurbin commented Jul 27, 2015

If you go to https://zenodo.org/record/18898#.VbZZpZNVhBd and hover your mouse over the "Download" button you will see the URL https://zenodo.org/record/18898/files/MHC_PosSel_dataset.zip which is a direct link to the file. You can email this link to someone and it will work.

screen shot 2015-07-27 at 12 18 18 pm

If you go to https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/DAGL4S and hover your mouse over the "Download" button the URL you see is https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/DAGL4S# which is not a link you can send to someone to download the file in question. You have to click the link (which does a POST) and then the file is downloaded. Furthermore in the URL to download this file, the file name is a number rather than "R_code_for_replication.R".

screen shot 2015-07-27 at 12 17 10 pm

At https://groups.google.com/d/msg/dataverse-community/Uz-_PoyxvY0/qCVxmTdlEDoJ this problem was expressed in this way:

So Adam...

You are happy using the SWORD api to get a list of file #'s and file names and then working that out off line to provide direct links to your files? I'm writing up some author instructions right now for using 3rd party repositories in AAS articles and this is utterly baffling to explain this compared to Zenodo, which uses restful real file names to resolve to files.

To be clear, if one is building an application around a Dataverse dataset, then the SWORD API seems like an awesome solution. But if all you (the dataset author) want to do is reuse the direct link to a file in another place this(*) is a huge, huge barrier.

But maybe I need another astronomer's perspective here on what is and isn't useful about file level links.

  • Gus

(*): calling a file named trees.png "https://apitest.dataverse.org/api/access/datafile/12" instead of something human readable.

@pdurbin pdurbin added the Type: Suggestion an idea label Jul 27, 2015
@keflavich
Copy link

👍 this is what I want!

@augustfly
Copy link

yah. me too. and if I think of any permutations i'll comment promptly.

@pdurbin
Copy link
Member Author

pdurbin commented Oct 30, 2015

Related: #2700

@mercecrosas mercecrosas modified the milestone: In Review Nov 30, 2015
@mheppler mheppler added UX & UI: Design This issue needs input on the design of the UI and from the product owner Feature: File Upload & Handling labels Jan 28, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@binarybottle
Copy link

What is the status of file-level persistent URLs?

@pdurbin
Copy link
Member Author

pdurbin commented Jun 15, 2016

https://help.hmdc.harvard.edu/Ticket/Display.html?id=236541 has details about another request for this feature. I've invited that person to comment here as well.

@djbrooke
Copy link
Contributor

djbrooke commented Oct 7, 2016

Going to close this in favor of #2700.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: File Upload & Handling Type: Suggestion an idea UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

8 participants