Oct 17, 2016 – Nov 10, 2016
Our original vision for Credits and Milestone requirements was that they could be configured through a user accessible web UI. As we documented the complexity and inter-relatedness of these objects it became clear that a user GUI was a bad approach. Configuring the many requirements would have been time consuming and error prone.
Instead we decided to create a declarative configuration file which would provide an orderly overview of entire requirements set. This config file has a loader that reads it and generate the operation database records to run the system.
Having this config in a separate file allows us to manage it in version control and test configuration in developement and deploy those exact changes to production.
Work Complete
Appreview
- Resolved empty committee assignment bug.
Courses
- Added reason options and locking to course release.
STEP
- Revised doctoral committee loader for change in Grad School data file.
Student 2
- Fixed import STEP users.
- Provided a basic CSV download. This only includes student name and program at the moment, but will be built out in future work.
- Modified the data load from UW Enterprise Data Warehouse to use student preferred name when available.
- Catalog STEP milestone rules and behavior for implementation in Student 2. Build database schema that will store milestones.
- Built a "Requirements Graph" system that loads all of the credits requirements and milestones requirements relevant to a specific student and bind the conditional and dependency relationships between requirements.
- Requirements config loader system. Includes a sparse readable configuration file which contains settings for Student Sets (rules for selecting students by program and degree), Credits Requirements, and Milestone Requirements. A loader system takes this file and generates operational entities in the database. The requirements config file can be managed in version control and promoted from development to production environment.
- Requirements can be filled (marked complete) based on data found in UW transcript via UW Student Web Service.
- Existing milestone data has been imported from STEP. This is a re-runnable sync process which will be regularly run through launch of Student 2.
- Milestones can be filled by import of doctoral committee data from Grad School.
- Form for staff to manually mark a milestone complete.
Tech Support
- Add CQEL as department in ticket system with custom email ingestion.