SQL for Data Analytics · Checking submissions

Checking submissions

What's in a file

A submission is a text file named for the unit and the student, like sql-practice-unit02-querying-single-tables-jordan-lee.txt. You can open it in any text editor.

The top is a summary: the unit, the student's name, when the file was made, how many questions are done, and a line per question with its status, the number of attempts, and when it was answered. Under that is the full history of everything they ran, and the checksum is the last line.

For completion grading, the line that says Done: 15 of 15 is usually all you need.

The grading tool

Open the grading tool ↗

It's also item 4 in the sidebar of this unit, so you don't have to come through this page.

In Canvas, open the assignment and choose Download Submissions. You get one zip file. Drop that zip on the grading tool, or use Add submissions. For one file, like a late submission, Paste one takes the contents of the file pasted in. Copying it straight out of SpeedGrader's preview works. Select all, copy, paste. Anything above the title line or after the checksum is ignored, and the line wrapping the preview adds is undone before the checksum is verified. The student is matched by the name in the file, and if their Canvas download turns up later, the two are joined under the Canvas ID. If you add the wrong file to somebody, remove this file on their page takes it out so you can add it again.

Nothing is uploaded anywhere. The files are read in your browser and kept in your browser, so the record builds up over the quarter. Export data saves everything to one file. Adding that file back, in this browser or another one, restores it.

Adding the same download again is safe. The tool keeps one file per student per assignment, the newest one, going by the time stamped inside the file. So you can download everything from Canvas again a week later and drop it in. Files it already has are skipped, and you're told how many. New students show up tagged new. A student who turned in a newer file shows up tagged updated, or resubmitted if you had already marked them graded.

Marking things graded is how you keep your place. Tick the students you've looked at in the list and click Mark selected as graded, or mark them one at a time from the student's page, or mark the whole assignment at once. The list can be sorted with the ones still to grade first, and the first screen shows how many are waiting in each assignment.

Getting around. The buttons at the top of the page show where you are: all assignments, then the assignment, then the student. Click one to go back to it. Inside an assignment, the list on the left has the class summary at the top and then every student.

All assignments is the first screen. It lists each assignment with how many are left to grade, how many students turned it in, how many finished everything, and how many are flagged. Under that is every student against every unit. Click a cell to open that student's work.

An assignment has the students down the left, each with a dot and how many questions they finished. Green means nothing is flagged. On the right are the numbers for the whole class: how many finished everything, the average number of tries, and for each question how many finished it, the mean and median tries, and how many got it on the first try. Students who turned in other assignments but not this one are listed at the bottom.

A student shows everything they ran, question by question, with the time and the result of each try.

The flags

Every file is checked when it's added, and every pair of files in an assignment is compared. A student's dot is the worst flag they have. The same list is under Flags in the tool.

Problem (red).

  • The file was edited after it was downloaded. The checksum at the bottom doesn't match the contents.
  • The Done: N of M line at the top disagrees with the history under it. So does the Points: N of M line, on a practice with questions worth more than 1 point.
  • Two or more entries have the exact same timestamp as entries in another student's file. Two people working separately never produce that. One file was turned in twice.

Worth a look (yellow).

  • One shared timestamp with another student.
  • Every question finished, and the whole history spans less than 15 seconds per question. Only checked on practices with five or more questions.

Noted, but the dot stays green.

  • Eight or more questions finished, every one on the first try, on a practice that has query questions.
  • The file is late. Canvas's download only says whether a file was late, so enter the due date at the top of the assignment, and the tool shows how late each file is, measured from when the student made it.
  • The name typed in the file doesn't look like the Canvas name on the download.

None of this is proof of anything. It tells you who to have a conversation with.

Checking one file

Open the single-file checker ↗

This is the older tool. Paste the contents of one submission file into it, and optionally a second one beside it, and it reports the same things for just those files.