Viewing a learner’s submission history
Before you can check the answer or answers submitted by a learner, you need the learner’s username.
To review a response submitted by a learner, follow these steps.
- Find the problem you wish to review in the LMS
- Select Submission History below the problem
- Enter the username for the learner whose work you want to review, and then select View History
To close the Submission History Viewer, click on the browser page outside of the viewer, or press
Esc on your keyboard.
Interpreting a Learner’s Submission History
The Submission History Viewer shows every timestamped database record of the interactions between a learner and a problem, which can include processes completed both in the browser and on the server. These records appear with the most recent interaction at the top of the Submission History Viewer, followed by each previous interaction.
The records below provides an example submission history for a problem with guidelines that can help you interpret a submission history. The number and complexity of the records that appear in this report vary based on the type of problem and the settings and features defined.
Record 1: Problem Viewed (Server)
The first interaction, shown at the bottom of the Submission History, records when the server delivered the problem component to the browser for the learner to view, i.e. they loaded the page that the problem is on.
#1: 2015-09-04 08:34:53+00:00 (America/New_York time) Score: None / None { "input_state": { "e58b639b86db44ca89652b30ea566830_2_1": {} }, "seed": 1 }
Record 2: Problem Checked (Browser)
The next interaction shown as you scroll up from the bottom records when the learner selected
Submit in the browser to submit an answer. Note that this record does not contain the actual answer submitted.
#2: 2015-09-04 08:35:03+00:00 (America/New_York time) Score: 0.0 / 1.0 { "input_state": { "e58b639b86db44ca89652b30ea566830_2_1": {} }, "seed": 1, "student_answers": { "e58b639b86db44ca89652b30ea566830_2_1": "choice_1" }
Record 3: Problem Checked (Server)
The next interaction records the results of the server processing that occurred after the learner submitted the answer. This record includes
student_answers
with the submitted answer value, along with attempts
, correctness
, and other values.
#3: 2015-09-03 18:15:10+00:00 (America/New_York time) Score: 0.0 / 1.0 { "attempts": 1, "correct_map": { "e58b639b86db44ca89652b30ea566830_2_1": { "answervariable": null, "correctness": "incorrect", "hint": "", "hintmode": null, "msg": "", "npoints": null, "queuestate": null } }, "done": true, "input_state": { "e58b639b86db44ca89652b30ea566830_2_1": {} }, "last_submission_time": "2015-09-03T18:15:10Z", "seed": 1, "student_answers": { "e58b639b86db44ca89652b30ea566830_2_1": "choice_1" } }
Record 4: Problem Retried (Browser)
When a problem gives learners multiple attempts at the correct answer, and the learner tries again, an additional record is added when a learner selects
Submit again. The server has not yet processed the new submission, so the data in the record is almost identical to the data in record 3.
Record 5: Problem Retried (Server)
The most recent interaction in this example records the results after the learner attempts the problem again and submits a different answer. Note the differences between values in this record and in record 3, including the reported
Score
and the values for student_answers
, attempts
, andcorrectness
.
#5: 2015-09-03 18:15:17+00:00 (America/New_York time) Score: 1.0 / 1.0 { "attempts": 2, "correct_map": { "e58b639b86db44ca89652b30ea566830_2_1": { "answervariable": null, "correctness": "correct", "hint": "", "hintmode": null, "msg": "", "npoints": null, "queuestate": null } }, "done": true, "input_state": { "e58b639b86db44ca89652b30ea566830_2_1": {} }, "last_submission_time": "2015-09-03T18:15:17Z", "seed": 1, "student_answers": { "e58b639b86db44ca89652b30ea566830_2_1": "choice_2" } }