When I give an extension on an assignment collection, I somehow expect the extension to hold for all assignments in that collection. However, (at least in the case) when the original deadline was not set at the higher level, the extension is not propagated to lower levels. Is that intended?

Submitted by Mathijs de Weerdt on 20 November 2015 at 10:22

On 20 November 2015 at 10:41 Eelco Visser commented:

Yes, that is intended. A deadline and extension are configured at the same node in the assignment tree.


On 20 November 2015 at 10:48 Eelco Visser commented:

I understand that this is about personal deadline extensions?

Still, if all the underlying deadlines are the same (since you can give a single personal extension), why not lift the deadline to the collection?


On 9 March 2016 at 13:44 Elmer van Chastelet commented:

Global deadline and extension seem to propagate down the tree. However, the penalty does not, which is not what I would expect. Should this be changed?

I.e. Right now a student who submitted work for some leaf assignment after the deadline, but within the extension does not get a penalty when deadline, extension and penalty are set at a parent assignment. There will only be a penalty when the penalty field of the leaf assignment is set.


On 9 March 2016 at 14:07 Eelco Visser commented:

Indeed. The penalty should not be computed at multiple levels, because then it is applied multiple time. However, we could consider computing the penalty at the leaf nodes. That would mean that an edit on just one of the leaf nodes of a collection does not affect the penalty of all assignments in the collection as is currently the case. It would be a good idea to make that an option to choose:

  • compute penalty at the root node of the assignment that has the deadline
  • compute the penalty at each of the leaf nodes of an assignment collection

On 9 March 2016 at 15:10 Elmer van Chastelet commented:

Ah, that makes sense. We can add this option, however it may complicate things configuration-wise. I would argue that when you have a single deadline and extension for a collection of assignments, it's okay to compute the penalty only at the collection level. Because the collection has a deadline, a penalty is given for the fact that someone submitted the collection of assignments too late.

Still, you can have separate penalties for each leaf node if you want.

So I think we can leave it the way it works right now, however the UI should make clear that it works this way (indicators in configuration and in grade calculation outputs).

Log in to post comments