Reviewing Results in New Quizzes (with Respondus LDB)

Jump to solution
hhartkopf
Community Explorer

I am an instructor who recently gave a quiz using Canvas New Quizzes and Respondus LockDown Browser/Monitor. The students were able to take the quiz, but none of them were able to review the results. Whether they started in their normal browser or in the LDB, the quiz was listed as "Locked" and they could not see any results. Under the quiz's settings, I had verified that I had not restricted results; under Grades, I had posted the grade. No good.

I had the bright idea of removing the date the quiz was available until. Now that the quiz was no longer closed, the issue was fixed and my students could review the results.

Is there not a way to have the quiz closed (so students cannot continue to take it after the deadline) and also have the results viewable?

0 Likes
1 Solution
TanyaUponAvon
Community Explorer

So, it's May of 2024 now, and it seems that this problem still exists in Canvas with New Quizzes; however, there is a manual workaround. Let me see if I have this right: 

Problem: When you are using Lockdown Browser and Monitor for a quiz/exam, it isn't possible to show students their results in a review window.  

Workaround solution: You can select a time after the quiz/exam has been completed, at which time you:

  • Manually disengage Lockdown Browser and Monitor.
  • Make sure Mulitple Attempts is also disengaged.
  • Extend the available Until date until the end of the review window you are offering students.

Then, at the end of your scheduled student review window, you must manually re-engage Lockdown Browser and Monitor.

Does this sound correct? I will be testing this method as soon as I can.

Update: I submitted a request on the Ideas and Themes board because it doesn't seem that there currently is one. Here's the URL: https://community.canvaslms.com/t5/Canvas-Ideas/Allow-student-review-period-after-using-Respondus-Mo...
Please upvote/comment if you would like to see this issue resolved! 

Thanks!

View solution in original post