-
Notifications
You must be signed in to change notification settings - Fork 492
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
Editing a deaccessioned dataset: the file edit options should allow the "delete" function to work #9351
Comments
2024/07/10
|
I can confirm this happens on deaccessioned datasets, while a solution is ready a quick way around is adding a file will create a draft version and will let it to be updated, this error happens when a file or any operation on the files is done on a deaccessioned dataset. |
The Id of the dataset is coming as null when it is retrieved from a deaccessioned Dataset in : Line 117 in c59746d
|
I think that makes sense - a draft version has just been created and is not yet in the db so has no id. The next line would retrieve the deaccessioned version when id is null. |
Thanks for the info @qqmyers! |
This should be solved by #10901 @sbarbosadataverse, thanks for opening the issue! |
@sbarbosadataverse you could test on https://beta.dataverse.org if you like. |
What steps does it take to reproduce the issue?
From a deaccessioned version, any file-related action (deleting, restricting files, adding tags, etc), results in error banners and confusing success banners to appear and doesn't cause a draft version to be created
Visit a deaccessioned dataset to edit for republishing. login, and select file, delete files
select files and select the delete option, or any other option
When you attempt to revive/edit a deaccessioned dataset for republishing
Dataset landing page
Error message that files can't be deleted/etc
curators, superusers
expected file actions to work and create new draft
Which version of Dataverse are you using?
latest release 5.13
Any related open or closed issues to this bug report?
none
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:
The text was updated successfully, but these errors were encountered: