You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 23
Next »
Initial Considerations
The Multi-Language Management app (MLM) allows one to translate an entire project into various languages. This includes data entry forms, surveys, alerts, error notices, etc. REDCap does not perform the translations for you, but provides a streamlined framework. Settings configured at the project level speed the process of translation as opposed to configuring each and every field variable.
To enable the MLM, one must have Design & Set Up user rights. When accessed from the left navigation panel, one can define multiple languages in the project. Once configured the project language configuration can be copied to another project which has similar set up and field variables. The MLM allows you to convert languages in surveys, data entry instrument, alerts, and elsewhere throughout the project. You can activate any given language for a data entry or survey instrument. For example, a pre-survey instrument can have German / Spanish languages and a data entry form have no language translation enabled.
The MLM supports the e-consent framework. You are able to translate all the command language and everything you see as part of the e-Consents framework. Also, if you e-consent using the framework, the pdf consent form stored in the file repository will be in the language in which the participant took the survey. This will be beneficial for CFR Part 11 compliance for e-consent which requires it to be in the same language in which they consented.
The Process
Click here to expand...
Create project per normal process (define forms, create fields, events, etc.)
Click on MLM in Left Navigation panel under ‘applications’
Click ‘Add new language’
In the ‘Language ID’ box, add your desired Language ID
It is recommended to use the ISO code, such as 'en' or 'en-US' for English, or 'es' for Spanish. Use only letters and hyphen. View list of ISO 639-1 language codes within the application as needed
Enter your language ‘display’ name
Click ‘Import from file or system’
CRITICAL STEP!
The default selections are NOT used as a best practice
De-select to include the ‘translations of user interface items’
Select import ‘from available system languages’
Select your language from the drop down menu
Click ‘import’
Your page should now look similar to the below where English is the first language listed and is identified as the default language
The vertical yellow line on the left indicates current changes are not yet saved. Click Save changes
Save changes frequently and often to avoid re-work!
Select the participant's preferred language field
If you don’t yet have a preferred language field save you changes thus far and go create you field following the below guidance:
ensure the choices are labelled as the language code and not a numerical value:
example)
Activate your language(s)
Under the "Active Column" click the radio button to activate each language.
Only click the RTL radio button if the language should be read right to left (like Arabic)
Enable items & translate using the Forms/Surveys tab
Here you will toggle on which instruments will be used as ‘data entry’ and / or ‘survey’
Select your first language and enabled accordingly
Select you 2nd language and enable accordingly
Remember, you have to select the language at the top of this page that you wish to enable/translate
Remember to SAVE CHANGES frequently!
Once data entry/surveys have been enabled, it’s time to translate!
To begin translating items, select the desired language widget
Select ‘translate’ under the fields column
Translate each field on the screen
After you translate the field, a green icon indicates it is done.
If the field is not to be translated (eg you wish some fields to remain in the default language, click the box next to the field variable name
Translate any/all desired survey settings
Click through tabs to translate each of the topic areas (e.g. Forms/surveys, Alerts, etc.)
If your projects utilizes ASI’s (automated Survey Invites) you must select each ASI’s Language source. Best practice is to select the ‘language preference field’ for the best results!
Save Changes!
NOTE: When translating Alerts, ensure you set language source for each alert.
This drives the language for the alert.
As a best practice, the participants language preference field should be used.
Save changes and review your MLM setup for accuracy
Shortcut to save is by using your keyboard buttons (Control + S)
Test your project configuration in development mode for accuracy and adjust as needed
Additional Considerations
Click here to expand...
@LANGUAGE-CURRENT-FORM | Allows you to capture the currently used language in projects where multilingual data is enabled on data entry forms. The @LANGUAGE-CURRENT-FORM action tag can be used on fields of type 'Text Box' (no validation), and 'Drop-down List', or 'Radio Buttons' (these need to have choices whose codes correspond to the IDs of the defined languages - e.g., 'en'). This action tag is only active on data entry forms and will always, when possible, set the field's value to the currently active language. However, it has no effect when viewing survey responses. |
@LANGUAGE-CURRENT-SURVEY | Same as @LANUGAGE-CURRENT-FORM, but works only on survey pages. For multi-page surveys, @LANGUAGE-CURRENT-SURVEY needs to be used on a field of each page where capture of the language is relevant (e.g. for performing branching). |
@LANGUAGE-FORCE | When used on a field, the data entry form or survey on which the field is located will be rendered in the specified language (which must have been set up using the Multi-Language Management feature). The format must follow the pattern @LANGUAGE-FORCE="???", in which the ID of the desired language should be inside single or double quotes - e.g., @LANGUAGE-FORCE="de". Piping is supported - e.g., @LANGUAGE-FORCE="[field_name]" (if the source field is a radio field, make sure to add the :value qualifier). When the language is forced successfully (i.e., it exists and is active), the language selector is hidden. This action tag is evaluated when the form or survey loads. Using this together with @LANGUAGE-CURRENT-FORM/SURVEY on the source field for @LANGUAGE-FORCE may be used to 'lock in' a user to their selected language. |
@LANGUAGE-FORCE-FORM | Same as @LANGUAGE-FORCE, but the effect is limited to data entry forms (i.e. this does not affect surveys). |
@LANGUAGE-FORCE-SURVEY | Same as @LANGUAGE-FORCE, but the effect is limited to surveys (i.e. this does not affect data entry forms). |
@LANGUAGE-SET | When used on a Drop-down or Radio Button field only, this action tag will allow the field's value to control the currently shown language (in the same way as switching the language via the buttons at the top of the page). |
Please refer to the MLM FAQs Knowledge Article for additional information.