Localization of selected items in the case details screen

When using ‘select questions’, I was initially setting my item values to
identifiers like ‘health_center’, assuming I would later localize these
values. However, after seeing these non-localized identifiers displayed in
the case details screen, I switched to set the item value to the Spanish
localization of the identifier (e.g. “Centro de salud”).

After recently noticing some log warnings about including spaces and other
non-alphanumeric characters in my item values, I suspect I should switch
back to using non-localized text ids as the item values. However, if I make
this change, I’m not sure if/how I can have the correctly localized items
values displayed in the case details screen. Question: is this what the
’ID Mapping’ format in the case configuration is intended for? If so, could
you tell me the required syntax for this format?

Thanks, Ray

FYI. I have confirmed that the ‘ID Mapping’ format enables item value
localization in the case details view. After switching my application back
to using a ‘text id’ as the item value and configuring an ID mapping as
shown below, everything is working great!

https://lh4.googleusercontent.com/-PWHMG-g6gfk/TqWe-y5fwnI/AAAAAAAADwA/8eX40Ze3Yio/Referred%2520to%2520mapping.png
As a future extension of CommCare, it would be great if I could configure my
text mappings at the application or module level instead the form level.
So, for example, an application (or module) level text id could specify a
"short" translation of the “referred_to” text id as the case label and the
localized value of “referred_to_health_center” or “referred_to_hospital” as
the case value (see below). In my current design, I am using the same
identifiers as my form text ids, item values and case property names, so the
same text id could be specified once and used many times.

Referred to
RefTo
Where was the patient referred to

Health center

Hospital

I expect that a change like this would be non-trivial to implement, and you
likely have a better solution already in the queue.

Ray

Hi Ray,

Thanks for the self-solution and suggestion.

I believe the current most streamlined way of configuring translations is to
use the “save and load itext” features in vellum under “Experimental
Features”. You’re right that it would be quite a lot of effort to move the
translations to the application level, so we’re trying to streamline the
process of adding them as much as possible. Unfortunately it will probably
be some time before we are able to make the change you suggested.

thanks,
Cory

··· On Mon, Oct 24, 2011 at 1:24 PM, Ray Brunsting wrote:

FYI. I have confirmed that the ‘ID Mapping’ format enables item value
localization in the case details view. After switching my application back
to using a ‘text id’ as the item value and configuring an ID mapping as
shown below, everything is working great!

https://lh4.googleusercontent.com/-PWHMG-g6gfk/TqWe-y5fwnI/AAAAAAAADwA/8eX40Ze3Yio/Referred%2520to%2520mapping.png
As a future extension of CommCare, it would be great if I could configure
my text mappings at the application or module level instead the form level.
So, for example, an application (or module) level text id could specify a
“short” translation of the “referred_to” text id as the case label and the
localized value of “referred_to_health_center” or “referred_to_hospital” as
the case value (see below). In my current design, I am using the same
identifiers as my form text ids, item values and case property names, so the
same text id could be specified once and used many times.

Referred to
RefTo
Where was the patient referred to

Health center

Hospital

I expect that a change like this would be non-trivial to implement, and you
likely have a better solution already in the queue.

Ray