Overview
A data catalog hierarchy is a way of organising data sources into categories and subcategories. In SEAtS, this means organising student data according to Faculty, School, Programme, Course or Module.
Catalog Hierarchy Levels
The hierarchy levels go from highest (Level 1) to lowest (Level 5):
- Level 1: Faculty: Faculty_ID,.
- Faculty_Name: Not mandatory.
- Level 2: School: School_ID,.
- School_Name: Mandatory (Student and Timetable imports).
- Level 3: Programme: Programme_ID,.
- Programme_Name: Not mandatory.
- Level 4: Course: Course_ID,.
- Course_Name: Mandatory (Student and Timetable imports).
- Level 5: Module: Module_ID,.
- Module_Name: Mandatory (Student and Timetable imports).
Levels 2, 4 and 5 (School/Course/Module) are mandatory within the Student and Timetable imports. Levels 1 and 3 are optional but if used, are required only in the Student import.
Site (Campus)
A Student's Site (Campus) is separate from the hierarchy. It is mainly used for the Devices hierarchy within SEAtS (Site/Building/Device) but can be set against each Student to use as a workflow constraint or as a dashboard filter.
Catalog Setup
The hierarchy setup depends on how many levels your institution needs. For example, a university with Department, Subject Area, Route and Module can map these in different ways, as long as mandatory levels 2, 4 and 5 are mapped to the correct fields.