Content for Stats Page

[peterwoodward-court]

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

[sima-qian]

The first two points of Basic feedback should be achievable before Friday. I'm less sure we'll have the time set up storage of user's past performance in the database (though I'm increasingly hopeful we'll be able to implement basic user login).

For the Follow on page, a list of missed mark scheme components is definitely feasible if we get on to building this page. A graph will almost certainly not be possible for this build, as it would require us learning and implementing D3 (within React). If you decide you want to carry on development of OSCEBossKey using this codebase, it's certainly do-able -- just not within the current timeframe.

For the general Stats page, if we get round to building that component, some of that data should be quite easy to grab and plug in. Something like Number of days studied in the last 30 could be trickier. I think we'll have to see how much time we have if/when we get to this point.

[peterwoodward-court]

@sima-qian super exciting stuff, thanks for all your (meaning everyone of course!) hard work in (hopefully) getting the extra parts we were hoping for. Makes complete sense with the D3 work and the stats page. 👍