Student cannot resubmit after approval

[Gregoire Detrez]

In some courses, it is common to accept imperfect but good enough submissions and encourage the student to resubmit if they want to make it perfect.

For this, the students need to be able to submit even after the submission was accepted.

[Evgeny Kotelnikov]

It complicates the data model. What would happen if the resubmitted solution is not good enough?

• If it's rejected, the logic of lab statuses in the roster should be — status "accepted" if there's an accepted submission, status of the last submission otherwise.
• If it's accepted with smaller grade, it would probably be fair to account the previous grade as the final grade for the lab. But we don't really have a generic way of comparing grades — they're just strings.
• New status / update of the accepted submission?

[Gregoire Detrez]

If it's rejected, the logic of lab statuses in the roster should be — status "accepted" if there's an accepted submission, status of the last submission otherwise.

That sounds acceptable...

If it's accepted with smaller grade, it would probably be fair to account the previous grade as the final grade for the lab. But we don't really have a generic way of comparing grades — they're just strings.

I don't think it's the role of the fire system to decide what's "fair" or not. It should allow the grader to change the grade and leave it to him to do what he sees best...

New status / update of the accepted submission?

IMO, it should still be "Accepted"

[Evgeny Kotelnikov]

I don't think it's the role of the fire system to decide what's "fair" or not. It should allow the grader to change the grade and leave it to him to do what he sees best...

What I meant is the following. We would like to have the complete course report in the roaster and there we would like to see the final grade for every lab. Currently we simply show the grade of the last lab. In order to always see the final grade of multiple accepted submissions, the grader would be expected to always grade the last accepted submission with the highest grade of them all, even when the current one is actually weaker than the previous one. This might not be obvious.

I guess, it doesn't sound too bad, just something to be cautious about.

[Gregoire Detrez]

What I meant is the following. We would like to have the complete course report in the roaster and there we would like to see the final grade for every lab. Currently we simply show the grade of the last lab. In order to always see the final grade of multiple accepted submissions, the grader would be expected to always grade the last accepted submission with the highest grade of them all, even when the current one is actually weaker than the previous one. This might not be obvious.

True. Although, I'm pretty sure the students would notice (and complain ;-)) But you're right, it should be made clear in the user interface of the grader that the new grade will replace the old one in any case.