Bug 35320 - Deleting a patron doesn't use AnonymusPatron to anonymize the circulation history
Summary: Deleting a patron doesn't use AnonymusPatron to anonymize the circulation his...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-13 14:26 UTC by Noémie Labine
Modified: 2023-11-14 16:09 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Noémie Labine 2023-11-13 14:26:13 UTC
I was under the impression that when AnonymousPatron is filled with a borrowernumber, deleting a patron (individually or with batch deletion tool) would anonymize their circulation history using AnonymousPatron, but it doesn't. After deleting a or some patrons, the circulation history in the book record shows blank spaces in lieu of the patrons.

It would make more sens that when deleting a patron using the batch deletion tool or the delete button in a patron's page, the AnonymousPatron is used to fill the circulation history of the deleted patrons.
Comment 1 Katrin Fischer 2023-11-13 15:05:01 UTC
It will be used when a patron or library decides to anonymize the history (patron privacy settings). Why do you think anonymous would make more sense than null? Or are the whole lines/entries gone?
Comment 2 Noémie Labine 2023-11-14 16:09:00 UTC
No, the entries are not gone, but to me it would make more sens to group all of the old issues that don't have a patron anymore (because of anonymization or deletion) under the AnonymousPatron's name so that if they look at their stats or in the circulation history of a document, they don't have null entries AND entries under the AnonymousPatron's name.

If they use an SQL query to look at their old issues and they group the issues using different borrower's criterias, they would have a null entry and then an entry for the AnonymousPatron. It would just be more user-friendly I think.