Loans (UXPROD-788)

[UXPROD-1120] Retain some patron information on anonymized loans Created: 18/Sep/18  Updated: 16/Sep/20  Resolved: 24/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, q3-2019-spillover, sig-ra
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-327 Backend for UIU-1043: show patron gro... Closed
Relates
relates to UXPROD-2062 Anonymized loans: retain patron custo... Open
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: 110
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R1
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): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R1

 Description   

Purpose: Retain patron information on anonymized loans for reporting purposes. The borrower ID should not be associated with the loan, but the patron group, statistical code, and custom fields (often used for indicating patron's department) should be, so that the library can track use by those fields.

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) [ 05/Dec/18 ]

Emma Boettcher, since this isn't needed by Chalmers to go live, I switched the fix version to Q2 2019.

Comment by Cate Boerema (Inactive) [ 13/Mar/19 ]

Emma Boettcher I am just switching these to Q3, as we are still focused on Chalmers go live plus stabilization. If we have time after the capacity planning, we can bring these back in.

Comment by Anya [ 29/Mar/19 ]

Comment from the March Meeting : Anonymized- this should be move to the Anonymized features

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