Bug 13831

Summary: Item history is anonymized when borrower anonymizes his reading history using Immediate deletion
Product: Koha Reporter: Olli-Antti Kivilahti <olli-antti.kivilahti>
Component: ReportsAssignee: Galen Charlton <gmcharlt>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: katrin.fischer, veron
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Attachments: [Signed-off] Bug 3831: Does not allow to delete the FA framework

Description Olli-Antti Kivilahti 2015-03-13 13:18:13 UTC
It is crucial to be able to tell who had the Item checked out last, so we can pursue mishandling of Items.
Currently if a borrower checks-in a loan, and goes to his/her
  "OPAC" -> "Your privacy" -> "Immediate deletion"
the Item history points to the statistical anonymizer borrower, instead of the real borrower.

The reading history anonymizer should not anonymize loans which should still be visible in the Item's history.

TEST PLAN:
0. Make sure the system preference "AnonymousPatron" is set and points to a
   existing borrower record.
1. Checkout a Item.
2. Checkin the same Item.
3. Look at the Item's history at catalogue/moredetail.pl and see that you are the
   "Last borrower"
4. Trigger "OPAC" -> "Your privacy" -> "Immediate deletion"
5. In catalogue/moredetail.pl, the "Last borrower" is now the statistical
   anynomization borrower.
6. Should we need to reimburse the "Last borrower" for any damages for the Item,
   we cannot know who it was.
Comment 1 Katrin Fischer 2015-03-16 00:23:33 UTC
Hi Olli,

this might be interesting for you: bug 9011
Comment 2 Marc Véron 2015-03-26 06:03:26 UTC Comment hidden (obsolete)
Comment 3 Marc Véron 2015-03-26 06:06:08 UTC
Comment on attachment 37251 [details] [review]
[Signed-off] Bug 3831: Does not allow to delete the FA framework

Wrong bug number, sorry...
Comment 4 Katrin Fischer 2015-05-15 22:00:08 UTC

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