The problem is that these libraries often want this behavior without using IB. I think the problem with IndependentBranches is 1) It's an all or nothing approach, 2) It must be implemented by hand for each feature, and 3) it has no flexibility. That's why I began working on independent groups. However, the idea I'm working on is more along the lines of having permissions defined on a per-branch basis so LibrarianA can edit patrons for branches A, B and C, can modify items for branch A, and can add holidays for branches A and B and so forth. We'd also have a 'super' for each permission. We could even have a 'default' if we wanted to so a library could edit say circ rules for "All libraries" and for branches A and B. But to answer your question, these bugs don't affect IndependentBranches at all. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com ) On Wed, Sep 17, 2014 at 3:54 AM, Renvoize, Martin < martin.renvoize@ptfs-europe.com> wrote:
Please enlighten me as to how this would play with Independent Branches; it sounds like a very much related feature which in my opinion should probably only be enabled along side independent branches.. not without it.
Chipping in,
Martin
Martin Renvoize Software Engineer, PTFS Europe Ltd Content Management and Library Solutions Skype: Landline: 0203 286 8685 Mobile: 07725985636
On 16 September 2014 22:16, Joel Sasse <jsasse@plumcreeklibrary.net> wrote:
+1 for only superlibrarians being allowed to edit the "all branches" rules.
I don't allow access to any library staff to overdue rules, notices, or circulation rules, default or otherwise. If library staff were limited to their own branches, I would allow access. Unfortunately, Koha permissions are wide open here. Koha is currently lacking in granular permissions but hopefully we can change that soon.
Joel Sasse Network Systems Administrator Plum Creek Library System 507-360-8961 O
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Katrin Fischer Sent: Tuesday, September 16, 2014 2:09 PM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Default to logged in branch vs "all branches'
I am a bit worried about the change in behaviour here.
You'd have to give your staff superlibrarian permissions in order to configure default overdue rules, default notice templates or default circulation rules - things they can currently do without being superlibrarian.
It seems like an unexpected change?
Katrin
Am 16.09.2014 um 20:37 schrieb Viktor.Sarge@regionhalland.se:
What about only allowing superlibrarians to edit the "all branches"
rules?
+1
Superlibrarian defaulting to "all branches" and others to their own
branch sounds most reasonable to me.
Kyle
On Tue, Sep 16, 2014 at 12:29 PM, Owen Leonard <oleonard@myacpl.org>
wrote:
I think that problems with librarians accidentally editing the default rule should be addressed by enhancing permissions for those
features.
-- Owen
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha