Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
EPAM-Veg Sprint 5, EPAM-Veg Sprint 7, EPAM-Veg Sprint 8, EPAM-Veg Sprint 9, EPAM-Veg Sprint 10, EPAM-Veg Sprint 11
-
3
-
Vega
Description
Purpose: As a library staff member who administers loan policies, I want to ensure that FOLIO can determine, at time of checkout, a revised due date timestamp (date+time) for a loan when the associated service point is scheduled to be closed at the system-determined due date originally defined by the associated loan policy. The system needs to calculate due dates and due times differently, depending upon the option chosen in the following scenarios, and in concert with other settings configured in the loan policy.
In general, while the system needs to affix both a due date and due time to a loan, the logic behind the due time is different depending upon whether the loan is:
- a) a short-term loan (i.e., 'Loan period' interval configured as X Hours or X Minutes) or
- b) a long-term loan (i.e., 'Loan period' interval configured as X Months, X Weeks or X Days)
Short-term loans ('a' above) need to ensure that, for the pre-calculated due date/time, the service point schedule is considered both on the specific day and at the specific time in determining whether the service point is open and, if not, how to apply the Closed Library Due Date Management configurations appropriately in determining due date and due time.
Long-term loans ('b' above) need only to ensure that the service point has any open hours for the pre-calculated due date and, if not, will apply the Closed Due Date Management configurations appropriately in determining due date. The Resource Access SIG has decided that the due time for long-term loans should be pre-set to 11:59:59PM* for the due date (for the purpose of calculating overdue statuses and applying fee/fine calculations).
Scenarios:
Long-term loans:
1. Scenario
• Given Loan Policy LP, which has:
- Loanable = Y
- Loan profile = Fixed OR Rolling
- Loan period = X Months|Weeks|Days (long-term) (Loan period applicable to ROLLING ONLY)
- Closed Library Due Date Management = Keep the current due date
• When new Loan L is associated with Loan Policy LP through loan rules AND
• When new Loan L is associated with Service Point ID SPID-1
• If SPID-1 is determined to be CLOSED for system-calculated due date
• Then the due date should remain unchanged from system calculated due date, and the due time should be 11:59:59PM*
2. Scenario
• Given Loan Policy LP, which has:
- Loanable = Y
- Loan profile = Fixed OR Rolling
- Loan period = X Months|Weeks|Days (long-term) (Loan period applicable to ROLLING ONLY)
- Closed Library Due Date Management = Move to the end of the previous open day
• When new Loan L is associated with Loan Policy LP through loan rules AND
• When new Loan L is associated with Service Point ID SPID-1
• If SPID-1 is determined to be CLOSED for system-calculated due date
• Then the due date timestamp should be changed to 11:59:59PM* for the closest previous Open=true day for SPID-1
3. Scenario
• Given Loan Policy LP, which has:
- Loanable = Y
- Loan profile = Fixed OR Rolling
- Loan period = X Months|Weeks|Days (long-term) (Loan period applicable to ROLLING ONLY)
- Closed Library Due Date Management = Move to the end of the next open day
• When new Loan L is associated with Loan Policy LP through loan rules AND
• When new Loan L is associated with Service Point ID SPID-1
• If SPID-1 is determined to be CLOSED for system-calculated due date
• Then the due date timestamp should be changed to 11:59:59PM* for the closest next Open=true day for SPID-1
*Note: Should be the equivalent of 11:59:59PM for the tenant's local timezone configuration once that functionality is available.
4. Scenario
• Given Loan Policy LP, which has:
- Loanable = Y
- Loan profile = Fixed OR Rolling
- Loan period = X Months|Weeks|Days (long-term) (Loan period applicable to ROLLING ONLY)
- Closed Library Due Date Management = Move to the end of the current day
• When new Loan L is associated with Loan Policy LP through loan rules AND
• When new Loan L is associated with Service Point ID SPID-1
• If SPID-1 is determined to be CLOSED for system-calculated due date (and timestamp as applicable for short-term loans)
• Then the due date timestamp should be changed to 11:59:59PM of the current day for SPID-1 (i.e., truncating the loan length)
Short-term loans:
5. Scenario
• Given Loan Policy LP, which has:
- Loanable = Y
- Loan profile = Rolling
- Loan period = X Hours|Minutes (short-term)
- Closed Library Due Date Management = Keep the current due date/time
• When new Loan L is associated with Loan Policy LP through loan rules AND
• When new Loan L is associated with Service Point ID SPID-1
• If SPID-1 is determined to be CLOSED for system-calculated due date and timestamp
• Then the due date timestamp should remain unchanged from system calculated due date timestamp
6. Scenario
• Given Loan Policy LP, which has:
- Loanable = Y
- Loan profile = Rolling
- Loan period = X Hours|Minutes (short-term)
- Closed Library Due Date Management = Move to the end of the current service point hours
• When new Loan L is associated with Loan Policy LP through loan rules AND
• When new Loan L is associated with Service Point ID SPID-1
• If SPID-1 is determined to be CLOSED for system-calculated due date and timestamp
• Then the due date timestamp should be changed to the endTime of the current service point for SPID-1 (i.e., truncating the loan length)
7. Scenario
• Given Loan Policy LP, which has:
- Loanable = Y
- Loan profile = Rolling
- Loan period = X Hours|Minutes (short-term)
- Closed Library Due Date Management = Move to the beginning of the next open service point hours
• When new Loan L is associated with Loan Policy LP through loan rules AND
• When new Loan L is associated with Service Point ID SPID-1
• If SPID-1 is determined to be CLOSED for system-calculated due date and timestamp
• Then the due date timestamp should be changed to the earliest SPID-1 startTime for the closest next Open=true available hours for SPID-1 (Note that the system needs to logically consider 'rollover' scenarios where the service point remains open for a continuity of hours that flow from one system date into the next - for example, a service point that remains open until 2AM; then reopens at 8AM. In such a scenario, the system should consider the '...beginning of the next open service point hours' to be 8AM. <NEED TO COME BACK TO THIS>
Additional Loan Policy Configurations which affect Due Date and Due Time Calculations:
1. Scenario (Opening Time Offset) UICIRC-64
• Given Loan Policy X, which has:
- Loanable = Y
- Loanable profile = Rolling
- Closed Library Due Date Management = Move to the beginning of the next open day
- Opening time offset = N (value > 0)
2. Scenario (Closed Library / Fixed due date - Conflict) UICHKOUT-455
• Given any scenarios wherein Closed Library Due Date Management configurations will lead to a due date timestamp that falls outside of the range of a Fixed due date schedule, then the loan period should be truncated to the closing time for the service point on the endDate of the appropriate Fixed Due Date Schedule
(NOTE: UICHKOUT-452 'Loan Policy Editor - Context-based behavior for Closed Library Due Date Management' documents additions/modifications that need to be made to the selection lists.
TestRail: Results
Attachments
Issue Links
- blocks
-
CIRC-158 Closed Library Due Date + Fixed Due Date
-
- Closed
-
-
CIRC-160 Loan Policy: support "Opening Time Offset"
-
- Closed
-
- is blocked by
-
CIRC-159 Implement Closed Library Due Date Management support during check out due date calculations
-
- Closed
-
-
UICIRC-107 Loan Policy Editor - Context-based behavior for Closed Library Due Date Management
-
- Closed
-
- relates to
-
CIRC-186 Implement Closed Library Due Date Management support in due date calculations - For Renewals
-
- Closed
-
-
CIRC-218 Due date-time for long-term loans
-
- Closed
-
-
FOLIO-1672 Consider using non-UTC timezone in reference environments
-
- Closed
-
-
MODCAL-22 SPIKE: Familiarization with the Calendar-API for Loan Policy stories
-
- Closed
-
-
MODCAL-33 Ensure Closed Library Due Date Management Works Across Calendar Periods
-
- Closed
-
-
MODCAL-34 Ensure Closed Library Due Date Management Respects Exceptional Closed Periods
-
- Closed
-
-
UICHKOUT-455 Closed Library Due Date + Fixed Due Date - Conflict
-
- Closed
-
-
UICHKOUT-456 Remove - 'Skip closed hours...' from Loan Policy Editor
-
- Closed
-
-
UICIRC-64 Loan Policy: Add "Opening Time Offset"
-
- Closed
-
-
UICIRC-107 Loan Policy Editor - Context-based behavior for Closed Library Due Date Management
-
- Closed
-
-
UXPROD-1385 Loan Policy: Impact of CLOSED LIBRARY DUE DATE Settings on Loans
-
- Closed
-