Navigation Menu

Click the "+" to see inside a chapter or use the search to the right.

.

Skip to end of metadata
Go to start of metadata

Once all the required modifications have been made and saved to the Exam Form configuration, you are ready to export the QTI Package file to be played in the Pearson VUE Player for the candidate to take the Exam. To generate this ZIP archive package file, click the Export button at the bottom. If you have made changes, you must click Save before clicking Export.

An Export options pop-up appears where you can decide how to generate the Question Review Form, which is a file named "Review.xml", that is also generated along with the other files in the export package. This file contains information about the list of Questions from the Exam Form.

The following selections are available in the Export options pop-up:

  • Generate question review form: The Question Review Form "Review.xml" is generated containing all the Questions from the standard Item Bank Project that are on the Exam Form.
  • Include items in delivery template item bank in review form: The Question Review Form "Review.xml" is generated containing all the Questions from the standard Item Bank Project that are on the Exam Form and also all the Questions that may be from the Delivery Template Item Bank via template applied to the Exam Form.

 

Icon

Questions in the Question Review Form are listed in the ascending Question ID order, regardless of whether the Question is from the standard Item Bank Project or from the Delivery Template Item Bank via template applied to the Exam Form. This is true even when the Question Review Form is divided into multiple files to include specific number of Questions per file, with the first file containing the start of the list of Questions.

 

The export begins when you click the Ok button. A progress indicator circular animation is shown while the QTI Export is generating. 

This may not be visible for smaller Exams because the QTI Export may happen very quickly, but it provides a good measure of the progress of the process for large Exam Forms. 

 

The ZIP file contains all the information about the examination along with the Exam Forms, Questions, and Assets. Shown below is an example of the contents of the ZIP archive.


Here is a brief explanation of the files that may be present within the zip file:

  1. "Itempool.xml": XML file containing information related to all the Questions.
  2. "AS1.xml": represents the unsectioned Section nodes and all Questions included in the section.
  3. "Assessment_<Form Name>.xml": represents the ExamForm nodes and the list of all sections in the Exam.
  4. "C<Case ID>.xml": represents Case Section nodes and all Questions included in the section.
  5. "ResourceMap.zip": This file contains "ResourceMap.xml" file used to define various display settings for Assets such as the scroll position and split screen state in the Pearson VUE Player.
  6. Image files (if any): Assets.
  7. "<Exam Name>.cpf": Pearson Compiler Project file, which can run in the Pearson VUE Player and play the examination.
  8. "manifest.xml": Manifest file. Identifies exam Language, and all the contents of the exam.
  9. "QAReview.xml": Group all items on one exam form for review purposes.
  10. "S<Section ID>.xml": represents Sections the user created and added to the Exam, and all Questions included in the section.


Icon

If you encounter this error while compiling your QTI, please consult with your application consultant.

Naming conventions followed by QTI Package files for idents with $ and #

Icon

For Section nodes:

When an Exam Form is exported to a QTI Package from the Delivery Configuration Tool page, the Section nodes are carried as XML files with the following naming conventions according to the format of their Idents:

  1. Alphanumeric Idents are carried as is. e.g., “Node1” is carried as “Node1.xml”.
  2. Section nodes in the first ExamForm node with Idents starting with a “, such as “$”, such as $S1, $S2, etc, are carried as AS1, AS2, etc. When there are Section nodes in the second ExamForm node, with similarly named Idents such $S1, $S2, etc, they are carried as BS1, BS2, etc. The alphabet is incremented by replacing the “$” when there are more ExamForm nodes.
  3. Section nodes in the first ExamForm node with Idents starting with a “, such as “#”, such as #S1, #S2, etc, are carried as 1S1, 1S2, etc. When there are Section nodes in the second ExamForm node, with similarly named Idents such #S1, #S2, etc, they are carried as 2S1, 2S2, etc. The numeric value is incremented by replacing the “#” when there are more ExamForm nodes.

For ExamForm nodes

ExamForm nodes (Assessment nodes) idents with # and $ also exhibit a similar behavior as Section nodes.


Under PearsonvuePrecondition (under ExamForm/Section nodes)

The $ and # replacement also happens on the following nodes LinkRefID attributes:

Variable Comparison (VARIABLE_COMPARISON)

Response Comparison (RESPONSE_COMPARISON)

Item State (ITEM_STATE)


The behavior is also seen for PearsonvueApplication - Calculator.

Icon

When an “&” (ampersand) symbol is used in a Question Stem or Answer Option, it is first carried to the “Itempool.xml” file.

 Therefore, a Question with a Stem having an “&” symbol as below,

 

will have a Stem entry in the “Itempool.xml” file as below,

 

where the “&” is replaced by “&amp;”, which is correct per HTML notation.

However, if the “Itempool.xml” is manually edited to change this entry to “&”, which is not its correct HTML notation, then it results in a compilation error in the Pearson VUE QTI Compiler and the compilation fails.

Icon

When any font attribute is modified for a MathML expression in the MathML window of any Question, an error message similar to the one shown below is generated in the Pearson VUE QTI Compiler and the compilation fails.

This can be fixed by editing the "Itempool.xml" with a text editor such as Notepad. Locate the affected code at the mentioned line number(s) and move the font attributes block (including mathsize, mathvariant, mathbackground, and mathcolor) from the <m:mrow> tag, into the <m:mtext> tag as shown in the example below

 

 

  • No labels