Summary: | Notices defaulting to print | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Notices | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | magnus |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31424 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30343 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23357 |
||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Christopher Brannon
2019-08-22 20:41:48 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. (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? 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) |