This is a bug, that makes sense to solve, when we develop the next stage of Termportal. Therefore it is turned into a sub-task, but actually has nothing to do with the new features, that have to be implemented for TRANSLATE-1405

tlauria Is this solved with the new TermPortal or still open? If open: Could you please contact me regarding the efforts to fix this?

problem

Although the segment contain terms, the terms are not shown in the segment meta panel:

reason

The most common reason is, that either

1. the TermCollection Association of the task was changed (complete new / other / additional term collection is selected)
2. The TermCollection is still the same, but was updated in the mean time

solutions

1. We change term tagging so that tagging on import time can be disabled btw. is not the default anymore
   • by uncheck the term tag checkbox in match analysis panel
   • by NOT running the termtagger by default when providing a TBX in import package, if here a complete tagging on installation is wanted on import this must be triggered via analysis operation then
2. We move the segmentMeta field termtagState into the LEK_segments table.
   • A PHP update script is needed to move the values from the meta into each view table
3. Each time the TBX hash of the task is updated we have to reset the termtagState of the segments to untagged where they have been tagged (so that we do not have to recalculate the other states here)
4. In the GUI:
   • From the first visible loaded segment on segment grid load or
   • from the current segment (opened or selected), check the next 5 segments if they are untagged
   • if yes, send them to the termtagger (import term tagger worker can be reused expect the fact that it tries to start automatically the next segments to be tagged)
   • This worker should be triggered as direct run (like the termtagger worker for a single segment save at the moment),
     • that means the GUI sends one request (as operation catched in the termtagger plugin) to the server to tag that 5 segments, updates the segment contents into the DB
     • if request (triggered operation) is finished the GUI gets then the new segment contents directly as request result, which are replaced in the GUI store then
     • Important: Only the segment contents may be overridden (no other fields like for example the match rate or editable flag)
     • Not editable segments: It is configurable if not editable segments should be termtagged or not, this configuration should be respected here too, so the GUI should trigger the retagging only for non edtiable segments if enabled in config: Remark TL this is implied in the termTagstate see below.
     • Not editable segments: it must be ensured that the termtagState calculation (untagged / oversized / ignore) is always done on import, regardles if termtagging should be started or not)
       Therefore we can rely in the frontend only on the termtagState "untagged" to identify the segments to be tagged.
   • If one of the five segments is opened for editing in the meantime thats just bad luck and we do NOT modify the content in the edited segment, so the user gets here the terms after saving (as usual)
5. One note to multi user: In multi user projects it can happen that the same segments are tagged if multiple users are looking on the same segments. This may be a problem but its rather unusual since User A edits Segments 1-100 and User B Segments 100 to 200 normally. If we get problems here, we have to include multiuser handling some how into the tagging process - but currently thats not needed.