available copies in web staff client not same as xul
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Unassigned |
Bug Description
This sounds familiar to me but I'm not seeing it elsewhere in bugs so hopefully it's not a dupe of an existing ...
In the xul client catalog search we have the following behavior,
search for 'patterson two heart' on initial login on xul client:
Two from the heart
Patterson, James, 1947-
Book Book (2017.)
Call number: F Patterson James
50 of 74 copies available at foo_consortium.
4 of 9 copies available at foo_system.
0 of 2 copies available at foo_branch.
change search scope from the default after login to consortium:
Two from the heart
Patterson, James, 1947-
Book Book (2017.)
Call number: F Patterson James
50 of 74 copies available at foo_consortium.
0 of 1 copy available at foo_branch.
So it continues to show branch copies for the logged in library even when scoped to consortium.
In the web based staff client we get:
Two from the heart
Patterson, James, 1947-
Book Book (2017.)
Call number: F Patterson James
50 of 74 copies available at foo_consortium.
4 of 9 copies available at foo_system.
0 of 2 copies available at foo_branch.
upon changing scope to consortium:
Two from the heart
Patterson, James, 1947-
Book Book (2017.)
Call number: F Patterson James
50 of 74 copies available at foo_consortium.
So, it no longer continues to show registered copies regardless of scoping. Since we've generally tried to make make patron and staff identical this may not be considered a bug but it is a chance in xul -> webby behavior that has confused some staff who expected it to still function this way.
It took me a few minutes to replicate the XUL client behavior, so I'll add a few data points.
In the xul client, an org unit needed to be selected as the workstation preferred library to display it in the availability counts for searches that were outside that scope. It looks like it displays no matter what the scope of the search.
In the web client, if you set an org unit as the workstation preferred library, it does not display regardless of the scope.