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

Improve Notice (Error) when trying to view a Previous version with non-restricted file #6057

Closed
shlake opened this issue Jul 26, 2019 · 5 comments
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: File Upload & Handling Type: Bug a defect User Role: Guest Anyone using the system, even without an account

Comments

@shlake
Copy link
Contributor

shlake commented Jul 26, 2019

When I tried to "download" a previous version of a file that had been originally unrestricted, and is now restricted, I get the error (makes sense, but would have thought the error would have been in the UI):

{"status":"ERROR","code":403,"message":"'/api/v1/access/datafile/309012' you are not authorized to access this object via this api endpoint. Please check your code for typos, or consult our API guide at http://guides.dataverse.org."}

My example: current version of dataset has restricted (just restricted - no request) file:
https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/GAU2NW

If select "Versions" tab and click on version 2.0
https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/GAU2NW&version=2.0

I see the "not restricted" link for this file "Optional Student Spring_2017.ppt"
and when click on download get the error in my browser.

Would have expected a popup window, or a "red" in-page warning box.

@jggautier
Copy link
Contributor

I think this is the same problem described in this GitHub issue, #3576, where it was proposed that the download button be removed from previous dataset versions.

@shlake
Copy link
Contributor Author

shlake commented Jul 26, 2019

@jggautier Yes, thanks for pointing that out. I try to search open issues before I create a new one, but it is hard with so many and with so many different takes on the same issue. Thanks.

@jggautier
Copy link
Contributor

Agreed, tough to keep track!

@djbrooke asked me to move info from #3576, which references an even older issue, into this issue:

In #4154, @sbarbosadataverse commented on Sep 25, 2017:

I created a new version of a dataset and restricted previously open data files. New version was published. I went back to the archived version and expected to see the data files now restricted, but no lock, red or green, was available (in super user mode or logged out mode).

The download option showed me all available tabular data options and only when I clicked on any of the download options did it show an error. Two ravens was also still available for me to click on and when I did, it redirected to two ravens but no error message and no variables.

The workflow should be that previously open data files (or any files), in archived versions, should not show explore, or download option, and should have the green or red lock to indicate file is restricted.

In #3576, @jggautier commented on Jan 17, 2017:

If previous versions of currently restricted files should not be downloaded, should their download buttons (and Explore-like buttons) be removed (or replaced with a request access button when the current file can only be accessed by request?)

@scolapasta replied on July 26, 2019:

@jggautier yes in previous versions download button should be removed, but we should also note that it had been unrestricted. i.e. just removing the button doesn't give complete info.

@shlake
Copy link
Contributor Author

shlake commented Jul 26, 2019

Should add that it is not just the Download button. On a previously unrestricted file (version page), the Download URL shows as well. Which does not work, gives same error as clicking the download button.

@pdurbin pdurbin added Feature: File Upload & Handling Type: Bug a defect User Role: Guest Anyone using the system, even without an account Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. labels Oct 15, 2022
@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
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Feature: File Upload & Handling Type: Bug a defect User Role: Guest Anyone using the system, even without an account
Projects
None yet
Development

No branches or pull requests

4 participants