160 | | Connects groups to events, holding other data about the group submission, etc. (many to many relationsip): |
161 | | |
| 160 | Connects groups to events, holding other data about the group submission, etc. (many to many relationship).[[br]] |
| 161 | I think that the extra columns are just to cache other data from the table, and display it to the user. |
| 162 | ||__Column__||__Type__||__Description__||__Foreign Key to table...__|| |
| 163 | ||'''id'''||integer||Primary_Key |
| 164 | ||''group_id''||integer||The ID of the group ||''groups'' |
| 165 | ||''event_id''||integer||The ID of the event ||''event'' |
| 166 | ||''marked''||string||One of ''not reviewed'',''to review'', ''reviewed''. Determined whether the instructor reviewed the comments for any offensive contents or the like. As I understand it, "Not reviewed" means not all submissions are yet complete from group members. "To review" implies that all submissions came in, but are not yet reviewed. "Review" means all submissions were turned in and reviewed by instructor. |
| 167 | ||''grade''||integer||I have no idea... NULL in all case I've seen so far. Unused (?)|| |
| 168 | ||''grade_release_status''||string||Can the users see the grades their group members gave them, or not? ''Some'', ''None'' and ''All'' are possible. |
| 169 | ||''grade_release_status''||string Can the users see the comments their group members gave them, or not? ''Some'', ''None'' and ''All'' are possible. |
| 170 | ||'''record_status'''||enum(A,I)||either 'A' or 'I', representing active or inactive. Not always checked by code. |
| 171 | ||'''creator_id'''||integer||the ID of the ''user'' who created this course.||users |
| 172 | ||'''created'''||date||a date entry for this entry's creation. |
| 173 | ||'''updater_id'''||integer||the last ''user's'' ID who changed this record.||users |
| 174 | ||'''modified'''||date||the last time of modification |