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

Bug #1952928 reported by Garry Collum
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

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.

Tags: cataloging
Revision history for this message
Jason Boyer (jboyer) wrote :

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

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Britta Dorsey (bdorsey-isl) wrote :

Confirmed still an issue on the 3.9 community demo server.

Revision history for this message
Britta Dorsey (bdorsey-isl) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.