Hold ratios in circ policies cause errors when trying to renew items
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.3 |
Fix Released
|
Medium
|
Unassigned | ||
2.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
We want to prevent renewals on titles with holds, but only if there are no available copies to fill the holds.
To do so, we set up a circ policy at the consortium level with the "renewal" flag set to true and with the "Minimum Available Copy/Hold Ratio to 1. When this circ policy is active, we get the following error message whenever we try to renew an item, regardless of whether there is a hold on the title or not.
The initial error is a network or server failure with the following:
method=
params=
THROWN:
{"payload"
STATUS:
I then get a message saying the renew failed. The Debug Output is:
Please open a helpdesk ticket and include the following text:
Sat Jan 19 2013 22:10:20 GMT-0500 (Eastern Standard Time)
Renew Failed for 777776
[
{
}
]
I then get another error with the following in the Debug Output:
Please open a helpdesk ticket and include the following text:
Sat Jan 19 2013 22:11:23 GMT-0500 (Eastern Standard Time)
Error in renew_via_barcode callback\nRenew probably did not happen for barcode 777776
{
"fileName"
"lineNumber
}
A similar error was produced when I tried using the Minimum Total Copy/Hold Ratio. If I remove the ratios from the circ rule, then the renewals go through without any problems.
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | 2.4.0-rc → none |
description: | updated |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Confirmed it in master and based on the paths in the supplied errors, I'm assuming that it is happening in 2.3.