Navigation Menu

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

.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated based on changes to Cases

...

Here is a brief explanation of the files seen abovethat 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 related settingsall Questions included in the section.
  3. "Assessment_Matching<Form Name>.xml": represents the ExamForm nodes and related settingsthe 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. "11<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.


Warning

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

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

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.

Note

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.

Note

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