Loans (UXPROD-788)

[UXPROD-1085] Automatically Anonymizing/Scrubbing Loan Data (through Settings) Created: 04/Sep/18  Updated: 16/Sep/20  Resolved: 27/Sep/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2019
Parent: Loans

Type: New Feature Priority: P2
Reporter: Emma Boettcher Assignee: Emma Boettcher
Resolution: Done Votes: 0
Labels: anonymizing, cap-mvp, convo, gdpr, loans, po-mvp, privacy, sig-ra, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-271 Anonymizing/Scrubbing Loan Data (On D... Closed
Defines
is defined by CIRC-325 Backend UIU-1042: Anonymize closed lo... Closed
is defined by CIRC-326 Backend for UICHKIN-99: Anonymized cl... Closed
is defined by UIORG-169 Loan history settings (anonymize clos... Closed
is defined by CIRCSTORE-137 Create new loan anonymization endpoin... Closed
is defined by UITEN-39 When user opens the loan history, loa... Closed
Gantt End to Start
has to be done after FOLIO-1953 SPIKE: propose an approach for schedu... Closed
Relates
relates to UXPROD-373 User endpoint to remove aliases tied ... Open
relates to UXPROD-374 Cron job to call endpoint to remove a... Open
relates to UX-206 Mockups for anonymization settings Closed
relates to UXPROD-2068 Anonymizing closed loans through sett... Closed
relates to UXPROD-2069 Anonymizing closed loans through sett... Closed
relates to UICIRC-54 Automatically anonymize loan history ... Closed
relates to UXPROD-375 Configuration settings from auto loan... Closed
relates to UXPROD-285 GDPR Analysis Complete
Epic Link: Loans
Front End Estimate: Large < 10 days
Front End Estimator: Jakub Skoczen
Back End Estimate: XXL < 30 days
Back End Estimator: Jakub Skoczen
Development Team: Concorde
PO Rank: 131
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R1

 Description   

Purpose: To schedule closed loans for automatic anonymization based on the institutions' preferences for how long they keep identifying borrower information on loans.

High-Level Requirements for Anonymization (across UXPROD-1085 Closed , UXPROD-1120 Closed , UXPROD-447 Closed , UXPROD-271 Closed ):
Due to privacy concerns (both legal and voluntary), many institutions anonymize loan data. In other words, they remove identifying information about the patron (e.g. name and identifiers) from historic loans. Other patron metadata (e.g. patron group) is retained for statistical reporting purposes.

  1. Loan scrubbing
    1. Tenants should be able to determine a time period (specified in days) after which loan data will be anonymized (it should also be possible to not ever anonymize)
    2. Ultimately, each library within a tenant/institution should be able to set their own time period (not v1)
    3. For institutions that don't anonymize for all users by default, we should offer the ability for users to indicate whether they want their data scrubbed (not v1)
    4. For a loan to qualify for scrubbing/anonymizing, it must:
      1. Be closed
      2. Not have any open fees/fines
      3. Be old enough to trigger scrubbing
        1. "Old enough" varies depending on if it has no closed fines/fees or not
    5. When a loan record is scrubbed:
      1. Any patron identifying information should be scrubbed from the loan record in the database.
      2. The only patron information that should be retained includes:
        1. Patron group
        2. Status
        3. Division/department (as of 5/14 RA SIG meeting)
        4. Branch/location (when implemented) Probably not, as of 5/14 RA SIG meeting - not patron info
        5. Custom fields or tags (when implemented)
        6. Date enrolled? No, as of 5/14 RA SIG meeting
        7. Expiration date? No, as of 5/14 RA SIG meeting
      3. The scrubbed loan should no longer display on the patron's Loans page
        1. But what about the Check in page? Institutions that have opted not to save ANY loan history, still need to be able to see the items they just checked in (see UICHKIN-10 Closed for details on what should display on the check in page). We need to make sure this is considered in our implementation.
      4. Anywhere else closed loans may display, the scrubbed loan data should display without any patron identifying information
    6. IMPLEMENTATION NOTE: Many systems log anonymized loan data in a reporting table as soon as the transaction occurs


 Comments   
Comment by Cate Boerema (Inactive) [ 29/Nov/18 ]

Removing scheduler blocker UXPROD-594 Closed as, per Jakub, we don't need a centralized scheduler anymore.

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Emma Boettcher, I am removing the Q1 2019 fix version on this one, as it doesn't look like we'll be able to fit it in.

Comment by Khalilah Gambrell [ 21/Mar/19 ]

Cate Boerema and Emma Boettcher, should this feature be assigned to Vega? If so, is it a Q2 2019 feature?

Comment by Anya [ 29/Mar/19 ]

Comment from the March meeting : GDPR/ PA - FOLIO doesnt have it as the FSE we will step up and anonymizing - this will need to be a seting - could be in Q3

Comment by Cate Boerema (Inactive) [ 24/Apr/19 ]

Marking blocked on FOLIO-1953 Closed

Comment by Emma Boettcher [ 27/Sep/19 ]

Moved incomplete/in progress stories to UXPROD-2068 Closed and UXPROD-2069 Closed

Generated at Fri Feb 09 00:12:49 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.