Date
Zoom
https://zoom.us/j/337279319 (pw: folio-lsp)
Attendees
@Pam Pfeiffer
Discussion Items
| Time | Item | Who | Description | Goals/Info/notes |
|---|---|---|---|---|
| 2min | Administrivia | National Holidays:
Germany
| ||
| 45Min | How are fee/fines implemented? | Andy Horbal and others |
|
Meeting Notes
Jana initiated a discussion about how early adaptor sites have implemented Fees and fines policies and workflows. Andy spoke about Cornell's implementation.
- Cornell's implementation included a drastic reduction in late fines except for items recalled by another patron or institution. This action was at least partially in response to the pandemic. They do schedule replacement costs for items that age to lost.
- Many Fee/Fine settings live in Settings > Circulation > Fee/fine. There are Overdue and Lost Item fee policies. Also, notice policies need to be ajusted to communicate fines to patrons.
- The Circ Rule invokes the Fee/Fine policies and the notice policies.
- There are also Fee/Fine settings in Settings > users > fee/fine. For example, F/F owners, waive reasons, payment methods and refund reasons.
- One major problem they encountered was overdue notices not sending correctly. The issue seems to have been a hidden permission needed by the operator doing the checkout to read notice policies.
- Travis described a workaround that involves creating a permission set with the hidden permission and then assigning the permission set as appropriate. Otherwise, there is a bug fix which should be available for Juniper soon.
- Also, issues related to multiple fee/fines being grouped on a single notice
- Finally, in regards to reports there are in-app reports (including under users - cash drawer reconciliation, financial transaction detail and refunds to process manually reports). Also, in Iris the LDP app.
- See also the follow up : https://folio-project.slack.com/archives/C3G05TF3R/p1636400382112700
- We will continue the discussion on Thursday.