Add Likert reflection to async PI (opt-in per course) with logging#1245
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds an optional Likert-scale “final reflection” step to the async peer instruction student flow (gated per-course via the enable_likert course attribute) and expands peer-instruction logging to capture richer mode/theme data.
Changes:
- Add a Likert reflection UI step after the second vote in async PI, blocking “Next Question” until submitted (when enabled).
- Add/adjust PI logging fields (mode classification + theme logging) and pass
enable_likertinto the async PI template. - Restrict
/assignment/peer/course_studentsto instructors (this appears to be a breaking change for student pages as currently implemented).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| components/rsptx/templates/assignment/student/peer_async.html | Adds Likert reflection panel + client-side gating/logging integrated into async PI step flow. |
| bases/rsptx/assignment_server_api/routers/peer.py | Adds enable_likert context, updates pi_mode logging, adds pi_theme logging, and changes auth on /course_students. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Contributor
Author
|
@bnmnetp I addressed the Copilot comments. Once it's merged, could you enable it for async-pi-study and test_py4e-int_api? rsmanage addattribute --course async-pi-study --attr enable_likert --value true |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added an opt in Likert scale step to the peer instruction flow that appears after students submit their second vote and before they move to the next question. The next question button remains locked until the Likert responses are completed, and the form resets for each new question.
Also expanded the logging to capture additional peer instruction data, including the async mode type, selected theme for personalized LLM interactions, and students’ Likert scale responses.
The Likert step is off by default and has to be enabled per course, so it won't affect any existing courses. It's gated behind the enable_likert course attribute, which can be set with:
rsmanage addattribute --course <course_name> --attr enable_likert --value trueCould the course
async-pi-studyhave this enabled once it's merged?