# Multiple translators

**URL:** <https://discourse.openehr.org/t/multiple-translators/15587>\
**Category:** Clinical (archive)\
**Created:** [13 March 2015 15:06 UTC](https://discourse.openehr.org/t/multiple-translators/15587 "2015-03-13T15:06:39Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![siljelb](https://discourse.openehr.org/user_avatar/discourse.openehr.org/siljelb/32/12_2.png) [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Post date:** [13 March 2015 15:06 UTC](https://discourse.openehr.org/t/multiple-translators/15587/1 "2015-03-13T15:06:39Z")

</div>

Hi,

At the Norwegian CKM [http://arketyper.no](http://arketyper.no), we’ve been doing quite extensive translation of international (English language) archetypes into Norwegian. During this process, we’re finding more and more translation isn’t a one-person job, but usually there’s a primary translator and one or more secondary translators. As of now there seems to be only one field in which to put translator information, so to attribute more than one person as the archetype translator, we need to put more than one name, organisation, etc into the same fields. This sort of works, but it’s not exactly elegant. Is there a better way to do this, either right now or in the works?

Kind regards,  
**Silje Ljosland Bakke**

Special Adviser, RN

R&D dept, E-health section, Bergen Hospital Trust

Coordinator, National Editorial Board for Archetypes, National ICT Norway

Tel. +47 40203298

Web: [http://arketyper.no](http://arketyper.no/) / Twitter: [@arketyper\_no](https://twitter.com/arketyper_no)

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [13 March 2015 15:34 UTC](https://discourse.openehr.org/t/multiple-translators/15587/2 "2015-03-13T15:34:06Z")

</div>

Hi Silje,

Having been in that position as a translator a couple of times, I think we put all our names in the field at that time.  
This of course isn’t ideal if you have two or more translators that share the work equally.

However, it is the same with the original\_author field - no real-world archetype has very been created by one person only.

Therefore, we have introdued the idea of other\_contributors already where editors, reviewers etc. are given credit.  
This is where potentially other translators could be added as well, e.g. if there is a prime/lead translator and several who check the translation.

BTW, for this checking translations, there is also the possibility to conduct translation reviews in CKM (ideally after the content has been published or it will be too burdensome I believe).

Cheers  
Sebastian

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [13 March 2015 15:38 UTC](https://discourse.openehr.org/t/multiple-translators/15587/3 "2015-03-13T15:38:03Z")

</div>

Hi Silje,

The current AOM has an other\_details attribute inside TRANSLATION\_DETAILS which would allow something like

other\_details =\<  
[“secondary\_translators”] = \<“Ian McNicoll, freshEHR, UK”, “Sebastian Garde, Ocean Informatics, DE”\>

> 

would that be enough, or do we need accreditation details for each translator? That would need a change to the Archetype Object model - easy to do but not until we get ADL 2.0 tooling.

Ian

---

<div class="post-metadata">

**Author:** ![mikael](https://discourse.openehr.org/user_avatar/discourse.openehr.org/mikael/32/881_2.png) [@mikael](https://discourse.openehr.org/u/mikael)\
**Post date:** [13 March 2015 16:02 UTC](https://discourse.openehr.org/t/multiple-translators/15587/4 "2015-03-13T16:02:04Z")

</div>

Hi,

If someone is interested in and would like to have some inspiration from how different IHTSDO member countries have dealt with translations of SNOMED CT descriptions (“terms”), the documents “Translation Guidelines” and “Translation Management Guidelines” can be found at the address [http://www.ihtsdo.org/snomed-ct/snomed-ct-worldwide/translations-of-snomed-ct](http://www.ihtsdo.org/snomed-ct/snomed-ct-worldwide/translations-of-snomed-ct) . (I guess that openEHR doesn’t have similar documents?)

Regards

Mikael

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [13 March 2015 17:04 UTC](https://discourse.openehr.org/t/multiple-translators/15587/5 "2015-03-13T17:04:23Z")

</div>

Hi Ian,

Yes, I agree that that is a better place - but I think you will find that while this is in the rm, tooling support for TRANSLATION\_DETAILS/other\_details it is rather poor at present.

In CKM, we could add something like this to the translation pages, which would make it easy for the (main) translator to add this.

Sebastian

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [13 March 2015 17:09 UTC](https://discourse.openehr.org/t/multiple-translators/15587/6 "2015-03-13T17:09:47Z")

</div>

Hi Sebastian,

I have looked at the AE code and I think it may be a relatively simple fix that mirrors the work done for the general other\_details section to support namespaces etc.

I will have a crack at updating AE and upload them to the Test CKM to see how we get on.

Ian

---

<div class="post-metadata">

**Author:** ![yampeku](https://discourse.openehr.org/user_avatar/discourse.openehr.org/yampeku/32/25_2.png) [@yampeku](https://discourse.openehr.org/u/yampeku)\
**Post date:** [13 March 2015 17:31 UTC](https://discourse.openehr.org/t/multiple-translators/15587/7 "2015-03-13T17:31:49Z")

</div>

Using LinkEHR you can define the other\_details in translations. We added an export function in order to generate archetypes as the AE is expecting (i.e. parse), so using LinkEHR once should not really be a problem 😉

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [14 March 2015 14:14 UTC](https://discourse.openehr.org/t/multiple-translators/15587/8 "2015-03-14T14:14:57Z")

</div>

er hang on - can we see a clear proposal first for:

&nbsp;&nbsp;\* the ideal solution - what we would do in ADL/AOM 2 - preferably  
&nbsp;&nbsp;&nbsp;&nbsp;somewhere under this wiki page  
&nbsp;&nbsp;&nbsp;&nbsp;\<[https://openehr.atlassian.net/wiki/display/ADL/ADL+2+Specifications&gt](https://openehr.atlassian.net/wiki/display/ADL/ADL+2+Specifications&gt);  
&nbsp;&nbsp;\* possible approaches to ADL 1.4 (preferably on this page  
&nbsp;&nbsp;&nbsp;&nbsp;\<[https://openehr.atlassian.net/wiki/display/ADL/ADL+1.4+Change+Requests&gt;\](https://openehr.atlassian.net/wiki/display/ADL/ADL+1.4+Change+Requests&gt;%5C))  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;o short term - e.g. 'other\_translators' inside 'other\_details'  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ does this include deeper structure or not  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;o medium term - any kind of ADL 1.5/1.6 change that actually could  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;be implemented in current tools like AE, with on-the-fly  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;conversion of existing archetypes  
&nbsp;&nbsp;\* CKM changes

We don't want to create too much rework for later.

- thomas

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [14 March 2015 16:15 UTC](https://discourse.openehr.org/t/multiple-translators/15587/9 "2015-03-14T16:15:06Z")

</div>

Sure - happy to wait until Silje and other clarify the level of detail needed.

Ian

---

<div class="post-metadata">

**Author:** ![siljelb](https://discourse.openehr.org/user_avatar/discourse.openehr.org/siljelb/32/12_2.png) [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Post date:** [17 March 2015 10:17 UTC](https://discourse.openehr.org/t/multiple-translators/15587/10 "2015-03-17T10:17:37Z")

</div>

For now, the other\_details attribute within TRANSLATION\_DETAILS should do the trick. The main issue is to keep the different translators separated, which this seems to do:

other\_details =\<

[“secondary\_translators”] = \<“Ian McNicoll, freshEHR, UK”, “Sebastian Garde, Ocean Informatics, DE”\>

> 

The main issue is probably getting support for this in the tooling (ie Archetype Editor and the CKM)?

Mvh.  
**Silje**

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [17 March 2015 10:25 UTC](https://discourse.openehr.org/t/multiple-translators/15587/11 "2015-03-17T10:25:08Z")

</div>

If I add the equivalent of this to ADL/AOM 2, will it be enough for the future? - thomas

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [17 March 2015 10:32 UTC](https://discourse.openehr.org/t/multiple-translators/15587/12 "2015-03-17T10:32:36Z")

</div>

There is also an older related issue on the specs tracker This issue highlights some potential problems as well, but doesn’t have a clear solution yet. I believe it should be considered at the same time. Cheers Sebastian

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [17 March 2015 10:52 UTC](https://discourse.openehr.org/t/multiple-translators/15587/13 "2015-03-17T10:52:37Z")

</div>

Right - exactly. Ideally, we need people who are developing archetypes and think there are limitations to say what they are. It isn't that hard to add more comprehensive meta-data to an archetype for translations, other\_contributors etc. Of course, we don't want to go overboard - using links / addresses to other resources is good too.

Once changes are agreed, they can be put in ADL 2, and the ADL Workbench and other tools can fairly easily upgrade the existing archetypes into new structures.

- thomas

---

<div class="post-metadata">

**Author:** ![Peter\_Gummer1](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/p/258eb7/32.png) [@Peter\_Gummer1](https://discourse.openehr.org/u/Peter_Gummer1)\
**Post date:** [17 March 2015 11:14 UTC](https://discourse.openehr.org/t/multiple-translators/15587/14 "2015-03-17T11:14:04Z")

</div>

Sebastian Garde wrote:

> There is also an older related issue on the specs tracker  
> [https://openehr.atlassian.net/browse/SPECPR-24](https://openehr.atlassian.net/browse/SPECPR-24)  
> This issue highlights some potential problems as well, but doesn’t have a clear solution yet.
> 
> I believe it should be considered at the same time.

Hmmm, yes, 2009 … that is old. Here’s another oldie that we never got around to acting on as well. It talks about needing to know who the terminologist was …

[https://oldocean.atlassian.net/browse/EDT-591](https://oldocean.atlassian.net/browse/EDT-591)  
_(Inaccessible to non-Ocean people, and probably most Ocean people would have lost their logins to this old Jira issue tracker too) …_

1. [Archetype Editor](https://oldocean.atlassian.net/browse/EDT)
2. [EDT-591](https://oldocean.atlassian.net/browse/EDT-591)

Need ability to enhance the archetype translator details and to add a Terminologist doing the bindings

Reporter:HeatherLeslieCreated:21/Jan/10 7:25 PM

Need ability to add Terminologist to the Archetype and enhance the metadata about the Translator to cater for CKM requirements re identifying the primary people doing the initial authoring of the translation/binding plus those who contribute to the reviews of translations/bindings  
These requirements are becoming a high priority in CKM development

- Peter

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)\
**Post date:** [17 March 2015 11:34 UTC](https://discourse.openehr.org/t/multiple-translators/15587/15 "2015-03-17T11:34:10Z")

</div>

Ian, is your proposal actually valid in 1.4?  
My understanding is that other\_details is a Hash\<String, String\>.

secondary\_translators is the key, but “Ian…” and “Sebastian…” are two values - which is not possible (and probably not really desirable fpr general other\_details either)

A further minor point, I would prefer other\_translators over secondary\_translators for consistency with other\_contributors.

Sebastian

---

<div class="post-metadata">

**Author:** ![siljelb](https://discourse.openehr.org/user_avatar/discourse.openehr.org/siljelb/32/12_2.png) [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Post date:** [17 March 2015 14:38 UTC](https://discourse.openehr.org/t/multiple-translators/15587/16 "2015-03-17T14:38:32Z")

</div>

The way I see it the whole translation author block should ideally be repeatable, including separate elements for name, organisation, email and accreditation, which would of course require the accreditation element to ble moved inside the author block (why isn’t it there in the first place?).

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [17 March 2015 16:30 UTC](https://discourse.openehr.org/t/multiple-translators/15587/17 "2015-03-17T16:30:09Z")

</div>

The current block looks like the following (from a test archetype):

language  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;original\_language = \<[ISO\_639-1::en]\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;translations = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["fr"] = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;language = \<[ISO\_639-1::fr]\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;author = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["name"] = \<"Frederik Tyler"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["email"] = \<"freddy@something.somewhere.co.uk"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;accreditation = \<"British Medical Translator id 00400595"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["ru"] = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;language = \<[ISO\_639-1::ru]\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;author = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["name"] = \<"Nina Alexandrovna"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["organisation"] = \<"Dostoevsky Media Services"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["email"] = \<"nina@translation.dms.ru"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;accreditation = \<"Russian Translator id 892230-3A"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>

Is this enough?

language  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;original\_language = \<[ISO\_639-1::en]\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;translations = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["fr"] = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;language = \<[ISO\_639-1::fr]\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;author = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["name"] = \<"Frederik Tyler"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["email"] = \<"freddy@medicaltranslation.co.uk"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["xxxx"] = \<"yyyyy"\>  
\*\*\*\*\*["accreditation"] = \<"British Medical Translator id 00400595"\>\*  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
\* other\_contributors = \<"Bonnie Tyler \<\*\*bonnie@medicaltranslation.co.uk\>", \*\*"Yannick Guillou\<yg@francaistrad.fr\>"\>\*

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["ru"] = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;language = \<[ISO\_639-1::ru]\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;author = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["name"] = \<"Nina Alexandrova"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["organisation"] = \<"Dostoevsky Media Services"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["email"] = \<"nina@translation.dms.ru"\>  
\* ["accreditation"] = \<"Russian Translator id 892230-3A"\>\*  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
\* other\_contributors = \<"Marcus Barakov\<marcus\*\*@medicaltranslation.co.uk\>", \*\*"Irina Pavlova\<irina@emias.ru\>", "Iliana Markova \<iliana.markova@gorodskaya.ru\>"\>\*  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>

or do we need more?

- thomas

---

<div class="post-metadata">

**Author:** ![siljelb](https://discourse.openehr.org/user_avatar/discourse.openehr.org/siljelb/32/12_2.png) [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Post date:** [17 March 2015 19:53 UTC](https://discourse.openehr.org/t/multiple-translators/15587/18 "2015-03-17T19:53:04Z")

</div>

If given complete freedom (possibly not a good idea), I’d prefer something like the following:

`language`  
`original_language = <[ISO_639-1::en]>`  
`translations = <`  
`["fr"] = <`  
`language = <[ISO_639-1::fr]>`  
`author = <`  
`["name"] = <"Frederik Tyler">`  
`["email"] = <``["freddy@medicaltranslation.co.uk"](mailto:freddy@medicaltranslation.co.uk)``>`  
`["xxxx"] = <"yyyyy">`  
`**["accreditation"] = <"British Medical Translator id 00400595">**`  
`>`

`author = <`  
`["name"] = <"Bonnie Tyler">`  
`["email"] = <``[" **bonnie@medicaltranslation.co.uk**"](mailto:freddy@medicaltranslation.co.uk)``>`  
`["xxxx"] = <"zzzz">`  
`**["accreditation"] = <"Whatevs">**`  
`>`

`author = <`  
`["name"] = <" **Yannick Guillou**">`  
`["email"] = <``[" **yg@francaistrad.fr**](mailto:freddy@medicaltranslation.co.uk)``">`  
`["xxxx"] = <"aabb">`  
`>`  
`**other_contributors = <”Jules Verne <[jules@nautilus.fr](mailto:jules@nautilus.fr)**`` **>** ``**”, “Victor Hugo <[vic@hunchback.net](mailto:vic@hunchback.net)**`` **>** `` **”>** `  
`>`  
`>`

``

However, the` other_contributors-`only variant will probably work just fine for now if that’s implementable in the shorter term.

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [17 March 2015 20:33 UTC](https://discourse.openehr.org/t/multiple-translators/15587/19 "2015-03-17T20:33:25Z")

</div>

this is doable as well, except not quite like that - multiples of the same thing have to have unique keys, so it would be more like the following. I also added in the 'version\_last\_translated' which was agreed in principle recently.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;translations = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["fr"] = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;language = \<[ISO\_639-1::fr]\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;authors = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["frederiktyler"] =\<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["name"] = \<"Frederik Tyler"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["email"] = \<"freddy@medicaltranslation.co.uk" \<mailto:freddy@medicaltranslation.co.uk\>\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["xxxx"] = \<"yyyyy"\>  
\* ["accreditation"] = \<"British Medical Translator id 00400595"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>\*

["bonnietyler"] = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["name"] = \<"Bonnie Tyler"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["email"] = \<"\*\_bonnie@medicaltranslation.co.uk\_\*" \<mailto:freddy@medicaltranslation.co.uk\>\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["xxxx"] = \<"zzzz"\>  
\* ["accreditation"] = \<"Whatevs"\>\*  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>

["yannickguillou"] = \<  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["name"] = \<"\*Yannick Guillou\* "\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["email"] = \<"\*\_yg@francaistrad.fr\_\* \<mailto:freddy@medicaltranslation.co.uk\>"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;["xxxx"] = \<"aabb"\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
\*other\_contributors = \<”Jules Verne \<jules@nautilus.fr \<mailto:jules@nautilus.fr\>\*\*\>\*\*”, “Victor Hugo \<vic@hunchback.net \<mailto:vic@hunchback.net\>\*\*\>\*\*”\>\*  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;version\_last\_translated = \<"2.0.1"\>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\>

However.. it's not clear who did the most recently translation, and who only did some old translation. How do we deal with representing what's a current picture of affairs? It might not matter - it's ok if we assume that the translation work is recorded in some registry for example. Finding the balance is the challenge.

- thomas

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [20 March 2015 11:25 UTC](https://discourse.openehr.org/t/multiple-translators/15587/20 "2015-03-20T11:25:44Z")

</div>

Anyone have further thoughts on this - if changes are to go into ADL2 for this, we need them sooner rather than later.

thanks

- thomas

[Next page](https://discourse.openehr.org/t/multiple-translators/15587.md?page=2)