commit | 10e9bd070bb74e7aa3c9662c6ae821c47339b3fc | [log] [tgz] |
---|---|---|
author | David Reed <david.reed.c@gmail.com> | Thu Jun 18 17:05:19 2015 -0400 |
committer | David Reed <david.reed.c@gmail.com> | Thu Jun 18 17:05:19 2015 -0400 |
tree | c17266a8ab272fee7e386c514cd4adef36266694 | |
parent | 42e20160df33186818eba56750c508f8d8d71af5 [diff] |
User-ALE will first check if a session ID is in the URL if it is it will pick it up and drop of a cookie so a redirect will pick it up. If the session id is not in the URL it will then check to see if a cookie exists. Finally if there isn't a sessionID in either of those places it will create one.
#User-ALE
##Background
The User Activity Logging Engine, or User-ALE, is a logging mechanism used to quantitatively assess the behavioural and cognitive state of a data analyst while interacting with Big Data Exploitation Systems (BDES).
To accurately measure the cognitive state of the user, tool developers associate model based workflow states with each user action. Did a user pan a map? Then they are exploring. Did a user click a search button? Then they are getting new data. These model based activities can then be processed to measure hidden empirical states that describe more accurately the user's workflow and behaviour.
##Who is the package for?
This package is for developers creating User facing tools, and who would like to log the users interaction with this tool, in order to gain an insight into the behavioural and cognitive state of the user.
##JavaScript Quickstart Download both the latest logging library and the latest worker library from Github.
###Instantiate the JavaScript Logger
// web worker url var worker = 'js/draper.activity_worker-2.1.1.js' var ac = new activityLogger(worker); .testing(true) // simulate POST, won't send log .echo(true) // log to console .mute(['SYS']); // don't log SYSTEM actions
###Register the logger
ac.registerActivityLogger( "http://xd-draper.xdata.data-tactics-corp.com:1337", "my-component", "v0.1" );
###Log a User Action
$('#button').mouseenter(function() { ac.logUserActivity( 'User hovered over element to read popup', // description 'hover_start', // activity_code ac.WF_EXPLORE // workflow State ); })
This will provision the base box which is an Ubuntu 14.04 machine. The Kibana/ELK server is running on http://192.168.86.100 while the developer box is running on http://192.168.86.10
vagrant up