Rubric point assignment is too rigid
Open
Nobody has claimed this yet.
awaiting prioritization
enhancement
product area: rubric
- Dominant language
- Python
- Stars
- 65
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
Assigning point level to a criteria – can’t predict where cut points need to be until instructor has seen submitted assignments and can gauge studentwork as a wholeMuch more work for faculty (having to parse out criteria and points so granularly) yet doesn’t fit actual needs of grading
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by clarifying how rubric point levels should be assigned after instructors review submitted work, and identify the existing rubric and grading workflow. Done should be defined as a specific, agreed-upon behavior that reduces the need for overly granular point assignment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100