Specify clickstream logging

[stevenbird]

Capture the low-level UI actions with timing data, so that a session can be remotely monitored, or stored in a repository and replayed. There are several use cases: teacher monitoring a student, researcher studying student performance, pair programming, answer garden (useful for vicarious learning), plagiarism detection (confirmation that a student did formally assessed work themselves instead of loading a file from another student).

Some requirements:

• click-through consent
• user authentication (so we know who is using this)
• confidentiality (student identity is obscured, but tracking of individuals is still possible)
• ability to opt out later (anonymising or deleting data)
• clickstream data is maximally robust to modifications of the software (e.g. what happens if a block no longer exists?)
• live replay (for teaching monitoring and pair programming)
• delayed replay from a repository (for research, answer garden, plagiarism)
• clickstream summary (e.g. a few images)
• social tagging in repository
• how to contribute this to Snap!

[stevenbird]

Events to log:

• the fact that a block is being run (might want to count how many runs; or initiate running on another client)
• anything that involves a block being instantiated (to a particular location), joined, destroyed
• actions on the stage to manually create a graph (but we don't care about the rendering)
• costumes (but not the dialogue that created it)
• block editor (actions that impact the ScriptsMorph)

[stevenbird]

Simplified approach, only log the first three types of event.

[stevenbird]

Note that all events should be timestamped, and attributed to a user.