OCS Capstones › Submissions

OCS Assignments System

The goal right now is to make grading faster and more trustworthy, and to let teachers do everything they need from the Pages frontend without digging into the Spring admin views. Below are the six things we're focused on, who's working on what, and the design notes we're working from.

Project board Open on GitHub

Current priorities

#1 Faster grading with your own AI key — Graders add their own Gemini key so AI grading isn't stuck waiting on one shared key.
Owner: Aditya
#2 Fix, build, and standardize lessons with CRUD — Add and delete operations so lessons can be cleaned up and kept consistent, instead of being patched one by one.
Owners: Rishabh (CSSE lesson) · Aneesh (Units 1 + 2)
#3 Grading corrections from the admin page — Example: a CSSE object literals lesson had a nested conditionals permalink, and that wrong link got saved in the database. Resubmitting doesn't fix the record because the submission process never updates it, so admins need a way to correct it from the admin page.
Owners: William + Nick · Katherine + Bridget
#4 Data collection for self-assessment — Collecting the data that self-assessment will be built on before it goes back into OCS.
Owner: Jacob
#5 Using OCS AI — Deciding whether grading goes through an OCS AI API or another option.
Owner: Whole team · approach still being decided
#6 Aaryav's omake — Speeding up make run time. This is on the agenda for the second mentor meeting.
Owner: Aaryav
Project Leads Aditya

AI Grading with Your Own Key

#1 Faster grading #5 OCS AI

About

Letting each assignment be AI-graded with a key the user uploads from Gemini or Claude. Every assignment's AI grade is out of 1 point.

View project →
Project Leads Aaryav

Student Grades Alongside AI Grades + Make Run Time

#6 omake

About

Letting a student grade go in next to the AI grade without overwriting it. Separately, cutting down make run time with omake.

Project Leads Katherine, Bridget

Kanban, Admin Dashboard + Student Success Insights

#3 Corrections

About

Keeping the Kanban board and this capstone page up to date, organizing the admin dashboard and the Spring backend behind it, and building Student Success Insights.

View project →
Project Leads William, Nick

Admin Dashboard: Assignments by Year

#3 Corrections

About

Organizing assignments by year in the admin dashboard. There are about 20 pages of assignments from several years, so the focus is on making them easy to find and fix.

Project Leads Aneesh

Unit 1 + 2 Teaching

#2 Lessons

About

Units 1 and 2 still need to be taught. This means working out the schedule and trying a new way of teaching lessons to get more engagement. Right now the focus is the homework for Mort's data structures lesson.

Project Leads Jacob

Self-Assessment Rework

#4 Self-assessment

About

Taking self-grading out for now and reworking it, using the data being collected, before it goes back into OCS.

View project →

Spring backend

Design notes

The "view grades" page in Spring has gotten huge. Teachers would be better served by a teacher view on the frontend.
Leave the legacy pages in place rather than ripping them out.
Grading still needs a proper design before more gets built on it.
The assignment tracker spans about 20 pages across several years. Starting from scratch would be cleaner but is too much work, so we're improving what's there.
AI grading uses a rubric out of 1 point.
Add only the CRUD operations admins actually need, not every possible one.

Pages frontend

Design notes

Submission screens for both graders and teachers.
Teachers should only ever need the frontend to do their work.
That includes starting AI grading from the frontend.

How we're working

Design notes

PRs should remove sharp edges, not add band-aids.
An AI grade and a student or grader grade should sit side by side. Neither one overwrites the other.
Fix bad data at the source. If a record is wrong, there should be an admin way to correct it.