Researchers: David Boulanger, Jeremie Seanosky
SCALE stands for Smart Competence Analytics on LEarning.
SCALE is a smart analytics technology that transforms learning traces into standardized measurements of competences.
SCALE is a smart competence analytics technology that analyzes your learning experiences in different learning areas. SCALE basically transforms your learning traces into measurements that will help you assess how proficient you are in the concepts introduced in your course. SCALE will also allow you to evaluate how confident you are at solving a particular exercise and how confident you are in the overall learning domain. SCALE’s mission is to provide you with a scale that will help you measure and optimize your learning as it occurs.
SCALE has been redesigned to become completely independent of the client-side CODEX and vice versa. Prior to that, the client-side sensor was communicating directly with the server-side SCALE processor to transfer data instances, but this had adverse consequences when we consider potential denial-of-service attacks and loss of service for other clients.
It was also impossible for the SCALE engine to handle tremendous amounts of data packets flowing continuously towards the server.
We, therefore, added one more layer between CODEX (client-side) and SCALE (server-side). This new layer is a NoSQL OrientDB database called the Transit Database.
In sequence, CODEX continuously sends data instances it captures at fixed intervals (e.g. 30 seconds) to the TransitDB via a Socket server. The Socket server handles huge quantities of data rather easily in comparison to the HTTP request approach previously used.
Data received by the Socket from CODEX are all relayed to the TransitDB to be stored and accumulated. This is the ONLY connection between CODEX and SCALE, therefore removing any dependency between CODEX and SCALE.
In simpler terms, CODEX does not have any direct link to SCALE, and vice versa.
SCALE, on its side, operates autonomously and independently. Based on its internal design, SCALE continuously looks into the TransitDB to see if there are data available from CODEX. If so, SCALE takes one CODEX data packet at a time, processes and analyzes it, and then marks that data packet as “processed” so the SCALE engine won’t process it again.
Upon completing the processing and analysis on a given data packet, SCALE stores the analysis results in a MySQL database, ready to be used by the visualization and reporting tools available, such as MI-DASH.