dataverse-frontend icon indicating copy to clipboard operation
dataverse-frontend copied to clipboard

Dataset Page: 404 error viewing Dataset if there is a deaccessioned version

Open ekraffmiller opened this issue 8 months ago • 1 comments

What steps does it take to reproduce the issue?

  1. Publish a dataset,
  2. Create a second version of the dataset and publish it
  3. Deaccession the second version of the dataset
  4. Logout
  5. Go to the Root collection page
  6. The Published version of the dataset should be visible, click on that
  7. 404 Error
  • Which page(s) does it occur on? Dataset Page

  • What happens? 404 Error

The API call generating the error is: http://localhost:8000/api/v1/datasets/:persistentId/versions/:latest-published/downloadsize?persistentId=doi:10.5072/FK2/IOFMXO&includeDeaccessioned=true&mode=Original

Error Message: {"status":"ERROR","message":"Dataset version :latest-published of dataset 4 not found"}

  • To whom does it occur (all users, curators, superusers)? users who are not logged in

  • What did you expect to happen? It should show the published version of the Dataset

Screenshots:

Image

ekraffmiller avatar Apr 30 '25 17:04 ekraffmiller

The file downloadSize cannot be fetched by public when the dataset includes a deaccessioned version. created a new issue https://github.com/IQSS/dataverse/issues/11465

In SPA, we have the 404 error on files/downloadSize and files/count, when dataset is deaccessoioned. In JSF, we only show the version tab here, instead of all info for unauthenticated user. Image

For ones having the access Image

Also,

  • If the version are deaccessioned, the version tab in dataset page should disable checkbox, version link and View Details of the deaccessioned version, so it would not call the compare 2 versions api (cause errors for deaccessioned version)

ChengShi-1 avatar May 02 '25 21:05 ChengShi-1