Skip to content

Commit aaf21f0

Browse files
committed
Adding photo and slight edit
1 parent 7f21dbd commit aaf21f0

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

_docs/grader/resolving_version_conflict.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,11 @@ title: Resolving a Version Conflict
55

66
## Overview of Issue
77

8-
Typically, this issue occurs when the student changes the 'active' version after the TA has finished grading. The use case Submitty aims to support is that students can submit multiple times before the due date. If we have any automated grading that runs on every submission, we store every submission and the teaching staff can review every submission version number and the autograding for each of those versions. Once the deadline passes, manual/TA grading opens and the TA/instructor will manually grade the current "active" version. By default, the students final/last version is the active version. We do allow students the option of picking a different version to be the active one. This is relevant if they made an additional submission after the deadline (a course might have a policy allowing a student the flexibility to submit by choice a subset of assignments "late"), but then decide that an earlier version is good enough and they will save their "late day" for another assignment.
8+
Typically, this issue occurs when the student changes the active version after the TA has finished grading. The use case Submitty aims to support is that students can submit multiple times before the due date. If we have any automated grading that runs on every submission, we store every submission and the teaching staff can review every submission version number and the autograding for each of those versions. Once the deadline passes, manual/TA grading opens and the TA/instructor will manually grade the current active version. By default, the students final/last version is the active version. We do allow students the option of picking a different version to be the active one. This is relevant if they made an additional submission after the deadline (a course might have a policy allowing a student the flexibility to submit by choice a subset of assignments "late"), but then decide that an earlier version is good enough and they will save their "late day" for another assignment.
99

1010

1111
## Resolving the Version Conflict Manually
1212

1313
To clear this, in the grading interface, open & close each component that is labeled as being in conflict to confirm/update TA grading for the new version. The interface requires you to click each component of the rubric and either edit and save or just save. The current active version is stored for each component, so each will need to be confirmed. Once all of the messages are cleared, the student will be able to see your comments for the whole gradeable again. Alternatively, from the TA grading interface you can switch back to the version of the assignment that was initially marked for grading.
14+
15+
![](/images/ta_grading/versionconflict.png)

images/ta_grading/versionconflict.png

152 KB
Loading

0 commit comments

Comments
 (0)