Teachers, Administrators and EA/TAs in the schools will be listed in a teacher table in the schools. As such they can be identified by a school:userid approach. For example a teacher in a school called St Mary's might be stmary:fredflintstone.
Other School Division staff not associated with a school, are stored in a single table listing their userid, name, agency (if not central office), and phone, email, and designation (psychologist, etc.)
We have divided educational expectations into different subjects, some of which are traditional subjects; some are not.
The subject areas are given numbers (and associated text). For example, Language - Receptive is number 105 while Gross Motor Development is 200.
Within each subject area, particular objectives are given numbers to identify them. For example, within 105 Language - Receptive, the first objective is 1 - Show Awareness of Speaker and would have a unique identification of 105-1 while the the third, 3 - Look in response to own name, would be 105-3.
When setting up an evaluation program for students, particular learning outcomes/objectives from each subject (105-1, 105-3) are added to a student's evaluation master for each subject. (S)he will then be evaluated throughout the year in each subject based on the objectives chosen for him/her.
Groups of objectives are added for each student in an evaluation master. We call these groups of objectives, subjects. Each of those subjects can have up to 32 objectives from that subject area.
When evaluations are done each term, a teacher will evaluate each student in each subject. If a subject record for this term already exists, its values are read. If no record exists for this term, a new one is created. Values and commentary are entered for this record and then it is stored.
Evaluations:
Report cards will be generated for this student and all evaluation records for this and previous terms will be read and used to create a simple report card.
In general we will link to other information in the school's database for contact information, etc. although this is only loosely linked so the IEP system could very well be stand alone.
id - record id
lastname - char(40) - student lastname
firstname - char(40) - student firstname
birthdate - date - birthdate
studnum - integer - division student number
provnum - varchar(12) - provincial/state student number
desdate - date - date of designation
ddpflvl - char(6), - ddpf level
designation - char(60) - designation
grade - char(6) - grade placement
school - char(60) - school (Name and code)
sex - char(1) - gender of student
medical - text - description of medical condition.
medication - text - medication required.
equip - text - required equipment for student.
adapt - text - school physical adaptations required by this student.
id - record number
userid - a short field identifying this person.
lastname
firstname
jobtitle
agency
phone
email
id - record id.
studnum - number of the student whose team this member is on.
userid - userid and school/agency identifying this person.
jobtitle - role
phone - redundant contact info
email - redundant contact info
id - record id
studnum - student number
category - char(255) - text matching category from assesscat.
reqdate - date assessment requested.
resdate - date assessment completed.
comment - text - commentary on assessment.
id - record id
category - char(255) - text specifying category
id - record id.
catnum - integer - a number specifying the category of this objective.
category - text - a word or phrase describing category of this objective - these two fields are tied.
idnum - int - a number for this objective/expectation. Identifies it within the category.
grade - char(8) - possibly the grade of the expectation (some subjects) - rarely used.
description - description of the objective/expectation - tied to idnum. They go together.
commentcodes - char(255) - codes linking to a comment table; unused currently.
id - record id
studnum - integer - the student number
subnum - integer - the category number (catnum) from the subject table (The idnums and descriptions of the objectives from the subject table are stored in each of the individual objectives obj1, obj2, etc). There is no need for lookup into the subject table once evaluation masters are created at the start of the year.
method - text - a brief description of the teaching techniques used.
responsible - text - who is responsible for implementing this subject.
obj1, obj2, ... obj32 - objectives/expectations. - text - contain text description of the subject.
Note: First fields common with the evalmaster; only term and commentary extra.
id - record id
studnum integer - the student number
subnum integer - matches subject in EvalMst table.
obj1, obj2, ... obj32 - char(16) objective results
term - the term number for this record.
comments - text; a long text field for commentary