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

Automatically Anonymizing/Scrubbing Loan Data (through Settings)

    Details

    • Type: New Feature
    • Status: Analysis Complete (View Workflow)
    • Priority: P2
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Epic Link:
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XXL < 30 days
    • Development Team:
      Vega
    • Rank: Chalmers:
      go-live
    • Rank: Chicago:
      go-live
    • Rank: Cornell:
      go-live
    • Rank: 5Colleges:
      go-live
    • Rank: Lehigh:
      go-live
    • Rank: TAMU:
      NOT NEEDED
    • Rank: U of AL:
      go-live
    • Rank: Bremen:
      go-live

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

        Attachments

          Issue Links

            Expenses

              Activity

              Hide
              cboerema Cate Boerema added a comment -

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

              Show
              cboerema Cate Boerema added a comment - Removing scheduler blocker UXPROD-594 as, per Jakub, we don't need a centralized scheduler anymore.
              Hide
              cboerema Cate Boerema added a comment -

              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.

              Show
              cboerema Cate Boerema added a comment - 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.

                People

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

                  Dates

                  • Created:
                    Updated: