Fees/Fines (UXPROD-792)

[UXPROD-2801] Future Fees/Fines: Refactor manual patron blocks Created: 04/Nov/20  Updated: 09/Jan/23

Status: Draft
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: None
Parent: Fees/Fines

Type: New Feature Priority: TBD
Reporter: Holly Mistlebauer Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: NFR, Unassigned-from-Holly, feesfines, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UIU-1942 Manual patron block expiration date c... Closed
Epic Link: Fees/Fines
Development Team: Vega
PO Rank: 0
Rank: MO State (MVP June 2020): R2

 Description   

While working on UIU-1942 Closed (now UIU-1942 Closed ) the Vega team discovered that much of the manual patron block business logic taking place in the front-end should be in the back-end (as was discovered with the fee/fine 'actions' earlier).

Here is the comment left by the dev on UIU-1942 Closed (now UIU-1942 Closed )...
Expired manual blocks are being cleared by frontend (not backend!). And it only happens when you input blocked patron's barcode on checkout screen or request creation screen. They are not cleared during renewal. Until you do that, the expired block will live and be visible as banner and icon on user details page as described in UIU-1943 Closed . We can follow the same approach and let frontend clear (or just hide) expired blocks the moment User Details page is being opened, but ideally this logic should be moved to backend. And as you already know by our recent mod-feesfines refactoring, this process is not quick and easy.



 Comments   
Comment by Stephanie Buck [ 09/Jan/23 ]

Alexander Kurash, is this issue still relevant/is this still true of patron blocks?

Generated at Fri Feb 09 00:26:57 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.