Due dates: Difference between revisions
Jump to navigation
Jump to search
| (5 intermediate revisions by 2 users not shown) | |||
| Line 27: | Line 27: | ||
!review_allowed_id | !review_allowed_id | ||
|int(11) | |int(11) | ||
|this is " | |this is "No", "Late" or "OK", depending on whether reviewing is allowed before this due date | ||
|- | |- | ||
!review_of_review_allowed_id | !review_of_review_allowed_id | ||
|int(11) | |int(11) | ||
|this is "OK", "Late" or "No", depending on whether reviewing | |this is "OK", "Late" or "No", depending on whether meta-reviewing is allowed before this due date | ||
|- | |- | ||
!round | !round | ||
|int(11) | |int(11) | ||
|Number of review | |Number of the review round to which this due date pertains | ||
|- | |- | ||
!flag | !flag | ||
| Line 47: | Line 47: | ||
!delayed_job_id | !delayed_job_id | ||
|int(11) | |int(11) | ||
|ID of the delayed job. | |ID of the delayed job, presumably the job that sends reminders of this due date. | ||
|- | |- | ||
!deadline_name | !deadline_name | ||
|varchar(255) | |varchar(255) | ||
|Name of the | |Name of the deadline. This is either NULL or the empty string in all deadlines. | ||
|- | |- | ||
!description_url | !description_url | ||
| Line 59: | Line 59: | ||
!quiz_allowed_id | !quiz_allowed_id | ||
|int(11) | |int(11) | ||
|ID of the quiz associated to the Due Date. | |ID of the quiz associated to the Due Date. No! This does not make any sense. efg has no idea of what this field is for. | ||
|- | |- | ||
!teammate_review_allowed_id | !teammate_review_allowed_id | ||
|int(11) | |int(11) | ||
| | |this is "OK", "Late" or "No", depending on whether teammate review is allowed before this due date | ||
|- | |- | ||
!type | !type | ||
Latest revision as of 04:30, 10 November 2024
The Due Dates table gives information regarding the due dates associated to each of the assignment.
Due Dates Variable Documentation
| Field Name | Type | Description |
|---|---|---|
| id | int(11) | Unique ID for each Due Date record |
| due_at | datetime | Deadline for submission |
| deadline_type_id | int(11) | whether a submission deadline, a review deadline, etc. |
| parent_id | int(11) | the assignment that the deadline is related to |
| submission_allowed_id | int(11) | this is "OK", "Late" or "No", depending on whether submission is allowed before this due date |
| review_allowed_id | int(11) | this is "No", "Late" or "OK", depending on whether reviewing is allowed before this due date |
| review_of_review_allowed_id | int(11) | this is "OK", "Late" or "No", depending on whether meta-reviewing is allowed before this due date |
| round | int(11) | Number of the review round to which this due date pertains |
| flag | tinyint(1) | Not clear what this is. It is zero in all due dates except some between 2010/11/15 and 2011/05/25. |
| threshold | int(11) | How many hours before the due date a reminder is sent to participants |
| delayed_job_id | int(11) | ID of the delayed job, presumably the job that sends reminders of this due date. |
| deadline_name | varchar(255) | Name of the deadline. This is either NULL or the empty string in all deadlines. |
| description_url | varchar(255) | URL of the description |
| quiz_allowed_id | int(11) | ID of the quiz associated to the Due Date. No! This does not make any sense. efg has no idea of what this field is for. |
| teammate_review_allowed_id | int(11) | this is "OK", "Late" or "No", depending on whether teammate review is allowed before this due date |
| type | int(11) | Type of the Due Date. |
E/R diagram for Parents Tables
Tables referred by the Due Date Table as Foreign Key Relationship.
E/R diagram for Child Tables
No Tables refer the Due Date Table as Foreign Key Relationship.
Back to Database Tables Main page.