HI Sean, et al,

 

This is extremely helpful to see all of these scenarios gamed out.

 

In terms of the fixed due date, at least at my institution, we only use fixed due dates for quarterly loans due on a given date (never hourly)—an item is assigned a fixed due date depending on the date it is loaned, but the loan is never prohibited. If we set a fixed due date to a date on which we are closed, that would be a pretty big mistake on our part. It would certainly be nice if the system could warn us (though it could happen in either order—a fixed due date could later be updated to closed or you could select a fixed due date that was already set as closed). But in practice, I think it’s not something we’re likely to screw up. Not sure how many others use fixed due dates.

 

I’ll take a closer look at the other scenarios tomorrow.

 

Best,

David

 

From: folio-ra@ole-lists.openlibraryfoundation.org [mailto:folio-ra@ole-lists.openlibraryfoundation.org] On Behalf Of Sean Thomas
Sent: Thursday, October 4, 2018 1:50 PM
To: folio-ra@ole-lists.openlibraryfoundation.org
Subject: Re: Skip closed dates in intervening period

 

Hi David,

 

Your examples are exactly why I want to game this out, using all of the desired features of the Loan Policy editor.

1) 14 day loan with 4 closed service point days (Desired outcome - give patron more time)

- Closed due date management=Move to the end of the next open day

 - Skip closed dates in intervening period=Y

 - Result: Due 4 days after service point reopens

 

2) 14 day loan with 4 closed service point days (Desired outcome - give patron reasonable, but more restrictive return time)

- Closed due date management=Move to the end of the next open day

- Skip closed dates in intervening period=N

 - Result: Due end of next day the service point reopens

 

3) 2 hour loan with checkout 1 hour before service point closes (Desired outcome - due before close same day)

 - Closed due date management=Move to the end of the previous open date

 - Skip closed dates in intervening period=N

 - Result: Due before close the same day as checkout? (NOTE: Need to confirm the system understands closed time vs. closed date)

 

4a) 2 hour loan with checkout 1 hour before service point closes (Desired outcome - due early the next day)

 - Closed due date management=Move to the beginning of the next open date

 - Skip closed dates in intervening period=N

 - Opening time offset = 1 hr

 - Result: Due one hour after service point reopens the next day

 

4b) 2 hour loan with checkout 1 hour before service point closes (Desired outcome - due early the next open day)

 - Closed due date management=Move to the beginning of the next open date

 - Skip closed dates in intervening period=Y

 - Opening time offset = 1 hr

 - Result: Due one hour after service point reopens the next open day

 

5) 2 hour loan with checkout 1 hour before service point closes (Desired outcome - prohibit checkout)

 - Closed due date management=Keep the current due date

 - Skip closed dates in intervening period=N

 - Result: I think this would still allow the checkout? - (NOTE: Need to confirm.  If so, it fails our desired outcome)

 

David, the only other mechanism for prohibiting the checkout (that I'm aware of) is the Fixed Due Date Schedule (due date limit), which wouldn't help in scenario 5, unless that date happens to be the end of a pre-defined period.

 

If any of the POs know if there are other configurations specific to checkout of hourly loans (either to prohibit checkout or to control hour/minute-level due dates/time), can you let me know? Otherwise, I'm wondering if we need another option:

 - Closed due date management=Prohibit checkout

 

Thanks again.

 

Sean


From: folio-ra@ole-lists.openlibraryfoundation.org <folio-ra@ole-lists.openlibraryfoundation.org> on behalf of David W. Bottorff <dbottorff@uchicago.edu>
Sent: Thursday, October 4, 2018 1:20:25 PM
To: folio-ra@ole-lists.openlibraryfoundation.org
Subject: RE: Skip closed dates in intervening period

 

CAUTION: External E-mail

 

With the basic scenario, I could see both the valid case described below (add the number of days the library is closed to the loan), as well as a simple logic of not making something due on a date that the Library is closed. For example, a 14 day loan with 4 closed service point days, the last of which is the date the item would normally be due. The item is instead assigned a due date of the following day-or 15 days, rather than 18 days.

 

Is this designed to solve both of these potential scenarios or only the latter? From my perspective, the latter is the more common—never assign a due date on a date when we’re closed.

 

I think there is another setting for determining when hourly loans are due—either the due time is truncated to the closing time on that date or it is assigned a specific time, such as 30 minutes after opening the next day. I would assume the skip date would come into play in a scenario where the default logic would make a 2 hour loan due 30 minutes the next day, but the next day is a closed day. It would then skip that date and make the item due 30 minutes after opening the first day the service point was open.

 

Does that make sense?

 

Best,

David

 

From: folio-ra@ole-lists.openlibraryfoundation.org [mailto:folio-ra@ole-lists.openlibraryfoundation.org] On Behalf Of Sean Thomas
Sent: Thursday, October 4, 2018 11:49 AM
To: folio-ra@ole-lists.openlibraryfoundation.org
Subject: Skip closed dates in intervening period

 

Hello again RA SMEs,

 

If I understand the role of this function, it's to remove from a due date calculation dates for which the library was closed.  So, for a long-term loan with Skip dates=Y (assuming no Fixed Due Date Limits are applied), the system should extend the calculation for due date based on the number of closed days for the service point.  For example:

 - 2 week loan with 4 closed Service Point days would mean that the item should be due in 2 weeks + 4 days, due at the end of the day unless otherwise configured, correct?

 

Assuming I've got the basics of this right, at what level of specificity is this feature meant to apply - i.e., should it be calculating to the hour/minute for due dates?  For example:

 - 2 hour loan checked out 1 hour before service point closes.  If Skip dates=Y, should the due date/time be 1 hour after the Service Point opens the following morning?

 - 2 hour loan checked out at 13 minutes before Service Point closes.  If Skip dates=Y, should the due date/time be 1hr:47min after the Service Point reopens?

 

I'm wanting to game out a number of scenarios that exercise the desired Loan Policy fields under different conditions and I'll be sharing those with the group to review.  Understanding the desired specificity of this feature will help to flesh those out.  Hopefully, we can find time in the schedule next week to walk through them and get these in front of the developers for implementation.

 

Thanks.

 

Sean

To unsubscribe from this list please go to http://archives.simplelists.com

To unsubscribe from this list please go to http://archives.simplelists.com

To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=HlPdNmMDsk02fL31CnSAJArYoxM5Hzwp