Circ Rules and Loan Policies (UXPROD-789)

[UXPROD-1439] Tenant-selected timezone compliance for circulation-related modules Created: 18/Jan/19  Updated: 16/Sep/20  Resolved: 21/Mar/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: Circ Rules and Loan Policies

Type: New Feature Priority: P2
Reporter: sthomas (Inactive) Assignee: sthomas (Inactive)
Resolution: Done Votes: 0
Labels: loan_rules_policies
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to CIRC-238 Respect tenant-selected timezone for ... Closed
relates to UICAL-55 Apply UTC time zone for date/time con... Closed
relates to MODCAL-29 Change GET /calculateopening API endp... Closed
relates to MODCAL-30 Change GET /calendar/periods endpoint... Closed
relates to UICIRC-178 SPIKE - Tenant-selected timezone comp... Closed
relates to MODCAL-32 Change GET, PUT and DELETE /calendar/... Closed
Epic Link: Circ Rules and Loan Policies
Front End Estimate: XL < 15 days
Back End Estimate: XL < 15 days
Estimation Notes and Assumptions: Front-end (ui-calendar) support time zone required
Development Team: Vega
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: 5Colleges (Full Jul 2021): R5
Rank: Lehigh (MVP Summer 2020): R4
Rank: MO State (MVP June 2020): R1

 Description   

Description
All due date calculations need to respect the timezone chosen for the tenant. While UIORG-55 Closed established the ability to set a time zone for the tenant, dependent back end modules that are used in the calculation of specific date+time operations for circulation-related activities do not currently perform calculations and return accurately translated results in the tenant-selected form.

Situation

  • Backend modules are not aware of the chosen timezone and so do not respect it in calculations

Desired Outcome

  • All calculations involving date and time should respect the chosen timezone

Assumptions

  • Stripes provides mechanisms for creating date and time representations that respect the chosen time zone
  • Stripes provides mechanism for converting date and time representations between chosen time zone and UTC
  • UI modules use these mechanisms consistently
  • The UI defaults the timezone internally (to the UI) to UTC
  • The reference environments don't define a chosen timezone


 Comments   
Comment by sthomas (Inactive) [ 18/Jan/19 ]

Cate Boerema Here's the feature for the tenant-defined timezone work.

Comment by Khalilah Gambrell [ 04/Feb/19 ]

Goals

  • Support check-in/check-out, renewal and renewal overrides to support time zone calculation to ensure proper closed due dates.
  • Have certain loans respect closed due date loans
  • impacted module
    • mod-calendar
    • mod-circulation
    • No work at storage level
Comment by Julian Ladisch [ 18/Feb/19 ]

There may be a clock adjusting for daylight savings.

Usually it works this way:

If the configured loan period is one day, then 9:00 + 1 day is 9:00, but the period may be 23, 24 or 25 hours long. (Reference: https://docs.oracle.com/javase/tutorial/datetime/iso/period.html )
If the configured loan period is 24 hours, then 9:00 + 24 hours can be 8:00, 9:00 or 10:00, but the period is always 24 hours long.

Comment by Cate Boerema (Inactive) [ 10/Mar/19 ]

sthomas can this be closed?

Generated at Fri Feb 09 00:15:36 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.