Okapi Framework - User contributions [en]

Terminology Leveraging Step

2017-09-11T14:13:08Z

Vmykhalets: /* Limitations */

{{Steps Header}}
__TOC__
==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==

<cite>Leverage</cite> — 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.

<cite>Annotate source</cite> — 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.

<cite>Annotate target</cite> — 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.

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

<cite>Connector Parameters</cite> — 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.

[[Category:Steps]]

Terminology Leveraging Step

2017-09-11T14:12:46Z

Vmykhalets: /* Overview */

Terminology Leveraging Step

2017-09-11T14:12:04Z

Vmykhalets: /* Parameters */

{{Steps Header}}
__TOC__
==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.
* It is '''not''' possible to chain several steps if you want to leverage against several terminology resources.
* Terminology resource connector is capable to define its own strategy for generation of glossary entry ids and glossary translation ids.

==Parameters==

<cite>Leverage</cite> — 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.

<cite>Annotate source</cite> — 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.

<cite>Annotate target</cite> — 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.

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

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

==Limitations==

* None known.

[[Category:Steps]]

Terminology Leveraging Step

2017-09-11T14:07:28Z

Vmykhalets: /* Overview */