Bug 18161 - Option to completely disable advance notice on loans with auto renewal
Summary: Option to completely disable advance notice on loans with auto renewal
Status: RESOLVED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-23 09:31 UTC by Stefan Berndtsson
Modified: 2023-09-11 07:44 UTC (History)
2 users (show)

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


Attachments
Option for disabling advance notice when auto_renew is set on item that is due soon (3.00 KB, patch)
2017-02-23 12:10 UTC, Stefan Berndtsson
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Berndtsson 2017-02-23 09:31:48 UTC
Some background.

In our current library system, we use long loans (loans with a guaranteed minimum due date, but a much much longer hard due date), with a recall function. This is only in use for parts of the content.

Koha does not support this, so we're looking at using auto renewal as a method to give a reasonable resemblance of long loans.

We also want advance notices to be sent when the due date is about to arrive, but having an advance notice and then an automatic renewal shortly after will produce a multitude of notices that will be considered as faulty by the end user.

The suggested solution to this is an option to simply disable advance notices for loans where auto renewal is active.
Comment 1 Stefan Berndtsson 2017-02-23 12:10:43 UTC
Created attachment 60593 [details] [review]
Option for disabling advance notice when auto_renew is set on item that is due soon

When SysPref is set to 'Do not send' no advance notice will be sent when item is issued with auto renewal
Comment 2 Katrin Fischer 2017-02-23 20:48:59 UTC
I think one of our libraries uses a combination of 'no renewal before' in circulation conditions that is set to a higher (or same?) value than the advance notice. In fact, the job for automatic renewals runs before the advance notices job, so you can do some timing there.

This way the renewal will be tried before the advance notice is sent out. If the renewal is successful - no reminder is needed. If it is not, the reminder will be sent out. This has the advantage of still being able to remind, when it's needed.
Comment 3 Stefan Berndtsson 2017-02-24 08:14:43 UTC
(In reply to Katrin Fischer from comment #2)
> I think one of our libraries uses a combination of 'no renewal before' in
> circulation conditions that is set to a higher (or same?) value than the
> advance notice. In fact, the job for automatic renewals runs before the
> advance notices job, so you can do some timing there.

Just to clarify, since the above doesn't exactly match my knowledge of "no renewal before" (should be loanperiod-noticedays, right?).

If we have a loan period of 30 days, an advance notice value of 2 days, I should set the no renewal before to 28 (or to be on the safe side, 27) days?

Similarly for a 7 day loan, I'd set 5 or 4 days there.

Sounds plausible. I'll run it by our testers to see.
Comment 4 Katrin Fischer 2017-02-24 08:23:50 UTC
> Just to clarify, since the above doesn't exactly match my knowledge of "no
> renewal before" (should be loanperiod-noticedays, right?).
> 
> If we have a loan period of 30 days, an advance notice value of 2 days, I
> should set the no renewal before to 28 (or to be on the safe side, 27) days?
> 
> Similarly for a 7 day loan, I'd set 5 or 4 days there.
> 
> Sounds plausible. I'll run it by our testers to see.

I haven't tested it out, so I might be off by +-1, but the 'no renewal before' is counted from the due date. So if you put 2 there, the renewal will be tried 2 days before the item woudl be due.

It might still need some improvement for you to work as you want exactly, but I thought sharing this might help as a workaround at least and maybe more.
Comment 5 Katrin Fischer 2023-09-10 13:00:07 UTC
Hi Stefan, did you figure out a workflow that works for your library with the 'no renewal before' or is this still needed?
Comment 6 Stefan Berndtsson 2023-09-11 07:44:49 UTC
Wow. This is from long before (more than a year before) we started actually using Koha in production. :)

I don't think we've ever used this patch, so I'll just set it to resolved/wontfix for now. I can't see a use for this really.