{"id":1659,"date":"2016-11-14T17:02:42","date_gmt":"2016-11-14T17:02:42","guid":{"rendered":"https:\/\/www.education.uw.edu\/coeir\/?p=330"},"modified":"2016-11-14T17:02:42","modified_gmt":"2016-11-14T17:02:42","slug":"cycle-45","status":"publish","type":"post","link":"https:\/\/coedev.education.uw.edu\/technologycenter\/workplans\/cycle-45\/","title":{"rendered":"Cycle 45"},"content":{"rendered":"<p>\n\tOct 17, 2016 &#8211; Nov 10, 2016\n<\/p>\n<p>\n\tOur 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.\n<\/p>\n<p>\n\tInstead 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.\n<\/p>\n<p>\n\tHaving this config in a separate file allows us to manage it in version control and test configuration in developement&nbsp;and deploy those exact changes to production.\n<\/p>\n<h2>\n\tWork Complete<br \/>\n<\/h2>\n<h3>\n\tAppreview<br \/>\n<\/h3>\n<ul>\n<li>\n\t\tResolved empty committee assignment bug.\n\t<\/li>\n<\/ul>\n<h3>\n\tCourses<br \/>\n<\/h3>\n<ul>\n<li>\n\t\tAdded reason options and locking to course release.\n\t<\/li>\n<\/ul>\n<h3>\n\tSTEP<br \/>\n<\/h3>\n<ul>\n<li>\n\t\tRevised doctoral committee loader for change in Grad School data file.\n\t<\/li>\n<\/ul>\n<h3>\n\tStudent 2<br \/>\n<\/h3>\n<ul>\n<li>\n\t\tFixed import STEP users.\n\t<\/li>\n<li>\n\t\tProvided a basic CSV download. This only includes student name and program at the moment, but will be built out in future work.\n\t<\/li>\n<li>\n\t\tModified the data load from UW Enterprise Data Warehouse to use student preferred name when available.\n\t<\/li>\n<li>\n\t\tCatalog STEP milestone rules and behavior for implementation in Student 2. Build database schema that will store milestones.\n\t<\/li>\n<li>\n\t\tBuilt a &quot;Requirements Graph&quot; 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.\n\t<\/li>\n<li>\n\t\tRequirements 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.\n\t<\/li>\n<li>\n\t\tRequirements can be filled (marked complete) based on data found in UW transcript via UW Student Web Service.\n\t<\/li>\n<li>\n\t\tExisting milestone data has been imported from STEP. This is a re-runnable sync process which will be regularly run through launch of Student 2.\n\t<\/li>\n<li>\n\t\tMilestones can be filled by import of doctoral committee data from Grad School.\n\t<\/li>\n<li>\n\t\tForm for staff to manually mark a milestone complete.\n\t<\/li>\n<\/ul>\n<h3>\n\tTech Support<br \/>\n<\/h3>\n<ul>\n<li>\n\t\tAdd CQEL as department in ticket system with custom email ingestion.\n\t<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Oct 17, 2016 &#8211; 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&#8230;<\/p>\n<div><a class=\"more-link\" href=\"https:\/\/coedev.education.uw.edu\/technologycenter\/workplans\/cycle-45\/\">Continue reading <span class=\"screen-reader-text\">Cycle 45<\/span><\/a><\/div>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[10,13],"tags":[],"class_list":["post-1659","post","type-post","status-publish","format-standard","hentry","category-workplans","category-workreviews"],"aioseo_notices":[],"featured_image_urls_v2":{"full":"","thumbnail":"","medium":"","medium_large":"","large":"","1536x1536":"","2048x2048":"","320w":"","480w":"","800w":"","mug-shot":"","sidebar-width":"","full-content":""},"post_excerpt_stackable_v2":"<p>Oct 17, 2016 &#8211; 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&hellip;<\/p>\n<div><a class=\"more-link\" href=\"https:\/\/coedev.education.uw.edu\/technologycenter\/workplans\/cycle-45\/\">Continue reading <span class=\"screen-reader-text\">Cycle 45<\/span><\/a><\/div>\n","category_list_v2":"<a href=\"https:\/\/coedev.education.uw.edu\/technologycenter\/category\/workplans\/\" rel=\"category tag\">Work Plans<\/a>, <a href=\"https:\/\/coedev.education.uw.edu\/technologycenter\/category\/workreviews\/\" rel=\"category tag\">Work Reviews<\/a>","author_info_v2":{"name":"Paul Hanisko","url":"https:\/\/coedev.education.uw.edu\/technologycenter\/author\/haniskowashington-edu\/"},"comments_num_v2":"0 comments","_links":{"self":[{"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/posts\/1659","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/comments?post=1659"}],"version-history":[{"count":0,"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/posts\/1659\/revisions"}],"wp:attachment":[{"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/media?parent=1659"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/categories?post=1659"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/coedev.education.uw.edu\/technologycenter\/wp-json\/wp\/v2\/tags?post=1659"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}