Internationalization and Localization (UXPROD-779)

[UXPROD-592] Multiple Language and Localization settings per institution (was Multiple timezones per institution) Created: 18/May/18  Updated: 09/Dec/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Internationalization and Localization

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: i18n, multiple_libraries_single_tenant, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-293 Union Catalog support Open
relates to UXPROD-1434 Cross-tenant union catalog support Open
relates to UXPROD-872 Consortia/Multiple Libraries (Single ... Draft
relates to UXPROD-293 Union Catalog support Open
relates to UXPROD-1434 Cross-tenant union catalog support Open
Epic Link: Internationalization and Localization
Front End Estimate: XL < 15 days
Front End Estimator: Jakub Skoczen
Back End Estimate: Small < 3 days
Back End Estimator: Jakub Skoczen
Estimation Notes and Assumptions: 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
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R5
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R5
Rank: Hungary (MVP End 2020): R5
Rank: Lehigh (MVP Summer 2020): R5
Rank: Leipzig (Full TBD): R5
Rank: Leipzig (ERM Aut 2019): R5
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): 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 Closed ) 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?



 Comments   
Comment by Kristin Martin [ 20/Jun/18 ]

While Chicago individually does not require this feature, will it be needed to support resource sharing/cooperative collections within consortia (many of whom will not be using FOLIO)? If so, then we would want to see this implemented within a year after go-live.

Comment by Holly Mistlebauer [ 09/May/19 ]

With the addition of the Primary Currency setting in Q2 2019, we have the need to have more than just the Time Zone able to have multiple settings.
As of Q2 2019 the "Language and localization" settings will include...

Locale (for language display, date format, number format, etc.)
Time zone (time zone used when showing date time information)
Primary currency (which just determines the currency symbol)

Although this issue does not mention the Locale setting, it matters as well due to its control over how numbers are displayed. Locale determines if a dot or a comma appear between the number and its decimals. It also determine what the grouping character will be (for thousands). For example, in the US we use a grouping character of a comma and a decimal character of a dot, like this: 9,999,999.99. In Germany they use a grouping character of a space and a decimal character of a comma, like this: 9 999 999,99

So if you have the Locale set to English - United States (because the institution in German speaks English) and Primary Currency set to Euro, you are going to get some strange results: 9,999,999.99 € When you want: 9 999 999,99 €
(In this case we would probably need to invent a Locale called English - Europe or some such think.)

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