https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40357
David Cook <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from David Cook <[email protected]> --- 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. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
