Data Model
The University Package uses two datatypes to store structured data: Global Datatypes, and Page Datafolders.
Organisational Structure
Although all academic institutions have a different structure, they can often be distilled down to something more generic:
-
Top level of the organisation (Global Datatype
BaileyWeb.University.Organisation)
-
Faculties or academic departments (Global Datatype
BaileyWeb.University.AcademicDepartments)
- Academic groups within the faculties (Page Datafolder BaileyWeb.University.Groups)
-
Committees (Page Datafolder
BaileyWeb.University.Groups)
- Committee working groups (Page Datafolder BaileyWeb.University.Groups)
-
Professional services and support groups (Page Datafolder
BaileyWeb.University.Groups)
-
Sub groups (Page Datafolder
BaileyWeb.University.Groups)
- Teams (Page Datafolder BaileyWeb.University.Teams)
- Teams (Page Datafolder BaileyWeb.University.Teams)
-
Sub groups (Page Datafolder
BaileyWeb.University.Groups)
-
Faculties or academic departments (Global Datatype
BaileyWeb.University.AcademicDepartments)
People, Groups and Teams
Institutions have senior staff, and these are linked from the top level organisation datatype:
-
Top level of the organisation (Global Datatype
BaileyWeb.University.Organisation)
- Senior staff (Page Datafolder BaileyWeb.University.People)
Academic departments have a Faculty Leader and a Senior Administrator, with all other staff included in sub-group and teams:
-
Faculties or academic departments (Global Datatype
BaileyWeb.University.AcademicDepartments)
- Faculty leader (Page Datafolder BaileyWeb.University.People)
- Senior administrator (Page Datafolder BaileyWeb.University.People)
-
Groups (Page Datafolder
BaileyWeb.University.Groups)
- Teams (Page Datafolder BaileyWeb.University.Teams)
Groups have a Group Leader, Senior Administrator and Group Members, with teams linked below. Each team has a Team Leader, Senior Administrator and multiple Team Members:
-
Committees (Page Datafolder
BaileyWeb.University.Groups)
- Group leader (Page Datafolder BaileyWeb.University.People)
- Senior administrator (Page Datafolder BaileyWeb.University.People)
- Group members (Page Datafolder BaileyWeb.University.People)
-
Professional services and support groups (Page Datafolder
BaileyWeb.University.Groups)
- Group leader (Page Datafolder BaileyWeb.University.People)
- Senior administrator (Page Datafolder BaileyWeb.University.People)
- Group members (Page Datafolder BaileyWeb.University.People)
-
Teams (Page Datafolder
BaileyWeb.University.Teams)
- Team leader (Page Datafolder BaileyWeb.University.People)
- Senior administrator (Page Datafolder BaileyWeb.University.People)
- Team members (Page Datafolder BaileyWeb.University.People)
Courses, Subjects and Modules
Courses are made up of one or two subjects, each of which contains a list of modules:
-
Top-level course information (Page Datafolder
BaileyWeb.University.Courses)
-
Main subject (Page Datafolder
BaileyWeb.University.Subjects)
- Multiple modules that make up a subject (Page Datafolder BaileyWeb.University.Modules)
-
Optional second subject (Page Datafolder
BaileyWeb.University.Subjects)
- Multiple modules that make up a subject (Page Datafolder BaileyWeb.University.Modules)
-
Main subject (Page Datafolder
BaileyWeb.University.Subjects)
Collectively, these are the programmes of study.
Courses are grouped by StartDate, CourseLevel (Global Datatype BaileyWeb.University.EducationLevels), then listed alphabetically by the CourseCode field. This allows variations in entry requirements, application methods, and even fee bands, according to the time of year that the course starts.
Subjects are grouped by SubjectLevel (Global Datatype BaileyWeb.University.EducationLevels), then listed alphabetically by the SubjectCode field. There is no StartDate field for subjects, so if you wish to introduce variations in the subject according to its start date, prefix the SubjectCode and SubjectName field with a year or date value.
Modules are also grouped by ModuleLevel (Global Datatype BaileyWeb.University.EducationLevels), then listed alphabetically by the ModuleCode field. Again there is no StartDate field for modules, so if you wish to introduce variations in the module according to its start date, prefix the ModuleCode and ModuleName fields with a year or date value.
CMA Guidance
In the UK, the Competition and Markets Authority (CMA) has issued guidance (Higher Education: consumer law advice for providers) to help institutions understand their responsibilities under consumer protection law when dealing with students. This is particularly important in relation to courses, subjects and modules, as well as fees (see below), where the student must be made aware of any changes made to them between initial enquiry, application, registration and enrolment, and onward until graduation.
The presence of the StartDate field in the data model for courses facilitates this, especially when combined with your institution's own course management and workflow processes.
Course and Module Fees
To keep things as simple as possible, the University Package uses fee bands to separate currency values from the course and module data. Courses and modules can each be given a fee band, and each fee band's currency value can change year-on-year. This lets applicants view how the fees have risen historically, and see how much a programme will cost if they defer entry. It also lets your institution market courses and modules individually, possibly creating new income streams.
-
Course information (Page Datafolder
BaileyWeb.University.Courses)
-
Course fee bands (Global Datatype
BaileyWeb.University.CourseFeeBands)
- Course fee band costs (Global Datatype BaileyWeb.University.CourseFeeBandCosts)
-
Course fee bands (Global Datatype
BaileyWeb.University.CourseFeeBands)
-
Module information (Page Datafolder
BaileyWeb.University.Modules)
-
Module fee bands (Global Datatype
BaileyWeb.University.ModuleFeeBands)
- Module fee band costs (Global Datatype BaileyWeb.University.ModuleFeeBandCosts)
-
Module fee bands (Global Datatype
BaileyWeb.University.ModuleFeeBands)
You can hide fee bands for some years by changing the Display field value in the Global Datatype BaileyWeb.University.AcademicYear.
Subjects do not have fee bands, as they are added when you create a course entry for the subject.
Course and Module Entry Profiles
Programmes have a list of entry requirements, many of which are standardised and common to multiple programmes. Therefore, we have datatypes for these entry profiles:
-
Entry profiles (Page Datafolder
BaileyWeb.University.EntryProfiles)
- Language requirements (Page Datafolder BaileyWeb.University.LanguageRequirements)
-
List of profile qualifications (Global Datatype
BaileyWeb.University.EntryProfileQualifications)
- Qualification types (Global Datatype BaileyWeb.University.Qualifications)
Because some entry profiles may be common across courses and modules, we don't need to have separate datatypes for them as with fee bands and costs.
Subjects do not have entry profiles, as they are added when you create a course entry for the subject.
Equivalent Qualification Frameworks
For institutions in the UK, this allows you to display qualification equivalents from the Regulated Qualifications Framework (RQF), alongside international qualifications from National Academic Recognition Information Centre (NARIC).
Projects, Case Studies and Publications
For research output, we detail the research project itself, the people conducting it, the outcomes, and related case studies that help to promote the research outcome.
-
Project information (Page Datafolder
BaileyWeb.University.Projects)
- People involved in the project (Page Datafolder BaileyWeb.University.People)
- Case-studies related to the project (Page Datafolder BaileyWeb.University.CaseStudies)
- Publications (Page Datafolder BaileyWeb.University.Publications)
Collections and Campaigns
Collections allow institutions to gather together all information about a specific topic in one place. The location of the the data doesn't change, but the campaign page acts as a hub linking the different pieces together in a coherent way.
-
Collection (Page Datafolder
BaileyWeb.University.Collections)
- Pages (C1 Pages)
- Courses (Page Datafolder BaileyWeb.University.Courses)
- Subjects (Page Datafolder BaileyWeb.University.Subjects)
- Groups (Page Datafolder BaileyWeb.University.Groups)
- Teams (Page Datafolder BaileyWeb.University.Teams)
- Locations (Page Datafolder BaileyWeb.University.Locations)
- News (Page Datafolder BaileyWeb.University.News)
- Events (Page Datafolder BaileyWeb.University.Events)
- Campaigns (Page Datafolder BaileyWeb.University.Campaigns)
- Case studies (Page Datafolder BaileyWeb.University.CaseStudies)
- People (Page Datafolder BaileyWeb.University.People)
- Projects (Page Datafolder BaileyWeb.University.Projects)
- Publications (Page Datafolder BaileyWeb.University.Publications)
Campaigns are similar to collections in that they group certain information together, but rather than being passive, they are designed to elicit a response from the website user.
-
Campaign (Page Datafolder
BaileyWeb.University.Campaigns)
- Campaign type (Global Datatype BaileyWeb.University.CampaignTypes)
- Group (Page Datafolder BaileyWeb.University.Groups)
- Team (Page Datafolder BaileyWeb.University.Teams)
- Enquiry contact (Page Datafolder BaileyWeb.University.People)
News and Events
The news and event pages describe what's going on at the institution. Once again they link off to related data elsewhere in the website.
-
News (Page Datafolder
BaileyWeb.University.News)
- Location (Page Datafolder BaileyWeb.University.Locations)
- Courses (Page Datafolder BaileyWeb.University.Courses)
- Subjects (Page Datafolder BaileyWeb.University.Subjects)
- People (Page Datafolder BaileyWeb.University.People)
- Project (Page Datafolder BaileyWeb.University.Projects)
-
Event (Page Datafolder
BaileyWeb.University.Events)
- Venue (Page Datafolder BaileyWeb.University.Buildings)
Locations and Buildings
These two datatypes provide information about the campuses, and the buildings, lecture theatres or venues they contain.
-
Location (Page Datafolder
BaileyWeb.University.Locations)
- Building (Page Datafolder BaileyWeb.University.Buildings)