https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/index.html Periodic tasks required to keep OAT running smoothly. Hugo en-us https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/permnums/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/permnums/index.html Permission numbers are used extensively by CS advisors to help students get into courses where something (prerequisites, class size, etc) is blocking them. Ideally, OAT would be able to fetch a permission number directly from Quest via a web service (see Implement permission numbers in OAT3, created 9 years ago and still outstanding). In the mean time, we ask the RO for a static list of permission numbers all with fixed expiry dates and a fixed set of permissions. Load them up into OAT where they get doled out by advisors. https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/plangroups/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/plangroups/index.html Plan groups are a really useful abstraction (especially for queries) but require maintenance as new plans are defined. Plan groups are defined by a set of queries in oat3/sql/operations/planGroups/. These queries update tables in the database. Advice: It’s best to do this against an up-to-date dev database first. That’s been hard to come by so it’s typically done with prayers against the production database. New plans (not in a plan group) are reported in the automatic morning “OAT Health” email. Don’t let the list get too long! The current methodology does not let you work on a subset. If the list gets too long, things get confusing. Here are the basic pieces: https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/updateforms/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/updateforms/index.html The contents of a form is controlled by JSON in the oat-forms project. This assumes you’ve got it cloned and pulled any recent updates. Update the JSON source Edit the source for the form in question (changes) or create a new file for a new form. Review Form Definitions for more info. Load the changes The bin directory in the oat-forms project contains the following scripts: archiveForms.sh: Used to archive forms after decisions have been made. It retains the information just in case, but those forms will no longer appear in the admin pages in OAT. updateForms.sh: Used to make minor adjustments to an existing form such as dates for it to accept submissions, minor wording changes, etc. newVersion.sh: Used to make major changes to a form or introduce a new form. Major changes include adding or removing questions, changing the available answers, changing the expressions for displaying answers, etc. Major changes should only be done when no form submissions are “in process”. Notes: https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/updatemathcomms/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://cs.uwaterloo.ca/~cs-oat/devdoc/ops/updatemathcomms/index.html _oat.math_communication_requirements Sam St. Amand generates new versions of tables encoding Math Communications requirements and anti-requisites. This typically happens in late August. She’ll open a git issue or send the CSV files. They need to be loaded into the appropriate tables. It’s expected that the contents of the CSV will simply replace the existing data. Workflow Save the math communications CSV to /oat3/sql/operations/math_comm_requirements/math_communication_requirements_YYYY_YY.csv where the Ys are filled in with the appropriate academic year (eg 2025-26). Run ./load_math_comm_requirements.scala math_communication_requirements_YYYY_YY.csv. Note that the script takes a --service argument (that defaults to oat-prod). _oat.uw_ug_antireqs Pretty much the same as _oat.math_communication_requirements but in the /oat3/sql/operations/ug_antireqs/ directory.