[FOLIO-2802] Recruit translators for library-defined policies (controlled vocabularies) Created: 17/Sep/20 Updated: 29/Jun/21 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Massoud Alshareef | Assignee: | Peter Murray |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | i18n | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||
| Development Team: | None | ||||||||||||||||||||||||
| Description |
|
Proposed text to translators: The development team at Knowledgeware has created a mechanism in FOLIO to translate the controlled vocabulary terms (sometimes called library-defined policies). This mechanism is on Knowledgeware's test server and in the process of being integrated into mainstream FOLIO software. This function adds a "Translation" action to term lists in the FOLIO Settings app. For example: The translation of these terms is different from what happens in Lokalise. In Lokalise, the words and phrases are a static part of the code. Knowledgeware's mechanism provides for translations of terms that are part of the configuration of FOLIO. Most of these term lists are supplied as part of a FOLIO installation, but they can be changed to meet the needs of each library. Work is underway to provide for the translation permission labels at the locale level. in a coming release of the translation app, the FOLIO tenant administrators will be able to grant permissions to certain users for translating vocabulary terms names for certain locale(s) only. Demonstration of the Translation FunctionalityTo put the dynamic translation engine into action, let's take a trip with a French translator aiming to translate the Inventory app vocabulary terms names in the “Resource types” instance (schedule) to French. We will login with user “kware01_test” credential since its preferred locale is set to French. (The table of credentials is listed below.) Now, let’s go to Settings → Inventory → Resource types (direct link is http://folio-testing.maktabat-guides.com/settings/inventory/resourcetypes and then switch the locale to French. We will translate two Resource types policies, namely “computer dataset” and “computer program” to French: Now, press the “Translate” button on the “computer dataset” entry in the Resource types instance. After translating and saving the two entries in the Resource types schedule, they will appear in French as shown in the following screenshot: Now, let’s go to the Inventory app (Inventaire in French) to see if the two Resource types we just translated to French will appear in French in the Resource types app filters and in the drop-down list within the Inventaire app when you add/ edit an instance record. The Inventaire app's Resource types filters show: We'll create a new instance in the Inventaire app, then we’ll go directly to the section within the app to see if the two vocabulary terms in the Resource types drop-down list will appear now in French: Translators can export the vocabulary term translations as a JSON file for a given app name. You can import this file into any other FOLIO installation with Knowledgeware's dynamic translation engine installed. You can export the entire vocabulary terms translation for a Locale via the translation app. Request for Translators to Make Translations of Controlled Vocabulary TermsTranslators are asked to make these translations on the Knowledgeware server. Any of the following FOLIO users' credentials can be used to login to the site and make translations in the current switched to language by the translation user, as shown in the image above.
All users above are given all permissions normally given to the "Superuser" use of FOLIO, with the required permissions to do the translation to any language as well. The only difference between them is that the preferred language for each user is different, simply to demonstrate the preferred language setting feature of the Users-level locales Switcher developed by KnowledgeWare. More details about the Users-level locales Switcher can be found under https://folio-org.atlassian.net/browse/UXPROD-510. When the Knowledgeware mechanism has been added to the mainstream FOLIO software, any site can upload the translations to their own server using the new Translations app: The list of vocabularies that need translation are: Agreements Circulation
Courses
Finance Licenses Invoice Inventory
Notes Orders Organizations Tenant Settings
Users
|
| Comments |
| Comment by Massoud Alshareef [ 18/Sep/20 ] |
|
Thank you Peter for introducing KnowledgeWare Dynamic Translation engine to FOLIO community, to enable translating library-defined policies from English (USA) to the other languages. Here is the FOLIO demo site hosted by KnowledgeWare, to introduce the User-level Locales Switcher and the Dynamic Translation Engine to enable libraries to have their Library-defined policies in their choice of languages that are supported by FOLIO. http://folio-testing.maktabat-guides.com/ Any of the following FOLIO users' credentials can be used to login into the site and try translating the library-defined policies in the current switched to language by the translation user, as described by Peter Murray above.
All users above are given all permissions normally given to the "Superuser" use of FOLIO, with the required permissions to do translation to any language as well. The only difference between them is that the preferred language set for each user is different, simply to demonstrate the preferred language setting feature of the Users-level locales Switcher developed by KnowledgeWare. More details about the Users-level locales Switcher can be found under https://folio-org.atlassian.net/browse/UXPROD-510. At this moment any of the credited users above can translate library policies names to any other language available for the current FOLIO tenant, and can also modify the original policy name (in English USA locale) in any instance (table) that belongs to any app. Therefore, it is assumed that users wanting to modify the original library policies names, or wanting to try translating some policies names to another language, are assumed to be fluent in the translated to language of choice. Work is under way to provide translation permissions to users at the locale level. in a coming release of the translation app, Library admin will be able to grant permissions to certain users for translating policies names for certain locale(s) only. To put the dynamic translation engine into action, let's take in a trip with a French translator aiming to translate the Inventory app policies names in the “Resource types” instance (schedule) to French. We'll login with user “kware01_test” credential since its (preferred locale) is set to French. Now, let’s go to Settings>> Inventory>> Resource types then switch the locale to French. We will translate two Resource types policies, namely “computer dataset” and “computer program” to French. Since I do not understand French, I will call Shaikh Google for help to capture the following translations: Now, press the “Translate” button in front of “computer dataset” entry in the Resource types instance. After translating and saving the two entries in the Resource types schedule, they will appear in French as show in the following screenshot: Now, let’s go to the (Inventaire) app to see if the two Resource types we just translated to French will appear in French in the Resource types app filters and in the drop-down list within the Inventaire app when you add/ edit an instance record. The Inventaire app's Resource types filters show: We'll create a new instance in the Inventaire app, then we’ll go directly to the section within the app to see if the two policies in the Resource types drop-down list will appear now in French: Translators can export the current library policy instance onto a JSON file given the instance name. You can import this file into any other FOLIO installation with the dynamic transalation engine installed. You can export the entire policies translation for a Locale via the translation app. |
| Comment by Peter Murray [ 28/Sep/20 ] |
|
Charlotte Whitt: The Inventory app has one of the heaviest usages of controlled vocabularies. This issue is about recruiting translators to begin the translation of those terms. Do the instructions in the Description of this field make sense to you? (Is this something that you think could be sent to the translators?) |
| Comment by Massoud Alshareef [ 29/Sep/20 ] |
|
Peter Murray Charlotte Whitt We are in the testing phase for delivering the capability of assigning a translator(s) per locale. This feature will enable the library admin to give permissions to translate the library-defined policies to a specific locale by a specific person(s) only. Also, you can notice in the Kware FOLIO demo that users groups in the Users app appear now in five different locales: English (USA), Arabic, French, Chinese and Spanish. After launching the Users app, simply switch between these five languages to notice that user groups are displayed in the language you have switched to. While switching between these five locales, you will also see that FOLIO users names are also available in each of the five languages. If you feel that user groups translation to Chinese, French or Spanish are out of tunes, please instead of blaming the translator (me) please blame Shaikh Google Translator! For other languages, policies names will appear in English (USA), as they are now, until translation of library-defined policies to the other locales takes place. |
| Comment by Peter Murray [ 13/Nov/20 ] |
|
Massoud: Charlotte pointed out that many of the RDA-based value vocabularies are available online with translations. For instance: http://www.rdaregistry.info/termList/RDACarrierType/?language=ar Is it possible to preload these into the translation tool? |
| Comment by Massoud Alshareef [ 13/Nov/20 ] |
|
Peter Murray attia.alshareefUsing the RDA-based value vocabularies available in many languages is an excellent idea! I do not see why not, and that could be a starting point for many language translations. I am sure thu that not all of the RDA translated vocabularies will be satisfying for the translators who are used to very localized terms in the targeted language, as I can see that the machine translation of Google Translator has some signature in the text shown in the page you've shared for the Arabic RDA terms. Of course this may not be the case for other languages. I hope to ask for Dina and attia.alshareef comment to Charlotte Whitt point. BYW, we are are about to release the new Translation app in the newly updated Kware testing demo of FOLIO. Now all translation work will take place within the Translation app only. Translators do not need to be go to Settings to translate. In fact, the Translate button are no longer accessible from the Setting UX for any app. This way Settings access is restricted to the tenant admin(s) only. Translators will need to have their own account registered first, where then a tenant admin will grant each translator the required permissions to create/edit/delete/import/export the translation for any particular language(s). A reporting tool to keep track of every translation work done by any translator will be provided. A very important tool to make available with Kware translation engine is the process script needed to translate enable the library-defined policies (library vocabularies) for an exiting FOLIO installation. The Kware team has done an excellent job in covering all possible scenarios that may face FOLIO libraries wanting to provide their services in a completely multi-language atmosphere. |
| Comment by Peter Murray [ 13/Nov/20 ] |
|
Thank you for the update, Massoud. I'm looking forward to seeing it on the Kware test system soon. I can adjust the steps needed for the translators in the issue description above based on that new version. |
| Comment by Massoud Alshareef [ 26/Nov/20 ] |
|
The Translation app is here now, Peter Murray. Please give it a try. http://folio.maktabat-guides.com/
Click on the Translation app icon on the apps Nav bar to launch the app: http://folio.maktabat-guides.com/translations/libTranslations You will see four section tabs to the left on top, as follows:
Our focus for now will be on the Library-defined policies section only. The above screenshot shows the Arabic translation version of the Library-defined policies for all of the Inventory app policies tables (instances). You can limit the display to a certain table, and you can also filter the view to the unrelated keys only. With Kware Translation app, you will have every string that is desired to be translated to other FOLIO languages in one place. You no longer need to switch to each FOLIO app settings to access its policy tables (instances). You can see all library policies names, all or translated only or not translated only, and at multiple levels including: at FOLIO level as a whole, at a certain app level to see all of its tables policies strings in one location, or at a specific table level that belongs to a specific app. The ultimate aim that we hope to accomplish with the Kware Translation app is to enable FOLIO to be a truly native platform for all library services, to be the platform of choice to bring all knowledge management apps under one roof, completely in the organization native language(s) of choice. Multilingual library platforms, or bilingual platform for the least, is becoming a requirement in most intellectual environments around the world where knowledge is intended to be curated, organized, published and shared. This implies that not only the apps UX strings that need to be in multiple languages, but also library policies, permissions names, users names, courses names, organizations/ vendors/ providers names, etc., are potential UX stuff to be put on the translation plate in a truly localized, multilingual platform. The above FOLIO users names have been added to the Languages Translators list in the Translation app Settings http://folio.maktabat-guides.com/settings/translations/locales-translators, containing four locales: Arabic, French, Spanish and Chinese. In order for a user to be able to translate to any available FOLIO language, his/her name must be added to the language(s) translators list in this Translation app setting page. I suggest that we create an account in this FOLIO installation for anyone willing to contribute to the Library-defined policies translation in their languages, providing their names, email, and the language(s) they like to translate the library policies (controlled vocabularies) to. |
| Comment by Peter Murray [ 30/Nov/20 ] |
|
Thanks, Massoud. I made some translations into Spanish in the Inventory app, and I think the process is more straight forward than the previous version. Is it safe to assume the editing the Languages Translators list is a new permission added to the system by the Translation app? I can see that some changes will need to be made to the instructions in the description of this issue to account for the new system. I'll need to set aside some time to do that. Was your team able to research the process for importing translations from the RDF website? If that is going to be possible but would take some time to implement, I am thinking that we would want to encourage translators to work on library-defined policies from non-RDA sources. |
| Comment by Massoud Alshareef [ 01/Dec/20 ] |
|
Thank you Peter Murray for trying the Translation app and for your positive comment. The Dynamic Translation process has added 8 permissions to FOLIO system, with translation admin and execution privileges as follows:
As for importing translations from the RDF website issue, I have asked Dina to look into the possibility of importing those RDF tables that are in use in FOLIO Inventory app as is. I do not think it's a hard task to accomplish, considering that only four tables of the Inventory app that are found with RDF source. I will come back to you with more details on this. attia.alshareef |
| Comment by Massoud Alshareef [ 08/Dec/20 ] |
|
Hello Peter Murray Charlotte Whitt The RDA sources we found in FOLIO are used in three tables of the Inventory app only, as follows:
There are two more Inventory app tables that seem to be sourced from external agencies also, as follows:
We searched for marcrelator and UC to see if these values are available in other languages but so far no luck. I would appreciate of someone can lead us to a site(s) where these values could be made in other languages already. You can download the three RDA sourced tables from the RDA Registry website in multiple file formats, but after we investigated the content of the downloaded file (the json file in particular), we realized it is much faster to copy those values manually into FOLIO Inv app tables than to create the required scripts for parsing and uploading these value programmabley. We now have the Arabic and French translations for the three RDA sourced tables uploaded into the Inventory app settings. The rest of translations are under way. |
| Comment by Peter Murray [ 08/Dec/20 ] |
|
Charlotte Whitt: Do you know a source for these?
|
| Comment by Massoud Alshareef [ 10/Dec/20 ] |
|
Peter Murray Charlotte Whitt The Contributor Type Authority List provides data values for the Organizational Contributor Type and Personal Contributor Type elements. The Contributor Type Authority List https://www.archives.gov/research/catalog/lcdrg/authority_lists/contributorlist.html is based on the MARC Relator Codes https://www.loc.gov/marc/relators/relacode.html (marcrelator). The marcrelator list is available in English only! |
| Comment by Massoud Alshareef [ 16/Jan/21 ] |
|
Peter Murray Please use the Testing FOLIO server for translating the library-defined policies (controlled vocabularies) to other languages, with the following credentials: http://folio-testing.maktabat-guides.com/ We have added the content of two RDA registry tables in French into two Inventory app tables, namely the Formats and Resource Types instances. The match between the RDA registry values and FOLIO English elements in these two tables are not 100%, as we left few elements untranslated due to no match found. Charlotte Whitt Since about three weeks ago the RDA Registry website stopped responding to display its tables values. For instance, when requesting to view the content type values: https://www.rdaregistry.info/termList/RDAContentType/, the site will loop for ever while loading these values. Not sure what is the reason behind this no response situation and for how long it will be like this. |
| Comment by Massoud Alshareef [ 02/Feb/21 ] |
|
Hi Peter Murray attia.alshareef Dina The RDA Registry website is working now. It had a security issues related to URL https//: which is fixed now. The library polices are about 61% ready in French as of today! http://folio-testing.maktabat-guides.com/translations/libTranslations Nizar Souda, a KnowledgeWare staff member from Morocco, is helping in making FOLIO ready in French soon. We may need help form French librarians to qualify some of the library terms commonly in use in French. However, we thought it will be nice to making a French FOLIO demo ready for presentation fully in countries using the French language officially, like France, Ontario/Canada and north Africa countries where Arabic, French and English UX are mandatory needed. |
| Comment by Charlotte Whitt [ 02/Feb/21 ] |
|
Hi Felix Hemme - please see Massoud Alshareef's comment above re. translation of RDA reference values. |
| Comment by Felix Hemme [ 02/Feb/21 ] |
|
Thanks Charlotte Whitt for pointing me to that comment. I'm still wondering if this feature will be in one of the upcomming Folio releases. It would only then make sense for us to add the translation. |
| Comment by Felix Hemme [ 26/Feb/21 ] |
|
Sorry Peter Murray, I have assigned it by accident to myself and re-assigned to you. |
| Comment by Massoud Alshareef [ 25/Jun/21 ] |
|
Please see issue [400] https://folio-org.atlassian.net/browse/UX-400 for an update on Kware Multi-lingual support for FOLIO (Kware User-level Locale Switcher, Kware Dynamic Translation engine and Kware Translation app):. |