Page Comparison

https://docs.google.com/document/d/104vSgLvfi5zyQk3PT0S3z-9KnO-9pAwdxHne_CnLHTQ/edit#

For PC review, new module that corrects security defect in mod-config with a new module called mod-settings
Mod-cofig stores permissions for apps, ex: LDP stores connection details for databases, Users stores list of users who are special and cannot be edited (admins)
Security flaw - only 2 permissions read/write, applies to all modules, if you can write to one, you can write to them all

TC discussed TCR-24 yesterday and Ingolf and Jeremy said they would do the review,

Initiative in TC to fix with a distributed config, but a lot of duplication of effort and potential confusion due to overlap
Easier way to fix the security flaw is to implement a separate module rather than adjust existing module(s) and use a more modern framework
Mod Settings, deprecate mod config eventually
Setting consists of an identifier, scope name of module or more specific, read some write others, sep scope
Admins can change other users settings and their own
3 permissions for each scope -- read, write, delete, much smaller module

For other dev teams to use this – there will be a migration guide to move off of mod-config onto mod-settings, but doing that is not required. Define permissions, change paths, handle new error states that didn’t exist before.

PC members will look at the document and Kristen posted to the PC channel and Mike and Charlotte can answer questions there. Take a formal vote next week on whether to include in the Orchid release.

Language challenges when English is not the main language, only 20% of world speaks English
No system can make it in the Middle East if it only provides one language
Kware vision --  trying to create a Language agnostic platform 
Challenge -- At the library data level, FOLIO is a singular language platform

Multi-linguity Multilingual not just at the user level, goes deeper Into library defined policies, controlled vocabularies, branch names, user groups, etc.
Dynamic translation engine/app for FOLIO interface and VuFind implementation
Arabic +12 other languages
Classic Arabic is the default but also allows for localization – within Arabic, terms used in libraries differ from country to county or region
Translation app allowed to change term used according to the library, don’t have to wait for the community
Embedded ability to check translations on Google, & Microsoft translation tools and update local terminology, then check what it looks like in the interface/context

As a user, can change language on the fly – no need to go to Settings
Documentation is also translated
FOLIO Admin can set default language for tenant, but user can change their own default

Tech Council -- should they be talking about translation app?
Architecture changes that not comfortable with? 
Not Regarding inclusion in flower releases, TC had concerns because it is not like a regular app and requires changes to the underlying system

Tech eval was paused because approach amend FOLIO separately 

Extension of FOLIO that is different

Can’t just add app in

Marc -- What is the interest? Where do we go from here?

Massoud said they didn’t touch back end, but decided not as pure as they claimed?

Kristen -- Interest in improving, need .

Need to loop back on this with TC and talk about it more

Massoud -- not waiting, but willing Middle East FOLIO users could not wait to implement this functionality, but is also happy to talk more and work with the communityDesperate need for solution, need to find a way to coordinate.