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

Anonymized loans: retain patron custom fields data

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
      Hide
      Requires integration with provider of custom-fields interface, this is a multiple implementation interface meaning that circulation needs to understand how to discriminate. I'm not sure how dependencies work for multiple interface implementations (it might be that it is satisfied by any implementation, which would mean this would break at runtime)
      Show
      Requires integration with provider of custom-fields interface, this is a multiple implementation interface meaning that circulation needs to understand how to discriminate. I'm not sure how dependencies work for multiple interface implementations (it might be that it is satisfied by any implementation, which would mean this would break at runtime)
    • Development Team:
      None
    • Calculated Total Rank:
      60
    • Kiwi Planning Points (DO NOT CHANGE):
      10
    • PO Rank:
      68
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Grand Valley (Full Sum 2021):
      R3
    • Rank: hbz (TBD):
      R2
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: MO State (MVP June 2020):
      R4
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      Current situation or problem:
      When an item is checked out to a borrower, the borrower's ID and patron group are stored on the loan. When loans are anonymized, there is no longer a link between the borrower and the loan, though the patron group at time of check out remains.

      Some institutions would like to keep additional information about patrons on the loan, in particular information which they've implemented using custom fields.

      In scope

      • Allow tenant to differentiate between which custom fields should be stored on loan (despite anonymization) and which should not
      • When loans are anonymized, retain custom fields so distinguished

      Out of scope

      • Retaining other patron information besides custom fields on loans

      Use case(s)
      A library has a custom field for "department" so they can track item use for humanities faculty vs. sciences faculty.

      Proposed solution/stories

      Links to additional info

      Questions

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                cmalmbor Cheryl Malmborg
                Reporter:
                ecboettcher Emma Boettcher
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases