-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fully-fledged "deadline extensions" #219
Comments
… final solutions. This is rarely useful, and hence not linked to from the praktomat site. It does, however, provide somewhat of a workaround to issue #219
If you have a look at my pullrequest https://github.com/KITPraktomatTeam/Praktomat/pull/238/files |
@mhecker : You asked
From point of a relational DBMS there should be (in words of Abrials min-max notation) a "Student-[0,N]-(solves)-[0,N]-Task"-relation, where the relation "solves" should have an attribute "until". The default value for "until" could be NULL. If "until" is NULL than Task.submission_date is used. If "until" is not NULL than this value overrides the submission_date limit for that tasks for that user. Yes, a Solution would be connected to relation "solves" as third but weak-entity having min and max cardinality 1. Coding that in Django we need additional view an template code.
A fully fledged deadline-extenstion should make the manual selection of "run all checkers" on Task-Admin listview optional. such an extension should contain a cron-job or at-job. |
Under some conditions, deadline extensions for specific students and tasks are desirable.
The current work-around, i.e.: letting the student send the solution to a tutor by email, who then submits it in lieu of the student, is unsatisfactory because the student can get no feedback whether his solution passes the public tests. It also does not scale with the number of students given deadline-extensions.
Open questions:
The text was updated successfully, but these errors were encountered: