Page Comparison

...

Notes

Holly encouraged the RA Sig members to attend WOLFcon on May 7-11, in Durham, NC, if at all possible. It will be an important opportunity to meet with other SIG reps and developers in working sessions to identify priorities and discuss issues.  Andrea and Holly will look into the possibility of virtual attendance at sessions.

Holly continued the discussion of the Fine Fee payment screen:

• The modal that appears when a payment is manually processed has a checkbox to notify the patron, and a free text comment box. The checkbox can be configured at the institution level to be checked as a default or not. There was some discussion around whether this could be configured at the library level. The work “user” next to the checkbox should be replaced by the word “patron” to avoid ambiguity about who is being notified.  How to view or edit the wording on the default notification? This issue is valid, but is out of scope for this portion of the work, and belongs in the task list of the notifications subgroup.
• There will be a confirmation message to the operator to show the payment/forgive transaction has processed
• Every action is associated with a date. When a charge is paid off, that action should also show a date. The balance column should show zero rather than a dash.
• Waiving fines: the reasons for waiving a fine can be added to a table, which will populate the pulldown list of reasons. The freetext Comment field to explain why the fine is being forgiven can be configured to be required or optional at the institution level.
• Transferring a fine (to Bursar or other system): this can be done through a system process or done manually. Q: how are libraries notified about bounced charges? Do we get an error report that needs to be acted upon manually? Holly anticipates we will be able to turn bounced charges back on (reactivate them). Some commentary that it would be nice to know when a patron actually paid a charge that had been sent to the Bursar. This feature would not be in V1.
• We also need a feature that will allow us to notate or otherwise transact a secondary action to send unpaid charges to a collections agency. Andrea noted that there are two kinds of Collections Agency: one that buys the debt from the library at some percent of dollar value; and the kind that does not buy the debt but does the work of dunning the patron to effect payment, and takes a percentage of the account as a fee. David noted that Chicago sends accounts in bulk at the patron level, not at the individual bill level. For this method, a tag would do. Andrea noted that the German libraries will have to weigh in on this to convey what their processing and reporting needs are.