https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30198
Steve, OSLRI, USA <ssp...@oslri.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssp...@oslri.net
--- Comment #3 from Steve, OSLRI, USA <ssp...@oslri.net> ---
It was suggested that I hop on board this bug, so here I go!
Reading the comments on this ticket, I would suggest we are talking about two
different things... both very useful!
1) I like the idea that Donna has originally suggested with the ability to
restrict access to data in certain tables. Perhaps one simple way to do this
would be to identify tables and/columns that ought to require special
permissions and create a single (or if warranted) a couple user permissions in
place for those. I'd agree with reading history. I'd also argue any PII fields
in the borrowers table.
2) What brought me here might be a little closer to Andrew's comment. (Maybe?)
We will potentially have many staff members in our system writing reports and
are concerned about "clutter". We'd love the ability for somebody to be able
to define a "sharing level" for a report. Perhaps, four levels: (1)
Private/Just Me, (2) Shared with My Branch, (3) Shared with My Library Group,
(4) Shared with Everyone. This would really help cut down on clutter AND allow
people to work on draft queries that are NOT ready for prime time without
somebody else attempting to use it by accident. I'd agree that super
librarians should see all. That way we can help somebody with a report in
their private reports should they ask for help. (Perhaps this is a different
bug?)
Cheers!
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
