web client: cannot batch edit call numbers in item status

[Elaine Hardy]

If multiple items checked in item status to edit call numbers in Edit volumes, multiple tabs open. This makes it impossible to quickly edit large numbers of volumes in cases where library might be changing a prefix embedded in call numbers (change old practice of FIC to new practice of F, as an example). There is no other place to batch edit call numbers across bibliographic records.

In the XUL client, choosing multiple items in item status to edit volume call number resulted in a grid list of the call numbers.

[Elaine Hardy (ehardy)]

Similar issue to https://bugs.launchpad.net/evergreen/+bug/1691861

[Elaine Hardy (ehardy)]

And https://bugs.launchpad.net/evergreen/+bug/1735539

[Diane Disbro (ddisbro)]

This is hugely important to circ staff. We edit item attributes on a regular basis and can't do more than one item at a time in Webby unless we create a copy bucket. We need Webby to function the way the XUL client did, allowing many items to appear in the copy editor and for attributes to be changed on multiple items all at once.

[Kathy Lussier (klussier)]

Hi Diane,

Are you talking about editing call numbers in batch or editing copies? If you're referring to editing item information, that issue has been fixed and released in the 3.0.3 release - https://bugs.launchpad.net/evergreen/+bug/1691861. Equinox is planning to do more work soon to address the issue with batch editing items with different stat cats, as well. (bug 1738893).

We still need a way to batch edit call numbers, of course, but I wanted to let you know that we have made progress on the item-editing front.

[Elaine Hardy (ehardy)]

This actually appears to be fixed. I was able to open one tab for all the items I have in item status. However, you cannot edit call numbers in item status, whether batch or singly -- the boxes are grayed out and not editable.

Also missing functionality to batch add the same barcode to all vols.

I will do bug reports on each of these, if someone hasn't already.

[Elaine Hardy (ehardy)]

Just reported bugs mentioned above as https://bugs.launchpad.net/evergreen/+bug/1746537 and https://bugs.launchpad.net/evergreen/+bug/1746536

[Andrea Neiman (aneiman)]

noting there is a PR on bug 1746536 that should address this bug as well