Data Capture: Define Internal Architecture

[bastianilso]

The aim of the JS data capture backend is to produce three types of files:

• Event CSV files, which contain event data
• Sample CSV files which contain continuous mouse movement data / touch data.
• Meta CSV files which contain information about the current device and static variables from the website itself in one row.

Eventually we should come up with an internal architecture for the data capture.

• directory structure
• javascript source code file name conventions
• Class/function name conventions

Before we do this, we need to have prototype Javascript implementations of each of the described data capture types. Also, we should first discuss what would make most sense together in this issue, before we implement a specific structure.

[bastianilso]

Logging System:

• LogEvent();
• LogContinous();
• LogMeta();
• SaveLogs(): purpose of this function is that it saves the logs.
• Rename/come up with function names for private functions too..

General structure of your JS file(s).

script.js: organize the functions such that you have:

global variables are also kept on top. public functions on top. and private function on the bottom.

Add comments above each function describing shortly what the function does.