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

Editing a deaccessioned dataset: the file edit options should allow the "delete" function to work #9351

Closed
sbarbosadataverse opened this issue Feb 1, 2023 · 7 comments · Fixed by #10901
Labels
Feature: Deaccession Size: 10 A percentage of a sprint. 7 hours. Type: Bug a defect
Milestone

Comments

@sbarbosadataverse
Copy link

sbarbosadataverse commented Feb 1, 2023

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 does this issue occur?

When you attempt to revive/edit a deaccessioned dataset for republishing

  • Which page(s) does it occurs on?

Dataset landing page

  • What happens?

Error message that files can't be deleted/etc

  • To whom does it occur (all users, curators, superusers)?

curators, superusers

  • What did you expect to happen?
    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:

@sbarbosadataverse sbarbosadataverse changed the title Editing a deaccessioned dataset: the file edit options should not show an error message Editing a deaccessioned dataset: the file edit options should allow the "delete" function to work Feb 1, 2023
@cmbz cmbz added the Size: 3 A percentage of a sprint. 2.1 hours. label Jul 10, 2024
@cmbz
Copy link

cmbz commented Jul 10, 2024

2024/07/10

  • Sized at 3, will resize if it turns out not to be an easy fix.

@jp-tosca jp-tosca self-assigned this Sep 30, 2024
@jp-tosca
Copy link
Contributor

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.

@jp-tosca
Copy link
Contributor

The Id of the dataset is coming as null when it is retrieved from a deaccessioned Dataset in :

@qqmyers
Copy link
Member

qqmyers commented Sep 30, 2024

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.

@jp-tosca jp-tosca added Size: 10 A percentage of a sprint. 7 hours. and removed Size: 3 A percentage of a sprint. 2.1 hours. labels Oct 1, 2024
@jp-tosca
Copy link
Contributor

jp-tosca commented Oct 1, 2024

Thanks for the info @qqmyers!

@jp-tosca
Copy link
Contributor

jp-tosca commented Oct 3, 2024

This should be solved by #10901 @sbarbosadataverse, thanks for opening the issue!

@jp-tosca jp-tosca removed their assignment Oct 3, 2024
@pdurbin pdurbin added this to the 6.5 milestone Oct 3, 2024
@pdurbin
Copy link
Member

pdurbin commented Oct 3, 2024

@sbarbosadataverse you could test on https://beta.dataverse.org if you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Deaccession Size: 10 A percentage of a sprint. 7 hours. Type: Bug a defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants