Details
-
New Feature
-
Status: Open (View Workflow)
-
P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
-
XL < 15 days
-
Small < 3 days
-
Jakub: I can only imagine this being implemented as a user set timezone since we have no notion of “subtenant”, I’d say it’s XL FE and S BE
-
-
R5
-
R5
-
R5
-
R1
-
R5
-
R5
-
R5
-
R5
-
R5
-
R5
-
R5
-
R5
-
R2
-
R5
Description
Per the WOLFcon discussion about single-tenant consortia implementations, we are not going to be able to get away with a single timezone per tenant. Multiple timezones are needed, not only for consortia, but also for institutions like Duke who have campuses in multiple timezones (Raleigh and China)
NOTE: So far all the institutions I have spoken with including Duke and the 5 Colleges, have wanted to have shared circulation meaning a single set of users, loan rules and policies and inventory across all campuses (in Duke's case) and institutions (for the 5 colleges). Loan rules and policies will differ depending upon the location, but that's already built in.
I need some help understanding what our options are for timezones. The need to specify a tenant-level timezone (UIORG-55) was actually surfaced by the developers as it was required for logical consistency when calculating due dates, overdue etc. Could the developers provide an option or two for this which I could run by the SMEs for acceptance? Maybe simply supporting user-based timezone for display in addition to tenant-level timezone for calculations would suffice?
TestRail: Results
Attachments
Issue Links
- relates to
-
UXPROD-293 Union Catalog support
-
- Open
-
-
UXPROD-872 Consortia/Multiple Libraries (Single Tenant)
-
- Draft
-
-
UXPROD-1434 Cross-tenant union catalog support
-
- Open
-
-
UXPROD-293 Union Catalog support
-
- Open
-
-
UXPROD-1434 Cross-tenant union catalog support
-
- Open
-