Investigate possibilities for a progress bar on the self-assessment

[ellemindwave]

What options would we have for a progress bar on the self-assessment?
feedback is that it is quite long, as some indication of how far through you are would be really useful.

Not sure how feasible this is due to the answers chosen during the assessment determining the length of the assessment

[reddog]

We don't currently receive any information from E24 in terms of how many questions there are in a given assessment in total, how many (maximum) are remaining given the user's current choices, how many are circumvented by the user's last answer, etc. The E24 algorithm can be traced from the starting point to many end points, based on user's answers.

We could:

1. if there are points in the assessment that are always reached, we could determine that these are x% through and use that as a measure of progress?
2. we could get the longest journey question count and use the number of questions answered / longest journey count as the percentage through. For routes much shorter that the longest journey, the user would see a slow progress until the very last question when there would be a big jump.
3. something else?

[ellemindwave]

Hi Elle. I think what we will need to do is:

1. on the server we need to:

a. build a cache of algo IDs, the max number of questions for that algo, and when we last checked (this might be in a separate redis layer)
b. provide a function for returning (to the client) the maximum number of questions in an algo
c. perform a check at some point (at a scheduled time, or when the algo question count is requested) of how old cached question count is, an re-get it if required.

2. during a traversal (ie someone is completing an assessment), we need to:

a. keep count client-side of which question number the user is on
b. pull in the max number of questions for this algorithm
c. display some sort of progress bar