Bug: Current Dataset Version Update failed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
- When does this issue occur?
After making two minor changes in the Related Publication fields Identifier and URL, I tried to update the current version of this TROLLing dataset: https://doi.org/10.18710/XKDBLF, with the superuser option "Update Current Version (will permanently overwrite the latest published version)", but got the following error message:
Error – Dataset Version Update failed. Changes are still in the DRAFT version. - edu.harvard.iq.dataverse.engine.command.exception.CommandException: Command edu.harvard.iq.dataverse.engine.command.impl.CuratePublishedDatasetVersionCommand@33eaee58 failed: Cannot merge an Entity that has been removed: edu.harvard.iq.dvn.core.study.FileMetadata[id=209002] If you believe this is an error, please contact DataverseNO Support for assistance.
-
Which page(s) does it occurs on?
On the dataset landing page of this TROLLing dataset: https://doi.org/10.18710/XKDBLF. -
What happens?
I get the error message pasted above. -
To whom does it occur (all users, curators, superusers)?
Superusers. -
What did you expect to happen?
The dataset to be updated without there being issued a new version.
Which version of Dataverse are you using?
5.13
Any related open or closed issues to this bug report?
No, but the issue was discussed in the Dataverse Google Group (https://groups.google.com/u/1/g/dataverse-community/c/6smbEFyq_Ok), and it turns out to be a bug in the Dataverse software.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on Dataverse 5.13 using the dataset and superuser update workflow described in the issue. Trace the CuratePublishedDatasetVersionCommand error involving the removed FileMetadata entity; done means the current published version updates successfully without creating a new version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100