Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

OL best-practices-online-workshop


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

OL best-practices-online-workshop

  3. 3. Online discovery services Agricultural domain can I have more options? why so many options? why terminology is not correctly transformed? can I search using terms in my language? why terminology is not transformed correclty?
  5. 5. The common multilingual processing framework
  6. 6. A number of open source tools that could be re-used • AgLR can be used to share digital resources and to provide semantic and multilingual annotation for them. • Language Analytics can be used a) to wrap several language services such as MS Bing, XEROX MT, MosesCore MT services b) to evaluate the quality of the translation by providing a simple rating and c) to keep analytics about all the translations. • MoKi can be used to collaboratively develop KOSs and to expose them in linked data format. • agriMoodle can be used to share learning resources and courses and to provide semantic and multilingual annotation for them • Organic.Edunet portal infrastructure that can be re-used to develop a multilingual online document discovery service • Proxy module for Moses MT that can be used as a free alternative for MT services for specific language pairs • Machine Translation Caching module • Tool for automatically matching concepts between multilingual Thesauri (RDF SKOS format)
  8. 8. The Best Practices were defined in the context of project based on the experience of developing a truly multilingual Pan- European online service, the portal 10 ways to become truly multilingual 1. Rely on REST style 2. Localize your service 3. Rely on multilingual KOSs 4. Publish KOSs as linked data 5. Be domain specific 6. Select the best MT service 7. Enable multilingual search 8. Wrap language services 9. Keep analytics 10. Think of users
  9. 9. Rely on REST style Follow a service oriented approach in the architecture of your online service Rely on REST style ✓ Follow a SOA approach using REST ✓ Integrate easily new language technologies ✓ Integrate easily KOSs to annotate your resources and allow navigation ✓ Cache information if performance matters
  10. 10. Localize your front end service Follow the concepts of the International web design (i18n) to localize your front end service Localize your service ✓ Internationalization ✓ Do not use graphics with text ✓ Localize all components of the portal e.g. generic content, feedback forms ✓ Use MT in interface translation as a supporting tool
  11. 11. Rely on multilingual KOSs Use and Manage multilingual KOSs centrally Rely on multilingual KOSs ✓ Use multilingual KOSs ✓ Keep them centrally ✓ Manage them with friendly open source tool that can be used by domain experts ✓ Allow collaborative KOSs evolution ✓ Rely only on KOS’s id and not on labels in your local db
  12. 12. Publish KOSs as linked data Published all the KOSs used in your online service as linked data Publish KOSs as linked data ✓ KOSs linking ✓ Link to external sources ✓ Use terms from external KOSs in search ✓ Use KOSs for domain adaptation
  13. 13. Be domain specific The language services should be domain specific especially if your online service targets a particular sector Be domain specific ✓ Collect domain language resources ✓ Train language services by using domain specific resources ✓ Use domain specific widely accepted KOSs
  14. 14. Select the best MT Select the best MT for the domain of your service Select the best MT ✓ Compare the different MT services ✓ Check open and free solutions ✓ Check domain adaptation capabilities ✓ Perform in vitro evaluation ✓ Ask users to help you in evaluation ✓ Add a simple rating for MT in your service
  15. 15. Multilingual search Allow users to search using their native language. Multilingual search ✓ Keep in mind that users know the terminology in their native language ✓ Translate queries ✓ Enrich your indexes with domain specific KOSs ✓ Put manual enrichment first
  16. 16. Wrap language services Add a component in your architecture that will wrap the language services Wrap language services ✓ Different language services for each language ✓ Do not integrate directly the language services in your portal ✓ Create a uniform REST interface for all the language services ✓ Share the same wrapping component among
  17. 17. Keep analytics Analytics can help you in understanding how the language technologies are used in your online service Keep analytics ✓ Track the origin of your visitors ✓ Create a linguistic profile of the users ✓ Use an analytics component in your architecture ✓ Add a simple rating for MT in your analytic services
  18. 18. Think of users Always think of users and their linguistic profile Think of users ✓ Study their geographical distribution ✓ Inform users about automatic translation ✓ Allow users to disable the automatic translation in search and browsing ✓ Enable feedback about the automatic translation ✓ Allow users to submit improved translations
  19. 19. ORGANIC.LINGUA ONLINE WORKSHOP 27/3/2014, 15:00 CET It is important to evaluate the MT services before their use in your online service Organic.Lingua project ✓ ICT – PSP ✓ Just finished ✓ Check our project site ✓ Check our service ✓ Check our open source tools Open_Source_Tools