-
Notifications
You must be signed in to change notification settings - Fork 500
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
Tags Attack! Tag Uniqueness is not enforced, resulting in multiples in select list and assigned in db. #5002
Comments
Highly related to Edit File Tags: Duplicate Custom Tags #2991. |
Moving comment from #2991 here and closing that as a duplicate.
|
|
To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'. If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment. |
Reported by our internal data curation team:
On Friday, I was meeting with Danny when he noticed that there continues to be duplicate tags listed when applying tags to files on Dataverse. He thought this bug was fixed in the latest release to the issue persists. I was working on a MRA study (https://hdl.handle.net/1902.1/00640) when he noticed the duplicates.
It turns out it is not uncommon to copy and paste an existing tag into the create custom tag edit field rather than selecting the already created tag of the same name from the tag list box. Since we do not enforce tag uniqueness for a dataset, this results in multiple tags of the same name both in the db and in the tag select list, causing confusion.
This ticket is about enforcing unique tags for a dataset and also cleaning up existing records that may have used these multiple tags.
A power user (Dawyne) requested to have a future solution detect a duplicate if entered and rather than fail, just use the existing tag.
The text was updated successfully, but these errors were encountered: