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

Automated Patron Blocks (Q3 2020 work split from Q2 2020)

    XMLWordPrintable

    Details

    • Template:
    • Potential Workaround:
      Hide
      Holly: We currently have Manual Patron Blocks, which are set in User Information. Automated Patron Blocks allow the library to set limits that are enforced automatically. For example, if a patron owes over $100 in fines they can be automatically blocked from checking out any more items. Or they can be blocked if they have more than 10 claimed-returns, etc. Whatever limits the library wants to set. The workaround for this would be for the library to run a query against the database (the data warehouse?) to find out who is violating their rules and then enter Manual Patron Blocks for the patrons who need to be stopped.
      Show
      Holly: We currently have Manual Patron Blocks, which are set in User Information. Automated Patron Blocks allow the library to set limits that are enforced automatically. For example, if a patron owes over $100 in fines they can be automatically blocked from checking out any more items. Or they can be blocked if they have more than 10 claimed-returns, etc. Whatever limits the library wants to set. The workaround for this would be for the library to run a query against the database (the data warehouse?) to find out who is violating their rules and then enter Manual Patron Blocks for the patrons who need to be stopped.
    • Epic Link:
    • Back End Estimate:
      XL < 15 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
    • Development Team:
      Vega
    • Calculated Total Rank:
      122
    • PO Rank:
      93
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R5
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      This feature was split from UXPROD-82 (Automated Patron Blocks) because two user stories were not completed by the Q2 2020 deadline:

      Until MODPATBLK-18 is completed, the following automated patron blocks will not work...

      • Maximum number of overdue items
      • Maximum number of overdue recalls
      • Recall overdue by maximum number of days

      The following automated patron blocks are available as of Q2 2020...

      • Maximum outstanding fee/fine balance
      • Maximum number of items charged out
      • Maximum number of lost items

      There are Q2 2020 hotfixes needed for the three automated patron blocks implemented as part of Q2 2020 to work properly...

      The Maximum outstanding fee/fine balance automated patron block will not work properly until hot fixes are released for the following bugs:

      • MODPATBLK-26 - Automated patron block 'Maximum amount of outstanding fees/fines' does not clear after outstanding fees/fines paid
      • MODPATBLK-27 - Blank 'Maximum outstanding fee/fine balance' automated patron block remains when condition removed by library
      • MODPATBLK-29 - 'Maximum outstanding fee/fine balance' automated patron block not going in effect when it should after changing patron's Patron Group
      • MODPATBLK-34 - Limits for 3 implemented automated patron blocks not working properly

      The Maximum number of outstanding lost items automated patron block will not work properly until hot fixes (planned for July) are released for the following bugs:

      • MODPATBLK-34 - Limits for 3 implemented automated patron blocks not working properly
      • MODPATBLK-38 - Automated patron block 'Maximum number of lost items' is not clearing properly - Part 2

      The Maximum number of items charged out automated patron block will not work properly until hot fixes (planned for July) are released for the following bugs:

      • MODPATBLK-34 - Limits for 3 implemented automated patron blocks not working properly

      There is also a user story impacting all automated patron blocks:

      • MODPATBLK-35 - Add diagnostic GET endpoint for UserSummary objects

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                hollyolepm Holly Mistlebauer
                Reporter:
                cboerema Cate Boerema
                Front End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Back End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases