Atomic delete

Toss out internal key for atomic delete. Use all segment data instead.

Result table

Remove internal key and segment Id columns.

In cell with actions for segment we have to add 2 new buttons:

1. Delete all with same source:

• On click FE will show confirmation window that all segments with same source regardless of current active filtering will be deleted
• FE will send source text and list of selected LRs.
• On OK response from back end FE will remove segments with same source text in already loaded list of found segments.
• Other fields do not matter

1. Delete all with same source + target:

• On click FE will show confirmation window that all segments with same source and target regardless of current active filtering will be deleted
• FE will send source text, target text and list of selected LRs.
• On OK response from back end FE will remove segments with same source and target text in already loaded list of found segments
• Other fields do not matter

Handlers of new delete buttons

Delete all with same source

Source text + LR ids will be received as params.

We will do fuzzy search with source text and delete all 100 matches one by one from highest internal key to lowest.

If t5memory responds, that segmentId does not match internalKey in delete request, we will redo fuzzy search.

Delete all with same source + target

Source text + target text + LR ids will be received as params.

We will do fuzzy search with source text and delete all 100 matches one by one from highest internal key to lowest where target text is exactly same as passed.

If t5memory responds, that delete is unsuccessful we will redo search and try delete founds again until no founds there.

What to test

1. Update of segment in task deletes old variation of segment in TM and saves new. This functionality should follow logic of https://jira.translate5.net/browse/TRANSLATE-5034
   So if skip config is set - field should not play a role in comparison process.
2. In Maintenance delete button should delete one exact segment, settings from 5034 should not play a role here.
3. New buttons for similar segment deletion should work according to description of this task
4. Different tag types should be tested in process of deletion of exact segment and similar segments as well: content protection tag (t5:n), ph, ept, bpt, g, x, ex, bx