Web client: Cannot successfully check in hold transit items
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Evergreen: master as of February 27, 2017 (2.12 beta)
When scanning an item at check in that needs to go into transit to fill a hold, the check fails without any feedback to the user. Instead, the checkin grid displays "No Items to Display". See the screencast at https:/
The following error is found in the console:
TypeError: transit.source is not a function
at Object.
at circ.js:224
at angular.js:16696
at m.$eval (angular.js:17994)
at m.$digest (angular.js:17808)
at angular.js:18033
at f (angular.js:6045)
at angular.js:6324
I am able to successfully check in items that need to go to the holds shelf and items that need to go into transit to return to its owning library. I am only seeing this problem with hold transits.
This is a regression in the web client code.
Changed in evergreen: | |
milestone: | 2.12-rc → 2.12.1 |
Changed in evergreen: | |
milestone: | 2.12.1 → 2.12.2 |
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
assignee: | nobody → Kathy Lussier (klussier) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
After continued testing, I've found that this problem doesn't occur for all holds transit items. When working with the Concerto dataset, it only appears to occur for items that need to fill a hold at SL1. Checking in items that need to transit to other locations to fill holds appears to work as expected.
There's still a problem, but I think we can put the priority down to medium since it isn't affecting all transit holds.