Summary: | Notices and Slips library selection | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Tools | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | alex, dcook, george, lisette |
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
2025-07-12 21:38:37 UTC
It's an interesting idea. At the moment, we store the "branchcode" in the "letter" table, which is why each library would need to create its own template. But your proposal would have us move "branchcode" out of that table and into a mapping/linking table. Generally speaking, this tends to be a better approach anyway. So instead of creating a new template per library, you'd just be choosing which notice you're using for a given library and a given module/code combination. Sounds good to me. We could also instruct the database to enforce the unique constraint so we don't have to worry about duplicates. (Although we'd have to update the constraints of the current "letter" table.) That said, if you could make many templates for a given module/code... you'd either have to specify every notice for every library, which could be burdensome (and have maintenance issues for new templates), or 1 given module/code could be labelled as "default". -- Anyway, it's not an enhancement I'll be working on, but it's an interesting idea. +1 -- Would save a good deal of copying and would be much easier to keep track of which libraries are using which notices. |