https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26342
Jason Robb <jr...@sekls.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jr...@sekls.org
--- Comment #2 from Jason Robb <jr...@sekls.org> ---
This has caused some confusion with my libraries. It usually happens when the
patron suspends a hold until a certain date, finds the item on the shelf and
checks it out, the hold unsuspends in the meantime and when they return the
item, it tries to give it to them again. That can lead to an upset patron if
they get notified to come back in to pick up a hold without realizing it is the
item they recently returned.
A clever patron could also abuse this to keep an item longer by placing a hold,
suspending it, checking the item out, then unsuspending right before they
return it. That would keep their hold at the top of the list so when they
return the item, they'd skip over any other holds and get the item again.
I can't think of a case where we would want to maintain a suspended hold if the
item is checked out to the requesting patron but we're in a largely public
library setting. Maybe "fill suspended holds on checkout" could be a system
preference?
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
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/
