Response maps: Difference between revisions
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
!reviewee_id | !reviewee_id | ||
|int(11) | |int(11) | ||
| | |Dependent on which subclass of ResponseMap this object is. For a ReviewResponseMap, the [[teams|team]] (AssignmentTeam) receiving the response. For a TeammateReviewResponseMap, the AssingmentParticipant who is being reviewed. | ||
|- | |- | ||
!type | !type | ||
Revision as of 14:53, 9 August 2021
Maps a connection between the participants as reviewers and participants or teams as reviewees
Response maps variable documentation
| Field Name | Type | Description |
|---|---|---|
| id | int(11) | The unique record id |
| reviewed_object_id | int(11) | The object being reviewed in the response. Possible objects include other ResponseMaps or assignments |
| reviewer_id | int(11) | The participant (actually AssignmentParticipant) providing the response |
| reviewee_id | int(11) | Dependent on which subclass of ResponseMap this object is. For a ReviewResponseMap, the team (AssignmentTeam) receiving the response. For a TeammateReviewResponseMap, the AssingmentParticipant who is being reviewed. |
| type | varchar(255) | Used for subclassing the response map. Available subclasses are ReviewResponseMap, MetareviewResponseMap, FeedbackResponseMap, TeammateReviewResponseMap |
| created_at | DATETIME | Date and Time for when the record was created |
| updated_at | DATETIME | Date and Time when the last update was made |
| calibrate_to | tinyint(1) | Tells whether the record will be used for calibration or not. |
Back to the database documentation