nusmodifications / nusmodifications/nusmods
Allow voting of modules to be offered in Special Term
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 689
- Forks
- 364
- Avg merge
- 7h 5m
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem? Please describe.
The list of modules offered over the Special Term is super limited. It makes my options for planning out my prospective academic calendar likewise limited. My assumption is that faculty departments don’t actually know how much students want certain mods to be offered; if they did would that influence what becomes available over the summer? Well, there’s one way to find out.
Describe the solution you'd like
Simple voting function somewhere on the module page, or even from searching based on Special Term availability (not sure what the best UX solution is), to indicate something like, yes I would like this offered during Special Term!
Describe alternatives you've considered
I literally emailed the Statistics Dept to ask them, is there a way for students to suggest modules to be offered during Special Term (with an example mod ST1131 just as an example). The reply was literally, ST1131 is not offered during Special Term thank you.
Additional context
Motivation is to avoid burnout and/or insanity with workload during normal terms.
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
The issue does not name files, tests, or entry points. Start by mapping the module page and module search flows, then clarify the voting UX, storage, and how department demand would be surfaced; done requires an agreed design and an end-to-end voting workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100