Improved granular permissions

For 3.2, Howard County Library propose adding the ability to create roles, as well as, expand upon the existing koha permissions.

Roles

The creation of roles would allow a System Administrator to more easily manage individual staff permissions.

  • Roles would consist of any number of certain specific permissions
  • A system administrator would have the ability to view a list of Employees and assign roles to multiple staff members at a time
  • Several example roles would be
    • Cataloging-Advanced
      • View, add, edit, delete authorities
      • View, add, edit, delete bibs
      • View, add, edit, delete items
      • Import bibs and authorities
      • Merge bibs
      • Do global authority updates
    • Cataloging-Basic
      • View authorities
      • View bibs
      • View, add, edit, delete items

Additional permissions

In addition to the permissions that currently exist in Koha, and the ones proposed by LibLime, it would be helpful to see the following permissions available.

  • Under LibLime's “for hold requests” add the ability to change the priority of existing holds
  • Acquisitions
  • Distinguish between running of existing reports vs. creation of new reports
  • Have separate permissions for view, add, edit, and delete bibs vs. a single permission for all four functions
  • Have separate permissions for view, add, edit, and delete items vs. a single permission for all four functions
  • Under ability to edit items, make it possible for the library to specify which item fields can be edited for different levels of staff – all fields for Cataloging staff, Lost and Shelving Location for Public Service staff, etc.
  • Ability for Circulation to create only fast add bibs and items without access to any other cataloging functions

Granular permissions work planned by LibLime

LibLime plans to add the following granular permissions

  • view, add, edit, and delete for the following record types
    • bibs
    • items
    • summary/holdings records
    • authority records
    • patron records
  • for circulation transactions, the following distinctions
    • check out
    • check in
    • change due date
    • use dropbox mode
    • circulation reports
  • for patron fines:
    • add fines/create manual invoice
    • pay fines
    • forgive fines
  • for hold requests:
    • view requests
    • add requests
    • edit requests
    • delete requests
  • for patron records:
    • update PIN
    • proxy patron maintenance
  • for serials
    • serials view
    • serials add subscription
    • serials edit subscription
    • delete subscription
    • serials check-in
    • serials claiming
  • a permission for each administration page
  • a permission for access to 'Lists' in the staff interface.
 
en/development/rfcs3.2/rfc32_improved_permissions.txt · Last modified: 2008/09/12 10:23 by danny.bouman
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki