Timed, unlimited submissions with a due date give students false impression they are able to complete the test even though due date has passed
Description
Attachments
is related to
Activity
Hudson CI Server March 5, 2014 at 3:22 PM
Integrated in sakai-trunk-java-1.7 #6 (See http://builds.sakaiproject.org:8080/job/sakai-trunk-java-1.7/6/)
SAM-1765: Timed, unlimited submissions with a due date give students false impression they are able to complete the test even though due date has passed (Revision 306817)
Result = UNSTABLE
Hui Tsao March 5, 2014 at 12:57 PMEdited
Stanford has made some changes in the Begin Assessment page to fix this issue. Please see the attached spec for detail (the three attachments which names start with CW-3181).
Jacqueline Mai September 7, 2012 at 1:13 AMEdited
Karen suggested that this JIRA should be separated into 2 since there are 2 issues at hand. The one having to do with the "Attempt to save your work automatically failed" popup is one issue. And, according to Karen, this issue is not related to timed assessment - it also happens to untimed assessment and involves auto-save. I can work with Karen to create a new JIRA to document this issue.
RE: what should happen if someone has already submitted once before the due date given the following variables: timed assessment, unlimited submissions with due date but no retract date and late submissions allowed?
If the student starts the assessment again before the due date, the student should not have the full time allowed. However, instead of adjusting the timer and automatically submitting when time is up, the student should be given a choice upfront - right after he clicks on the assessment title - whether to proceed with taking the assessment or not. If a student sees a warning that he only has 5 minutes to complete the assessment, he might very well decide that it's not worth his time to take the assessment again.
If the student has no submission prior to the due date and takes the assessment before the due date, he should be given the full time allowed. However, submission will be marked as late if submission happens after due date/time. Example, assessment is 30 minutes long, student starts test 10 minutes before due date/time, student will be given the full 30 minutes to complete but submission will be marked as late if not submitted within 10 minutes. Student should be alerted upfront RE: how much time they have to submit before it's marked as late.
If the student has no submission prior to the due date and takes the assessment after the due date, he should be given the full time allowed each time he takes the assessment. However, each submission will be marked as late.
Stanford UX is proposing these changes as part of the Settings page re-design. The changes call for a fairly significant change to how late handling is implemented so we'll have to decide if late handling re-design should be addressed sooner rather than later. Something to discuss during the next SAMigo Working Group call.
Hui Tsao September 6, 2012 at 1:35 PM
Just a note for everyone...
Stanford Ux is discussing the possible solution at this point. I believe Jackie will update the JIRA once they come up with a final solution.
Thanks,
Karen
Sam Ottenhoff September 6, 2012 at 1:18 PM
Hi Andrea,
Is this modification in oncourse trunk samigo code?
In a timed assessment, with unlimited submissions, having a due date (no retract date), the student can start an assessment again before the due date, the timer shows the full amount of time available even though the timer should have adjusted to the due date/time. Yet, when the student then tries to submit, the 'Late submission not allowed' page displays.
According to the 'Late Accepted' instructions:
"Late submissions WILL be accepted after the due date. However, this applies only to students who have not submitted their work prior to the due date. They will be given one chance to do so and their submission will be tagged as late."
In the case of my test, the student received 0 points because all questions were on one page and record last score is set. Also, "Attempt to save your work automatically failed" pop-up displays approx. at the time of the due date/time.
To reproduce:
Create an assessment that is timed, allows unlimited submission and has a due date. Select to record the last score.
Publish the assessment
As the student, submit the assessment once or more times before the due date.
A minute or so before the due date/time, start the test again.
Notice the full amount of time displays for the timer.
At approximately the due date/time moment, the "Attempt to save your work automatically failed" pop-up displays
Close the pop-up and continue working in your test
After the due date/time has passed, submit the test - 'Late submission not allowed' displays
As the instructor, check the submitted assessment
The student's last submission displays and shows:
Student took full 6 minutes
Student submitted late
Student received 0 points
Open the student's last submission - no questions are answered
-----------------------------
CO SP12 101 a 201250
https://qa29.longsight.com/portal/site/16567336-c764-4890-9e11-559ee351fa76
"0801B" :
Timed: 6 minutes
Due Date: 08/01/2012 10:05:00 AM
The complete Assessment is displayed on one Web page
Mark for Review checked
Unlimited submissions
Feedback on submission - release all
Record last score
Late Submissions accepted
Timed_Multi_DueDate.swf: Shows student view of second test
0801B_Sub_InstructorView.swf: Shows instructor view of submission
AttemptToSave.png - pop-up when student is in test for second time and due date/time passes