Internationalization and Localization (UXPROD-779)

[UXPROD-883] Localization and language should be separate settings allowing for [***ish] speaking users in FOLIO while keeping the locale settings. Created: 21/Feb/18  Updated: 16/Sep/20

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

Type: New Feature Priority: P3
Reporter: Theodor Tolstoy (One-Group.se) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue links:
Relates
relates to UXPROD-510 User-level locale and time zone setting Open
Epic Link: Internationalization and Localization
Front End Estimate: Medium < 5 days
Front End Estimator: Jakub Skoczen
Back End Estimate: Small < 3 days
Back End Estimator: Jakub Skoczen
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R5
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R5
Rank: Leipzig (Full TBD): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

Overview:
This was collected from the first impressions received showcasing FOLIO for the first time to Chalmers.

Setting locale is currently not doing a lot beside of how date format is handled and which translation is being used. However, looking forward you would expect that locale settings would have deeper impact on how the systems behaves.

Given the fact that library staff might not have the given locale as their first language there is a need for separating locale and user language.

From my meeting with Chalmers, it was also surfaced that it might simplify cooperation with the FOLIO community if we could keep English at the primary language of the UI while at the same time being able to explore the different localization aspects of FOLIO.



 Comments   
Comment by Cate Boerema (Inactive) [ 22/Feb/18 ]

Thanks Theodor Tolstoy (One-Group.se). This is actually different than what I expected you to file. I thought Chalmers was asking that you be able to set the date date format separately from your display language which is actually a request we've heard from others (but seems like a relatively low priority change to me).

But now that I read this story, I see you are actually asking for the ability for users to select a display language that differs from the default for the institution. This is not in the plans for v1. For v1, FOLIO localization settings are at the tenant level. Each tenant can select one locale, which drives language and date/time format (and probably number format down the road) for anyone using FOLIO for that tenant. We recognize this will be an issue for many institutions and have plans to support user-level localization post-v1.

given that some countries have multiple official languages that must be treated equal, there is a need for separating locale and user language.

I don't follow this logic. There is not a single locale per country. Countries with multiple official languages have multiple locales. For example, Switzerland has: de_CH (german), fr_CH (french) and it_CH (italian)

Comment by Theodor Tolstoy (One-Group.se) [ 22/Feb/18 ]

I think you are right with regards to locale. I was more thinking along the lines of other settings that depend on nation more than locale and language.

Comment by Cate Boerema (Inactive) [ 14/Jun/18 ]

Hi Theodor Tolstoy (One-Group.se). I am trying to decide what to do with this story. The "user story" portion of the description makes this sound like a duplicate of UXPROD-510 Open (which is about letting a user select a different language (actually, locale) from the default for the tenant. But the summary makes it sound like you want to separate out the language from the formatting settings for date/time, number etc. Is it one or the other or both? Thanks

Comment by Theodor Tolstoy (One-Group.se) [ 14/Jun/18 ]

its the latter Cate Boerema. I might be wrong, but i keep thinking that going forward there will be more and more ibrary-specific things (like filing rules) tied to the Locale setting which would lead to the user interface becoming too different between locales.

Comment by Cate Boerema (Inactive) [ 14/Jun/18 ]

Okidoke, I get it and, I hope it's okay, but I removed the User Story in the description because I think it confused things. I'll get this estimated. Cheers.

Comment by Theodor Tolstoy (One-Group.se) [ 14/Jun/18 ]

Thank you for considering it!

Comment by Cate Boerema (Inactive) [ 18/Jun/18 ]

Theodor Tolstoy (One-Group.se), I discussed this briefly with Jakub Skoczen today and he suggested we might let the selected locale drive some default format display settings that you could then override. To start out with, this would all be at the tenant level, but we do have other features in the backlog to make this settable at the user level as well.

What do you think about this approach? Here's a rough mockup.

Generated at Thu Feb 08 23:10:39 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.