"no-op" checkins use old global behavior for floating items
Bug #1473054 reported by
Jason Etheridge
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.10 |
Fix Released
|
Medium
|
Unassigned | ||
2.11 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This happens when you use the Suppress Holds and Transits checkin modifier during Item Check In, or when you use the "Normal Checkin then Checkout" action when attempting to check out an already circulating item.
If a floating group is set on the item, the code just treats it as "true" and changes the circ library, regardless of the floating group membership.
Circ/Circulate.pm, line 2583
} else { # no-op checkin
if ($U->is_true( $self->
}
}
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | 2.next → 2.12-beta |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I can confirm that this is an issue in 2.8.4.
We have been scratching our heads about why items were floating to a different library system occasionally. Finally figured out that it happens when an item that is already checked out, gets checked out to a new patron using the "Normal Checkin then Checkout" action. Then found this bug report.
We are a consortium of two regional library systems, one system floats everything, and the other floats nothing. We also share all holdable items between both systems.
Steps to test this issue.
1. Setup a copy with a floating group that allows floating in System A only. The copy should have a circ lib of a branch is system A.
2. Check out the item to a patron at a branch in System B.
3. Check out the item to a second patron at System B without checking it in first.
4. When you check out the item, choose the "Normal Checkin then Checkout" action.
5. View the copy to see that the circ_lib has been changed to the branch in system B.
Would the proper fix be to use the new floating groups logic, or to just not float from a no-op checkin?
Josh