- Article Type: General
- Product: Voyager
- Product Version: 7.1.1
Bug Report Form for Issue 16384-9649
Release(s) replicated in: 7.1.1, 7.2.0
Server Platform(s) affected: Solaris/all
PC O/S (if this is PC specific): n/a
Browser type & version (if WebVoyage): n/a
Loss of functionality from (previous version, if applicable): 7.1.0
Expected Results: Loan periods should be calculated accurately regardless of how extended hours/overnight loans are configured in the calendar in use for the transaction.
Actual Results: When a calendar is set up to be open past midnight, uses overnight loans, and and specify an In Effect date that falls on or after midnight, any minutely/hourly loan checked out that day will be given a due time of the overnight loan due time the following day.
Workflow Implications: If your library policy dictates that hourly/minutely loans charged on or after midnight should be due the next day at X time, any hourly/minutely loans you check out that day will have an unreliable due date.
In SysAdmin, create a new calendar with Sun-Sat opening at 7:00am, closing at 2am, a Due time of 8:00am, and an In Effect time of 1am.
In the policy definition of record for the transaction, move in your new calendar (you may have to move out the original calendar first, if the dates overlap).
In the policy definition of record for the transaction, make sure that Apply Fixed Due Time is checked on the Policies tab.
In the matrix tab, set up a matrix that has an hourly or minutely loan (say, 2 hours or 240 minutes).
In Circulation, create a patron using the patron group from the above matrix, and an item using the item type in the above matrix.
At a time that is well before the 1am In Effect time, charge your item out to your patron.
--> You’ll see that instead of setting a due time of 2 hours from now, you’re given a due time of 8am tomorrow.
Other information: maybe related to -6211, 16927?
- Article last edited: 3/19/2015