[Evergreen-general] Hourly / End of the day checkouts, in building use checkouts

Frasur, Ruth RFrasur at library.IN.gov
Tue Oct 26 13:34:10 EDT 2021


Would it possibly be easier to use the booking module for this?

Ruth Frasur (she/her)
Evergreen Development and Support Administrator
Indiana State Library
140 N. Senate Ave.
Indianapolis, IN 46204
(317) 232-3691

From: Evergreen-general <evergreen-general-bounces at list.evergreen-ils.org> On Behalf Of Josh Stompro via Evergreen-general
Sent: Tuesday, October 26, 2021 1:32 PM
To: Evergreen Discussion Group <evergreen-general at list.evergreen-ils.org>
Subject: [Evergreen-general] Hourly / End of the day checkouts, in building use checkouts

**** This is an EXTERNAL email. Exercise caution. DO NOT open attachments or click links from unknown senders or unexpected email. ****
  Hello, we are looking at circulating laptops for in building use only, and are looking into options for how to handle the checkout timing.

We would like to check out each item until the end of the day.  So if a branch closes at 9pm, then we would always set the due date to 9pm for any checkouts that day.

We want to be able to immediately bill the next morning, or even that night.  We are not currently thinking to charge fines, so we don't need to worry about those right now, or all the current issues with hourly fines.

We were thinking of having a duration rule that specifies 12 hours, since that covers the longest time period that our locations have open.  But that causes checkouts in the afternoon to be pushed to the next day, with potentially extra days added if the next day is a closed day for that branch.

So maybe we should use a shorter time period for the duration rule, to avoid that.  But then staff will see a due time a few hours in the future, which may cause confusion.  Ideally the initial checkout due date would be set correctly, so the receipt could show the exact time the customer should return the item.  Or maybe we should just not show the exact time for the due date to keep customers from reading too much into it.

I was looking at how the duration rules work... and I wonder if it would work to create one, or several special duration rule strings.  And then teach create_due_date in Circulate.pm how to handle those?

"eod" = end of current day/end of current open period.  (For when the split hours feature comes in).
"bond" = beginning of next open day
"eond" = end of next open day

Otherwise maybe I could change the duration rule over the course of the day, so subsequent checkouts don't get pushed to the next day at least... so at 7pm change the duration rule to be "2 hours" instead of 12... and do that every couple hours over the course of the day.  Set the interval to now() - 9pm every time the script is run....  normal=(now()::date + '21 hours'::interval) - now().

We have also thought of just updating the due dates for any non returned items at 9:01pm each night, so at least the billing would happen correctly the next morning.

Does anyone have any suggestions for how to make this work?

[Company logo]
Josh Stompro
IT Director
stomproj at gsuite.larl.org<mailto:stomproj at gsuite.larl.org>
218-233-3757 ext. 139 | Mobile: 218-790-2110

Lake Agassiz Regional Library | www.larl.org<https://protect2.fireeye.com/v1/url?k=fc4fc02f-a3d4f8d9-fc4b892f-8681010e5614-d519383656203cde&q=1&e=bb7cc6d7-9340-4d75-8d71-d1a49e725806&u=http%3A%2F%2Fwww.larl.org%2F>
118 5th ST S
Moorhead MN 56560
Celebrating 60 Years of Service in 2021!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20211026/1f2680c9/attachment-0001.html>

More information about the Evergreen-general mailing list