[Koha-devel] Autorenewals renewing an item then sending a renew failure email the next day

[David Cook]

It looks like the libraries I support don’t want to turn off the notices (by removing --send-notice) but they also don’t want to have the behaviour of getting emails saying the item can’t be renewed because of a hold when it’s still too soon. 

 

So we need to work something out. 

 

I have other priorities at the moment that need my attention, but let’s see if I can write something quickly…

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of McGowan, Janet
Sent: Tuesday, 11 December 2018 4:02 AM
To: Holger.Meissner at hs-gesundheit.de
Cc: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Autorenewals renewing an item then sending a renew failure email the next day

 

Yes, using the PREDUE notice is a way around this, however it would only work if No renewal before is set to 1. 

Having said that there are many benefits to the --send-notice functionality - the end user is notified about the reason why a material is renewed or otherwise - so ideally we would like to be able to use this separate autorenewal notification.

I believe the community bug for this is https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19014 

but in a few brief tests I don't believe it totally fixes the problem, I'm afraid I haven't had a chance to test the fix properly yet though.

-Janet


 


Janet McGowan

 <https://www.ptfs-europe.com/> 


Director of Operations


 


 


Phone: +44 (0) 1483 378728

Mobile: +44 (0) 7985 431 266


Email:  <mailto:janet.mcgowan at ptfs-europe.com> janet.mcgowan at ptfs-europe.com

 <https://www.ptfs-europe.com/> www.ptfs-europe.com


 

	

 

	

 

	

 


Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30

 

The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com <mailto:info at ptfs-europe.com> 

 

 

On Mon, 10 Dec 2018 at 16:47, Holger Meissner <Holger.Meissner at hs-gesundheit.de <mailto:Holger.Meissner at hs-gesundheit.de> > wrote:

On Mon, Dec 10, 2018 at 10:56 AM McGowan, Janet <mailto:janet.mcgowan at ptfs-europe.com <mailto:janet.mcgowan at ptfs-europe.com> > wrote:
> Our feedback from customers has been that the user only needs to be informed that the autorenewal
> cannot take place at the point that the renewal would take place (ie at the point that the No renewal
> before policy values kicks in).

I wonder if the regular PREDUE notice is sufficient for that or not? Maybe we don't need a special auto renewal notice, but rather a way to make sure that the PREDUE trigger can't be set to any value > no renewal before?

We actually use OPACUserJS to hide that setting.

Regards,
Holger
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org <mailto:Koha-devel at lists.koha-community.org> 
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20181211/7194dbe7/attachment-0001.html>