Item Translations Import Data Format
Header |
Required |
Data Type |
Data Requirements |
ItemName |
Yes |
String |
Summary: Notes: Must match an existing Item Name for the Blueprint, and existing translations cannot be overwritten. |
Scenario |
Yes, if used for source language |
String |
Summary: Notes: |
Stem |
Yes |
String |
Summary: The stem of the item.
Notes: See "Item Import with Formatting" and "Item Import with images" |
ResponseOption# |
Yes, if used for source language |
String |
Summary: The response option number starts with 1 and goes to the number of response options for an item type. For example, a MC4 (four option single response item) requires four columns with the header "ResponseOption1", "ResponseOption2", "ResponseOption3", and "ResponseOption4"; and each of the columns must be populated for that item row.
Response options not used for a given Item Type should be left empty. For example, ResponseOption4 will be empty for a MC3 item (three option single response)
Notes: See "Item Import with Formatting" and "Item Import with images" |
Item Translation without Exhibit Import Sample File
- Item Translation Import Sample.csv
- Sample file with multiple item types containing translations in Spanish
- Items in the file match the Item Import Data Format and Sample File, and will allow user to add translation to the sample items
- Additional columns then those listed above will be ignored
- The item export contain additional columns, and is frequently used for translations outside the system.
- The item export file can be updated with translation to the fields listed above, and additional columns will be ignored.
For additional guidance, explore our How-to Step-by-Step guide available [here].
Contact Us
If you have any questions or need additional assistance, please contact us by either emailing support@certiverse.com or by submitting a ticket from this article.