Term-translation-Workflow

• In the TermPortal for the role Term-PM for users that also have the normal PM role create the possibility to transfer the terms that correspond to the current filtering directly for translation into a translate5 project (any number of target languages). Restriction: Only TermCollection of max. one customer can be selected.

• The term translation process is started from the TermPortal filter dialog with a window asking for the task name and the target languages.

• This means that the translate5 project import can be provided with a TermPortal filter setting on the API side instead of an import file.

• The source language in the project import then determines which terms that correspond to the TermPortal filter setting are sent into the translation process.
• The client for the created task will be the client, to whom the current TermCollection(s) belong. The process can only be started, if a client filter is set to only one client in the TermPortal (or if anyway the user has only the right to access the terms of only one client). If more than one client is selected in the filter settings (or available for to me searched), the button to start the term translation workflow is disabled and a tool tip shows why.

• The target languages in the project import can determine which terms go into the translation. For each language, only those terms are selected for translation that do not already exist in the target language. This means that the terms to be translated may be different depending on the target language. Whether only these terms are translated or also those for which a translation already exists is determined by a check-box "Do send also translated terms to translation".

• The TermCollection(s) on which the import is based are automatically used to mark up the terminology. Thus, the most important term attributes "Definition", "Do not use", "Preferred term" and the synonyms of a term are directly visible in the translation editor. In case if TermCollection(s) on which the import is based have no language associations, they should anyway be assigned to task, despite they won't be shown in the language resources tab of the task properties
• The language resources that are assigned as "to be assigned by default" for this client and language combination will be assigned automatically to this translation task - nothing more or less.

• In addition, the term is linked to the TermPortal in the right column of the translate5 editor, provided that the translator has the right to use the TermPortal. Clicking on the term in the editor then opens the term in the TermPortal in a new browser tab, so that the translator can see additional term attributes and the translations from other languages, if applicable.
• In addition to the usual export option "Export => Original format, translated" in the GUI there should be an option "Transfer translated terms to TermCollection(s)".

As hint as implementation:

• I would export one TBX file for all termEntries, that stem from the same TermCollection. That means, if more than one TermCollection is base of the current filter set, more than one TermCollection will be exported. The file name could reflect the ID of the TermCollection in the languageresources table.
• The created TBX files only contain the selected source language for each termEntry. All terms of other languages are not present in the file
• For this file I would create an Okapi bconf, that converts this tbx (xml) file into an xliff
• This xliff would be the file to import and translate
• The TermCollections from what the export is done, will also be assigned as languageResources automatically
• When the translation is ready, the TBX is recreated from the xliff for each target language
• Now we simply have to change the language code in the translated TBX file to that one of the target language and then re-import them in the corresponding TermCollections. Also we need to delete the term-tbx-id, so translate5 creates a new one on import automatically for the new term the import creates instead of importing it in the existing term of the source language
• Once Save button is pressed on 'Transfer to T5'-window, it should be replaced with MsgBox saying 'Your task is being created, and it would approximately take xx sec'