Web Client: Record Bucket duplicates require separate removal

[Anna Goben]

Evergreen 3.0
Chrome 65.0.3325.162

If you accidentally (or intentionally) add a record to a record bucket multiple times staff-side, it folds the records so you only see one entry for each record (with no indication that there are duplicates entered). If you attempt to remove the titles from the bucket then you have to remove the titles in batches as it appears to have failed for any duplicate entries. It has only removed one copy of the record from the bucket, so then you have to repeat the removal as often as you've added the record. This is both confusing for staff and adds extra work.

I assume this also affects patrons, but haven't tested on that side.

[Pamela Smith (pamela-smith)]

Related to this, when duplicate items are removed from a copy bucket in the Web client, they still appear in the same bucket in the staff client.

Also, we have found duplicate items added to copy buckets, but not sure how they got there?
It's possible that double clicking on add to selected bucket causes a duplicate entry, in testing we were able to see that it did add the same title twice, however it didn't happen every time we double clicked.

We never had this a problem of duplicate items in copy buckets in the staff client, this is definitely a new problem with the web client.

Our staff will continue to use the staff client for this function.

[James Fournie (jfournie)]

See also 1485695

[Josh Stompro (u-launchpad-stompro-org)]

The same issue is present in the user buckets. It is possible to add a pending user multiple times to a user bucket.
Josh

[Jennifer Weston (jweston)]

Discussed in Cataloging IG meeting on Oct 11, 2022; highlighted as popular workflow improvement request with many utilization examples

[Vince Giordano (vincegiordano)]

Related to this: when you accidentally (or intentionally) add a record to the same record bucket multiple times staff-side, you get the green message saying "successfully added to bucket." Is that a bug or working as designed? If working as designed, I'll consider adding a wishlist request as it would be helpful to know if the record already existed in the bucket.