-
Notifications
You must be signed in to change notification settings - Fork 24
WISE Events
Hiroki Terashima edited this page Feb 16, 2016
·
2 revisions
An Event (added in WISE5.0) stores user's interactions with WISE like entering/exiting nodes, opening/closing the NoteBook, and events triggered in embedded simulations. Together with ComponentState, it provides a detailed account of what the student did in WISE.
An Event has a Category, Event, and Data. Examples of (Category, Event, Data) for are: ("Navigation", "stepEntered", "{nodeId:node4,time:123}"), ("UserInteraction", "runButtonClicked", "{time:145,numLivesLeft:3}")
create table events (
id integer not null auto_increment,
category varchar(255) not null,
clientSaveTime datetime not null,
componentId varchar(30),
componentType varchar(30),
context varchar(30) not null,
data text,
event varchar(255) not null,
nodeId varchar(30),
serverSaveTime datetime not null,
periodId bigint not null,
runId bigint not null,
workgroupId bigint not null,
primary key (id)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
- id: unique id of this Event
- category: category of this Event, can be specified by emitter of the event. E.g. "Navigation", "Simulation"
- clientSaveTime: client timestamp when this Event occurred
- componentId: id of the component this Event is for
- componentType: type of the component this Event is for. e.g. "OpenResponse", "Draw"
- context: which context this Event is in, e.g. "VLE", "Component"
- data: extra data to save along with this Event
- nodeId: id of the node this Event is for
- serverSaveTime: server timestamp when this Event was saved in db
- periodId: id of the period that this Event was created for (id of period of workgroup who created this Event)
- runId: id of the run that this Event was created for (id of run of workgroup who created this Event)
- workgroupId: id of the workgroup that created this Event