[Koha-bugs] [Bug 15261] Verify if checkouts or reserves requests periods overlap with existing reserves

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261

--- Comment #23 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
(In reply to Katrin Fischer from comment #19)
> can you maybe explain the usual use case for the HoldDateInFuture setting?
> Maybe this will help to clear things up about the differences even more. I
> am not quite sure about myself and would like to understand better how it's
> currently used.

We have enabled a.o.: AllowHoldDateInFuture, ConfirmFutureHolds=2,
OPACAllowHoldDateInFuture.
This offers the user to supply two additional dates with a hold request: Hold
starts on date, and Hold not needed after.

What does that mean? The patron tells us here that he would like to have the
book only in the indicated (future) period. So we do not put the book in
waiting status for him until this period is very close (ConfirmFutureHolds). In
the meantime we can issue the book to someone else or let others place holds.
Similarly, another patron can also say: I want this book between A and B. No
problem if this overlaps the period of patron 1. Priority is here based on
[future] start date.
If the book could not be put in waiting status for patron 1 in the indicated
period somehow, the expired hold will be cancelled.

This is imo just a straightforward use of the two dates as Koha offers by
default. Our specific local situation is not relevant in this discussion.

Note that I am still missing any response from the authors of this patch.

-- 
You are receiving this mail because:
You are watching all bug changes.