[Koha-bugs] [Bug 35693] Granular Permissions to Everything

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35693

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #3 from David Cook <dcook at prosentient.com.au> ---
(In reply to Christopher Brannon from comment #0)
> I am hoping that Koha will start thinking more about roles in the library,
> and allowing us to give specific people access to specific pages,
> customizations, etc.  This goes even further with who can override things. 
> We don't have a lot of control over who can do what specific things.

I think that you make a very good point, but Koha developers are a fairly loose
group which support a variety of different libraries, and I think most
developers have never worked as librarians themselves (with the exception of a
few of us). Change usually comes from starting with one developer/vendor and
then building support across the group.

Personally, most of my (many) libraries have very small staff sizes, and I
haven't heard any complaints around permissions (except for the latest one
about requiring "edit_borrowers" to search/list borrowers). So I'm unlikely to
get sponsorship for such a change. But I imagine there are other vendors who
support libraries with larger staffs who would be more likely to get that kind
of sponsorship.

In the meantime, something that could be helpful is libraries coming up with a
list of "personas" and "scenarios". These are useful elements of system design. 

Something basic like "Joe is a collection development librarian" (persona). The
collection development librarian "needs to search the catalogue" (scenario),
"needs to update only certain allowed lists" (scenario), "needs to update only
collection development HTML pages" (scenario). 

Basically just outlining the hypothetical people and the things they need to
do. 

>From there the developers can start working out how we can technologically
allow those people to do those scenarios.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.