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

Requests: Anonymization of closed requests

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      CB: Per agreement with Jakub and the cap planning team, some of us non-developers will estimate the remaining unestimated features so as not to disrupt development. I am estimating this based on the estimates for anonymizing loans and fee/fines (UXPROD-271 and UXPROD-447).
      Show
      CB: Per agreement with Jakub and the cap planning team, some of us non-developers will estimate the remaining unestimated features so as not to disrupt development. I am estimating this based on the estimates for anonymizing loans and fee/fines ( UXPROD-271 and UXPROD-447 ).
    • Development Team:
      Vega
    • Calculated Total Rank:
      99
    • Kiwi Planning Points (DO NOT CHANGE):
      40
    • PO Rank:
      89
    • PO Ranking Note:
      Hide
      2021-03-08 - BT: Making PO rank the same as calculated rank for now.
      2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
      2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
      Show
      2021-03-08 - BT: Making PO rank the same as calculated rank for now. 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now. 2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R2
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Grand Valley (Full Sum 2021):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Mainz (Full TBD):
      R1
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

       

      Current situation or problem:

      Institutions will want to anonymize closed requests, breaking the link to the requesting patron, but retaining demographic and other data for statistical and reporting purposes

      The anonymization will need to be done in batch, both manually run and automated, based on intervals set by the institution

      In scope

      • Automated anonymization of closed requests
      • On-demand anonymization of one or more requests

      Out of scope

      Use case(s)

      Proposed solution/stories [draft]

      • Add additional demographic data to the request storage data model (un-deprecate patron group)
        • Department
        • Custom Fields (need to consider this, since we don't currently have a way to indicate whether custom fields are PII)
      • Add setting to configure automated anonymization, a la loan history
        • Different settings for "Closed - Cancelled", "Closed - Filled", "Closed - Pickup expired", and "Closed - Unfilled"
        • Implement a scheduled anonymization job
      • Add action to Requests app results list pane action menu to anonymize all results
      • Add action to request detail action menu to anonymize the specific request

      Links to additional info

      Questions

      • Do we need different settings for each form of "Closed"?
      • Do we want to support bulk manual anonymization? (eg. search results action menu)
      • How can we handle custom fields?
         

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                brookstravis Brooks Travis
                Reporter:
                cboerema Cate Boerema
                Front End Estimator:
                Cate Boerema Cate Boerema
                Back End Estimator:
                Cate Boerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases