[Koha-bugs] [Bug 9382] Bold necessary permissions for staff client access.

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Jan 28 20:16:06 CET 2013


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9382

Owen Leonard <oleonard at myacpl.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #14762|0                           |1
        is obsolete|                            |

--- Comment #5 from Owen Leonard <oleonard at myacpl.org> ---
Created attachment 14902
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=14902&action=edit
[SIGNED-OFF] Bug 9382 - updating permission labels

first, replicate:
go to More -> permissions on any user. Notice that it says various things
"privileges, flags, permissions" they are interchangeable and inconsistent.
also note that some of the permissions are nonsensical and/or not descriptive
enough, or not using canonical terminology (borrowers instead of patrons, for
example)

To test:
interface consistency changes

-> means "turns into"

- page title - privileges -> permissions
- breadcrumbs - privileges -> permissions
- headings - privileges -> permissions
- "set flags" button -> save

Permissions that have changed description:

- Catalogue changes to "Required for staff login" in bold (this was the
original impetus for this boatload of changes)
- reports
- editauthorities
- management
- serials
- updatecharges
- circulate
- parameters
- borrowers
- tools
- staffaccess
- edit_patrons (only on updatedb, not on new db)

- Read through and make sure there are no typos, and that the descriptions seem
to jive with what privileges the permission gives the user. Suggestions are, in
fact, welcome.

- If you are feeling ambitious, go ahead and create a new, clean database and
check the wording there as well - it should match what has been done in the db
update.

Signed-off-by: Owen Leonard <oleonard at myacpl.org>

Tested both with existing database and new database

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


More information about the Koha-bugs mailing list