Review of Teacher Training and Subject Data Model

[Ghislain Hachey]

Some things need to be reviewed, discussed and maybe refined. Some notes:

• TeacherSurvey’s tchTrained, tchSubjectTrained, tchSubjectMajor, tchSubjectMinor and tchSubjectMinor2. What they really are in each adopting countries and how to best keep this consistent (all had their repective lookup tables?)
• TeacherTraining’s trMajor and trMinor how they related
• lkpTeacherTraining how it relates and how best to use
• lkpSubject and ISCEDField* tables. These are pretty clear but make sure how they fit in the big picture.
• How does it link with in-service training

‌

[Ghislain Hachey]

While this was not high priority for some time latest effort by some other consultants in FSM have brought the light back on this. It is important to be able to link teachers with their trained subjects with relatively cleaned dataset. the approach I am taking is summarized as follow.

lkpSubject can be used for subjects taught in schools by teacher, subjects teachers were trained in (in their academic degree major for example, and essentially anywhere a “subject” is needed). This allows a link to ISCED-F standardized subjects everywhere making for better data analysis.

The workbook’s Field of Study for staff is already linked (without a foreign key constraint) to the lkpSubject table. The workbook loads the dropdown list from there and the procedure puts the subjCode on the TeacherSurvey row. This ones provides decent data down the line.

I am going with a similar strategy for dbo.TeacherTraining in trMajor/trMinor. We get the subjects from there. First, I extract all the data in there and clean it a little before putting into lkpSubjects (when missing). Then I map the lkpSubjects code in trMajor/trMinor. Then I will build the dropdown UI in the EMIS online to ensure cleaner subject data going forward.

There will be no foreign key constraint at first but it would be good to consider them. Allowing free entry just gets messy and needs manual intervention to get the ISCED-F link and clean analysis.

I have created a seperate issue for this work #1201

[Ghislain Hachey]

Also, I have notice that the staff loading no longer maps the field of study to a column in TeacherSurvey.

We had data there I am not sure anymore if I promoted this ad-hoc from SQL query of the xml data. But as is this code should not just be commented as the code of the subject should be the one stored on the tchSubjectMajor (and not tchTrained?!)