Defining Question Templates

Once you have your Content Grid completed, it's time to create your question templates to pull everything together. mLevel uses question templates to define the format and structure of each question presented in the games - they separate the pool of data that the Activities can use. Question templates are associated to specific game types and define the following:

  1. The question script, including both static (i.e. manually written) and dynamic (i.e. retrieved from content) parts of the question.
  2. A question template can leverage {{topic}}, {{attribute}}, {{item}} and {{value}}.  The minimum needed are either {{item}} or {{value}}.
  3. mLevel uses question templates to produce Multiple Choice or Multiple Correct questions and True False statements.

Below is an example of an actual question generated from a question template.  Notice how the dynamic content - the name of  the topic (2012 Smartphones), the Attribute (Manufacturer), and the value (Sony) - is incorporated within the static text starting with "Which of the following".  The answer will be the items.  Depending on what data is loaded to produce a question, mLevel will know with Item(s) are correct and use the other items randomly as wrong answers.



You can determine what your answer is made of by evaluating what elements you've included in your Question Template.

If you include a Value in your Question Template, then Item would be set as the answer. Vice versa... if Item is included in your Question Template, then Value would be set as the Answer.

For example, you wouldn't ask "what color is the iPhone 5?"  And have an Answer option of: iPhone 5.  In this case, since the Item (iPhone 5) was included in the Question Template, you would set the Answer type to Value (correct answer being Black & White).


Common Templates

Some Common examples of question templates are:

  • What is the definition of {{item}}?
  • The {{item}} is ___.
  • Where can you find the {{item}}?
  • How much does {{item}} cost?
  • {{Attribute}} is available in?
  • What {{attribute}} services are available under this plan?

Changing Capitalization in Templates

It is also possible to change the capitalization of your elements when they are pulled into templates so they make grammatical sense. For example, writing {{(lower-case item)}} instead of {{item}} will remove any capitalization of the term, so the words will not look strange if they are in the middle of a sentence. These modifiers are listed below:

  • Changing {{item}} to {{(lower-case item)}}: will remove capitalization of any words pulled into the template when using items
  • Changing {{value}} to {{(lower-case value)}}: will remove capitalization of any words pulled into the template when using values
  • Changing {{attribute}} to {{(lower-case attribute)}}: will remove capitalization of any words pulled into the template when using values
  • Changing {{topic}} to {{(lower-case topic)}}: will remove capitalization of any words pulled into the template when using values

Common Examples of Templates:

  • What is the definition of {{item}}?
  • Give an example of {{item}}.
  • Which key term/product could be described as {{value}}?
  • Select the {{(lower-case attribute)}} of {{item}}.


Putting Questions and Content Together

mLevel uses question templates to produce a pool of questions and answers.  The question templates are applied to your topic.  To get started, you may find it easier to write your question templates into your Excel document above the attribute(s) they apply to as seen in the example below:



Best Practices

  • To get started it is easier to write your Question Templates into your excel document above the attribute, as seen in the above example.
  • Keep in mind you do not have to use the Topic or Attribute in the Question Template.
  • Items, Attributes, and Topic names must be less than 80 characters, including spaces.
  • We suggest having at least 5 unique Values per Attribute (column).
  • Wrong answers or Values can be added in the very bottom row.
  • We suggest maintaining the same verb tenses and capitalization throughout the document.
  • Wrong answers (or distractors) pull from other correct values within the same column.  Make sure logical values are grouped together.
  • Where values are relevant for multiple items, word them identically and they will not be leveraged as distractors.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk