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
As briefly discussed yesterday, unless you have a better idea, it might make sense to log a few key events in a separte table usage_data with the columns id, ts (or created, edited, ...), type and additionalInformation:
The idea of additionalInformation is to flexibly add extra context/data, where useful. In past studies, we sometimes added json objects that we could later easily parse.
The following event-types (for now):
start (app start, also log timezone and app version number)
stop (app shutdown)
lock-screen (logout/signout/lockscreen)
unlock-screen
startExport
finishExport (+ settings)
opened + closed/answered experience sampling popup and wheter it was automated or manually opened
anything else that makes sense?
The text was updated successfully, but these errors were encountered:
As briefly discussed yesterday, unless you have a better idea, it might make sense to log a few key events in a separte table
usage_data
with the columnsid
,ts
(or created, edited, ...),type
andadditionalInformation
:The idea of additionalInformation is to flexibly add extra context/data, where useful. In past studies, we sometimes added json objects that we could later easily parse.
The following event-types (for now):
The text was updated successfully, but these errors were encountered: