dataverse
dataverse copied to clipboard
Dataset with "Submitted for Review" Banner but Already Published
What steps does it take to reproduce the issue?
-
When does this issue occur?
-
Which page(s) does it occurs on? Dataset page
-
What happens?
We (Cirad Dataverse) noticed a strange error in the database. In the datasetlock table, there are 10 datasets with the status "in review". However, on the GUI, only 8 datasets show the same status. Upon inspecting these datasets, we observed that the 2 additional datasets had no drafts in progress and that the revision dates of these drafts were earlier than the supposed review request dates:
-
Dataset 1: Last version date: 2023-06-05; review request date: 2024-02-23
-
Dataset 2: Last version date: 2024-01-25; review request date: 2024-03-12 The "submitted for review" banner appears on these pages for those with admin rights. We upgraded to version 5.13 in December, and no maintenance dates seem to match any potential problems.
-
To whom does it occur (all users, curators, superusers)?
A contributor to the dataset can no longer edit it. Which is logical, given that the dataset is in the datsetlock table. Admin can edit the dataset, as expected
- What did you expect to happen?
A solution is describe in this page I think we're in a similar situation to the one described in the admin guide https://guides.dataverse.org/en/latest/admin/troubleshooting.html#a-dataset-is-locked-and-cannot-be-edited-or-published
Which version of Dataverse are you using?
V5.13
Any related open or closed issues to this bug report?
https://github.com/IQSS/dataverse/issues/8875
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
- https://help.github.com/en/articles/file-attachments-on-issues-and-pull-requests