All work

Select view

Select search mode

 

Automatically Anonymizing/Scrubbing Loan Data (through Settings)

Done

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, UXPROD-1120, , ):
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 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

Priority

Fix versions

Development Team

Concorde

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Details

Reporter

PO Rank

131

Front End Estimate

Large < 10 days

Front End Estimator

Back End Estimate

XXL < 30 days

Back End Estimator

Rank: FLO (MVP Sum 2020)

R1

Rank: 5Colleges (Full Jul 2021)

R1

Rank: Cornell (Full Sum 2021)

R1

Rank: Chalmers (Impl Aut 2019)

R1

Rank: BNCF (MVP Feb 2020)

R1

Rank: GBV (MVP Sum 2020)

R1

Rank: hbz (TBD)

R1

Rank: Hungary (MVP End 2020)

R1

Rank: TAMU (MVP Jan 2021)

R5

Rank: Chicago (MVP Sum 2020)

R4

Rank: MO State (MVP June 2020)

R1

Rank: U of AL (MVP Oct 2020)

R1

Rank: Leipzig (Full TBD)

R1

Rank: Lehigh (MVP Summer 2020)

R1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 4, 2018 at 2:12 PM
Updated September 16, 2020 at 9:05 PM
Resolved September 27, 2019 at 4:53 PM

Activity

Show:

Emma BoettcherSeptember 27, 2019 at 4:53 PM

Moved incomplete/in progress stories to and

Cate BoeremaApril 24, 2019 at 4:25 PM

Marking blocked on FOLIO-1953

AnyaMarch 29, 2019 at 10:11 PM

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

Khalilah GambrellMarch 21, 2019 at 6:51 PM

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

Cate BoeremaDecember 5, 2018 at 11:51 AM

, 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.

TestRail: Cases
TestRail: Runs