Module instance start date(MODINSTSTARTDATE)
Navigation: Index / Data Dictionary / ModuleInstance / MODINSTSTARTDATE
Key | Value |
|---|---|
| Name | Module instance start date |
| Short Name | MODINSTSTARTDATE |
| Parent Entity | |
| Type | Field |
| Applicable To | England Northern Ireland Scotland Wales |
| Coverage | All ModuleInstances |
| Description | This field records the date of the start of the Module instance. |
| Notes | Where returned, the start date of the Module instance is the point at which scheduled learning and teaching begins for this Module instance. If students do not commence their module during an Induction or 'Freshers'' week, the start date should reflect the start date of the module attendance and not the induction week. If a ModuleInstance is recording a student's engagement with a Module that started in a previous StudentCourseSession, the start date should reflect the start of the engagement within the current StudentCourseSession, rather than backdated to the original start date. The ModuleInstance.MODULESTARTDATE should therefore always fall within the start and end dates of the associated StudentCourseSession. Where the ModuleInstance is being returned with no activity associated with it (ModuleInstance.INACTIVEMOD = 01), this date should align with the start date of the associated StudentCourseSession. All date fields must be completed using the ISO8601 format of YYYY-MM-DD. |
| Reason Required | To indicate the date on which the Module instance commenced, to determine whether to include the Module instance in any particular population definition. |
| Field Length | 10 |
| Quality Rules | Quality Rules to follow |
| Minimum Occurrence | 1 |
| Maximum Occurrence | 1 |
| Primary Key? | False |
| Revision History | No Revision History entries for this collection. |
