Fees/Fines (UXPROD-792)

[UXPROD-2572] Loan: Aged to Lost using ACTUAL COST Created: 09/Jul/20  Updated: 14/Aug/23  Resolved: 06/Dec/21

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: Duplicate Votes: 0
Labels: cap-mvp, feesfines, needs-testrail, po-mvp, q1-2020-at-risk, q4-2019-at-risk, q4-2019-spillover, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Zip Archive Lost Item Processing.zip     JPEG File Lost-Item-Policy.JPG     PNG File screenshot-1.png    
Issue links:
Blocks
blocks UXPROD-846 Fees/Fines in-app report: Lost items ... Closed
is blocked by UXPROD-87 Loan: Aged to Lost using SET COST Closed
Defines
defines UXPROD-3079 Implement actual cost for lost items In Progress
is defined by CIRC-892 Aged to lost: Renewal (effect on lost... Closed
is defined by CIRC-893 Aged to lost: Check in (effect on fee... Closed
Gantt End to End
has to be finished together with UXPROD-846 Fees/Fines in-app report: Lost items ... Closed
Relates
relates to UXPROD-2391 Loan: (BE) Declared Lost/Aged to Lost... Closed
relates to UXPROD-3564 Loan: (FE) Declared Lost/Aged to Lost... Closed
relates to UXPROD-3565 Loan: (BE) Lost Item Fees processing ... Closed
relates to UXPROD-3377 Loan: (FE) Lost Item Fees processing ... Closed
relates to UXPROD-3744 Loan: (FE) Lost Item Fees processing ... Closed
relates to UXPROD-3554 Loan: Lost Item Fees processing page ... In Refinement
relates to UXPROD-780 Implement e-2-e automation of test ca... Closed
Epic Link: Fees/Fines
Front End Estimator: Zak Burke
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: New back end developers are still getting used to working in the team (and FOLIO) and are all unfamiliar with this area.

zburke: I don't believe there is any front-end work defined here.
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 71
PO Rank: 95
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: MO State (MVP June 2020): R1
Rank: U of AL (MVP Oct 2020): R4

 Description   
July 9, 2020 Change

UXPROD-87 Closed (Loan: Aged to Lost) was split into:

Aging items to lost is a process many larger libraries do in order to encourage patrons to return their overdue items. After an item is overdue a specified period of time (see 'Item aged to lost after <number> <interval>' in attached Lost Item Fee Policy), the library will age it to lost by changing the item Item Status to 'Aged to lost' and billing the patron lost item fee(s) per the Lost Item Fee Policy. When a patron receives a bill for a 'lost' item that is most likely just 6 weeks overdue, they usually return the item immediately.

Some libraries wait a week or so between notifying the patron of the upcoming charge for the aged to lost item and actually billing the patron, giving the patron time to return the very overdue item before a bill is cut. This is determined in the Lost Item Fee Policy setting 'Patron billed after aged to lost <number> <interval>'.

The patron may also be charged a lost item processing fee depending on the Lost Item Fee Policy setting 'Charge lost item process fee if item aged to lost by system?'

There are many user stories defining this features because after an item has a status of 'Aged to lost' the system needs to block checkout, renewal and all requests, take special action at check-in, etc.

The 'is defined by" user stories with a Status of DRAFT are user stories Holly copied over from 'Declared lost" but has not updated for 'Aged to lost' yet. The other users stories, which are directly related to aging an item to lost, are ready for development.

Attached zipped folder Lost Item Processing.zip contains mock-ups and in-progress requirements for this feature.



 Comments   
Comment by Holly Mistlebauer [ 06/Dec/21 ]

The user stories associated with this feature have all been moved to UXPROD-2391 Closed ...

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