|
Current situation or problem:
New work on Fee/fines and item states as claimed returned etc. were not present when first iteration of inventory's check for item dependency was implemented 2 years ago. Right now, patrons with appropriate permissions can delete item records in Inventory, with a dependency checks on certain transactions (see
UIIN-534
Closed
). This feature is about covering the implementation of dependency checks for fee/fines, loan statuses etc.
Usecase:
An item may have an associated unpaid or unresolved fee/fine even if the item is available and/or does not have an active loan. This occurs with overdue or overdue recall fines, where items can circulate to multiple users and accrue fines without ever becoming lost. So the dependency check must actively check fine records, not just item statuses like 'declared lost' or 'aged to lost'.
In scope
- Do not allow item deletion if an account record, tied to the item, exists with an "open" status - this indicates that money is still owed to the library
- Do not allow item deletion if
Out of scope
Use case(s)
Proposed solution/stories
Links to additional info
Questions
- Do libraries want a warning even if all of the associated accounts are closed? It doesn't appear to warn for closed requests or closed loans, though this use case is arguably different because money is involved.
- Are there libraries that would never want to delete an item if it has any fine history? That doesn't seem tenable, but they may be out there.
- Are there libraries who would want to be able to configure a time check? E.g., don't allow deletion, even if the fine is closed, unless the fine is more than ___ years old? Or is the information still retained on the fine record enough to account for any record retention needs?
|