Bug 10819 - Allow for auto filling of holds when items are checked in via SCO
Summary: Allow for auto filling of holds when items are checked in via SCO
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Self checkout (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-04 16:04 UTC by Chris Nighswonger
Modified: 2023-07-08 17:22 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Nighswonger 2013-09-04 16:04:58 UTC
When an item with a hold on it is checked in via the SCO module (web), no further processing is done which results in the hold being overlooked unless the circulation desk workflow includes a regular run of the hold reports.

The least fix for this would be to add a system pref allowing for the option of auto-filling the highest priority hold on an item checked in via the SCO module. Perhaps other options allowing for various alternate workflows might be added here as well.

I'm listing this as an enhancement because depending on one's workflow, this may not be a bug.
Comment 1 Oliver Behnke 2015-07-23 13:16:35 UTC
I support this request.
Comment 2 Katrin Fischer 2015-07-23 14:43:04 UTC
Maybe we need another status - that marks the item until it can be processed. If we just set it to 'Waiting' it might be hard to figure out which books need to be sorted out from the returns to go on the pickup shelf.
Comment 3 Chris Nighswonger 2015-07-24 00:18:34 UTC
I'm not familiar enough with the holds logistics to comment much on the best way to handle this, but do know it has been an issue a number of times for our circulation desk. What happens is that a book with a hold on it and returned via self-check ends up checked back out to a patron other than the one who put the hold on it.
Comment 4 Katrin Fischer 2015-07-24 05:51:35 UTC
Hm, we had a similar situation with SIP - thinking about it, I think it sets holds now to 'waiting' - but haven't tested.
Comment 5 Katrin Fischer 2023-07-08 17:22:33 UTC
Adding an equivalent of HoldsNeedProcessingSIP for SCI and SCO with returns might be what's needed here.