Patron Notices (UXPROD-18)

[UXPROD-3574] Remove send errors in the circ, that are due to anonymisation Created: 22/Feb/22  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Patron Notices

Type: New Feature Priority: P4
Reporter: julie.bickle Assignee: julie.bickle
Resolution: Unresolved Votes: 0
Labels: notice_error, patron_notice
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2022-02-22-17-46-06-271.png    
Issue links:
Defines
is defined by UXPROD-2385 Improved logging related to patron no... Closed
Epic Link: Patron Notices
Development Team: Volaris
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2
Rank: Mainz (Full TBD): R2

 Description   

Current situation or problem:

Why is this message is appearing (a lot) in the circ log?

In short: The anonymisation process removed the userID from the loan (the "null"). This "error" is noticed by FOLIO and posted to the circ log... BEFORE FOLIO checks other criteria, e.g. is the loan closed? (THEN no need to send a notice --> the scheduled notice is deleted).
This is assuming that no other changes to the loan or generally to the relevant data sets is happening via API.

Essentially, this case was not considered when doing the work for Improved logging related to patron notice processing ( UXPROD-2385 Closed ). 

Why are you able to see the patron barcode for that log entry? Because this log entry is not related to a loan, but to a scheduled notice. The barcode is being pulled in via the userID stored in the scheduled notice.

In scope

Out of scope

Use case(s)

Proposed solution/stories

After downloading the loan data, then interrupt the download of the rest of the data. Then, if the loan = closed, then go straight to the Evaluate conditions. !! Would this work for bundled notices?

Is it true, that we do not need to send notices for closed loans? What about f/f aged to lost adjusted?

Links to additional info

Questions


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