-
Notifications
You must be signed in to change notification settings - Fork 0
Student Actions
This document contains exhaustive details of terms in the "Student Action Grammar", which forms part of the core data model in our "Student Outcome Accelerator" (SOAR). An example of such a term is Attended Practical, the meaning of which should be fairly self explanatory.
The rest of the document is split into two sections. First we list the actions which we may infer directly from the datasources available to our project. We refer to these as 1st order actions. Then we list any actions which require inferred 1st order actions in order to be inferred.
For each action we include a brief description, a list of its dependencies and the specifics of how it will be inferred. Where appropriate we may also add xAPI recipes for each action so that we can more easily export data to compatibile learning record stores etc...
A student has printed something.
Points of interest: Were they logged on in a nearby cluster when they did i so? Also, are the students in the midst of a materials gathering session?
-
Printer: The printer which the student used to print. From our perspectives the key piece of information in this datasource is where the printer is. This datasources is represented by the table
DIM_Printer
in sql12, which has the following schema:CREATE TABLE [dbo].[DIM_Printer] ( [PKprinters] [int] IDENTITY(1,1) NOT NULL, [Location] [nchar](50) NULL, [PageSize] [nchar](3) NULL, [Colour] [nchar](10) NULL )
-
Print: The print job which the student initiated. References
PKprinters
from theDIM_Printer
table. From our perspectives the key piece of information in this datasource is when the print job took place. The datasource is represented by the tableSTAR_Print
in sql12, which has the following schema:CREATE TABLE [dbo].[STAR_Print] ( [timestamp] [datetime] NOT NULL, [CalendarDate] [date] NULL, [PKstudent] [int] NOT NULL, [PKstudy] [int] NOT NULL, [PKstage] [int] NOT NULL, [PKprinters] [int] NOT NULL, [numsides] [int] NULL, [cost] [int] NULL )
-
Cluster Session: The cluster session which the student may have initiated prior to the print job in question. From our perspectives the key piece of information in this datasource is how long the cluster session is. I.e. did the student solely log in to print some material then log out immediately afterwards? The datasource is represented by the table
STAR_Cluster
in sql12, which has the following schema:CREATE TABLE [dbo].[STAR_Cluster] ( [timestamp] [datetime] NOT NULL, [CalendarDate] [date] NOT NULL, [PKstudent] [int] NOT NULL, [PKstudy] [int] NOT NULL, [PKstage] [int] NOT NULL, [PKCluster] [int] NOT NULL, [Time] [time] NULL, [duration] [bigint] NULL, [endtime] [datetime] NULL )
A student has attended a scheduled practical.
Points of interest: Do they stay for the entire practical slot? Are they doing what they're supposed to be doing during the practical slot?
-
Cluster: The phsyical cluster in which the student logs on to a machine. From our perspectives the key piece of information in this datasource is the cluster id. This datasource is represented by the table
DIM_Cluster
in sql12, which has the following schema:CREATE TABLE [dbo].[DIM_Cluster] ( [PKCluster] [int] IDENTITY(1,1) NOT NULL, [PCname] [nchar](40) NULL, [Cluster] [nchar](40) NULL, [Building] [nchar](40) NULL, [isbookable] [char](1) NULL )
-
Cluster Session: The session that a student has initiated in a given cluster. From our perspectives the key piece of information in this datasource is how long the session lasts for, especially relative to the practical length. References
PKCluster
fromDIM_Cluster
. The datasource is represented by the tableSTAR_Cluster
in sql12, which has the following schema:CREATE TABLE [dbo].[STAR_Cluster] ( [timestamp] [datetime] NOT NULL, [CalendarDate] [date] NOT NULL, [PKstudent] [int] NOT NULL, [PKstudy] [int] NOT NULL, [PKstage] [int] NOT NULL, [PKCluster] [int] NOT NULL, [Time] [time] NULL, [duration] [bigint] NULL, [endtime] [datetime] NULL )
-
Timetable: The timtable service from which we retrieve a practical's scheduled time and cluster. This time and cluster will be compared to the information across the two datasources above to infer a practical attendance
A student uses a cluster for Independent study outside of a scheduled practical slot.
This action requires the same datasources as Attended Practical, except that we use the timetable to verify that there was no scheduled practical session at the time/cluster which a student is using.
-
Module
-
Content ID
- How Long?
- Code
-
Date
-
Code
-
Decision Code
-
Final Mark
- Code
- Final Mark
- Code
- Final scheduled slot
- Did student physically attend?
-
Length of Recap session As a ratio of the length of the Recap vid. A short session could imply that the student only cares about a small portion of the content covered, which would be consistent with the use of the material for reference or revision.
-
Repeated Recap watch? Repeated watches of a specific Recap vid would be consistent with Revision. This is especially true if the recap watches are somewhat spread out over time, and/or their total length isn't close to the total length of the Recap Vid in question.
- Has the Student got an upcoming submission or exam?
-
Session Length
-
Teaching Materials Accessed If a student uses blackboard for a short amount of time, accesses multiple pieces of teaching materials (across one or multiple modules) and uses a printer then they may be assumed to be materials gathering.
If two students sit at machines close to one another during independent cluster use or practical attendance then they may have collaborated. The likelihood of this collaboration increases if the physical collocation is frequent. The likelihood also increases if the start/stop times for a session of independent cluster use are similar.
-
Where?
-
Which machine?
-
How Long? (Start/Stop times)
-
Where?
-
Which machine?
-
How Long? (Start/Stop times)