Summary: | You can delete a patron who has created virtualsheves without any warn | ||
---|---|---|---|
Product: | Koha | Reporter: | Mathieu Saby <mathsabypro> |
Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED MOVED | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P3 | CC: | aleisha, gmcharlt, kyle.m.hall, veron |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10910 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13910 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Mathieu Saby
2013-09-18 09:09:23 UTC
Why is it bad? I think if the lists are just personal, they should be deleted with the patron, if it's a shared list (which is currently not yet possible I think?) - it should probably stay around until the last user is deleted... but I thought that was already the case looking at some of the code recently. It is bad because we have some "duplicate" patrons in our base (for some reasons, migration issues, or double import from LDAP when somebody has 2 accounts in LDAP) Some colleague found it was safe to delete a patron's account in Koha, but they suppressed the account he used for making suggestions and for making lists. And he asked us explanations when his lists and suggestions disappeared... All I could say was "it is a kind of bug in our system" ;-) Mathieu See Bug 11889 - I have created a patch for a syspref that lets you choose whether to delete a user's lists when you delete their account, or if the ownership of those lists will get transferred to the person who deleted the owner. |