Live-Tagging of terminology based on Multiterm

Based on the currently available information the best way to implement live-tagging of terminology is to use Multiterm-API to create a Termbase export and use xliffTermTagger to tag the terms inside translate5.

To achieve best performance and as well as real live tagging it is best to implement the feature in the following way:

• first of all: Live-Tagging can be (de)acitvated via configuration of translate5

• if Multiterm support is activated via configuration of translate5, translate5 connects to Multiterm on login time of a user to get the list of available termbases
• on creation of a task, the user is offered the list of available termbases and can select one of them for marking terminology. Alternativly he can pass a TBX-file as usual.

• after importing a task in translate5, the necessary Multiterm export is done for the first time
• based on this export all segments of the task are tagged with xliffTermTagger
• when opening a task for editing,
  • all terminology is tagged already - due to the tagging right after the import (which might be a few days or weeks old)
  • another Multiterm export of the relevant terminology is triggered
  • based on this second export,
    • the segments of the current selection are tagged a second time (if they have not already been tagged after the task had been opened; if a next selection is made before all segments of the previous selection have been retagged, the retagging of the previous selection stops and the tagging of the next selection is started).
    • At first this new tagging will be done for the segments currently loaded by the browser, at first for the top few segments of the current range. This way it is made sure, that at least after the first few segments all segments opened for editing already are newly tagged against the second Multiterm export.
    • If the current selection is changed in translate5 through setting of a filter or through scrolling down more than 200 segments, it is taken care of, that this new selection is newly tagged at first (if not done already)
    • If a change to the initial tagging result is detected, the browser is notified and loads the newly tagged segment.
    • The user is notified, in which of the currently loaded segments the termTagging did change. If this change does affect a segment currently opened for editing, the user is notified about this. He has to close (and if he wants to reopen) the segment in order to see the new termTagging.
  • if a segment is opened for editing which has not been tagged at all so far, it is tagged against the current set of terminology before it finishes opening for editing
  • on saving of each segment, the segment always is newly tagged against the Multiterm export which had been fetched at task opening.

Techical requirements

• Multiterm API is only running on windows and can only be connected via COM. For good architecture and performance it makes sense to decouple Multiterm and translate5 in a way that they can run on different machine. For this purpose a small REST-service will be written, which can be queried for a TBX-file and returns it. See subtask "REST-service for Multiterm".