Regarding putting in all languages or not, there are competing interests which you have to balance. On one hand, having all languages in the question bank makes it easy to manage and control the edits made to each language. On the other hand, your question bank is going to get very large quickly, and certain functionality may slow down a bit if you have too many questions in there (e.g., searching or exporting the question bank). It will still be usable, but may be slower than you’re used to.
In addition, each time you want to build collections, exams, or create assignments in the system, remember to ALWAYS specify a language criteria in the searches, otherwise it will pull up not only the English questions, but also the other languages. The “Save Searches” function will allow you to build with the language criteria intact so that you don’t forget.
An alternative approach is one where:
1. Only the English questions go into the ExamDeveloper “Question Bank”
2. The SMEs make their changes as needed to those questions
3. The finalized English exams are built in ExamDeveloper and printed using the “Word” output button.
4. The Word version of the English Exam is uploaded as an Asset
5. The translators are given permission to view and modify the Assets. They are asked to download the English version and create their own target language version (if working from new document) OR revise their existing Target Language exam with “track changes” (if one already exists and only small changes are needed).
6. Once they are finished, they can upload their “Finished” exam for all of the target languages (You add the date of revision in the name so you can differentiate easily among older language versions).