[Bug 8838] New: Digest option for HOLD FILLED notice?
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8838 Priority: P5 - low Change sponsored?: --- Bug ID: 8838 Assignee: koha-bugs@lists.koha-community.org Summary: Digest option for HOLD FILLED notice? Severity: enhancement Classification: Unclassified OS: All Reporter: mcoalwell@nekls.org Hardware: All Status: NEW Version: rel_3_6 Component: Notices Product: Koha Is there a way to set Koha to only send one email to a patron when they have several items on hold instead of one email for each item? We've had a couple of patrons ask and 12 emails put a patron over her email inbox quota. Thanks, Erica Voell Bonner Springs City Library -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8838 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de Version|rel_3_6 |master --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi Mickey, there is currently no way to do a digest for hold notices. I think the idea is to let patrons know as fast as possible about holds being ready for pickup. I am not sure how a digest could work here. Maybe by circulation session? Summarize hold notices for a certain amount of time? I am not sure how hard it would be to implement something like this. I am resetting the version to master, because this is an enhancement request for a future version. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8838 dmin <dminuck@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dminuck@gmail.com --- Comment #2 from dmin <dminuck@gmail.com> --- This issues is also coming up for our library, as we regularly have patrons place holds on up to 50 items at a time (often with most of them being on shelf, and therefore getting a very large number of notices). As a possibility to realize this enhancement, consider treating reserves in the same way as overdues: Create a new pl to merge the content of the pending reserves in the table at time of running the cronjob (will need a way to specify if a notice has been sent or not, e.g. new column notification_date, or something). Create a new SysPref to either run as a cronjob (scheduled as the library sees fit, like other cronjobs), or in the way was previously done. This would therefor require adding a check for this syspref to the existing perl which sends notifications. Modify existing Holds notice template to list all items available, or make available the option to count the items. Just an idea. I have not really looked into doing this yet, so not sure how feasible it is, but we'll be looking a doing something, because the high volume of notices we are currently sending out is overwhelming some of our patrons (and we need to have the option to notify them when holds are available. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8838 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Maybe another idea for a possible solution would be to solve this similar to the checkout notices. For the first checkout the notice is created, for every checkout after that the notice is amended (I think) and then send out with the next run of the process_messaqueue job. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org