Fees/Fines
(UXPROD-792)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | Fees/Fines |
| Affects versions: | None |
| Fix versions: | None | Parent: | Fees/Fines |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Holly Mistlebauer | Assignee: | Holly Mistlebauer |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | feesfines, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue links: |
|
||||||||||||
| Epic Link: | Fees/Fines | ||||||||||||
| PO Rank: | 0 | ||||||||||||
| Description |
|
While addressing
This "discovery" led Holly to test the various Loan History (aka loan anonymization) settings to see what happens with the fee/fine records. She ran 3 different tests... 1) Anonymize closed loans 2 hours after loan is closed, with no special treatment for closed loans associated with fee/fines... Of the tests above, 2 and 3 passed (you can see the results on tabs "Settings 2" and "Settings3" of the attached spreadsheet Loan-anonymization-testing.xlsx). Test 1 above did not fully pass (you can see the results on tab "Settings 1" of the attached spreadsheet Loan-anonymization-testing.xlsx). The issue has to do with aged to lost and declared lost loans that are fully paid. In this case, the loans were not anonymized. Given loans with fees/fines are not meant to be treated differently with this Loan History setting, they should have been anonymized. Holly will confirm this with the RA SIG. |
| Comments |
| Comment by Holly Mistlebauer [ 23/May/22 ] |
|
Holly presented this to the RA SIG on May 23, 2022. (The slide deck is available at https://docs.google.com/presentation/d/1Osu5z9i9B04lJ0WF8X7hOVWRvzsJDjcX5JJ6q9c8jDs/edit?usp=sharing.) It is known that the fee/fine specific criteria for loan anonymization do not work right now. Holly will close this feature and re-open
|