Translations in progress and not updated for a long time are present in CX database. Resuming these old draft translations are not successful compared to fresh drafts. As the source article change a lot, restoring old translations againt it is difficult and sometimes end up as using old source revision as source article. These are suboptimal. There is a chance that the translator may not come back to continue the translation. In that case, the draft translation is preventing from another translator to do the translation of same article(since we don't support collaborative translation).
Also as noted in {T183485} , cx_corpora table is growing as more translations happen and its size is becoming a concern.
To address this issue, one suggesion is to remove the entry from cx_translations table and the data from cx_corpora table.
Questions to consider before implementation:
* Should we send notifications to translators? If so
* What should be the notification sending mechanism? Echo?
* Should we wait for a finite time before purging old drafts?
* What should be the time frame for defining a draft as "old enough to notify"?
* Should there be a time frame for defining a draft as "too old for notification, just purge"?
* Should we display this old translations in translation dashboard as "non resumable" translations that can only start from scratch from latest version of source article? If so, we should purge data only from cx_corpora table
* Should we treat translations that are published once and remain in draft state(due to editing after publishing) differently?
* How many old drafts are present in our system?
* Should we schedule this clean up in regular time intervals?
# Notifications
We want to use notifications at different points to let users know what is going on and encourage them to complete their translations. These are the notifications to support:
- {T106693}
- {T89707}
- {T184268}
The diagram below illustrates how these notifications work together:
{F12259461}
# Backend tools
Some other scripts and tools are needed to properly support this process:
- {T189087}
- {T189088}
- {T189089}