Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Target release
User Story

SWIK-196 - Getting issue details... STATUS

Document status

DRAFT

Date Created 
Document owner
Designer
Developers
QA
Work Package & deliverables 
Related JIRA tasks

Task - A task that needs to be done. SWIK-109 Create Translation Service

Task - A task that needs to be done. SWIK-96 Create a prototype for TranslationPanel component

Summary

  • As a user I want the system to translate the content of existing decks and slides to another language and store the translation.


Background and goals

T2.5. Support of collaborative authoring of multilingual content: (Start M1, End M36; Lead: Fraunhofer; Participants: VUA, UPM, SOTON, Pupin, UFRJ, ATHENA, InfAI). Language is one of the main barriers to the reuse of Open Educational Resources (OER). Crowdsourcing translations will make educational content more accessible in all European languages. The main goal of the task is to enable authoring and semi-automatic translation of content in different languages and to provide tools for content synchronizaton between the versions in different languages. We will also work on internationalization and localization of the SlideWiki service itself.

D2.5 SlideWiki multilinguality support (M18). Support of multilinguality in both content and user interfaces for content authoring, presentation and exploration.

Assumptions

  • Users will be able to select from a per-defined list of of languages.
  • Users will be able to manully or automatically translate slides.

Requirements

#TitleUser StoryImportanceNotesJIRA
1

As a user I want to see what languages slides are avaialble in


  
2 As a user I want to be able to create a new translation of a slide or deck and save it   
3 As a user I want to be able to correct a translation of a slide   

User interaction and design

Description of fields/input/elements + validation + test scenarios


Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionAsked byOutcome
How does translation of slides linked to the content revisioning strategy?Abi

Not Doing

FeatureStatus
  

Source material for user/stakeholder feedback


Requirements (/user stories) from pilot roadmap:

 

Evaluation/improvements by Farid Hasanov master thesis :

 

Translating issues. Some minor problems occurred with the embedded Google translator.

 

Issue1 - size of button. First of all, the language information and ’translate’ button are small, and it requires effort to find and click them.

 

Metric violated: Organization.

 

A Possible Solution could be to move it closer to the left, near the name of the presenta- tion, and to increase the size. The new appearance would be not dissimilar to the name of a presentation and below would be the ability to change it.

 

Issue2 - translation from the translated copies. There is no way to translate from the translated copy of a presentation. Translation is possible only from the original.

 

Metric violated: Friendliness.

 

Source.One user brought up this issue.

 



 

Evaluation at UniBonn :  


Project Partners feedback:



 

  • No labels