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

Anonymized loans: retain patron custom fields data

    XMLWordPrintable

Details

    • Medium
    • Large < 10 days
    • 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)
    • None
    • 10
    • 68
    • R4
    • R1
    • R1
    • R2
    • R2
    • R3
    • R2
    • R2
    • R4
    • R1
    • 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

            is blocked by

            New Feature - New feature requests UXPROD-1295 Users App: Add phone number type and email validation to user records

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1400 Users App: Implement Affiliation Group/Statistical Codes support in same manner as Inventory App

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2143 Q1 2020/Q2 2020 | Custom Fields (for User Record and as General Platform Feature): Frontend Development

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2148 Users App: Support multiple External System IDs

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Analysis Complete
            relates to

            New Feature - New feature requests UXPROD-1120 Retain some patron information on anonymized loans

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2936 Check-Out App: Allow Custom Fields as Patron Identifiers for Check-Out

            • TBD - To be determined
            • Closed
            requires

            New Feature - New feature requests UXPROD-2147 Users App: Department Field

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                cmalmbor Cheryl Malmborg
                ecboettcher Emma Boettcher
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases