Item Import Data Format and Sample

Header

Required

Data Type

Data Requirements

ItemName

No

String

Summary:
The item name, which is typically auto generated for new items.

Notes:

If item name is omitted an item name will be generated using the Blueprint settings for new items. Item names must be unique for every item within your organization.

ItemType

No

String

Summary:
The item type being used.

(If field is omitted, a default of MC4 will be used)

To view list of Certiverse supported item types, visit the end of this article.

TopicDisplayID

No

String

Summary:
An existing Topic ID from the Blueprint into which the items are being imported.

Notes:

Only the lowest level Topic/Subtopic ID in a tree can be assigned

If the TopicDisplayID is omitted, the item will be assigned to "0. Unassigned Topic", and the items topic can be updated in Item Management after the item is imported

The string can have the character "#" at the beginning, which we strongly recommend, so that the Topic ID is not mistaken for a number value when editing data in applications like spreadsheets

Examples:

“#1.1” 

“1.2.1”

Exhibit

No

String

Summary:
Exhibit will be displayed split screen with the item during test delivery.

Notes:
See "Item Import with Formatting" and "Item Import with images"

Scenario

No

String

Summary:
Scenario is displayed during test delivery above the stem. The scenario can be stored separately from the stem to separate background information and the question.

Notes:
See "Item Import with Formatting" and "Item Import with images"

Stem

Yes

String

Summary: The stem of the item. Be sure to end each stem with a question mark or a colon.

Notes:

See "Item Import with Formatting" and "Item Import with images"

ResponseOption#

Yes

String

Summary:
The # response option for the item. "#" should be replaced with the response option number. The required response option columns in a file depends on the maximum number of response options for the Item Types contained in the file.

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.

If the number of response options for an Item Type is less then the response option column number, the field should be left empty. For example, if the item is a MC3 item (three option single response), the "ResponseOption4" will be empty.

Notes:

See "Item Import with Formatting" and "Item Import with images"

ResponseOption#IsKey

Yes

Boolean

Summary:
Indicates if the first response option is a correct answer.

Notes:

TRUE = Response is correct (key)
FALSE = Response is incorrect (distractor)

MC (single response, example item type "MC4") items can only have one ResponseOption#IsKey field be TRUE

MCR (multiple correct response, example "MCR5-2" items must have the number of correct options be TRUE.

For example:

MCR5-2 must have two ResponseOption#IsKey be TRUE

MC2 can only have one response option can be TRUE

ResponseOption#Rationale

Yes

String

Summary:

The rationale for the response option.

Notes:

See "Item Import with Formatting" and "Item Import with images"

Reference

No

String

Summary:

The reference(s) for the item.

Notes:

See "Item Import with Formatting" and "Item Import with images"

ItemTags

No

String

Summary:

Tags associated with the item.

Notes: 
Item Tag must already exist for the Blueprint.

Item Tag Value must be valid for the configured Item Tag. 

Item Tag and Tag Value should be data pairs separated by a colon.

Multiple Tag and Tag Values can be included, and should be separated by a semicolon.

Only one Tag Value per Tag 
Item Tag Values can have letters, numbers, periods, hyphens and spaces.

Item Tag Values cannot use punctuation, including commas or colon sign.

Example: “Color:Blue; Size:Medium”

Notes

No

String

Summary:

Any notes about the item.