Learning Analytics Documentation

Overview of the approach

The architecture is open to any supplier working with a University or College, or who wishes to enter the market. The project has two phases: Pilot Phase and Production Phase.

Pilot Phase

During the pilot phase all elements of the service are provided by Jisc to institutions. Suppliers for this phase were selected by Framework, and are Blackboard, CETIS, Torchbox, Tribal and Unicon/Marist/Hull.

Production Phase

The service will formally enter production phase in Summer 2017. However we are gradually phasing in production processes in advance of this date. Whilst the full details are still be finalised, the service will broadly be split into two areas, show in the diagram below in Red and Blue.

image-la-arc-overview

Blue elements are core Jisc services, whereas Red Service are areas that members may wish to buy the service that best meets their needs. Jisc may provide 'lite' services in these areas to help institutions develop a full idea of the service they which to buy.

Conceptually, we have been using an analytics maturity model to describe the services an institution needs at various levels of analytics maturity. Learning Analytics is part of this, and services provided by Jisc and suppliers can also be viewed using this model as shown below.

Analytics Maturity and Services

We are currently developing a procurement framework for these services. The aim of this is:

  • ▪ To make the services easy to buy
  • ▪ To provide a degree of quality assurance to institutions.

A broad technical overview

On a technical level, the first thing to consider is your application type, the data scenario, and your stage. The route to integrating depends on these three factors:

Application types:

  • ▪ Data contributor
  • ▪ Data reader

Scenarios:

  • ▪ Data models and recipes already in architecture
  • ▪ Need new data or recipes

Stage:

  • ▪ Working with a University
  • ▪ Bringing new product to the sector

Examples

1. Data contributor >> Data models and recipes already in architecture >> Bringing new product to the sector

  • ▪ Contact Jisc briefly describing application
  • ▪ Jisc provide key contact, and access to ‘University of Jisc’ Sandpit
  • ▪ Review legal documentation for data sharing and agree in principle
  • ▪ Vendor integrates with ‘‘University of Jisc’ Sandpit
  • ▪ Jisc approves application (this is optional, but we think will help!)
  • ▪ Customer requests application allowed to submit to their LRW (Staging or Production)
  • ▪ Three way data release document signed (Jisc, Vendor, University)

2 Data contributor and reader >> Needs new recipes >> Working with existing University/College Institution

  • ▪ Contact Jisc briefly describing application
  • ▪ Jisc provide key contact, and set up data definition/recipe process.
  • ▪ Review legal documentation for data sharing and agree in principle
  • ▪ Other interested parties invited to collaboration on definition process
  • ▪ Data/Recipe definition process >> recipes, definition released
  • ▪ Partner institution requests application has access to staging/production
  • ▪ Application trials/pilots as previous example.

Contributing to development of the Architecture

Role 1) Contributor

Action: Review activity on Github, contributing issues and requests.

Role 2) Technical member

Action: participation in short, regular online meetings to review pull requests, and approve patches and releases

Role 3) Steering member

Action: participation in longer face-to-face meetings to contribute to direction of architecture