--- Comment #3 from Martin Renvoize <[hidden email]> ---
My plan was to either add a distinct email_for_acquisitions field to the
existing branches table, or perhaps add a 'branch_librarians' table setup a
foreign key relationship such that it's extensible for other branch specific
I was then going to add accessors to Koha::Library which would look for the
corresponding field and if empty continuously fallback through branchreplyto,
branchemail, defaultreplyto and finally kohaadminemail system preferences until
it found a populated one.
I was also temped to allow the field to take either a plaintext email address
or a borrowernumber which we could use to lookup a librarian.. but I've not
decided whether I like that concept or now yet.. up for debate.
Once I had that it's a model for how other such branch specific addresses could
Finally, I'd plumb it into the suggestions notification system such that the
'to' address was populated using this new accessor.
--- Comment #4 from Jonathan Druart <[hidden email]> ---
I would go with a list of patrons we could link to a library.
Like what we have for funds (join table aqbudgetborrowers):