copy location groups and OPAC-visiblity

Bug #1743639 reported by Galen Charlton on 2018-01-16
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
High
Unassigned

Bug Description

It appears that the opac_visible column on asset.copy_location_group was meant to control whether or not the group showed up in selectors in the OPAC.

However, the work in bug 1698206 (inadvertently) extended the interpretation of acplg.opac_visible by having it also affect whether /copies/ in that group were OPAC-visible. As a consequence, if a copy location group was marked as not OPAC visible (meaning that it should only show in selectors in the staff interface), any copies associated with that group became hidden from OPAC display.

This should be changed back to the original behavior; while we may or may not want to have acplg affect visibility of copies in the OPAC, that should be handled separately (and, presumably, via a separate Boolean column on acplg).

Evergreen 3.0+

Mike Rylander (mrylander) wrote :
tags: added: pullrequest webstaffclient
Mike Rylander (mrylander) wrote :

I've updated this branch to 1) be more defensive with input and 2) use locations as a proxy for location groups in QueryParser.

Kathy Lussier (klussier) wrote :

It works for me! I've signed off on the code and merged it to master and release 3.0

Changed in evergreen:
status: New → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers