Delete Empty Call Numbers silently fails if deleted items are attached to the Call Number

[Garry Collum]

EG 3.7 and current master.

In the holdings view using Delete Empty Call Numbers only works if the Call Number has never had items attached.

To verify create a new call number with no items and use the Delete Empty Call Numbers. The call number is deleted.

Create another call number, add an item, delete the item, and then try to use the Delete Empty Call Numbers option. The option silently fails.

It looks like the item's deleted flag is ignored.

The pseudo-empty call number can be deleted if the Call Numbers and Items option is used.

Most likely the behavior described in LP1946785 with incorrect counts is related.

[Jason Boyer (jboyer)]

Ran into this today, can confirm that things have changed between the AngularJS and Angular holdings views.

[Britta Dorsey (bdorsey-isl)]

Confirmed still an issue on the 3.9 community demo server.

[Britta Dorsey (bdorsey-isl)]

Can also confirm still an issue in 3.9.1

Deleted items attached to the call number in Item Status. Returned to Holdings View to delete empty call number, and it silently failed.

[Britta Dorsey (bdorsey-isl)]

Was not able to replicate the issue in 3.11.2.

In Item Status, I selected the item and then chose Delete Items in the Actions menu. Confirmed to "delete 1 item and 0 call numbers." Item Status refreshed with the "Item Not Found" message.

Clicked on the title of the now-deleted item and accessed Holdings View. I changed the library selector between the consortium-level and branch level of the library system. All "show" options were checked and the empty call number was gone.

Was able to replicate with a second item.