Dataverse don't show alerts when a user wants to delete files in a dataset with metadata value corrupted.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
In recent days, an user sent us a ticket that talking about a problem when he wants to delete a file. Basically, when he clicks on the remove button and confirms, dataverse doesn't do anything. Not messages error in UI or internal logs and it doesn't create an draft version.
We investigated and tried to recreate the issue we make some test wich can be help us:
- We changed a metadata field. If all things was correct a draft version was created. But, dataverse showed this error:
@alejandratenorio found that the error was caused for a metadata value, it had a blank space.
She resolved the metadata issue and saved the changes. Eventually, Dataverse created the draft version, and we were also able to delete the data file. If she hadn't checked the metadata fields, we wouldn't have identified the error, as establishing a connection between the corrupted metadata value and the ability to delete a file from the dataset can be misleading.
Our question is: Do you have any way to alert when the dataset has a problem with its metadata values? I mean, in case to the users only want to delete a file without change info. Dataverse don't show any alert and the problem can be confuse for users with little experience in Dataverse
- When does this issue occur?
When we want to edit metadata in old datasets. I think before a field validation.
- Which page(s) does it occurs on?
In dataset.xhtml
Which version of Dataverse are you using?
5.10.1
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 with dataset.xhtml and trace the file-deletion confirmation flow, then inspect how metadata validation failures are handled for older datasets. Reproduce the corrupted metadata case and determine where the failure becomes silent; done means users receive a clear alert instead of an apparently ineffective deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100