Holdings View: Delete Call Numbers and Items sometimes does not work

Bug #1866548 reported by Jane Sandberg
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Medium
Unassigned

Bug Description

In 3.4.2, we're running into issues where we can't Delete Call Numbers and Items in the AngularJS Holdings View. This is a silent failure: we confirm that we want to delete those items and call numbers, and then they just stay there. There is no message in the console to hint at what went wrong.

However, we can still delete them from Item Status. We can also delete the items successfully, then go back and delete the call numbers.

Revision history for this message
Meg Stroup (mstroup) wrote :

Can confirm on 3.3.6 (Chrome). Multiple reports in SCLENDS.

It's happening as Jane describes and is a silent failure.

To delete the item, we: delete the item (not call number and item). Then, delete from MARC edit. That seems to wipe out all holdings. This will only work if you're deleting a last holding, though. Jane's workaround would likely be preferable in most situations.

Changed in evergreen:
status: New → Confirmed
Changed in evergreen:
importance: Undecided → Medium
Revision history for this message
Andrea Neiman (aneiman) wrote :

I haven't been able to reproduce this on the Angular Staff Catalog (3.6+) - was this something happening sporadically, or all the time?

tags: added: usability
removed: webstaffclient
tags: added: silent
tags: added: silentfailure
removed: silent
Gina Monti (gmonti90)
tags: added: angularjs
Revision history for this message
Andrea Neiman (aneiman) wrote :

Unless someone can confirm this in the Angular Staff Catalog I think we should mark this as won't fix.

Revision history for this message
Elaine Hardy (ehardy) wrote :

I have not experienced this and have not had any reports from our catalogers, not in 3.10 or earlier versions.

Revision history for this message
Jennifer Weston (jweston) wrote :

Discussed in Cat IG meeting on March 14, 2023. No concerns expressed over marking this "won't fix" as the problem has not been seen in the last few versions of Angular Staff Catalog.

Revision history for this message
Andrea Neiman (aneiman) wrote :

Thank you Elaine, Jennifer, and Cat IG for feedback - marking won't fix.

Changed in evergreen:
status: Confirmed → Won't Fix
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.