Continuing module(CONTINUING)
Navigation: Index / Data Dictionary / ModuleInstance / CONTINUING
Key | Value | ||||
---|---|---|---|---|---|
Name | Continuing module | ||||
Short Name | CONTINUING | ||||
Parent Entity | |||||
Type | Field | ||||
Applicable To | England Northern Ireland Scotland Wales | ||||
Coverage | All ModuleInstance entities where applicable | ||||
Description | This field indicates where a module is being continued from a previous StudentCourseSession | ||||
Notes | ModuleInstances must not span StudentCourseSessions. Therefore, when a student studies a module that spans StudentCourseSessions, multiple ModuleInstances would be required to be returned. Where the ModuleInstance represents a student studying a module that started in a previous StudentCourseSession, this field must be returned to indicate this. For example, a student studies a Module that spans StudentCourseSession 1 and StudentCourseSession 2. ModuleInstance 1 would cover the period where the student is engaging with the module as part of StudentCourseSession 1. This ModuleInstance would have a ModuleInstance.MODULEUTCOME of 06 Will continue Module in subsequent StudentCourseSession'. ModuleInstance 2 would cover the period where the student is engaging with the module as part of StudentCourseSession 2. This Module Instance would have ModuleInstance.CONTINUING = 01. This ensures that it is recorded that the module is spanning StudentCourseSessions and so prevents double counting of information such as fees. | ||||
Reason Required | To record where modules span StudentCourseSessions and prevent double counting. | ||||
Field Length | 2 | ||||
Quality Rules | Quality Rules to follow | ||||
Minimum Occurrence | 0 | ||||
Maximum Occurrence | 1 | ||||
Primary Key? | False | ||||
Valid Values |
| ||||
Revision History | https://www.hesa.ac.uk/support/coding-manual-tools/revision-histories?Collection=22056 |