https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32565
--- Comment #11 from Pedro Amorim <[email protected]> --- (In reply to Katrin Fischer from comment #10) > * Have some other way of triggering re-allocation - I don't think we have an > option there apart from cron? Discussed this with Martin, an option would perhaps have it be a "scheduled job" (think background jobs, but scheduled to run at a specific given time instead of whenever possible), but I don't think we're there yet. Brainstorm idea, but if a hold is placed today and no library is open today, why not have RTHoldsQueue check tomorrow? and the day after that, and so on, until it finds a suitable one? (within a sensible limit) That's what would happen anyway through the cron, right? Maybe we'd have to add a way of flagging the hold that it can't be satisfied immediately as the library is closed but it could show the hold as "pre-allocated". This may not be a great idea, but let me know what the problems are with it as I lack the hold queues workflow knowledge required to see it. -- 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/
