Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

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

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 three automated patron blocks implemented in Q2 2020 are not handling the limits properly. This is how they should work...

Maximum number of lost items

  • If Limit set at 2, block shows up on User Information at 3- - does not work correctly now

  • If Limit set at 2, patron is blocked when attempting to check out an item after losing 3rd item - does not work correctly now

  • If Limit set at 2, patron is blocked when requesting an item after losing 3rd item - does not work correctly now

  • If Limit set at 2, patron is blocked when renewing an item after losing 3rd item - does not work correctly now

Maximum outstanding fee/fine balance

  • If Limit set at 100.00, block shows up on User Information at 100.01 - - does not work correctly now

  • If Limit set at 100.00, patron is blocked when attempting to check out an item at 100.01 - does not work correctly now

  • If Limit set at 100.00, patron is blocked when requesting an item when at 100.01 - does not work correctly now

  • If Limit set at 100.00, patron is blocked when renewing an item when at 100.01 - does not work correctly now

Maximum number of items charged out

  • If Limit set at 3, block shows up on User Information at 3 - works correctly now (this is different than how the other blocks work, but if we don't show the block on User Information at 3, then when checkout, requesting and renewing are blocked and the staff member presses 'View block details' there would be nothing to see)

  • If Limit set at 3, patron is blocked when attempting to check out the 4th item - works correctly now

  • If Limit set at 3, patron is blocked when requesting if 4th item checked out - does not work correctly now

  • If Limit set at 3, patron is blocked when renewing if 4th item checked out - does not work correctly now

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

2
  • 19 Aug 2020, 12:47 AM
  • 19 Aug 2020, 12:47 AM

is cloned by

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Holly MistlebauerAugust 20, 2020 at 4:06 PM

This fix should be released with the Q2 hotfix release. The fee/fine balance block issues have been created as a separate ticket: https://folio-org.atlassian.net/browse/MODPATBLK-48#icft=MODPATBLK-48. This ticket will be released as a hotfix at a later date.

Holly MistlebauerAugust 20, 2020 at 3:51 PM

The issues Holly found when testing in BUGFEST will be created as separate issues. https://folio-org.atlassian.net/browse/MODPATBLK-34#icft=MODPATBLK-34 has improved how patron blocks work, so we will close and release it as is. This will go out with the Q2 2020 hotfix release as is.

Holly MistlebauerAugust 20, 2020 at 2:21 PM

The loans could have been scrubbed. I believe the scrub processing is running on Bugfest as it would in production. Loans are scrubbed for patron privacy.

Alexander KurashAugust 20, 2020 at 1:17 PM

I checked Laurie Zorn on BugFest and to me it looks like data is inconsistent. How can this patron have 0 loans - both open and closed? If you try to click View under Loan details it'll fail to show the loan. At the same time, these missing loans are referenced from both fine entries and mod-patronblocks user summary entries. Don't know yet whether this has affected the calculation.

Also, Suzy Q Librarian has more open fines on mod-patronblocks side than on the mod-feesfines side, looks like some messages aren't getting through or were incorrectly handled. I'll proceed with the investigation.

Holly MistlebauerAugust 19, 2020 at 5:22 PM

I also re-encountered https://folio-org.atlassian.net/browse/UIU-1364#icft=UIU-1364, which is an issue UNAM is working on right now.

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Vega

Fix versions

Release

Q2 2020 Hot Fix #1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 10, 2020 at 9:54 PM
Updated October 8, 2020 at 3:55 PM
Resolved August 20, 2020 at 3:51 PM
TestRail: Cases
TestRail: Runs

Flag notifications