Bug 23497

Summary: Notices defaulting to print
Product: Koha Reporter: Christopher Brannon <cbrannon>
Component: NoticesAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: katrin.fischer
Version: Main   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31424
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Christopher Brannon 2019-08-22 20:41:48 UTC
Why is it that Koha defaults to printing?  Shouldn't the default be no notification, and we have to select which notices are printed, if any?

Right now, if a patron doesn't have an e-mail selected as the form of notification, the notice defaults to print.  I would like to suggest that a print column be added, and if nothing is checked, nothing is generated.  Maybe in the notices tab for the patron a place holder could be made saying that patron opted for no notification, or something like that?
Comment 1 Katrin Fischer 2019-08-22 21:08:58 UTC
At the moment overdue notices and patron messaging allows to select multiple messaging preferences. And multiple messages will be generated.

I think instead of just adding a print column, we might need to define fallbacks? If no email... fall back to text message... fall back to print ... do nothing.
Comment 2 Christopher Brannon 2019-08-22 21:16:42 UTC
(In reply to Katrin Fischer from comment #1)
> At the moment overdue notices and patron messaging allows to select multiple
> messaging preferences. And multiple messages will be generated.
> 
> I think instead of just adding a print column, we might need to define
> fallbacks? If no email... fall back to text message... fall back to print
> ... do nothing.

As a patron setting, a general preference, a library preference, or maybe with the patron type settings, where the defaults are set?
Comment 3 Katrin Fischer 2019-08-22 21:18:59 UTC
It's a good question. I think patron might be too low level... We don't have this kind of configuration on library level yet. Maybe start global and move down later? (no funding here... just thinking loud)