Bug 5763 - Add users private list management functionality for administrators
Summary: Add users private list management functionality for administrators
Status: CLOSED DUPLICATE of bug 13417
Alias: None
Product: Koha
Classification: Unclassified
Component: Lists (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Target Milestone: ---
Assignee: Galen Charlton
QA Contact: Bugs List
URL:
Whiteboard:
Keywords:
: 5487 (view as bug list)
Depends on:
Blocks: 7310
  Show dependency treegraph
 
Reported: 2011-02-15 18:31 UTC by Frédéric Demians
Modified: 2017-03-06 08:33 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Bot Control: ---
When did the bot last check this:
Who signed the patch off:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric Demians 2011-02-15 18:31:03 UTC
In Koha Staff Interface, Home > Lists, a professional user can manage
Public Lists and his Lists. But there is no way for a Koha administrator
to manage users lists. From time to time it'll be very usefull to clean
users lists which grow indefinitely.
Comment 1 Nicole C. Engard 2011-02-15 19:37:01 UTC
I see a major privacy issue with this.  I think it would be great to delete lists of users who have been deleted, but I don't like the idea of librarians being able to access user lists at all.
Comment 2 Frédéric Demians 2011-02-15 20:02:53 UTC
(In reply to comment #1)
> I see a major privacy issue with this.  I think it would be great to
> delete lists of users who have been deleted, but I don't like the idea
> of librarians being able to access user lists at all.

Good point. Thanks. And controlling access via Koha permissions in order
to control which librarians are allowed to see/manage lists of users? In
any case, even if there is a technical barrier, anyone having access to
Reports can see users private lists.
Comment 3 Owen Leonard 2011-02-16 13:39:44 UTC
This duplicates Bug 5487, but since the discussion is here I'll mark the other the duplicate.

Librarians already have access to patrons' contact information and checkout history. I don't see how giving them access to patrons' lists is any different. My suggestion in Bug 5487 was specifically for a granular permission giving access to patrons' lists. If we don't want to give access to the contents, we should at least be able to edit the title (in the case of inappropriate language) or delete the whole list (in the case of inactive patrons).
Comment 4 Owen Leonard 2011-02-16 13:39:54 UTC
*** Bug 5487 has been marked as a duplicate of this bug. ***
Comment 5 Nicole C. Engard 2011-02-16 13:54:44 UTC
Owen, if the patron chooses not to let the library have their circulation history then they don't have access to that anymore and I see lists in the same light.

Maybe lists needs to be part of the opac privacy settings.
Comment 6 Owen Leonard 2011-02-16 14:01:40 UTC
> Owen, if the patron chooses not to let the library have their circulation
> history ...

History, maybe, but current checkouts are always known to the staff.
Comment 7 Nicole C. Engard 2011-02-16 14:04:40 UTC
True.  I don't really care either way, I just know that many librarians will care and many paranoid patrons will care as well. Since we have a mechanism for privacy, why not let patrons decide if librarians can see their list contents?
Comment 8 Katrin Fischer 2016-06-19 22:53:54 UTC
There is now a way to delete public lists covered by a separate permission.
Comment 9 Marcel de Rooy 2017-03-06 08:33:46 UTC
(In reply to Katrin Fischer from comment #8)
> There is now a way to delete public lists covered by a separate permission.

We can close this bug now. See bug 13417.

*** This bug has been marked as a duplicate of bug 13417 ***