Course Dossier: Semantics of late submission
Yesterday I had a discussion with Robbert and Hayley who need to administer the late days for students. The idea is to use the course dossiers for this, which shows the aggregated numbers of late submissions.
In current implementation, the dossier counts a submission as late when the submission was handed in after the “deadline”.
This “deadline” can be, in order,
- a personal deadline
- the deadline of assignment the submission belongs to, or
- the inherited deadline from a parent submission, except for inline assignment collections.
A potential issue with (3) can be illustrated by the following example.
Take an assignment collection named
Lab Week 1, which has 5 assignments in it. The deadline of
Lab Week 1is set to
date_w1and an extension is set to
date_w1 + 2days. When a student submits 4 out of 5 submissions one day after
date_w1, the course dossier will count this as 4 late submissions.
This won’t work for the “Algoritmiek en Datastructuren” course, and I think it makes more sense in general to change the late-submission counting logic to only mark submissions late for assignments that hold a deadline, which is similar to the penalty system, i.e. not applied for assignments with inherited deadline. In other words, drop (3).Submitted by Elmer van Chastelet on 8 February 2017 at 10:54
Note that the dossier will still show warning texts on each submission that was handed in after (a possibly inherited) deadline, so these indicators will remain.
Log in to post comments