Issues

Select view

Select search mode

 

Anonymize closed loans on demand

Done

Description

Purpose: When an institution defaults to maintaining patrons' loan history, the patron may want to anonymize their loans (similar to how they may perform other self-service functions, like renewing their books). Staff should also be able to do this on behalf of a patron.

  1. Scenario

    • Given the closed loans screen :check_mark:

    • When the user clicks "Anonymize all loans"

    • Then the closed loans no longer have any borrower information linked to them, and no longer appear as closed loans for a patron. :check_mark:

    • A-M: we tested, but you have to refresh your screen to get rid of the 1 closed loan in the summary of the borrower details. Should that happen automatically when the loan is anonymized? If you try to click the 1 closed loan after anonymizing, then you go to a blank closed loan screen.

    • See Michal's comments below. Logged this as a separate bug UIU-647.

  2. Scenario :check_mark:

    • Given that a user's loans have been anonymized

    • When viewing Closed Loans

    • Then no closed loans prior to when the loans were anonymized should be shown, as if the user has never checked anything out.

Out of scope: how this affects closed loans with "unfinished business", like those with a fine/fee attached.

Includes anonymizing the affected loans, loan action history as well.

Clarification: Anonymizing closed loans is not deleting them. Institutions still need to be able to track whether an item circulated & and for how long, among other details. The only information that anonymizing a closed loan affects is that of the borrower.

Environment

None

Potential Workaround

None

Attachments

4
  • 18 Sep 2018, 07:53 PM
  • 07 Sep 2018, 04:15 PM
  • 07 Sep 2018, 04:09 PM
  • 24 Aug 2018, 04:54 PM

Checklist

hide

TestRail: Results

Details

Assignee

Reporter

Priority

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created April 6, 2018 at 8:58 PM
Updated October 10, 2018 at 4:47 PM
Resolved September 20, 2018 at 6:15 PM

Activity

Show:

Ann-Marie Breaux September 20, 2018 at 7:35 PM

Perfect - thank you!

Michal Kuklis September 20, 2018 at 6:29 PM

No worries . Yes it is the same issue. I created this one: https://folio-org.atlassian.net/browse/STCON-71 to cover these two cases.

Ann-Marie Breaux September 20, 2018 at 6:12 PM

Thanks, I'm sorry I didn't get a chance to attend to this, so I appreciate your taking care of it. Do you think it's the same type of bug that we're seeing with https://folio-org.atlassian.net/browse/FOLIO-1506#icft=FOLIO-1506, where the number of tags doesn't update simultaneously when the number in the 4th pane changes?

Michal Kuklis September 20, 2018 at 12:57 PM
Edited

I filed JIRA for this bug here: https://folio-org.atlassian.net/browse/UIU-647
I'm going to move this to "in review"

Michal Kuklis September 19, 2018 at 4:45 PM

this sounds like a bigger issue with data / cross component synchronization. It revealed itself in this story but I worry this is a bigger issue. Since this story has been included in Q3 last week I wonder if perhaps we could create another bug to keep track of this issue. What do you think?

TestRail: Cases
TestRail: Runs

Flag notifications