Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Content for Stats Page

Open
  • Is something wrong?
#110 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

The issue lists possible basic, follow-on, and stretch-goal statistics but names no files or tests. Start by locating the stats-page navigation and the existing station-submission data flow, then confirm which subset is in scope. Done means the agreed statistics are implemented and their display and calculations are verified.

Written by the indexing model from the issue text.

Description

Following from yesterday - here are some thoughts about what we could have on the stats page, let me know if suggestions are too technically complicated to implement to be worth it

Basic (when you have pressed 'submit' on your current station):

  • Time taken to complete
  • Percent correct (i.e. number of individual 'points' on the mark scheme the user go divided by the total number of points on the mark scheme)
  • Previous best (top score ever achieved on the given station) OR we could do an average score from the previous three attempts (previous three rather than average from all attempts to prevent outliers from when you first started practicing affecting your score). Which is best to do is something we could test with med students/your friend @sima-qian

Follow on page:

  • List of components from the mark scheme that were missed and, if possible, a display to the user the number of times they have missed that particular point in the mark scheme
  • Graph with date along the X axis and score on the Y axis drawing a simple line graph of how their performance has changed over time

Stats page (i.e. the section on the nav bar at the bottom - these are less essential and fit into 'stretch goals'!)

  • Total number of OSCE stations practiced
  • Average score for a given OSCE station
  • Average time taken for a given OSCE station
  • Number of days studied in the last 30 (i.e. when at least one OSCE station was completed)
  • An ability to select a specific station and see your stats on it

Let me know thoughts/improvements/ideas!

Peter

@njons @sima-qian @martingaston @Brymon

Dominant language
JavaScript
Stars
4
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fac-14/OSCEBossKey

All issues in fac-14/OSCEBossKey

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.