[AT] II. Storing translations

[LaszloKecskes]

This issue is about the database/entity side of the translation storing process. Fetching the results from the service are handled in a different issue. Validations will be the responsibility of the worker process.

The saving process should:

• store the translation in the metadata
• append a machine_translated flag in the metadata (edit: we are not appending a flag but a regular text as part of the value).

Make sure that:

• the entity flows (get, save, etc.) leave this flag intact (edit: I think this is not needed since there is no flag but rather appending the text in the value, if the user edits it it is ok to remove this data)
• denormalization works and carries this information over (edit: this should be already denormalized as part of Uwazi's regular denormalization).

[aphilop]

@LaszloKecskes In the last product call, we made the decision to use a textual disclaimer (“AI translated”) that should be displayed in the translated property and could be removed manually by the users when editing the property. Is this the correct issue to document this so that it is considered during development?

[LaszloKecskes]

@LaszloKecskes In the last product call, we made the decision to use a textual disclaimer (“AI translated”) that should be displayed in the translated property and could be removed manually by the users when editing the property. Is this the correct issue to document this so that it is considered during development?

For the display, there are no front end issues yet. The backend issue about the flag removal is #6956