The ICNP BaT from translation tool to translation server


Published on

Description of a translation servo that could be a solution for information systems that have to maintain several translations of a terminology.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The ICNP BaT from translation tool to translation server

  1. 1. The ICNP BaTFrom Translation Tool To Translation Web Service<br />Ulrich Schrader<br />
  2. 2. Content<br />Briefly: The web-based translation tool used to help with translating the ICNP<br />2 Scenarios using different translations in practice<br />Challenges posed for information systems<br />Proposal for a solution<br />Experiences with a prototype<br />
  3. 3. Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences<br />ICNP BaTBrowser and Translation-Tool<br />Support all three phases of a collaborative translation effort<br />Translation phase<br />Evaluation phase<br />Finalizing and export<br />Multilingual<br />Support several languages<br />Multi-version<br />Support the concurrent translation of several versions of the ICNP<br />Automate the migration of already existing translations of a prior version of the ICNP to the next version<br />Support multiple translation of a concept<br />Preferred term, synonyms<br />Support the communication, cooperation, and coordination between teams of translators and evaluators of a specific language<br />
  4. 4. Multilingual/Multiversion<br />Select language 1<br />Select language 2<br />Select version<br />Language 2<br />Language 1<br />
  5. 5. A multilingual dictionaryofnursingconcepts<br />
  6. 6. Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences<br />Integrated Languages<br />German<br />Norwegian<br />Cantonese<br />French<br />Polish<br />Slovenian (ICNP Beta)<br />Italian (ICNP Beta)<br />
  7. 7. Experiencesleadingtothis talk<br />Existingtranslationscome in all kindsofformats:<br />MS Word<br />MS Excel<br />Text files (CSV)<br />Import intothedatabase<br />Manual<br />Time comsuming<br />Error prone<br />Challengingif different translationshavetobeintegratedintoinformationsystems<br />
  8. 8. Usesof a translationservice1st scenario<br />Multilingual countries<br />eg. Switzerland (French, German, Italian, and Rhaeto-Romanic)<br />Multilingual nursing workforce<br />globally recruited<br />Goal: Multilingual nursing documentation<br />
  9. 9. Properties of1stscenario<br />All nursing concepts of the specific domain<br />Target languages are known<br />
  10. 10. Usesof a translationservice2nd scenario<br />Patient traveling to another country<br />Goal: Nursing documentation should be at least partly readable in another language<br />Coded content can be translated automatically, if translation table for this language available<br />
  11. 11. Properties of 2nd scenario<br />Only some nursing concepts of the specific domain need to be translated<br />Languages are unknown beforehand<br />
  12. 12. Assumptions<br />Nursing care data are represented as standardized terms sometimes appended with free text. <br />ICNP is used in a computerized system as<br />interface terminology or <br />reference terminology<br />Translation would require looking up the code mapped to the desired translation.<br />
  13. 13. Possible Solution<br />Eachsystemin eachinstitutionmaintainsall translationtablesto all availablelanguages<br />Challenges<br />Version changesofthe ICNP<br />Intermediate revisionsofeachtranslation(eg. Correctionoftypos, errors)<br />New versionshavetobeimported (manually?)<br />
  14. 14. Consequence:Constant update isnecessary<br />ProposedSolution<br />TranslationServer<br />Code, version,targetlanguage<br />Concept in<br />target language<br />
  15. 15. Service-orientedarchitecture (SOA)Translation service<br />Web service based on HTML protocol(No extra ports needed)<br />Accessible over the internet<br />Machine readable (XML based)<br />Independent of operating system<br />Request for<br />All translations of a target language of an ICNP version (scenario 1)<br />A few translation s of a target language of an ICNP version (scenario 2)<br />
  16. 16. PrototypeProofofconcept<br />XML-RPC (modifiedlibrary)<br />getLanguages<br />getTranslationByCode<br />getTranslationByText<br />Performance<br />Rented, commercial, virtual server<br />PC client application (PHP script)<br />Average response 0.13 seconds (getTranslationByCode)<br />Almost enough for translation on the fly<br />
  17. 17. To do<br />Authentication/Authorization<br />Encryption?<br />Evaluate other protocols<br />XML-RPC<br />Simple object access protocol (SOAP)WS-Security<br />
  18. 18. Conclusions<br />Challenges not restricted to ICNP translations<br />Translations do change frequently over time<br />It does not make sense for each institution to maintain their own translation tables<br />A central translation server using SOA could simplify the maintenance task of the translation tables<br />
  19. 19. Ulrich Schrader, FH Frankfurt am Main – University of Applied Sciences<br /><br />Thankyouforyourattention<br />Photo by Stephen Downes<br />