-
Type:
New Feature
-
Resolution: Unresolved
-
None
-
Affects Version/s: None
-
Component/s: TermPortal, translate5 AI
-
Medium
-
None
-
Configure which term attributes from term collection will be used by AI on pre-translation.
-
None
-
Emptyshow more show less
Problem
Some terms require context or more detailed information. For example a product name may be kept as is in source and target name but translator and LLM need to know which gender the term should use.
Solution
TermPortal
In TermPortal we should add the possibility to select per TermCollection which attributes and their corresponding values are given to the LLM for translation/TQE and in addition a column "Attribute name for LLM" that is send to the LLM instead of the name used in TermPortal (if empty, name in termPortal is used). A tooltip on this "attribute name for LLM" column explains, how it is used and what is used if empty.
In addition add a configuration option in the language resource management for configuration of a termCollection, if it should send also homonyms to the AI (bypassing our current logic, what homonyms should be send to the AI):
- If active, all homonyms except forbidden terms should be send, as long as they have the configured process status (which still should be respected)
- A tooltip/info icon in Termcollection configuration in language resource management should hint: "CAUTION: To activate this, you need to configure all necessary attributes in TermPortal for this TermCollection, that the AI needs to be able to decide, what homonym to use for translation".
- A tooltip/info icon in above TermPortal configuration (where you can configure attributes to be send to AI) should hint: "CAUTION: If you want AI to decide itself based on the attributes, that you configure here, what homonym to choose, you need to activate sending of homonyms to AI in the settings of the TermCollection in the language resource management".
See mockup:

Of course usage and process status should not be editable and still use our current logic, unless we decide otherwise
Processing with LLM
- blocks
-
TRANSLATE-5261 InstantTranslate & translate5 AI: Support Term-RAG for AI-based translations text-field translations
- Code review
- relates to
-
TRANSLATE-5748 AI terminology lookup fails for edited segments (duplicate "target" field)
- Done
-
TRANSLATE-5600 Allow own glossary entry for synonyms with attribute full or short form
- Selected for dev