Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-271

Anonymizing/Scrubbing Loan Data (On Demand)

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XXL < 30 days
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      90
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      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 share the high-level requirements for this feature with the tech team so we can begin a conversation around best path forward.

      Background: 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.

      Institutions may anonymize data either as policy (scrubbing patron information from all closed loans), or at the request of a specific patron. This story only covers one-time, manual anonymization of closed loans, breaking the link between the closed loan & the patron and removing the anonymized loans from the patron's list of closed loans.

      Anonymization of closed loans elsewhere:

      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

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ecboettcher Emma Boettcher
                Reporter:
                cboerema Cate Boerema
                Front End Estimator:
                Jakub Skoczen Jakub Skoczen
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases