search

TSSlade / tusome_db

Repository for design and development of Tusome's M&E database
0 stars 6 forks source link

List of persons- I propose below for this section #6

Open Lwambari opened 5 years ago

Lwambari commented 5 years ago
  1. Lists of Persons o These are primarily reference lists of personnel in whom Tusome has an interest. The data would include their phone contacts and their email addresses They would include but not necessarily be limited to  teachers: mapped to their streams, grades, and schools  Head teachers- mapped to their schools  Deputy head teachers- mapped to their schools  CSOs or coaches: mapped to their zones  SNE CSOs mapped to their sub counties and areas of specialization.  education officials: these includes: Regional Cordinators (MoE and TSC), County directors (MoE and TSC), TSC deputy County directors QASOs (MoE and TSC), SCD (MoE and TSC) CPCs. MoE head office directors and TSC directors. SAGAs directors and SAGAs contact person mapped to their geographic area of responsibility and their institution  NTTs mapped to their employers (MoE, TSC, SAGAs)  PPTCs: Names, Location (county subcounty and tusome region) Name of Principle and deputy and contacts. Dean of Cir name, Lectures numbers for English and kiswahili  RTI personnel: mapped to their geographic area of responsibility and their unit/team (technical vs Operations)  Training captains in CSO trainings mapped to their county  TOT trainers mapped to their role and county/subcounty/zone of work.
TSSlade commented 5 years ago

Thanks for the notes, Lucy. FWIW, I'm having a hard time quickly seeing what's new. Consider making the changes directly in the db_scoping_notes.md and then submitting a PR.

If I'm seeing things properly, you've flagged HTs and DHTs. I think those are important - good call. My main question would be whether we should think of "teachers" as actually being "school-based personnel" and then where one attribute of the person is "grade", we could also have an attribute that is "head" (boolean true/false) and another attribute that is "deputy head" (boolean true/false). That way we can very gracefully deal with the cases where the HT and DHT have teaching duties as well, and we keep all of our school-based personnel in a single list.

Good call on the SNE-CSOs. I'm not sure if the fact that they're mapped to subcounties instead of zones necessarily requires that they be treated in a separate list from CSOs - that'd be something for the DB schema designer to advise us on.

For NTT, I think it's a cleaner database if our list of education officials has a boolean flag for "member_of_NTT".

Good call on adding the PTTC personnel. I think the PTTCs are an entity (distinct from schools), and I think DK was going to add something to that effect to his PR. Keep an eye out for it and add your own if you don't see his come in.

For the training captains, I think that's a list we derive from joining our personnel (teachers, CSOs) to our training venues - I don't think it's a list we should maintain separately. Ditto for TOT trainers - although the fact that you're bringing in the TOT trainers may suggest the need for an update to our activity-based thinking to reflect training events/activities at levels other than simply the last stage of the training.