Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

survey: timestamps should all be generated at the same place #785

Open
tahini opened this issue Nov 15, 2024 · 0 comments
Open

survey: timestamps should all be generated at the same place #785

tahini opened this issue Nov 15, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@tahini
Copy link
Contributor

tahini commented Nov 15, 2024

The server should be responsible to timestamp event (start, completion, updates, section events, etc). Also, individual surveys should not have to worry about that.

Currently, it's a bit arbitrary where those timestamps come from. Mostly from the browsers, in the preload or saveCallback functions of the individual survey, so a bit error-prone.

Having a single autority for the clock will allow times differences to be meaningful and comparable.

For now, only the timestamp in the logs field all come from the server and can be used for comparison. And in most surveys, the timestamps in the _sections data come from the browser and should also be comparable.

@tahini tahini added the bug Something isn't working label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant