https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31484
Avery Campbell (Butte County Library (CA)) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |v --- Comment #1 from Avery Campbell (Butte County Library (CA)) <[email protected]> --- We have seen the same situation. We have 'AllowRenewalOnHoldOverride' set to 'Don't allow' and 'AllowRenewalLimitOverride' set to 'Allow'. When there are renewals remaining and a hold, it will just say 'On Hold' but when there are no renewals remaning and it is on hold, it says '4 Not renewable (0 of 4 renewals remaining)' and it allows us to override the renewal. After we renew, however, it says 'renewal failed: on hold.' If it were to just say 'On Hold' and now allow the override, then that might be clearer for staff to know they can't renew the item. It seems like a prioritization issue between 'AllowRenewalOnHoldOverride' and 'AllowRenewalLimitOverride'. - If on hold and renews are not maxed, it will say 'On Hold'. (current behavior) - If not on hold and renews are maxed, it will say 'Not Renewable' (current behavior) - If it is on hold and renews are maxed, it will say 'On Hold' (changed behavior) I don't know if this will make sense if both sysprefs are marked 'allow', so a combo message, like Lucas suggested (The message should include some language saying the item can't be renewed because it is on hold AND it is overdue.) might be clearer for all situations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
