Our previous conclusion (between Mohammad and Mojtaba) was: “Drop prompt time from anywhere in the UI. It can still be recorded though.”
But IMO we should really decide whether we need it or not. Otherwise we’d end up with having unused fields but are still in the DB. We had such cases in the study DB table for example.
In our Reference we define prompt time as “Same as Scheduled Time”. But prod isn’t like this.
Initially, scheduled_time was the time the survey was scheduled. We tried to prompt the survey exactly at that time, but because of some technical issues, it could be up to 10 minutes +/-. So we added the field prompt_time to capture when exactly the survey was prompted. Later, we changed the code such that the survey was exactly prompted at scheduled_time. So having prompt_time was not needed anymore. But the word prompt_time still lingered around.
In some cases, (I can only think of time use), we re-used prompt-time for some other thing. I think we started storing start of the session in scheduled time and end of the session in prompt time. I think if you exclude time use sessions and surveys, the remaining data will have prompt time almost equal to scheduled time.
Check how many sessions have different s_time and p_time. See if we can deprecate p_time: MM thread
I checked the data, but we should recheck whenever we reach it: MM thread
Category:
Activities - Sessions