Chris, I've been meaning to write a Contextual Preferences Engine for Koha for a while now, to solve the problems we have with the Circ Matrix, as well as with global sysprefs that should really be more configurable. The idea is that it will be a DB table with 5 main columns: Branch, Patron Category, Item Type, Key and Value. Any of the first 3 can be a specific value or "default". If a contextual preference doesn't make sense to factor in one of the 3 values, it'll be ignored. This, along with a rewritten editor and rules tester tool, would solve a bunch of our customizability problems in one go, without necessarily introducing too much complexity for users (provided we make a good interface). I hope to have a patch for this started after 3.8 releases (and all our DB revs are stable for a while). Any help would be welcomed. -Ian 2012/3/22 Chris Nighswonger <cnighswonger@foundations.edu>

Recently the need has arisen locally to run the self-checkout (sco) under multiple user accounts to accommodate multiple branches using the sco module. To the best of my understanding this is not currently possible due to the way in which the user for the sco module is defined using a system preference. While there may be a number of ways to accomplish this, it seems that it may be desirable to have a category of "branch specific" system preferences. This would be an attempt to group system preferences into one of two general categories of "global" or "branch." Before launching out into writing such a feature, I thought I'd run it by both lists to see if a) I'm way off base, b) if such a feature is desirable, and c) if I'm off on an insanely hard project.

Kind Regards, Chris

_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/