Need a feature for exporting Archetype translation before the translation get reiview and published. For now, there is no way to export translation . Therefore, no way to review translation before the translation get reiview and published.
If the translation has not been approved/published, the translation would be missing/lost for the translator. And embarrassingly, this has happened (more than once) to me before, and I have long forgotten what Archetype I translated.
Alternatively, Archetype translation can be submitted by uploading a locally translated Archetype adl file to CKM.
AFAIK both features are actually avaiable by importing/exporting to branches but I’m not an expert on translation processes. @varntzen@siljelb@sebastian.garde can advise
As Ian says, you can export any branch, apply a translation from one branch to another, translations can be published individually, there can even be review rounds for translations before them being published, etc. You can also select the archetype language in the tabbed view, etc. to view it.
CKAs, translation admins and editors can commit a new translation from a branch to the trunk.
There are at present 41 archetypes in the international CKM with translation to zh, most of them are initial/predraft archetypes. Some of them are also only partly translated.
Translations are “difficult” in the way that anyone can translate in their own branch, but the branch need to be committed to the trunk by an editor, admin or a translation admin. Sometime the translation is left in the branch, and missed in the committing process because there are multiple translations for the same language, or it is not translated properly. The editors and administrators doesn’t always have the knowledge to decide whether the translation is OK or not, or consistent with the words and phrases used in other archetypes. This is why the new Translation Administrator is made, and the Clinical Program Board are about to define the requirements to possess such a role. Somehow there should be an appointment by “someone” representing each language, and the CKA’s could give that role to the appointed user.
Your branch laboratory analyte result with translation to Chinese (PRC) is now merged with the branch of Julio de Sosa, which had an updated translation to Spanish. And then committed to the trunk.
Ideally your translation should be through a translation review, or confirmed by a Translation Administrator (of Chinese (PRC)), but as we’re missing this, it was committed without.
