Perfect - that lead me back to here: http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_readingrecordh... . I can tell our librarians that it's in the works for 3.2. Sharon On Nov 16, 2008, at 8:08 PM, Nicole Engard wrote:
Sharon - I don't know the answer, but I'd much rather see the patrons decide what is kept and what isn't. I have submitted this as an enhancement request a while back: http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1987
---
Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce@liblime.com AIM/Y!/Skype: nengard
http://liblime.com http://blogs.liblime.com/open-sesame/
On Fri, Nov 14, 2008 at 5:08 PM, Sharon Moreland <smoreland@nekls.org> wrote:
Hello,
According to the developer's wiki, the 3.2 System Groups work will be:
1. Adding the ability to link settings to a branch.
This means that a setting can be "owned" by a branch, i.e., have one value or set of values at one branch and a different value at another. Settings that could be owned by a branch include:
* item types * patron categories *acquisitions settings such as funds and currencies *selected system preferences *authorized values *notice templates (note that this is related to Mason's RFC of May 29). *calendars *MARC record matching rules
My question is this - will of those "selected system preferences" include the ability to turn off/on circulation history at the 'branch' level? Our consortium is made up of many independent public libraries and they would like to have local control of this feature.
Sharon Moreland NEKLS/NExpress
Thanks for the sound cue's info! _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha