|
Overview
The current implementation of refunding fees/fines is a thin thread, only intended to be in place until refunds could be fully implemented. Now that we have had many sites implement, it has become clear that the thin thread solution is not sustainable. The main issue has to do with the refund being reported on the Fee/Fine Details page as having taken place, when in fact it has not. The refund will not take place until the library processes the "Refunds to process manually report". Another issue has to do with how credits are being shown. We are not using negative numbers but should be. What is displayed on the Fee/Fine Details page is confusing to people at the desk who need to interact with patrons. (The current refund process is documented here.)
Plan
- Jana (Convener to the RA SIG) is putting together a sub-group of people who actually work on fee/fine refunds. (She also set up a Slack channel: ra-refund-subgroup.)
- At the first meeting, Duke will demo Aleph refunding and Chicago will demo OLE refunding. By looking at other systems that do refunds well, we can determine what changes are needed to FOLIO's refund process.
- The sub-group will continue meeting to hash out how they want refunds to work.
- Hopefully the end result will be a final design of how refunds should work, with the steps we need to take to get there.
Related Features
- UXPROD-3645: Provide option to cancel a fee/fine at the time a manual refund is entered
- UXPROD-1876: Use fee/fine refund to pay other fees/fines
- UXPROD-1879: Notify Bursar (and other transfer accounts) of refunded fees/fines
- UXPROD-3137: Allow "No fees/fines shall be refunded if a lost item is returned more than" to be determined by a fixed date
|