Interesting. Do you want this out of privacy reasons?
JATOS right now stores the start and end date (a Unix timestamp) for each component run by a participant. The same it does for the whole study. From start and end date it calculates the duration.
Additionally it has a 'heartbeat' sent regularly (every 2 min by default) back to the the JATOS server while the study is running. Whenever a 'heartbeat' arrives at the JATOS server the 'last seen' date (again a Unix timestamp) is stored in the database.
That said, there is no configuration parameter yet to turn this off. It probably could be implemented without too much effort. Anyway without start and end date you wouldn't have the duration too.
Comments
Hi,
Interesting. Do you want this out of privacy reasons?
JATOS right now stores the start and end date (a Unix timestamp) for each component run by a participant. The same it does for the whole study. From start and end date it calculates the duration.
Additionally it has a 'heartbeat' sent regularly (every 2 min by default) back to the the JATOS server while the study is running. Whenever a 'heartbeat' arrives at the JATOS server the 'last seen' date (again a Unix timestamp) is stored in the database.
That said, there is no configuration parameter yet to turn this off. It probably could be implemented without too much effort. Anyway without start and end date you wouldn't have the duration too.
Best,
Kristian
Dear Kristian,
thanks for your fast reply.
This problem is related to privacy-concerns , so yes!
Would be interested to see it coming in the next update!
Thanks,
Amin
Okay, I will do.