Allow members to retake quizzes

[victorandree]

Background

Right now, if you've taken a quiz (successfully), you cannot redo it. It would be useful, however, to retake a quiz as a refresher. For example, if the wood room is reopening, taking the relevant quizzes can be a good way to freshen up your knowledge.

This was brought up in this Slack thread: https://stockholmmakerspace.slack.com/archives/C4MM2M5EV/p1764326574309419.

What happens?

• You can still load a quiz that you've taken, but when you press the Start! button, the call to GET quiz/quiz/1/next_question returns {"data":null,"status":"ok"}.
• This moves the frontend component to the "done" state, rendering the completion screen.

The logic for filtering questions is driven by

makeradmin/api/src/quiz/views.py

Line 98 in 4637976

@service.route("/quiz/<int:quiz_id>/next_question", method=GET, permission=USER)

, which filters out questions that the user has answered correctly.

The simplest solution is therefore probably for this endpoint to accept a timestamp parameter, ignoring questions answered before a point in time. This would be in line with the suggestion by @HalfVoxel in this Slack thread: https://stockholmmakerspace.slack.com/archives/C9LB8R8VB/p1764333141905889?thread_ts=1764332637.657959&cid=C9LB8R8VB.

The model for questions and answers supports multiple answers per question per member. But let's be careful about what might happen if there's >1 correct answer per question per member. Would it mess up any statistics, for example?

[HalfVoxel]

Great!

But I think the timestamp to ignore answers before will need to be stored in the database. The quizzes should support the user reloading the page without the state getting lost.

[HalfVoxel]

The statistics will probably handle this fine.
Most statistics code just takes the first answer for each question. To see if the member got it right on the first try.

[victorandree]

Regarding storing the timestamp: I was thinking to hold this in a query string parameter. That would survive a page reload.

Storing this in the database... Right now it seems like we're just storing answers. Storing this in the database seems like trying to model "quiz attempts" which seems like a bigger refactor.