Date
Zoom
https://zoom.us/j/337279319 (pw: folio-lsp)
Attendees
Tatjana Rabeneck
Jenny Zerban
@Regina Frindt
Astrid Heilmaier
Discussion Items
| Time | Item | Who | Description | Goals/Info/notes |
|---|---|---|---|---|
| 2min | Administrivia |
| Note taker: Jana Freytag | |
| 60Min | German Reminder Fees | Holly Mistlebauer | Update and Requirements for the German reminder fees UXPROD-2015 | |
| 30Min | ACTUAL COST for lost items | Holly Mistlebauer | postponed |
Meeting Notes
Reminder fee (for more notes please see the presentation as well as chat and captions)
- When will the polling be and how (configurable or not)
- Naming the fee type 'reminder fee' is ok for Leipzig because the translation will differ
- What will be the trigger for sending reminder fee notice?
- We would need a daily routine to check for overdue books and then send a notice out to the patron
- Reminder fee charged is the trigger here (similar to aged to lost)
- set blocking (requests, loan, renewal) at every sequence
- automatic or manual block
- A possible additional scope that could be of interest for US libraries:
- Thomas Trutt (in Chat): What brooks said makes sense, adding the US request for "you will be fined XX" notifications to this ticket; extending the functionality.. What i realized was that the 'reminder fees' look like they would count against the patrons maxium fine/fee automated block, where the other ticket that may no be the desirable action. we would want patron to know they will be billed $$ because its overdue but not block them until the fee is added.
- Scope for development: maybe phasing out can be an option so that there is something for a nearer release
- Collections is not implemented yet - although transfer should be possible
- Mock-ups: