You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is in current production. Students can hold many reviews without starting reviewing any. This cause the authors receive many empty or useless reviews. We need to place restrictions to this. The best fix should be that students can “save” and “submit” reviews. Students cannot request more reviews if (s)he hold K outstanding reviews. A student holding k reviews must drop or submit a review before being allowed to choose another artifact to review. If a review is submitted, it cannot be changed till next round. Instructor needs to announce to class that they are only going to get points for up to M (should be on syllabus) reviews. They are welcomed do more reviews but they will not get extra points. (We need to add submit button in addition to save button)
This should be implemented in production first.
The text was updated successfully, but these errors were encountered:
This is what we do in current Rails 4 branch: when students holds 3 reviews without starting them, they cannot request more reviews. There is no "drop" button there, should we have one?
This is in current production. Students can hold many reviews without starting reviewing any. This cause the authors receive many empty or useless reviews. We need to place restrictions to this. The best fix should be that students can “save” and “submit” reviews. Students cannot request more reviews if (s)he hold K outstanding reviews. A student holding k reviews must drop or submit a review before being allowed to choose another artifact to review. If a review is submitted, it cannot be changed till next round. Instructor needs to announce to class that they are only going to get points for up to M (should be on syllabus) reviews. They are welcomed do more reviews but they will not get extra points. (We need to add submit button in addition to save button)
This should be implemented in production first.
The text was updated successfully, but these errors were encountered: