[Koha-bugs] [Bug 19014] Patrons should not get a on_reserve notification if the due date is far into the future

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19014

--- Comment #34 from David Cook <dcook at prosentient.com.au> ---
(In reply to Ray Delahunty from comment #32)
> (In reply to Andrew from comment #26)
> 
> Are we focussing too much on manipulating when the auto-renewal takes place
> as being the driver of limiting how many people receive renewal-failure
> emails? I think we need a better driver. Auto-renewing an item earlier than
> the moment it is due back penalises other users who may want the item. 

No it doesn't. Other users can place a hold on the item. 

> If it
> has already auto-renewed (early) and they place a reservation / hold on it,
> they will have to wait longer for it. 

The same thing could be achieved by a person manually renewing it. I don't see
how this is relevant?

> That is why we have opted for the
> (admittedly harsh) situation where we only warn users that items have failed
> auto-renewal when they are overdue. (We use a No Renewal Before value set to
> zero, but we do use a long grace period.)
> 

I think this is what most people do with Koha at the moment.

> We have multiple copies of the same item (with various loan periods) out on
> loan. If a reservation is placed we want to send renewal-failure
> notification only to users whose copy is due “soon”, and not to people who
> have, say, just taken a long-term loan copy out. Native Koha auto-renewal
> functionality currently sees every holder of the item emailed.  But the
> first copy returned satisfies the reservation. Why pester everyone- we want
> to better target the email.
> 

Fair enough although I think that's a separate issue to this one. 

> In comment 26 Andrew mentions what I think could be the ideal solution- a No
> Notice Before parameter. Rather than this being a system preference I see it
> better as an additional column in the Circulation & Fine rules. This would
> be configurable line by line (user category / item type) and allow the Koha
> library to email as many or as few current holders of the non-renewed items
> as they wished.  Libraries that wanted to be more lenient that us could
> increase the No Renewal Before to 1, 2, or 3, say, but it would be the wise
> choice of a No Notice Before value that would be the best driver in
> targeting users whose items are likely to fulfil the reservation / hold.

I'm not interested in this idea, but you are free to pursue that idea by
yourself or pay someone else to pursue it. 

I've provided my alternate patch as it's how me and my clients think the
auto-renewal should work, and we've already implemented it locally and are
satisfied with that. I've uploaded it here as I think other people would
benefit from it as well. That's the limit to my contribution on this particular
bug report though.

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