Response maps: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
!type | !type | ||
|varchar(255) | |varchar(255) | ||
|Used for subclassing the response map. Available subclasses are ReviewResponseMap, MetareviewResponseMap, FeedbackResponseMap, TeammateReviewResponseMap | |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 | |||
|BIT | |||
| | |||
} | |||
Back to the [[Documentation_on_Database_Tables|database documentation]] | Back to the [[Documentation_on_Database_Tables|database documentation]] | ||
Revision as of 22:55, 25 April 2018
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) | The team (AssignmentTeam) receiving the response |
| 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 | BIT |
}
Back to the database documentation |