Terminology Leveraging Step

From Okapi Framework
Jump to: navigation, search

Overview

This step leverages glossary terms into extracted text units.

Takes: Filter text unit events. Sends: Filter text unit events.

This step allows you to send the list of unit segments to a terminology resource and get a list of found glossary terms for corresponding segment, if any is available. The terminology resource should split the segment into source terms or apply any other technique which will provide a list of existing glossary terms found for corresponding segment.

  • The text units that are flagged as non-translatable are skipped.
  • Terminology resource connector is capable to define its own strategy for generation of glossary entry ids and glossary translation ids.

Parameters

Leverage — Set this option to enable the step. This option allows you to keep the step in your pipeline and to set it on and off.

Annotate source  — Set this option to enable the source unit segment annotation with found glossary entries. Annotation will be done if term is found within source segment text.

Annotate target  — Set this option to enable the target unit segment annotation with found glossary entries. Annotation will be done if translation of the term is found within target segment text.

Connector Class Name  — Select a terminology resource connector. It can be the subclass of the BaseTerminologyConnector abstract class or custom implementation of the ITerminologyQuery interface.

Connector Parameters  — Click this button to edit the settings associated to the terminology resource you have selected.

Limitations

  • It is not possible to chain several steps if you want to leverage against several terminology resources.