Uploaded image for project: 'mod-patron-blocks'
  1. mod-patron-blocks
  2. MODPATBLK-41

Limits for 3 implemented automated patron blocks not working properly - CREATED IN FOLIO PRE-GOLDENROD

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 94, EPAM-Veg Sprint 97, EPAM-Veg Sprint 98, EPAM-Veg Sprint 99
    • 13
    • Vega
    • Q3 2020
    • Incomplete/missing requirements

    Description

      UPDATED ON AUGUST 17, 2020

      Holly has split MODPATBLK-34: Limits for 3 implemented automated patron blocks not working properly into two separate bugs...

      • MODPATBLK-34: Limits for 3 implemented automated patron blocks not working properly - ACTIONS CREATED IN FOLIO POST-GOLDENROD
      • MODPATBLK-41: Limits for 3 implemented automated patron blocks not working properly - ACTIONS CREATED IN FOLIO PRE-GOLDENROD

      What do we mean by ACTIONS CREATED IN FOLIO POST-GOLDENROD? This means that all of the 'actions' being included for block consideration were created after Goldenrod was implemented, when Automated Patron Blocks was first available. In other words, a limit of 100.00 for fees/fines would not include any fees/fines migrated from a previous ILS or billed before upgrading to Goldenrod.

      What do we mean by ACTIONS CREATED IN FOLIO PRE-GOLDENROD? This means 'actions' to be included for block consideration include those created within FOLIO before the Goldenrod release (before Automated Patron Blocks existed).and after the Goldenrod release. Those created before the Goldenrod release need to be processed by a script to be pulled in.

      Any 'actions' (loans, fees/fines) MIGRATED INTO FOLIO FROM A PREVIOUS ILS will be treated as if they were created within FOLIO as long as they were imported into FOLIO via the same APIs FOLIO uses to create loans, fees/fines, etc. within FOLIO. If not, the 'actions' would need to be processed by a script to be pulled in.

      The purpose of this user story (MODPATBLK-41) is to write a script that will process pre-Goldenrod 'actions' and migrated 'actions' not imported using the standard APIs, so they are included in the Automated Patron Block counts.

      The MODPATBLK-34 user story fixed when the blocking was occurring for the three implementing limits...

      Maximum number of lost items

      • If Limit set at 2, block shows up on User Information at 3
      • If Limit set at 2, patron is blocked when attempting to check out an item after losing 3rd item
      • If Limit set at 2, patron is blocked when requesting an item after losing 3rd item
      • If Limit set at 2, patron is blocked when renewing an item after losing 3rd item

      Maximum outstanding fee/fine balance

      • If Limit set at 100.00, block shows up on User Information at 100.01
      • If Limit set at 100.00, patron is blocked when attempting to check out an item at 100.01
      • If Limit set at 100.00, patron is blocked when requesting an item when at 100.01
      • If Limit set at 100.00, patron is blocked when renewing an item when at 100.01

      Maximum number of items charged out

      • If Limit set at 3, block shows up on User Information at 3
      • If Limit set at 3, patron is blocked when attempting to check out the 4th item
      • If Limit set at 3, patron is blocked when requesting if 4th item checked out
      • If Limit set at 3, patron is blocked when renewing if 4th item checked out

      TestRail: Results

        Attachments

          Issue Links

            clones

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-34 Limits for 3 implemented automated patron blocks not working properly - ACTIONS CREATED IN FOLIO POST-GOLDENROD

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

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-45 SPIKE: Find a way to include events created before Goldenrod into automated patron blocks calculation

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

            Bug - A problem which impairs or prevents the functions of the product. MODPATBLK-21 Automated patron block 'Maximum number of lost items' is not clearing properly

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

            Page Loading...

            Activity

              People

                roman-barannyk Roman Barannyk
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases