Angular catalog shelf browse uses deleted call numbers
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.
description: | updated |
tags: | added: signedoff |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
A proposed fix is at https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ gcollum/ lp2003742_ call_number_ browse_ uses_deleted_ call_numbers