Web client has no way to recalculate patron penalties

Bug #1823225 reported by Blake GH
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
High
Unassigned
3.8
Fix Released
High
Unassigned

Bug Description

EG 3.1.10 and likely all versions of Evergreen where the web client is primary.

XUL client had a button called "Refresh" which would trigger a patron penalty calculation. As far as I know, there isn't a way to cause the web client to perform that action.

Related IRC

http://irc.evergreen-ils.org/evergreen/2019-04-04#i_401330

tags: added: patron webstaffclient
Andrea Neiman (aneiman)
tags: removed: webstaffclient
Revision history for this message
Christine Burns (christine-burns) wrote :

This is still an issue in EG 3.7

Ideally, when the penalty threshold changes there could be a way for the system to search for existing bills that meet or exceed the threshold and apply blocking messages to user accounts or conversely to remove blocking messages on patron accounts that do not meet the threshold.

If that isn't possible, then a Refresh button that would re-calculate the penalty thresholds and apply/ remove blocking messages for an individual patron account would also be great.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Michele Morgan (mmorgan) wrote :

Changing importance to High on this as it allows circulation transactions to proceed that should be blocked.

We have recently configured new patron blocks and have run across this issue.

Various processes in Evergreen will calculate penalties. Some examples are circulation transactions and fine generation. But retrieving a patron in the client or opac does not calculate penalties. This leads to the situation where a patron is allowed to perform a transaction that should be blocked. It also causes confusion for staff as one transaction is allowed, but subsequent transactions are blocked.

To reproduce this on a Concerto system:

Check out the following 2 items to patron 99999376864:

CONC40000628
CONC50000720

- In Items Out, select CONC50000720, and under Actions, choose Mark Lost
- Edit the stock penalty threshold for PATRON_EXCEEDS_LOST_COUNT, changing the stock threshold to 1
- Retrieve the patron and note there is no block even after refreshing.
- In Items Out, select CONC40000628, and under Actions, choose Renew
- Note that the renewal proceeds normally, but the patron now has the 'Patron exceeds max lost item threshold' block
- Select the other item and attempt to renew.

Note that the block now appropriately prevents renewal.

Changed in evergreen:
importance: Undecided → High
Revision history for this message
Michele Morgan (mmorgan) wrote :

Also adding links to related bugs:

bug 1944986
bug 1890822

Michele Morgan (mmorgan)
tags: added: circulation
Revision history for this message
Bill Erickson (berick) wrote :

Here's a patch that updates patron penalties and reloads the page:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1823225-patron-penalty-refresh

The new menu entry is under the "Other" menu labeled "Refresh Penalties"

Changed in evergreen:
assignee: nobody → Bill Erickson (berick)
milestone: none → 3.9.1
assignee: Bill Erickson (berick) → nobody
tags: added: pullrequest
Revision history for this message
John Amundson (jamundson) wrote :

Works for me! Thanks, Bill.

I have tested this code and consent to signing off on it with my name, John Amundson, and my email address, <email address hidden>.

tags: added: signedoff
Michele Morgan (mmorgan)
Changed in evergreen:
assignee: nobody → Michele Morgan (mmorgan)
Revision history for this message
Michele Morgan (mmorgan) wrote :

Pushed to master, rel_3_9 and rel_3_8.

Thanks Bill and John!

This restores missing functionality from the xul client. There was some discussion on IRC about the possibility of penalties being recalculated automatically on patron load or with a page refresh, rather than requiring the staff user to click an option. I'll open a new bug to continue that discussion.

Changed in evergreen:
status: Confirmed → Fix Committed
assignee: Michele Morgan (mmorgan) → nobody
Revision history for this message
Michele Morgan (mmorgan) wrote :

As promised, bug 1983621

Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.