History: Collaborative_Multilingual_Terminology

Preview of version: 110

When completed, this profile will allow a group of users to collaborate on creating a multilingual glossary of terms for a site. This kind of glossary is invaluable to help with the translation of content, and ensure consistent use of terms and their equivalents.

The profile will essentially emulate the HTAGlossary site:


However, as of 2009-06-01, it is not ready for prime time yet.



Features & settings

YAML
instructions: Get Started with Multilingual Terminology preferences: feature_wiki : y # # Page title only displayed once, so we can't use page title # to display the term. Instead, ask the user to enter the # term on the first line # feature_page_title : n feature_messages: y feature_multilingual : y feature_categoryobjects: y wiki_edit_plugin: y wiki_comments_displayed_default: n feature_translation: y feature_urgent_translation: y quantify_changes: y feature_categories: y feature_freetags: y feature_wiki_description: y feature_search: y feature_print_indexed: y feature_multilingual_one_page: y feature_mytiki: y feature_userPreferences: y feature_wiki_comments: y wiki_comments_displayed_default: y allowRegister: y validateRegistration: y auth_ldap_adminuser: y auth_ldap_adminpass: y validateUsers: n


removing for now:
wikiHomePage: Get Started with Multilingual Terminology

Modules

YAML
objects: - type: module ref: module_translation data: name: translation position: right groups: [ Registered, Anonymous ] order: 10 - type: module ref: module_quick_edit data: name: quick_edit position: right groups: [ Registered ] order: 20 - type: module ref: module_since_last_visit_new data: name: since_last_visit_new position: right groups: [ Registered ] order: 30 - type: module ref: module_switch_lang data: name: module_switch_lang position: right groups: [ Registered, Anonymous ] order: 25


Wiki


This is where we include some wiki pages
Id Page Last modification Categories
278 collaborative_terminology_platform_blog
Thu 08 of Mar, 2012 03:16 GMT-0000
Documentation
279 collaborative_terminology_platform_bl...
Thu 08 of Mar, 2012 03:17 GMT-0000
Documentation
244 collaborative_terminology_platform_fi...
Thu 08 of Mar, 2012 03:29 GMT-0000
Documentation
286 collaborative_terminology_platform_in...
Admin page for Terminology features
Thu 08 of Mar, 2012 03:30 GMT-0000
Documentation
367 collaborative_terminology_platform_in...
French User guide for Collaborative Multilingual Terminology module
Thu 08 of Mar, 2012 03:33 GMT-0000
Wiki pages included by profiles
277 collaborative_terminology_platform_in...
Thu 08 of Mar, 2012 03:33 GMT-0000
Wiki pages included by profiles
396 collaborative_terminology_platform_in...
Template for German terms
Sat 17 of Mar, 2012 02:29 GMT-0000
Documentation
305 collaborative_terminology_platform_in...
Template for new English terminology entries
Sat 17 of Mar, 2012 02:29 GMT-0000
Documentation
375 collaborative_terminology_platform_in...
Sat 17 of Mar, 2012 02:30 GMT-0000
Documentation
309 collaborative_terminology_platform_in...
Modèle pour entrées en français
Mon 15 of Oct, 2012 01:57 GMT-0000
Documentation
242 collaborative_terminology_platform_in...
Help page for the profile.
Sun 18 of Mar, 2012 20:42 GMT-0000
Wiki pages included by profiles
288 collaborative_terminology_platform_mo...
Sample terminology entry in French
Mon 28 of Jul, 2014 16:10 GMT-0000
Wiki pages included by profiles
374 collaborative_terminology_platform_Mo...
Just a sample spanish term
Sun 18 of Mar, 2012 20:40 GMT-0000
Documentation
243 collaborative_terminology_platform_rs...
Thu 08 of Mar, 2012 03:15 GMT-0000
Documentation
281 collaborative_terminology_platform_ta...
Taggage
Sun 18 of Mar, 2012 20:44 GMT-0000
Wiki pages included by profiles
280 collaborative_terminology_platform_ta...
Tagging
Sun 18 of Mar, 2012 20:45 GMT-0000
Wiki pages included by profiles
287 collaborative_terminology_platform_wi...
Just a sample term.
Sun 18 of Mar, 2012 20:45 GMT-0000
Wiki pages included by profiles

collaborative_terminology_platform_include_module


YAML
objects: - type: module data: name: last_modif_pages position: right order: 1 groups: [ Editors, Registered, Admins ] - type: wiki_page ref: collaborative_terminology_platform_include_get_started_with_multilingual_terminology data: name: Get Started with Multilingual Terminology lang: en content: wikicontent:collaborative_terminology_platform_include_Get_Started_with_Multilingual_Terminology_include - type: wiki_page ref: collaborative_terminology_platform_include_admin_page data: name: Admin page lang: en content: wikicontent:collaborative_terminology_platform_include_admin_page - type: wiki_page ref: collaborative_terminology_platform_include_register_and_set_your_languages data: name: Register and Set your Languages lang: en content: wikicontent:collaborative_terminology_platform_include_register_and_set_your_languages - type: wiki_page ref: collaborative_terminology_platform_rss_feed data: name: RSS feed lang: en content: wikicontent:collaborative_terminology_platform_rss_feed translations: [ $collaborative_terminology_platform_fil_rss] - type: wiki_page ref: collaborative_terminology_platform_fil_rss data: name: Fil rss lang: fr content: wikicontent:collaborative_terminology_platform_fil_rss - type: wiki_page ref: collaborative_terminology_platform_wiki_engine data: name: Wiki engine lang: en content:wikicontent:collaborative_terminology_platform_wiki_engine translations: [ $collaborative_terminology_platform_moteur_wiki] - type: wiki_page ref: collaborative_terminology_platform_moteur_wiki data: name: Moteur wiki lang: fr content:wikicontent:collaborative_terminology_platform_moteur_wiki - type: wiki_page ref: collaborative_terminology_platform_tagging data: name: tagging lang: en content:wikicontent:collaborative_terminology_platform_tagging translations: [ $collaborative_terminology_platform_taggage] - type: wiki_page ref: collaborative_terminology_platform_taggage data: name: taggage lang: fr content:wikicontent:collaborative_terminology_platform_taggage





Permissions

YAML
objects: - ref: Multilingual_Permissions permissions: Anonymous: allow: -view -comment -wiki_view_comments -post_comments -search -search_categorized -view_categories Registered: description: Will be ignored because group is already created allow: -view_categories Editors: description: Can edit & delete all content allow: -edit -rename -admin_categories Admins: description: Have all rights allow: [ admin ]



Questions to answer


  • How do I set up the glossary profile and make it multilingual?
  • How do I create a glossary entry in say, French?
  • Given an entry in say, French, how do I create the corresponding entry in say, English?
  • How do I avoid reinventing the wheel? For example, say I create a French entry for word X, and then want to create the corresponding entry Y in English, but someone already created Y, how do I find out about it and tie the two together. In particular, what happens if the existing Y is a very slight variation on the Y that I am currently trying to create (eg: I am creating the verb form, whereas the existing Y used the noun form)?
  • I don't want to change an entry... just comment on it.
  • How can I respond to someone else's comment?
  • Can I create an entry in French that has more than one English equivalent?
  • How do I create a domain hierarchy?


Unmet needs at the moment


Below is a list of needs that are not well met by the profile, with ideas for how to address them.

Need to support more than one equivalent for a term


A term in English like "web browser", will often have more than one possible equivalent in French. For example, "navigateur web" or "fureteur web". When looking for an equivalent to "web browser", I want to see all equivalents in French.

How to do this?

One possible solution is to have page "Web browser" have the most common equivalent "Navigateur web" as its "translation" into French, but list "fureteur web" as a synonym on the page for "navigateur web".

That will work if we are looking for an equivalent for "web browser". You will find "navigateur web", then see at the bottom of that page that it can also be said as "fureteur web".

But what if I am looking for an English equivalent for "fureteur web"? I would then go to the page "fureteur web", and see that it doesn't have a "translation" (because "web browser" is the translation of "navigateur web", not "fureteur web".).

So, how to deal with this.

A possible solution would be for the search "fureteur web" to be made not only on the page name, but also on the synonyms sections.

BTW: THIS IS REALLY CRUCIAL FOR TRANSLATORS!

TODO: Discuss possibilities with Marc and LPH.

One possible solution would be for the search to search not only in the page name (i.e. the title), but also the synonyms. So if I search for "fureteur web", it would find "navigateur web", I would click on it, and see "fureteur web" in the list of synonyms. So I would know that the translation of "navigateur web" is what I am looking for.


Term should only be specified once


At the moment, you have to use the Description field to enter the type, and to re-enter that term as the name of the page, without accented characters. This is a real pain. Who wants to specify the same term twice? Also, when you rename the page, you have to remember to rename the description also.

My understanding is that this choice was made to avoid having accented chars in the URL. But this hack does not garantee that folks won't enter the page name with accented chars, so it does't really help. In fact, my own experience with that is that the pull of wanting to enter the term (with accented chars) as the page name is really strong, and that even I (AD) forget to not do it.

I suggest we go for an approach where the page name for the term IS the term (with accented chars). In any case, Tiki is smart enough to do URL encoding of the URLs. And most browsers are smart enough to render them prperly in the URL box (i.e., accented chars will appear as accented chars in the browser's URL field, eventhough internally, they are store as %nnn url encoded chars... also, when you copy from the browser's URL field, what gets copied is the %nnn version, not the version with accented chars). Worst case scenario is that some people will see the URL with URLEncoded characters %nnn in the browser's URL box, if their browser is not smart enough about this. But who cares...

One problem with this design is that at the moment, if you go to multilingual page and ask for "all" languages, you only see the title of the "main" page. So, you only see the term in the "main" language. So, need to modify the code so that when "all" languages are chosen, we see the title of all language versions.

TODO: Modify the code so that when "all" languages are chosen, we see the title of all language versions..


Shouldn't have to always say I want "all" languages


Right now, everytime I look at a term, I have to re-select "all" languages in the picklist. This is really annoying.

TODO: Modify code so that the user's choice of language in the picklist is persistent.

In other words, the language the page is displayed follows the following pecking order:
  • Last choice of language made EXPLICITLY BY THE USER by clicking on the language picklist (including the possibility that "all" was selected).
  • User's language preferences set for that site in her profile
  • User's language preferences set in Firefox


Need to search only on the term name


Say I search for the term RSS feed. Then I only want to find terms that have RSS feed in the term itself. If the entry for a term has RSS feed in the definition of the term, I don't want to have it in the hits (at least, not unless I have asked for a full text search).

Apparently, this can be done as follows:


Recherche limité à une langue donnée


Sinon, il risque d'y avoir des conflits entre des langues similaires (ex: terme qui s'écrit pareil en italien et en français)

Recherche par synonymes





Todo


  • First paragraph of the profile should provide a plain English description.

  • Put comments in the YAML stuff to document the various decisions made.

  • Make it so that comments are invisible by default
    • Pofiling of that feature does not seem to work.
    • For now, just added instructions on the admin guide telling them to do this manually.

  • Profile does not correctly set the home page to be the Get Started page.

  • Refactor the instructions pages into one long page called "Guide to collaborative multilingual terminology creation". The guide will have a section for Admins, and a section for Editors.
    • Section for editors comes first.
    • Section for editors talks about:
      • Searching for a term
      • Creating a new term
      • Creating an equivalent for a term
      • What to do if a same word can mean different things (create different pages which are more explicit, ex: tag — dog plaque, vs tag — metadata).
      • Tracking certain pages or the whole site
      • Using categories for domain classification
    • Section for admins talks about:
      • Finalising the installation
      • Keeping abreast of new users
      • Approving new users
      • Tracking the whole site

  • The guide should provide instructions about using categories to assign domains.


  • Right now, categories take too much space
    • Displays categories, plus list of pages in each category.
    • Marc says you can configure it so that you only see the category path at the top. Chang profile so it does that.
    • Note: This will end up only showing the categories for the page corresponding to the first language. So, if the categories assigned to the French and English pages are not the same, only categories assigned to the page that corresponds to the URL will be displayed.

  • Guide should provide instructions about how to manage users.
    • Ask for email notification of new users.
    • Move new users from Registered to Editors soon after registering.
    • What are the different groups and their permissions.

  • Guide should bring users attention to the Last changes module as a way to keep track of what others do. Also, explain the page tracking feature.

  • Guide should mention breadcrumbs feature.

  • Should editors be allowed to control addition, deletion of categories?
    • Editors should definitely be allowed to assign categories to pages. But should they be allowed to create new categories, or delete existing ones?

  • The guide should provide instructions about how to deal with the situation where a same word can refer to different things. For example, Tag can refer to metadata, to a markup element, or to a dog tag. The solution is to create pages with slightly different names, for example "tag — metadatat", "tag — markup", "tag — identity plaque".

  • Add page tracking, and provide instructions in the guide.

  • Guide should provide instructions on how to track the whole site (not just individual pages)

  • Make it so editors can view history.

  • Make it so editors can revert changes.

  • Make it so that Anynoymous can see comments (only enabled for admins at the moment)

  • Activate breadcrumbs.

  • Have a standard template for terminology entry (ex: synonnyms, etc...)

  • Make it so that the guide is available in French and English.

  • Put a new users dashboard for admins, so they can move new users to the Editors group.

  • Limit term search to a particular language.

  • Need language indicator in front of the term in the list of equivalents. Ex: fr: Fil RSS, en: RSS feed.

  • Need to prevent users from creating page names that have accented chars in the name.
    • See discussion below about transliterating page names.



History

Information Version
Tue 09 of Jun, 2009 18:21 GMT-0000 alain_desilets 111
Tue 09 of Jun, 2009 17:57 GMT-0000 alain_desilets 110
Tue 09 of Jun, 2009 17:43 GMT-0000 alain_desilets 109
Mon 08 of Jun, 2009 20:40 GMT-0000 alain_desilets 108
Mon 08 of Jun, 2009 20:32 GMT-0000 alain_desilets 107
Mon 08 of Jun, 2009 20:24 GMT-0000 alain_desilets 106
Mon 08 of Jun, 2009 20:16 GMT-0000 alain_desilets 105
Mon 01 of Jun, 2009 13:02 GMT-0000 alain_desilets 104
Wed 20 of May, 2009 12:27 GMT-0000 alain_desilets 103
Mon 18 of May, 2009 19:37 GMT-0000 alain_desilets 102
Mon 18 of May, 2009 19:36 GMT-0000 alain_desilets 101
Mon 18 of May, 2009 18:32 GMT-0000 alain_desilets 100
Mon 18 of May, 2009 18:30 GMT-0000 alain_desilets 99
Mon 18 of May, 2009 18:29 GMT-0000 alain_desilets 98
Sun 17 of May, 2009 14:13 GMT-0000 Nelson Ko What this did was set the url to use to blank, which white screens 97
Sat 16 of May, 2009 11:49 GMT-0000 alain_desilets 96
Sat 16 of May, 2009 11:45 GMT-0000 alain_desilets 95
Sat 16 of May, 2009 00:52 GMT-0000 alain_desilets 94
Sat 16 of May, 2009 00:27 GMT-0000 alain_desilets 93
Sat 16 of May, 2009 00:06 GMT-0000 alain_desilets 92
Fri 15 of May, 2009 16:15 GMT-0000 alain_desilets 91
Fri 15 of May, 2009 15:59 GMT-0000 alain_desilets 90
Fri 15 of May, 2009 15:54 GMT-0000 alain_desilets 89
Fri 15 of May, 2009 15:49 GMT-0000 alain_desilets 88
Fri 15 of May, 2009 15:42 GMT-0000 alain_desilets 87