Store Score Action

image\Actions_Score_Store.jpg

The Store Score action allows you to award points to Scoring variables when the user supplies a correct, incorrect or a partially correct answer to a question.

This action is normally triggered when a user selects their response to a question. For example, if you have added a True FalseQuestion Page from the Question Page templates, the True and FalseButton objects have a Store Score action on the Left Mouse Click trigger. Equally however, if you created your own drag and drop question, you could have a Store Score action activated when the user activates an Object Dropped trigger.

Note:
You don’t have to worry about the Scoring variables as Creator fills in the details for you, however, if you want to show the user their current score you will need to know which Scoring variables to use – see Preset Variables Glossary for a list of Scoring variables available in Creator.

Setting up the Store Score action:

  1. Add the Store Score action to your trigger, as described in adding actions. The Store Score tab will automatically appear when you add the action.

  2. Use the Store Score as panel to set if this action is adding points to the Scoring variables because the response by the user is correct or incorrect. Click Correct when the users response is the correct answer to the question, and Incorrect if it is not.

  3. A running total of correct answers are stored in the Scoring variable SCORE_CORRECT (e.g. 3 out of 5 are correct), while incorrect answers are stored in SCORE_INCORRECT variable. The SCORE_TOTAL variable shows the total number of questions answered.

  4. In the Score Value panel below you can set the user’s response as partially correct, for example, you can award 3 points out of 5 for giving this response.

  5. Use the Score this answer as worth box in the Score Value panel to enter the amount of points you want to award for the user’s response. This can be a positive or a negative number. Use the spin buttons to set the number or type it directly in the box.

Note:
Notice this is the amount of points awarded for the users response and NOT necessarily the total amount of points that can be awarded for this question – e.g. the user may get 3 points but 5 points could be the maximum they could get (see next point).

The number entered here is added or subtracted from the Scoring variable SCORE_VALUE, which contains the user’s current total score.

  1. Use the …out of box in the Score Value panel to enter the total number of points that could have been awarded for this answer. This can be a positive or a negative number. Use the spin buttons to set the number or type it directly in the box. This is useful for indicating that the chosen answer is not as valuable as an alternative.

This is most effective where only one answer can be chosen – otherwise more than one answer can contribute to the overall SCORE_VALUE_TOTAL – chosing one answer which scores 1 out 2 and another which scores 2 out of 2 would end up scoring 3 out of 4 when you may have wanted either 1 out of 2 or 2 out of the same 2. For this result you should mark each answer as worth 1 out of 1 and so getting both right will score 2 out of 2.

Note:
The number entered in this box is added to the Scoring variable SCORE_VALUE_TOTAL which is a running total of the maximum possible points awarded for all answers selected so far.

  1. Click on the Apply button to save your changes.

Understanding the Score Varaibles.

To facilitate multiple-response questions, weigthing and text input answers, the Creator scoring system is focussed on individual answers not questions. There may be more than one answer in a question which scores a mark, and some answers may score more than others. Creator does not support the Question Object found in Opus Pro so you will need to track question totals manually.

  1. SCORE – Manual – This is a variable for you to store custom scores independently of the Creator scoring system variables detailed below. Use the Set Variable or Add/Subtract actions to alter this variable to keep track of scores yourself. Useful for scoring in games which do not need the other scoring calculations.

  2. SCORE_VALUE – Automatic – Calculates the total value of scores for the answer so. Use this to display the points scored. For example, the user must answer find 4 correct questions with scores allocated thus: Q1 = 1, Q2 = 3, Q5 = 5 and Q6 = 2. If the user only selects the first three answers the score value would be 9. If all answers were selected the score would have been 11.

  3. SCORE_VALUE_TOTAL – Automatic – Calculates the total possible value of the answers which have been selected, whether the user answered the question correctly or not. This value will only differ from SCORE_VALUE if you are providing some answers which are given partial scores e.g: 1 point out of a possible 2 (suggesting that while this answer is correct another answer would be a fuller answer – this is particularly useful when scoring text input answers).

  4. SCORE_VALUE_PERCENT – Keeps track of the total value of available points as a percentage for a single question. It is not the total scored for all questions.

  5. SCORE_CORRECT – Automatic – This variable conatins the number of correct answers which have been given so, e.g. 5 out of 7 answers. If each question only has one answer then this will also be the number of questions answered correctly.

  6. SCORE_INCORRECT – Automatic – This variable contains the number of incorrect answers provided e.g. 2 out of 7 answers. If each question only has one answer then this will also be the number of questions answered correctly.

  7. SCORE_TOTAL – Automatic – Keeps track of the number of answers the user has given, whether that answer was correct or not. (It is not their total score, which is stored in SCORE_VALUE).

For example, if there are 10 questions with 4 possible answers to each (whether they are correct or not), the user has attempted 7 questions and clicked on 2 answers for each, but only got 4 correct, the SCORE_TOTAL would be 14 but the SCORE_VALUE would be 4. This variable allows you to check that the user has not simply clicked on every button and also a low number of answerts selected might indicate a lack of understanding.

  1. SCORE_PERCENT – Automatic – Calculates the percentage of answers which have been chosen correctly, for example 6 correct answers out of a possible 10 correct answers would produce a score of 60%, 6 out of 15 questions would be 40%.

  2. SCORE_TOTAL_POSSIBLE – Manual – A suggested variable in which to store the maximum possible score for the whole quiz/test irrespective of how many the user has answered. You need to calculate the value of all the answers in the test and then type this in via the Variables section of the Publication Properties.

  3. SCORE_CURRENT_POSSIBLE – Manual – User-defined variable to store the total possible score. It should be calculated as SCORE_TOTAL_POSSIBLE minus SCORE_VALUE_TOTAL using the Set Variable action on the Programming tab.

  4. SCORE_PASS_THRESHOLD – User-defined variable to store the score required to achieve a pass. This allows you to monitor the SCORE_CURRENT_POSSIBLE value against the Pass mark and force the user to go back over the training until a pass level is maintained. Or it useful to check that the final mark is adequate for a pass certificate.

Tracking Questions

You may want to keep track of the total number of points available for all questions. You would do this in a separate custom variable, so that at the end of the quiz you can tell the user the number of points awarded for each question answered. In this case, create a new variable in your publication and save the points awarded in it. You could use a standard Publication variable to save the data and add a Set Variable action to the same trigger as this Store Score action.

Alternatively, an Array variable would be a good method of saving the users points for each question, in which case you would add a Set Variable Array action to the same trigger as the Store Score action and add the users points to an element of the array.

Related Topics:

Introducing the Scoring Actions

Preset Variables Glossary