@Daimona If the number of participants who answered the affiliate question or the number of responses, 20 yes 20 no, don't change after people cancel their registration, why can't we leave the 'No responses' value the same after registrations are canceled?

In T349650#9277376, @gonyeahialam wrote:

@Daimona If the number of participants who answered the affiliate question or the number of responses, 20 yes 20 no, don't change after people cancel their registration, why can't we leave the 'No responses' value the same after registrations are canceled?

Mostly because we are talking about participants who cancel their registration after aggregation, and for whom we don't know what the individual answers are.

Surely after aggregation that number should be frozen, a snapshot in time of the aggregated data?

In T349650#9278728, @MHorsey-WMF wrote:

Surely after aggregation that number should be frozen, a snapshot in time of the aggregated data?

Aggregation can happen at different times for different participants, though. But even if it didn't, we don't have a place to store that snapshot.

Maybe we could store the "No response" in the database, but that also needs to be considered very carefully.

Aside from the potential bloating the table, this is also tricky if we decide to let organizers add/remove questions (T322209). Considering the following scenarios:

• A certain question is enabled for the event, but someone decides not to answer it when registering
• No questions are enabled for the event, people register, and then the organizer enables questions

We would store a "no response" explicitly in the first scenario, but likely not in the second. Which could then lead to ambiguity when deciding what the number of no responses should be (because it may or may not be stored explicitly).