Fees/Fines (UXPROD-792)

[UXPROD-3668] Phase 2 of refund fees/fines Created: 16/May/22  Updated: 29/Sep/22

Status: Draft
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: None
Parent: Fees/Fines

Type: Umbrella Priority: TBD
Reporter: Holly Mistlebauer Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: feesfines, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-1879 Refund enhancement: Implement issue c... Open
relates to UXPROD-3645 Provide option to waive or cancel a f... Open
relates to UXPROD-1876 Refund enhancement: Implement issue c... Draft
relates to UXPROD-3137 Future Fees/Fines: Allow "No fees/fin... Draft
Epic Link: Fees/Fines
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1
RCA Group: TBD

 Description   

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

  1. 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.)
  2. 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.
  3. The sub-group will continue meeting to hash out how they want refunds to work.
  4. 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

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