Default to logged in branch vs "all branches'
As many of you already know, there are a good number of areas in Koha where we have settings for each library, and an "all libraries" default. Examples of this are the circulation rules, slips and notices, overdue status triggers, etc. Some librarians would like the default view to be the library's rules, rather than the "all libraries" rules. The idea being that this would stop librarians from editing the "all libraries" rules by accident. The two bugs in question are: Bug 11625 - Default to logged in library for circ rules and notices & slips http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11625 Bug 11747 - Default to logged in library for Overdue notice/status triggers http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11747 Please let us know how you feel about this! 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 )
Some librarians would like the default view to be the library's rules, rather than the "all libraries" rules. The idea being that this would stop librarians from editing the "all libraries" rules by accident.
My vote is that in cases where a default rule can be set, the page should open to the default rule--not the logged-in library's rule. I think that problems with librarians accidentally editing the default rule should be addressed by enhancing permissions for those features. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
I do agree, but that's more of a long term goal. I suppose we could throw some more permissions in the existing system, but that feels like a kludge. What about only allowing superlibrarians to edit the "all branches" rules? 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
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
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.
+1 with a hope that permissions will be enhanced in the future to control who can edit "all libraries" rules
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
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
I don't think we are talking about removing the ability to edit those, just changing what they see when the page is loaded as a default. Anyone could still edit either, but it would hopefully reduce accidental consortia wide changes which are not always easy to spot
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.
+1 -- Nick Clemens Quechee & Wilder Libraries Nick@quecheelibrary.org http://www.QuecheeLibrary.org Q (802) 295-1232 W (802) 295-6341
+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
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 http://www.ptfs-europe.com 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
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
Salvete!
T he 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.
First of all, thank you very much for wrestling with some large sticky problems. I know that there are many people working on very large stuff and very annoying things that have been with us way too long. Thanks! Second, if we're going to make everything more granular, which I totally support, may we please consider having a few example permissions roles already set for usability's sake or at very least outlined on the relevant page or linked to the right part of the manual? These could then be activated by a simple rename, click, or clone. For instance, I can see having a fake Duhrector account and a fake IT head account already in the pipe with the permissions set as if they were current superlibrarians and had access to everything. I'm just always curious about what we can be doing to have things easier for Libraries out of the box. I wish there were modules, since happily a lot of people don't ever have to worry about either branches or permissions. I just worry that while Koha is becoming more and more rich in features (wonderful, thanks!) is also becoming more difficult to sort out during installation (aww bummer!). Cheers, Brooke
Katrin, I'd say that's the entire point! At least some libraries don't want the current behavior. 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 Tue, Sep 16, 2014 at 3:09 PM, Katrin Fischer <Katrin.Fischer.83@web.de> wrote:
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
I agree with Owen! Nancy Keener Systems Librarian I.T.O.S.C. Chair Washoe County Library System Reno, Nevada 775 327-8347 nkeener@washoecounty.us -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Kyle Hall Sent: Tuesday, September 16, 2014 8:45 AM To: Koha Subject: [Koha] Default to logged in branch vs "all branches' As many of you already know, there are a good number of areas in Koha where we have settings for each library, and an "all libraries" default. Examples of this are the circulation rules, slips and notices, overdue status triggers, etc. Some librarians would like the default view to be the library's rules, rather than the "all libraries" rules. The idea being that this would stop librarians from editing the "all libraries" rules by accident. The two bugs in question are: Bug 11625 - Default to logged in library for circ rules and notices & slips http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11625 Bug 11747 - Default to logged in library for Overdue notice/status triggers http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11747 Please let us know how you feel about this! 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 ) _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
participants (10)
-
BWS Johnson -
Joel Sasse -
Katrin Fischer -
Kearns, Sheila -
Keener, Nancy -
Kyle Hall -
Nick Clemens -
Owen Leonard -
Renvoize, Martin -
Viktor.Sarge＠regionhalland.se