webclient: Holdings view retrieves holdings for workstation OU, not the context OU selected in dropdown menu

Bug #1539282 reported by Kathy Lussier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Undecided
Unassigned

Bug Description

When the holdings view first loads in the web client, the grid retrieves holdings for the workstation library, even if the "Show holdings at or below" dropdown is set at a different OU.

Many of our libraries prefer to see all libraries' holdings in this view by default. The nice thing about this display is that the org unit selector is sticky so that they can set a default, but the initial retrieval isn't honoring what's selected in this menu.

A screencast showing the behavior is available at https://drive.google.com/file/d/0B74gDMUDwDXqcUxIV0t3WmFzWXc/view

Revision history for this message
Kathy Lussier (klussier) wrote :

Adding an additional data point.

This behavior only occurs the first time you load Holdings View for a record during a catalog search session. If I return to results or if I conduct new searches, if I access Holdings View again, the holdings retrieved will be correct for whatever OU is selected in the dropdown.

However, once I leave that iframe to do something else, when I return to the catalog again and access Holdings view, the default display will be based on the workstation OU, not the OU selected in the dropdown.

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

Also seeing this.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Mike Rylander (mrylander) wrote :

This is addressed in the sprint4 collab branch (and on webby) now, via http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=8db6c5be944a61c1788b356b5217ad3027272fa9 . Marking as committed, since it will be merged to master at some point in an omnibus merge.

Changed in evergreen:
status: Confirmed → Fix Committed
Kathy Lussier (klussier)
Changed in evergreen:
milestone: none → 2.12-beta
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.