Skip to main content

Collection Design Project: version 3

Welcome to design phase version 3 of the Collection Design Project

Please note, version 3 pages are still available for your reference, but we have disabled links to avoid confusion: please refer to the Data Futures Resources page for project documents for your consideration.

Version 3 is an evolution of the model presented at version 2, it represents the final version of the Collection Design Project.  After this the model, will move into the Detailed Design Phase of the Data Futures programme.  The model will continue to evolve throughout this and the pilot phases until it is finalised.

This has been shaped by the feedback from version 2. We believe the design to be nearly complete, except where deliverables are specifically marked out of scope or where a small number of open questions are still under review.

The main additions to version 3 are the data journeys, the translations between the current and future physical states, and detail around the quality assurance process.

If you have comments or concerns about this model, please use our feedback form, there are links to it throughout the following pages.

The outputs from version 3 – including any of your feedback – will form the starting point for the Detailed Design Phase which is due to run from March to August 2017. More information will be made available on the Data Futures programme pages.

We have listed below what has changed between the versions for your understanding, alongside new content - beneath this table is the user journey, with additional user journeys available to download as PDFs:

Page/s What's changed
NEW: What's changed between V2 and V3  
HE Providers: Supply Side NEW: V3 Supply Side
Supply-side: Logical Model

NEW: V3 Logical Model

  • Segment schematic
Supply-side: Implementation

NEW: V3 Supply-side Implementation

  • Updated data dictionary
  • Translation mapping
NEW: Derived fields  
Data Customers: Demand Side NEW: V3 Demand Side
UPDATED: QA Overview is now QA Implementation

NEW: QA Approach

UPDATED: QA Overview is now QA Implementation

Known Issues NEW: V3 Implementation approach
UPDATED: V3 Areas of Feedback Updated with new areas
UPDATED: Glossary of Terms Updated with new terms
UPDATED: FAQ

Updated with V2 queries

Introduction to version 3

The collection design model views data as a natural output of the HE provider’s own internal business processes, therefore submissions follow in close proximity to business events such as registration and enrolment.

The design proposes two Reference Points within the academic year. The Reference Points are points in time where HE providers sign-off their data for statutory and public purposes and reliable cross sector analysis can be performed. Each Reference Point contains: data on enrolments and; more widely the status of the student population including leavers, changes, achievements between Reference Points. In effect this provides four data viewpoints during the academic year.

The schematic below demonstrates how this will work for a typical full-time undergraduate enrolling in Autumn.

Scenario A: Student data journey for cohort enrolling in the Autumn semester (full-time undergraduate)

The table below describes a number of common business events triggers and the relation of these events to reference points.

Business Event

Condition Segment Latest submission for this scenario Comments Exceptions
Registration Student registers S2 registration Reference point 1a New registration

Student changes/ leaves/ joins HE provider - update registration or leaver details as appropriate by Reference Points

Enrolment Student enrols S3 Enrolment Reference point 1a New enrolment

Student changes/ leaves/ joins course – update enrolment details by Reference Points

Enrolment Continuing student enrols S3 Enrolment Reference point 1a

New enrolment and previous enrolment status updated

Student changes/ leaves/ joins course – update enrolment details by Reference Points

Student starts module

Students starts module

S4 Learning Event

  • Depending on module start date:
  • Reference Point 1a
  • Reference Point 2a
  • Reference Point 1b

New learning event

Student changes/ leaves/ joins module - update learning event details by Reference Points

Student completes module

Student completes module and marks given

S4 Learning Event

  • Depending on module completion date:
  • Reference Point 1a
  • Reference Point 2a
  • Reference Point 1b
Update learning event  
Student completes course session

Student completes course session (continuing student)

S3 Enrolment Reference Point 1b Update enrolment status  
Award qualification

Student completes all course sessions and awarded qualification

S5 Leaver Reference Point 1b

New leaver and qualification award

Interim awards require S5 to add new qualifications but do not result in creation of leaver entity

We have modelled out a January nursing start, an OU or distance learning student and an ITT journey in the same level of detail, download the PDF below to find out more:

Data Journeys