Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to edx/edx-exams#154.
JIRA: https://2u-internal.atlassian.net/jira/software/projects/MST/boards/584?selectedIssue=MST-1961
Description
As of now, the ACS endpoint only supports a flag action. We would also like to support terminate as a way for Proctorio to communicate that they have ended an attempt.
Upon receiving a terminate request, the attempt referenced in the request should be moved to a corresponding status, depending on the reason for termination (reason_code) and incident_severity. The reason_code mappings should be clarified with Proctorio, and the incident_severity should be discussed internally to decide what range of values are considered passing.
Reason codes:
user_submission: move attempt to verified or second_review_required
error: move attempt to error
Severity:
we can just use a constant set to 0.25 for this at the moment
terminate with severity > 0.25 will move to second_review_required otherwise verified
Question: Do we want to store the reason code and incident severity in another model (similar to a review)?
work with dev on MST-1992: Return review info to exams-dashboard