Patron Notices
(UXPROD-18)
|
|
| 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: |
|
||||||||
| Issue links: |
|
||||||||
| 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). Essentially, this case was not considered when doing the work for Improved logging related to patron notice processing (
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 |