2022-04-06 - Translation User Group Meeting

Shaping our collaboration with SNOMED International;

Translation process uncovers errors, which are too many to submit through regular SLA.

SI has now created a separate CRS project which the group can use to submit duplicates, spelling mistakes, obsolete concepts etc.

How do we shape the collaboration?

Rory: use batch requests, which are vetted every biweekly meeting. We will do so every biweekly meeting.

Camilla: can we submitters do anything to make it easier?

Monica: note distinction between simple and complex changes, e.g. in justification field

What to do for concepts that require a text definition, because we don't understand them?

Monica: submit that through freshdesk - i.e. send email to info@snomed.org, that will create a freshdesk ticket.

If we have a concrete proposal, we can submit that through CRS; that does require an authoritative source though.

Stefan: top level nodes and semantic tags can be difficult to translate, but actually guidance as to their intended meaning is available in the documentation. Could these be added as / reworked into text definitions, so they are visible in the browser?

Monica & Rory: something for the content team to discuss. Possibly it should be done in the MRCM, or as an annotation.

Guillermo: editorial guidance has been much improved, but it is increasingly difficult to keep up-to-date with it. We would like to have some kind of permalink in the editorial guide. Their translators link their ECL to editorial guidance, but that requires stability or more atomic items. To stay up to date we need more editorial guidance + link to specific concepts it pertains to. It would be good to be able to partition updates into particular projects / work packages. 

Monica: is the early visibility page helpful? Link: 2022 Early Visibility Release Notifications

Guillermo: yes, but the quantity of changes (translation, modelling patterns) increases the burden on NRC's to keep up.

Monica: we can add one of the SI terminologists to the group, to keep us posted on updates to naming conventions etc.

Marie-Alexandra: Possibly in future we could propose / work the change ourselves, review as a group, which would then be reviewed by a SI terminologist; collaborative authoring.

Rory and Monica will come back with a proposal towards achieving this.

 Current version can be found at https://confluence.ihtsdotools.org/download/attachments/82871138/IHTSDO_Guidelines_Management%20Translation%20SCT%20-%20FH%20-%2020220402.docx?api=v2

Next meeting: review chapters 1 & 2.

https://confluence.ihtsdotools.org/display/TRANSLATIONUSERGROUP/Training+material+for+translators

Guillermo: identify different translation roles in combination with their requirements. E.g. proficiency in CRS; basic terminology principles. 

Terminology user group could test new foundation course for usefulness to translators, and also identify any modules they would also require. The same for authoring level 1 & 2 courses; some of those things could be useful to translators.

Possible to watch only certain modules? E.g. only product hierarchy & substance hierarchy for those who translate clinical drugs.

Editorial guide is too much to ask for translators; but a summary of naming conventions would be a useful subset to work with.

Ole: can we create a matrix of roles & competencies, with directions to the materials that explain those competencies? Identify competencies first; then see if there is sufficient material. 

Ole & Guillermo will create a matrix of competencies, taking the matrix from the Authoring Level courses as a starting point. 

Also we should negotiate with the e-learning committee to make such modules available outside the actual courses

Stefan: to what extent can the Spanish translations be considered to be as authoritative as the English?

Guillermo: I prefer to only use the English; though we are very experienced it is difficult to keep up to date with all the changes. Using addition