Fees/Fines
(UXPROD-792)
|
|
| 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: | Unassigned-from-Holly, feesfines, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Potential Workaround: | Holly: This was always viewed as a future feature. No workaround is needed. | ||||||||
| Epic Link: | Fees/Fines | ||||||||
| Front End Estimate: | Large < 10 days | ||||||||
| Front End Estimator: | Holly Mistlebauer | ||||||||
| Front-End Confidence factor: | Low | ||||||||
| Back End Estimate: | XL < 15 days | ||||||||
| Back End Estimator: | Holly Mistlebauer | ||||||||
| Estimation Notes and Assumptions: | Will need a sharable component for calculating pending fees/fines on the fly. | ||||||||
| Development Team: | Vega | ||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 2 | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: BNCF (MVP Feb 2020): | R1 | ||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||
| Rank: Grand Valley (Full Sum 2021): | R4 | ||||||||
| Rank: hbz (TBD): | R4 | ||||||||
| Rank: Hungary (MVP End 2020): | R4 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||
| Rank: Leipzig (ERM Aut 2019): | R5 | ||||||||
| Rank: Mainz (Full TBD): | R2 | ||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||
| Description |
|
Calculate pending fees/fines that are not included in the outstanding balance but are displayed within User Details, Checkout Borrower , Loans History and Details, and Fee/Fine History and Details. Attached zipped folder Pending.zip contains mock-ups and in-progress requirements for this feature. |
| Comments |
| Comment by Lisa Sjögren [ 20/Jun/18 ] |
|
Hi! We're in the process of filling in the Feature Prioritization Spreadsheet here at Chalmers, and are not sure that we understand what this feature does. I think what confuses us is the concept of having a fee/fine that is not included in the outstanding balance. Does "pending" in this case indicate some kind of state where the fee/fine is not yet "definitive", i.e. might under certain circumstances not become a "real" fee/fine after all? Thank you! Best regards, |
| Comment by Holly Mistlebauer [ 20/Jun/18 ] |
|
Lisa Sjögren, that is correct. The fee/fine is not real yet. Most likely the item is overdue but the loan policy provides for a "grace period." For example, a book may have a one-week grace period. We are letting the patron know that the book is overdue when the due date is by-passed, and start calculating the overdue fines that will be owed if the book is not returned during the one-week grace period. Everyday the pending fee/fine will increase. If the book is returned before the grace period ends, the pending fee/fine goes away. If not, it will continue to grow until the book is returned when it will become a "real" fee/fine. Most libraries view this as a lower priority. |
| Comment by Lisa Sjögren [ 21/Jun/18 ] |
|
Thank you for the very clear explanation of of pending fines and grace period, Holly Mistlebauer! Best, |