Web client: cannot transfer contents of buckets to pending

[Elaine Hardy]

In the web client, there is no longer a way to transfer contents of either copy or record buckets to pending so that they can be transferred to another bucket.

We are able to do this in the XUL client. This functionality is useful when items or records are added to the wrong bucket, which happens more frequently than we would like. The work around in the web client adds several more steps and is not as efficient.

(Ideally, of course, would be the ability to bypass pending and transfer directly to another bucket.)

[Beth Willis (willis-a)]

Confirmed in v.3.0.1.

There should be an option on the Actions menu allowing the user to move selected copies from the copy bucket to the "Pending copies" tab and to move selected records from the record bucket to the "Pending records" tab.

[Eva Cerninakova (ece)]

Confirmed in 3.1.4

The function is not only about "adding records to wrong bucket" but it is used in various other ways and workflows. E.g., when more staff members are working on a project each of them using their own buckets. Than finally buckets are joined together to one bucket to be exported, batch edited ... at once.

[Eva Cerninakova (ece)]

Unchanged in 3.2 beta

[Kyle Huckins (khuckins)]

I've pushed a branch here adding the new action "Move selected Records/Copies to Pending Records/Copies:" https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/khuckins/lp1735835-transfer-bucket-contents-to-pending

[Bill Erickson (berick)]

Thanks, Kyle. Any reason the records are de-duped as they are moved but not the copies? Minor nit, console.log(recs) should be console.debug (or removed).

[Kyle Huckins (khuckins)]

The record buckets UI de-dupes records to ensure you don't have duplicate records when adding to pending already, but the copy buckets don't appear to have the same functionality. I erred on the side of working with how both UIs already functioned when adding items to pending. That may be worth opening a new bug for, if it's not intentional.

Nice catch on that stray console.log, I'll amend it out.

[Bill Erickson (berick)]

Thanks, Kyle. Updated patch merged to 3.2 and above.