Summary: | expand independant branches functionallity | ||
---|---|---|---|
Product: | Koha | Reporter: | Michael Hafen <michael.hafen> |
Component: | Searching | Assignee: | Galen Charlton <gmcharlt> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P2 | CC: | koha.sekjal, kyle, veron |
Version: | Main | ||
Hardware: | PC | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: | proposed patches. |
Description
Chris Cormack
2010-05-20 23:38:43 UTC
Comment on attachment 64 [details] [review] proposed patches. Marking this patch obsolete, as it's not a Git patch, and seems based on Koha 2.2.5 My suggestion here would be to clarify exactly "Independant Branches" should mean. There are several different functions that library networks may or may not want to enable: * Hiding other branches' materials in Search (either at first, or completely) * Hiding other branches' patrons in Patron Search (either at first, or completely) * Hiding other branches' reports, lists, etc * Prevent other branches from editing your items * Prevent other branches from editing your settings * Prevent other branches from editing your patrons * Prevent other branches from editing your reports, lists, etc. We're close on the first section, through various mechanisms. The second session looks more like individual permissions, rather than global sysprefs. For example, we'd want certain privileged individuals to be able to edit EVERYTHING (even if that's only one admin account). Is this bug still necessary? I think this bug is too unspecific and could only be an omnibus bug of some kind. I am adding Kyle as he has been working in this area recently, maybe there is some inspiration to be found, but closing it in favor of newer bug reports. (In reply to Katrin Fischer from comment #4) > I think this bug is too unspecific and could only be an omnibus bug of some > kind. I am adding Kyle as he has been working in this area recently, maybe > there is some inspiration to be found, but closing it in favor of newer bug > reports. Agreed! |