Summary: | Customize notice recipients | ||
---|---|---|---|
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: | andrew |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
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
2022-11-18 19:48:43 UTC
This seems like a hard idea to implement with how Koha thinks about notices now. Generally, some event prompts Koha to go look for a letter with a given code and a borrower with a given borrowernumber, then send that letter to that borrower. So there'd need to be some mechanism for the letter-based value you've suggested to override the originally-intended recipient. Maybe instead there could be a new page in administration that lists events that trigger notices and allows one to set whether those go to patron or to staff? OR to both, actually, that could be helpful. We'd have to somehow tell it *which* staff. Yes, thinking through this more, it would be a matter of determining for each template if the notice is going through the owning library, the issuing library, or the patron's home branch, and then determining the staff associated with that template and particular branch. I could envision a page that lists the available templates based on the selected library, and then setting settings/e-mails for each particular template. One could assume that the staff e-mails and selections associated with a template would be based on however the notice originally is sent to the patron (from owning library, the issuing library, or the patron's home branch). |