Bug 6223 - Patron categories should have a default set of permissions
Summary: Patron categories should have a default set of permissions
Status: RESOLVED DUPLICATE of bug 18787
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement with 20 votes (vote)
Assignee: Kyle M Hall
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-20 16:16 UTC by Fernando L. Canizo
Modified: 2019-05-17 14:49 UTC (History)
8 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando L. Canizo 2011-04-20 16:16:36 UTC
If you set a patron to a certain category then that patron should receive a set of permissions. If I'm saying that 'Joan Doe' has category 'staff' then it shouldn't be necessary to give him appropriate permissions. They should be filled according to category.

This means that we will need to add default permission sets as system preferences for each defined patron category.
Comment 1 David Cook 2013-08-13 05:01:26 UTC
I think that this is a great idea. 

I've recently had a library ask if this is a possibility, so it would be great to see this get into Koha. 

I have other priorities at the moment, but I would be happy to test any patches and maybe write my own sometime in the future.
Comment 2 Joy Nelson 2014-02-20 23:15:59 UTC
I have had a library ask for this same thing.  The downside I see here is that libraries may start setting up a billion patron categories because of the granularity in permissions.  

Something to consider.
joy

(In reply to David Cook from comment #1)
> I think that this is a great idea. 
> 
> I've recently had a library ask if this is a possibility, so it would be
> great to see this get into Koha. 
> 
> I have other priorities at the moment, but I would be happy to test any
> patches and maybe write my own sometime in the future.
Comment 3 Barton Chittenden 2014-10-27 20:53:51 UTC
I don't think that setting default permissions goes far enough -- this works when a new patron is added, but it doesn't help when permissions need to be added or changed across a group of existing patrons.

Perhaps we need to introduce the concept of "role" that encompasses a group of permissions, which could be changed en-masse: 

borrower has a role
patron category has a default role
a role has many permissions
a role may be based off a parent role (when the parent changes, all permissions not specified by the child will also change).

This would allow some independence between patron categories and groups of permissions, while still allowing mass-insert and/or update of permissions as necessary.
Comment 4 Katrin Fischer 2018-05-17 22:49:30 UTC

*** This bug has been marked as a duplicate of bug 18787 ***