2023-11-13 Resource Access Meeting Notes
Date
Recordings
Find all recordings here: https://recordings.openlibraryfoundation.org/folio/resource-access-sig/ (pw: folio-lsp)
Zoom
https://zoom.us/j/337279319 (pw: folio-lsp)
Attendees
Leah Anderson
Claire Hoag
Discussion Items:
Time | Item | Who | Description | Goals/Info/notes |
|---|---|---|---|---|
| 5Min | Administrivia | Cornelia Awenius | no meeting on Nov 23 Poppy release is postponed to December | Note taker: Elizabeth Chenette
|
| Reminder Fee Feature Presentation | Florian Ruckelshausen | See UXPROD-2015 and related issues |
Meeting Notes
Florian presented a Reminder Fees slide deck of the main settings and results in the bugfest environment.
Feature Items already complete for Poppy:
- new fee/fine type “reminder fee”
- Reminder process is an automated job that creates notices and fees
- Overdue policy includes reminder fee section
- Tokens for printed reminders (e.g., primary address)
- Patron account details
- Circulation log entries
Items moved to Quesnalia for development:
- Files for printed reminders
- Policy fine-tuning for closed days, renewals, grace periods (not yet implemented)
- Patron blocks because of reminders
Current example has the process scheduled to run once a day usually shortly past midnight where the number of reminders and the interval in which they will be sent is defined. The trigger for the first reminder is usually the overdue event, and after that the previous reminder is the triggering event for the next reminder. Currently reminder notices are email, but it should also be possible to generate print notices once that is set up for Quesnalia.
Question: If you have enough loans, scheduled notices may take half an hour or more to run, and we’ve found that trying to overlap batch notices and reminder notices may cause issues. If the creation of the fee is what’s triggering the event I want to make sure I understand how it’s working.
Answer: The notice as well as the fee is triggered together and it's currently just for testing purposes to do it 1 minute after midnight. The Okapi timer set for the reminder fees is distinct from all other notices and other settings where we are using a timer.
It's not a batch process. You get an email for each item. Not bundled in one mail.
Question: Will it be possible to set time per tenant?
Answer: Yes. Charlotte mentioned that perhaps an explanation could be included in the release notes for where to set this time so it's very clear if libraries want to run these at different times by tenant.
Question: It's only one book per paper, right?
Answer: Yes.
Question: But how do you access the printed versions?
Answer: There will be a module that makes a PDF version out of the out of these layouts. And there will be a list of the reminders that you can download from and print them.
Question: And has that module just been developed for reminder notices or is it available for notices more generally?
Answer: Charlotte says, “There is a feature we are working on for print notices and we are right now building a new Lean module which we are calling.
Mod batch print. Will have it get it through the TCR process for the technical council early next year.https://folio-org.atlassian.net/browse/UXPROD-4181
Charlotte shared her screen -- In settings, circulation under patron notices, there will be a new menu: patron notice print jobs. And here you can then click on that given nightly job which has been run, get your file and print it. In this mock up, the order of these files has the newest on top. It will be possible to click on the actions menu and then delete the selected jobs so that you can clean them up regularly
Bjorn expressed his appreciation for all the team’s work.
Question: Is it possible to not send a notice on a specific line so to have just notices on every second or third line?
Answer: Well currently it's not possible, but from the development perspective it should be no big deal to say you don't have to send the notice but at least you have to do something. And if you don't send out a notice, you at least have to create a fee.
Charlotte mentioned that they are gathering some of these tickets for future development and she encouraged others to add to that list. https://folio-org.atlassian.net/browse/UXPROD-4003
Cornelia asked for clarification: “When you said we postponed it, it means, It won't be done and you don't know who will be doing it?”
They are still working and discussing other things that have to be solved like the closed days things which are a little bit more complicated than anticipated and Florian doubts they can can realize it in the remaining time.
Charlotte shared info about the team working on this: 2 full back-end developers and one full stack developer, and then Mikhail Kuchlis doing the UI.
Question: In the original requirements, you have to do at least one action.
It was either a fee or notice or a block. To implement blocks will be finished?
Answer: Yes
Question: And will it be possible to download more than One print file?
Answer: So the current setup is that all the printed reminders for this job are in one file with several pages and then you open it. The only disadvantage is that you can only print them to one printer.If you want to distribute the reminder notices to other libraries where they have to be printed then you have to select which pages have to be printed there.
Question: What's the order of the reminders in the job?
Charlotte asked what order would you like? Because we have not generated the PDF yet. Is it by a patron name?
Answer: By patron.
In chat -- Notice sort order wish list:
1st patron group, 2nd patron name
Question: on the loan policy we have minutes, hours, days, weeks, and months and on the overdue fine policy we have all. At the moment, bugfest environment has minutes, days, and weeks. Why is that not consistent with the rest of the policies?
Answer: If you run the reminder job multiple times a day from the logic perspective, it would be possible. But, doubtful that libraries want to run reminder jobs multiple times a day so we decided that The day is the minimum limit for these intervals.
The suggestion was made to leave those options there in case people want to use them for short-term loans and to be consistent with all the other policies.
Another topic discussed was -- Known issue: CIRC-1970Hebis. Reminder fee. When 0 EURO then the dash in the billed column, cause Bulk payment of Fee/Fines to fails
It was mentioned that the issue is present not only in the bulk payment. It is also not working correctly when you want to do a single action on the reminder fees. Charlotte said they are looking into it and trying to determine if it is in the UI or a backend issue.Charlotte suspects the dash is causing this to fail.
It was mentioned that entries on the action table are not correct yet. Like reminder fee billed has Checked out as an action
A final comment that it would be nice if the first reminder had an amount of 0 that you could see that on the loan details, if the reminder sequence could be edited to show, even when there is no fee.