Skip to content

Tags Attack! Tag Uniqueness is not enforced, resulting in multiples in select list and assigned in db. #5002

@kcondon

Description

@kcondon

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions