need a log file for submissions
Description
is duplicated by
is incorporated by
Activity
Matthew Jones September 21, 2016 at 2:10 PM
This was incorporated by https://sakaiproject.atlassian.net/browse/SAM-1368#icft=SAM-1368
Mathieu Plourde October 2, 2009 at 10:13 AM
Hi Charles,
Would you consider the downloads human readable by faculty members? I wonder why there wouldn't be a GUI for this info that would be searchable, sortable, and using real student names, assignments, and IDs, something that would give Instructors the power to troubleshoot quickly when a student implies that they have submitted an assessment and that the system doesn't show it... Maybe it's simply a matter of adding an option in the current system to show "Unsubmitted attempts" as well and submitted ones... Any thoughts on this?
WebCT did a great job at this. A table would show a list of students with their final grade, then a list of attempts. By clicking on an attempt number, the instructor could drill down to see what has been recorded, or simply visualize all the user's actions (answered question 2 at 12:45:23, saved question 2 at 12:45:45, skipped question 3 at 12:46:49, test submitted for grading at 12:56:32, etc.). Attempts sent automatically as time expired could be flagged so instructors could pay attention to them.
Charles Hedrick October 2, 2009 at 9:07 AM
Actually at Rutgers our download function includes both assessments submitted and not submitted. So the faculty member can see anything that a student has saved, submitted or not. When combined with autosave, you can see just about everything. This has greatly reduced the student disputes we've had to process. Even if the system somehow missed a submit, we have the contents.
We also have a facility for faculty to see attachments uploaded for assignments even if the student didn't submit the assignment. I've thought of adding autosave to assignments, but I suspect that most people use attachments rather than authoring substantial items in the tool.
These are both JSP's that require no modification to Sakai to use, although we add links to them from Samigo and assignments, respectively.
Mathieu Plourde October 2, 2009 at 7:56 AM
All submitted and unsubmitted tries should be recorded and visible to the Instructor and the student.
Also relates to https://sakaiproject.atlassian.net/browse/SAK-15073#icft=SAK-15073 and https://sakaiproject.atlassian.net/browse/SAM-595#icft=SAM-595
Comment from an Instructor at Delaware:
"The students would still have to "submit for grading" the entire assessment in order for me to see it, wouldn't they? Which means that saving each answer vs. saving the whole assessment for later doesn't make a difference. This seems not to be like WebCT, where I was able to see all of the answers that they saved, even if they didn't click the "finish" button before the closing time of the assignment."
UD Jira reference: UDSAKAI-193
Lydia Li April 20, 2008 at 4:47 PM
We added event logging, that might help a little.
We've had a few cases of students who claimed to have submitted a test, but we can't find it. So far none of these has resulted in any formal action, but I'm concerned that at some point it could have enough effect on a grade that we would be asked to explain. I think a dean might not be satifised with "we don't think Samigo has any bugs that would result in losing a submission."
I'd like to see a separate log file, to which entries are written right before the screen displayed to the user confirming submission. We need to make sure we can prove that the user doesn't get that screen unless a log entry has been successfully written. I would be willing to say that it is essentially impossible for us to lose both the data for an assessment in the database and an entry in a log file that is being written sequentially. I'd also like to see events written to the events table. Obviously we need an event for submission, but I'd like to see intermediate entries in either the events table or the log file showing when a student starts an assessment and maybe even as they progress through it. That would help us find out whether the student didn't start the test at all or something went wrong at the final submission.