You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a custom LTI variable that can be passed Canvas.assignment.allowedAttempts which indicates to a LTI tool how many attempts are allowed. However it seems like this tool only allows for a single attempt at the Qualtrics survey. It seems like it could be nice to pass this along and provide multiple attempts.
The easiest solution seems like to always take the last completed attempt, but an instructor may also want to take the highest or average score of multiple attempts which would take more work to implement both in the tracking and the UI.
The text was updated successfully, but these errors were encountered:
Interesting. Out of curiosity, what's the use case you're trying to support here? I can see how this is useful for a quizzing tool, but didn't even think of it as an option for a survey tool.
So thinking about it, the scoring issue probably wouldn't since these aren't specifically scored and they are associated with the same assignment. I think this request came in from an instructor that wanted students to be able to retake a survey on the same assignment and be able to see each attempt. I don't 100% know what their use case was, but I think it was to have a record a response each day for a week.
On a multiple attempt it just says "Thanks for taking the survey your response has been recorded".
There's a custom LTI variable that can be passed
Canvas.assignment.allowedAttempts
which indicates to a LTI tool how many attempts are allowed. However it seems like this tool only allows for a single attempt at the Qualtrics survey. It seems like it could be nice to pass this along and provide multiple attempts.The easiest solution seems like to always take the last completed attempt, but an instructor may also want to take the highest or average score of multiple attempts which would take more work to implement both in the tracking and the UI.
The text was updated successfully, but these errors were encountered: