You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to know which proportion of respondents have taken the survey a single time, twice, three times, etc. over previous years.
I could see different approaches:
1. track this in surveyform and submit it as part of every save
Pros: distributes the workload over every save
Cons: only works for future respondents
2. do it as part of the normalization process
Pros: will work for every response, even for past surveys if we renormalize them
Cons: will slow down normalization drastically (+1 db request per response processed)
3. do it as part of a surveyadmin script
Pros: since this is something that doesn't change, we can calculate it once per survey even if it takes a long time
Cons: easy to forget to run it
The text was updated successfully, but these errors were encountered:
For 2. If you index surveys per (editionId, userId), your agregation should actually be fast during the normalization process
For 3., the advantage in the long run is that it would set a basis to run further computations, like we could call LLM APIs over each response. So you may want to focus on automating running these scripts just after normalization? The only limitation is that you'd want to avoid any computation that implies loading all responses in memory, because at some point it might become too big, and stick to computations that can be done in a stream
I already added 3. It stores the data on the raw response, not the normalized response. So we only need to run it once after the survey ends, and even if we renormalize everything we don't need to run it again (since it's data that can't change anyway).
It would be nice to know which proportion of respondents have taken the survey a single time, twice, three times, etc. over previous years.
I could see different approaches:
1. track this in
surveyform
and submit it as part of every savePros: distributes the workload over every save
Cons: only works for future respondents
2. do it as part of the normalization process
Pros: will work for every response, even for past surveys if we renormalize them
Cons: will slow down normalization drastically (+1 db request per response processed)
3. do it as part of a
surveyadmin
scriptPros: since this is something that doesn't change, we can calculate it once per survey even if it takes a long time
Cons: easy to forget to run it
The text was updated successfully, but these errors were encountered: