We want to have an understanding of what instructors need, so we send them mail before the start of term to learn of any changes to our current understanding. At the same time we let them know who their Point of Contact is (for each course they're teaching). We also use data provided by ISG to let them know who (if any) their Instructional Support Coordinator is.
The email is automated, using
/software/courses-cscf/maintenance/course-term-email
A typical workflow is:
cd /software/courses-cscf/config/sponsorshipswhere term names are of the form [WSF]\d\d\d\d, e.g.
cp ThisTerm NextTerm
chmod a+r NextTerm
cp F2015 W2016
course-term-email -d -p ./PoC >./datawhich records course information in "./data", and CSCF PoC assignments in ./PoC. `course-term-email` will assume the upcoming term if it's within a month from now, otherwise use the "-t" option to specify the term. You might find it handy to stash the ./PoC and ./data to facilitate quick lookup of course information.
crdb-in /software/courses-cscf/data/config/sponsorships/NextTerm | psql -h postgres.cs -d postgres -f /dev/stdinwhich assumes that you have a login to the database, and that it has the needed permissions, by being a member of the "_cscf_root" role. It's a PostgreSQL database and the Who Does What list suggests (as of 2015-08) that Isaac can provide the needed access, via "grant _cscf_root to <userid>".
course-term-email >tosend
course-term-email -s
ST-comment+NNNNNN@cs.uwaterloo.cawhere NNNNNN is the ST number created earlier.
In theory, everything we need to know about course needs should be in the course outlines maintained by the Course Coordinator. However that doesn't work in reality.