CSC/ECE 517 Spring 2026 - E2600. Reimplement review mapping controller
Review Strategy Tab: Frontend Documentation
This page documents the functional behavior and UI logic for the Review Strategy tab. The interface manages how reviewers are assigned to submissions, incorporating conditional logic based on global settings defined in the "General" tab (e.g., Calibration, Topics, and Teams).
Overview
The Review Strategy interface allows instructors to toggle between manual and automated assignment models. This version renames legacy strategies to improve clarity and introduces dynamic field visibility based on the system state.
Primary Strategy Selection
The instructor initiates configuration via the Review strategy dropdown:
- Static (formerly "Instructor-Selected"): Used for manual or rule-based distributions.
- Dynamic (formerly "Auto-Selected"): Used for algorithmic, real-time distributions.
Static Strategy Configuration
When Static is selected, the following interface elements are exposed:
Assignment Methods
Instructors select from three methods under the prompt: "How should reviewers be assigned?"
- Round robin: Includes an info tooltip explaining sequential distribution.
- Random: Assignments are distributed randomly.
- Import File:
- UI Logic: Selecting this option reveals an Import Button.
- Visibility: The "Number of reviews" and "Pre-submission" fields are hidden when this method is active.
Review Counts & Logic
Field labels and visibility depend on the Calibration for training setting in the General tab:
- Standard Label: "Number of reviews each reviewer is required to do."
- Calibration Label: If Calibration is enabled, the label changes to: "Number of uncalibrated reviews each reviewer is required to do" and a new field, "Number of calibrated reviews", becomes visible.
- Pre-submission Assignments: A checkbox labeled "Assign reviewers to review projects that have not yet been submitted" (Defaults to Checked).
Execution
- Assign Reviewers Button: Visible only when required parameters are defined. Clicking this triggers the backend mapping logic.
Dynamic Strategy Configuration
When Dynamic is selected, the following configuration fields are exposed:
- Number of reviews each reviewer is required to do: Integer input field.
- Max. number of reviews each reviewer is allowed to do: This field is automatically pre-populated with the value entered in the "required" field.
- Review topic threshold (k):
- Visibility: Only appears if Has topics? is enabled on the General tab.
- Default: Pre-populated with 1.
- Tooltip: "A topic is reviewable if the minimum number of reviews already done for the submissions on that topic is within k of the minimum number of reviews done on the least-reviewed submission on any topic."
Global Review Settings
These settings are persistent across both Static and Dynamic strategies, though some are subject to conditional visibility.
| Field | Visibility | Description |
|---|---|---|
| Is reviewing anonymous? | Always visible | Students cannot see the identity of their reviewers. |
| Are self-reviews required? | Always visible | Reviewers/teams must review their own work in addition to assigned peers. |
| Is reviewing role-based? | Only if Has teams? is checked | Each team member selects a role and reviews based on a role-specific rubric. |
| Are reviews to be done by teams? | Only if Has teams? is checked | Assignment logic treats the team as a single unit rather than individuals. |
Technical Implementation
The frontend captures the current state of all visible fields and transmits the configuration to the backend API. This ensures the specific assignment parameters and conditional logic states are correctly persisted in the database.