Bucket contents may be removed by other users without warning

[Anna Goben]

We had a situation pop up with a catalog clean-up. We'd preloaded a bucket for catalogers to reference.
One cataloger wanted to clone the bucket to address the contents locally. She selected all of the titles in the bucket and chose "Move Selected Records to Pending Records." That wiped out the entire contents of the bucket, even though it wasn't her bucket.

This could create significant issues since all buckets are shared on the back-end and anyone could potentially clear a bucket permanently without the owner being aware of the changes.

Permissions are supposed to restrict removing contents of a bucket to the bucket owner. Moving records to the Pending area should copy the records and not remove them when working in another user's bucket.

Tested and observed in 3.2 and 3.4.

[Elaine Hardy (ehardy)]

It would be helpful if there was an option to either retain the records in the bucket or not when you selected add to pending.

[Anna Goben (agoben)]

+1 Absolutely!

[Andrea Neiman (aneiman)]

For record buckets this is superseded by the sharing features implemented in bug 2063146 - you can share with edit privileges or as read-only.

Additionally, bug 2063146 removes the "Pending Records" workflow.