Advanced Search -> Numeric Search -> Call Number (Shelf Browse) does not honor opac visibility flags

Bug #1174840 reported by Jason Etheridge
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

In master with stock test data, I created a bib record with the title "zz test", added an item with barcode "zz1" with a call number label "zz label". I set the item to OPAC visible = No.

Doing a normal keyword search for "zz test", I receive the expected "no entries were found". However, searching for "zz" from Advanced Search -> Numeric Search -> Call Number (Shelf Browse), I do see an entry for "zz label" along with the "zz test" title.

I'd expect for this search to honor the OPAC visible flag here.

This also happens in 2.3.3.

-- Jason

Tags: opac search
Ben Shum (bshum)
Changed in evergreen:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Steve Callender (stevecallender) wrote :

I've seen what I believe is this same type of issue in 2.4. It looks like going to the Advanced Search -> Numeric Search -> Call Number (Shelf Browse), as long as there is 1 call number available on the bib it will also display the call numbers for all the other items on the bibs no matter if an actual item exists or not.

In my testing, I had a single bib with Call number X and Y and only X has an item attached. In the browse shelf window, it displayed both X and Y, however clicking on Y, it actually linked back to the item under call number X even though the label it was displaying was clearly that of Y.

Steve

Revision history for this message
Sarah Childs (sarahc) wrote :

Still occurring in 2.5

Call numbers for items not generally OPAC visible such as those with a status of Lost or Discard/Weed show up in the call number browse. This occurs even if none of the holdings are OPAC visible, so when you click on it you get a record with no apparent holdings. Or as Steve described above there may be other holdings which may not match what you were browsing.

tags: added: search
Revision history for this message
Erica Rohlfs (erohlfs) wrote :

This is an older bug, but confirming that the same behavior exists in Web Client version 3.2.

Changed in evergreen:
status: Triaged → Confirmed
tags: added: opac
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.