Angular catalog shelf browse uses deleted call numbers

Bug #2003742 reported by Garry Collum
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Undecided
Unassigned
3.9
Fix Released
Undecided
Unassigned

Bug Description

EG 3.9.1 and current master.

The shelf browse tab in the angular catalog does not take into account if a call number has been deleted when displaying the browse list. Deleted items do not display, it just uses the sort_key of a deleted call number to determine where the list should begin.

To reproduce this in Concerto. (logged in with BR1 as the OU)

1. Go to a bib and click on the shelf browse. Notice where the browse list begins. For example, record 92 starts browsing at 780 R86.
2. Add a new item with a call number less than the starting point of the browse list and does not exist in the record. I created an item with call number 100 A10.
3. Refresh the browse screen, and notice that the list now begins based on 100 A10.
4. Delete the item and call number that was just created.
5. After a refresh the browse list still begins on a call number based on 100 A10.

Garry Collum (gcollum)
description: updated
Revision history for this message
Garry Collum (gcollum) wrote :
tags: added: pullrequest
Revision history for this message
Bill Erickson (berick) wrote :

Issue and fix confirmed. Merged to 3.9 and up. Thanks, Garry!

Changed in evergreen:
assignee: nobody → Bill Erickson (berick)
milestone: none → 3.10.1
status: New → Confirmed
status: Confirmed → Fix Committed
assignee: Bill Erickson (berick) → nobody
tags: added: signedoff
Changed in evergreen:
status: Fix Committed → Fix Released
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.