Page Comparison

...

...

• 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 Brooks said makes sense, adding the US request for "you will be fined XX" notifications to this ticket; extending the functionality.. What i I realized was that the 'reminder fees' look like they would count against the patrons maxium maximum 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
• Desired feature is for column in fee/fine details page as to whether reminder fee is e.g. the 1st, 2nd, or 3rd reminder fee.
• Collections is not implemented yet - although transfer should be possibleMock-ups:
• Notices need to be speced
• Next steps:
  • Holly is going to add these requirements and come back to us
  • the german libraries are going to share the presentation and are going to talk about this in their regional meeting