Skip to content

News

Open House

On September 15th we held an Information System Open House. We had the following project summaries posted and asked the staff and faculty who participated to vote for the ones that had value for them, were most valuable to college operations, should be prioritized.

Following are the projects listed in order of votes by Open House participants.

Courses

Better Support for Fiscal and ABB 18 Votes

Use Cases

  • As a fiscal manager I would like to see where the course plan affects the budget.
  • As leadership I would like to understand how future course plans will impact ABB allocations.

Implementation Plan

  • Identify triggers with fiscal implications, create reports that surface these conditions.
  • Add metadata to the system that allows categorization using ABB metrics. Example instructor roles.

Issues to Address

  • Some ABB inputs are out of scope of the courses database, for example ABB credits are based on the major of student who enroll in courses, not the unit offering the courses.

Person

Person Search 17 Votes

Use Cases

  • College faculty and staff would like to know what relationships a person has with the college. “Who is Jane Doe?”

Implementation Plan

  • Search interface for people that shows results over various college information systems.

     

    • Prospective students in Recruitment
    • Applicants in Applicant Review
    • Students in Student database
    • Instructors in Courses
    • Grant personnel
    • Faculty & staff

Fiscal & Budget

Faculty Commitment Database 12 Votes

Use Cases

  • Budget managers would like to have a record of commitments made to faculty for operations, budgeting, and forecasting. Specifically need to track items that can not be represented as encumbrances in UW central financial systems.

Implementation Plan

  • Commitments database would be accessible by the COE fiscal office. Commitment records could be edited and reported on.
  • System would integrate available UW person, appointment, and financial data to provide context and minimize user effort.
  • Additional requirements gathering is needed…

Courses

Put Course Plans on College Websites 10 Votes

Use Cases

  • As faculty I would like courses I teach included on my page on the College of Education website.
  • As administrator of a college program I would like courses related to the program listed on the program website.

Implementation Plan

  • Provide current courses and upcoming course plan as a web service.
  • College of Education website and program websites can consume this service to include up-to-date course information on their website.

Recruitment

Keep Me Informed 9 Votes

Use Cases

  • We would like prospective students to be presented with an approachable and concise form when they express interest.
  • Developer would like to have program list and program descriptions up-to-date in the Recruitment database.
  • College recruiters would like prospective students to accurately communicate their interests.

Implementation Plan

  • Let the college public website be the guide to college programs. Prospective students can click “Keep Me Informed” button on a program web page.
  • Button leads to a basic form that only asks for name and email. Secondary form prompts for additional prospect information like address and demographics.
  • Subsequent clicks on “Keep Me Informed” buttons no longer prompt for input, just show programs prospect has expressed interest in.

Student

Include Minors in Student Database 8 Votes

Use Cases

  • Advisors would like a list of students in the ELS Minor
  • Advisors would like to used Tracked Issues feature with ELS Minor students

Implementation Plan

  • Change population definition for student database to students who have College of Education major or College of Education minor.
  • For all students in population display all of their UW majors and minors.
  • Show all majors and minors that are included in degrees earned.
  • Create a list of students with ELS minor.

General

More Documentation 6 Votes

Use Cases

  • As a new employee of the college I would like self-guided learning tools to help with the college’s information systems.
  • As a current user of college’s information systems I would like clear explanations about purpose and meaning of systems.

Implementation Plan

  • More written documentation of college database available on a web site. Possibly in the COE Wiki or COE IR Blog.
  • More getting started video tours. These will be linked on the web site and included in the orientation Canvas course.
  • Better inline documentation. When building tools plan for new user to get the instruction they need.

Appreview

New Home Page 6 Votes

Use Cases

  • As a reviewer I would like to easily find specific applicants and have the important tools clearly highlighted.
  • As an administrator I would like database features listed so it’s easy to scan for the tool I need.

Implementation Plan

  • Revise Applicant Review home page in the style of Student database.
  • Show search bar on home page by default
  • Highlight important reviewer tools with visible buttons
  • Move menu options into site map displayed on home page

Tech Support

Better Tool for People Inputs 6 Votes

Use Cases

  • Tech staff would like to be able to set ticket fields with people quickly and accurately.

Implementation Plan

  • Person inputs replaced with type-ahead fields, user begins typing and matching persons are suggested. Input is matched against name and UW NetID.
  • Who ticket owner (client is)
  • Who assigned tech is
  • Who watchers are

Rooms

Room Info in Room Schedule 5 Votes

Use Cases

  • College faculty and staff would like to see any special instructions when scheduling a room. For example video conferencing help on the Zoom room schedule.

Implementation Plan

  • Add room notes to MRBS room schedule tool. When you look at the room schedule for a specific room or area helpful notes are displayed above the calendar.

Appreview

Data Warehouse for Application History 4 Votes

Use Cases

  • Applicant Review database must be brought into compliance with UW document retention policies. This means deleting non-admitted applications after 1 year.
  • As a program administrator I would like to know how applications have changed over time. Examples: number, demographic, academic background, admission rates.

Implementation Plan

  • Automated systems that purge applicant files after document retention deadlines.
  • Create an application data warehouse where anonymized versions of old applications can be stored for analysis.

Appreview

Sleeker Tools for Adjusting Committees 3 Votes

Use Cases

  • As a reviewer I would like the system to accurately reflect the applications I am reviewing. 
  • As a program lead or administrator I want to adjust review committees quickly without a lot of clicking around.

Implementation Plan

  • Provide reviewers a list of committees (default reviewers per program) they are assigned to.
  • Assign review teams from a list of applicants to a specific program. Suggest recently assigned teams.
  • Add a “Not Reviewing” recommendation. This would hide an applicant from reviewer’s My Applicants list.

Recruitment

Mailing Lists 3 Votes

Use Cases

  • College recruiters would like configuration in recruitment database to clearly express the behavior it affects.
  • College recruiters would like prospects to have the option to change interests instead of globally unsubscribing.

Implementation Plan

  • Convert unclear configuration concept "Interest Audiences" into Mailing Lists. Convert "Interests" configuration in to COE Programs.
  • COE Programs can be associated with Mailing Lists.
  • Automated email campaigns will be sent to Mailing Lists.
  • College recruiters can extract list of prospects based on Mailing Lists or Programs.
  • When prospects use an Unsubscribe link they are given option to remove Mailing List subscriptions (presented as "Interests") or to unsubscribe globally.

Test Scores

All Test Scores have Pass / Fail 3 Votes

Use Cases

  • Administrative staff looking at student test score would like clear indication of whether scores are sufficient.

Implementation Plan

  • Update imports to ensure all available agency Pass / Fail evaluations are brought into system and displayed in all test score contexts.
  • Implement pass/fail rules in system where that is applicable.
  • Provide interface for administrative staff to set Pass / Fail in other conditions. Our main case here is edTPA which has Pass / Fail criteria that change over time, by evaluation, and by state and UW campus.
     

Appreview

Better Rubric Score Reporting 2 Votes

Use Cases

  • As a reviewer I would like row-by-row comparisons of rubric scores entered for different applicants to my program in support of making and entering decisions.
  • As a program administrator I would like to download rubric scores for external analysis.

Implementation Plan

  • Revise rubric score data model to better support viewing multiple scores at once and extraction of data.
  • Option to download all scores entered using a specific rubric.

Appreview

Spreadsheet for Program Review Teams 2 Votes

Use Cases

  • As a program lead I would like to download a spreadsheet that I can use with my team that includes more fields relevant to the review and decision process.

Implementation Plan

  • Provide a download spreadsheet option tailored to review teams.

     

    • Include assigned reviewers and their recommendations
    • Include comments
    • Include GPA

Issues to Address

  • Some fields don’t lend themselves to two-dimensional spreadsheets, how can these be displayed usefully.
  • Certain field need context to be meaningful. For example meaning of GPA is impacted by degree, timeframe, school, etc.

Recruitment

End Communication 2 Votes

Use Cases

  • College recruiters would like recruitment database to include persons currently interested in college programs with out manual maintenance.

Implementation Plan

  • Make prospective student records dormant when we receive and application from the same email address.
  • Make prospective student records dormant when they have not expressed interest in the last year.
  • Separate the dormant and unsubscribe conditions. Dormant has a different meaning that recruiters may choose to override.

Courses

Streamlined Instructor Approvals 0 Votes

Use Cases

  • As an instructor I would like streamlined tools for reviewing and approving my courses. Important fields should be surfaced and it’s easy to provide feedback.
  • As the curriculum coordinator I would like to know who has reviewed their planned courses and see any feedback they provide.

Implementation Plan

  • All in one tool for instructors to review courses before UW time schedule construction. Important fields are displayed, one click Approve button, room preference fields are one that page.
  • Course approvals are displayed in the course offering detail in the workflow box. Approval whos and whens are included in log.

Cycle 65

8/28/2017 – 9/8/2017

This cycle I dug into including students with ELS minor in the student database. Including minors is a new data concept for out system and is requiring some low level restructuring. Updates on this next time.

Second project in process is a new interface for instructors to review and approve course plans for time schedule construction. This will get the relevant information surfaced without as much clicking around, streamlining the review process.

Met with a group of subject matter experts to review and plan for improvements to the Recruitment database.

Work Complete

Person

  • Updated the person import from UW institutional data for new name fields.

Student

  • Fixed a user interface bug that made student search bar inaccessible on small screens.
  • OSPI eCert records match our local teacher / admin certification data when issued date is within one month of our recommendation date.
  • Teacher career reporting is modified to hold job category values: "Teaching", "Working in Education", "Working, in in Education".

Cycle 64

8/14/2017 – 8/25/2017

Work Complete

Appreview

  • Made descriptions in the Apply portal configuration view more helpful.

Courses

  • Course fee fields are only displayed on offerings that have fees, previously labels and empty fields were displayed on all offering details. (This update is complete, but will be put on production with an upcoming release.)

Grants

  • Grants web database has been retired. Over the last few year UW grants reporting and tracking tools have improved to the point that this system is no longer needed. We will continue to maintain this database as a back end system for college reporting and to support the faculty merit helper tool.

Student

  • Update reporting of test scores for certified teachers required by WA state. Reporting from the new Student 2 database, added logic to select single applicable tests for each basic skills and endorsement category.
  • Letters of recommendation from application are now included in Student attachments.
  • Institution option list in edit placement form displays City, ST to differentiate institutions with the same name.
  • Built tools to support long term reporting of career data for teachers who recieved certification through College of Education. The final report shows percent of certified teachers who are teaching for the ten years following certification. Create table, import process, and web form for managing this data.

Recruitment

  • Fixed the "How did you hear about us?" question on the public "half sheet" form for prospective students. It was showing label and help text for college staff.

Test Scores

  • Update the test score assessment configuration views. Break down into assessments by test type to make list more usable.

 

Cycle 63

7/31/17 – 8/11/17

Work Complete

Courses

  • Report filter for Online component. This is based on UW Time Schedule value where course can be traditional, partially online, or completely online. Courses database allows filter to "only traditional" or "courses that are partially or completely online".
  • Added filter to Course Responsibility report for academic year. This report shows which college area, program, etc is responsible for scheduling and staffing a particular course. Academic year filter helps us prioritize active courses for Area reorg.

Recruitment

  • Further refined spam URL remover to better handle email addresses embedded in question field.

Student

  • Added import and comparison tools for WA State OSPI eCert file. This file includes state teacher and administrator records for people with certification recommended by the College of Education. We use this file to quality check our local certification data. This feature provides tools for reviewing differences and quickly reconciling them.
  • Ignore feature for eCert file comparison. This is used when a former student's certification status changes, but not based on recommendation through the college.
  • Report for OSPI Certificates that have a recommended date, but no issued date. OSPI response generally comes within two weeks. This report helps us with data entry and to surface problems during certification process.
  • Always display UW email in student database. In some cases a student's UW email address was not displayed in the student database. If a student has a UW NetID their UW email is, now, always displayed first. Also the same email address should not be displayed multiple times.
  • When student contact information has an empty value "0" for a phone number, that is no longer displayed.
  • Add advisor form uses student's first enrolled quarter as the default advisor start quarter.
  • Inactive students are included in the Students with Multiple Advisors reports. This report is used by OSS to accurately maintain advisor relationships.

 

Cycle 62

7/17/2017 – 7/28/2017

Work Complete

Courses

  • Added Online Learning Type field. This is a new field in UW Time Schedule construction which captures whether courses are traditional (in-person), hybrid, or fully online. Default value and comparisons set up so no data entry required for this field on traditional courses. Online Learning Type field is not displayed on traditional course detail, but gets special highlighting for online courses. Online courses are indicator with sticker in list views.
  • Removed the redundant Distance Learning (yes/no) field.

Person

  • Migrate appointment import from HEPPS data to Workday data. Appointment data is used primarily for updating authorizations in college info systems. Update person views for new data model.
  • Converted authorization "glance" icons from plain color coded bubbles to pills with an inital for the information system represented.

Recruitment

  • Migrated email system from SMTP to external email service. This provides better email handling, reduces spam false positives, and provides excellent tracking.
  • Show count of applications from persons who RSVP'd for an event. Match on email address.
  • Update to Ask a Question prompt for Student Services.
  • Fixed broken links on "bulk add email" results page.

Student

  • X grade tracked issues are rechecked nightly for grade that are submitted late and resolved automatically.
  • Placement types can be modified. Previously type attribute was locked due to difference in fields between types. When placement type is modified placement edit form reloads with appropriate fields.
  • Special Education placements types can be changed without disrupting automated placement creation. Placement rules system creates implied placements from course records using general placement type. These placements can be changed to the correct, more specific types.
  • Implied placement configuration for EDC&I 561 and 601, special rule with unique handling that looks for these two courses taken during the same quarter.
  • Add "Download as CSV" for placements by institution report. This includes the Generated Placement report which uses the null value "Unknown Institution". Prototyped a CSV field manager that provides reusable components for assembling export files.
  • Update the data importer for Doctoral Committee data, Grad School changed report format.

Cycle 61

7/5/17 – 7/14/17

Work Complete

Appreview

  • Reworked reviewer committee configuration. Now shows committee members and the programs they review. Ability to add programs from the committee edit page. Committee assignment by program view is still available as a separate view linked in header.
  • Deadline dates for Apply portal (undergraduate applications) are available to edit by authorized program administrators.
  • Report view shows all contingencies that have been flagged for expected application materials and endorsement expected coursework. This report can be downloaded as a CSV text spreadsheet.
  • Further adjustment to OSS material evaluation tools. Made complete, contingency toggles available from the main applicant detail view.

Person

  • Investigated new UW Data Warehouse tables based on Workday data. Wrote a new appointment query to update person database with this data. Person database "appointment" record will need to be restructured, Workday has a significantly different representation.

Student

  • Added system where Placement records can be generated by the system when students take specific courses during configured programs. For example the course EDTEP 593 is the course teacher education students take for their "Secondary TEP Field Experience". These generated placement appear in a report so staff can enter actual institutions and other placement details.

Tech Support

  • Tool to sync current students as tech support users. Tool can be run quarterly by the tech office to make students available for support and equipment reservations.

Test Scores

  • Fixed display issues with requirements configuration for state endorsements.
  • Rework search tool in test scores to return a combined view of COE person records (for matched scores) and imported person records (for imported scores not linked to a COE student or applicant).
  • Provide links from test score person view to other systems, preview where records exist. Links to Student, Appreview, and Person databases.

Cycle 60

6/19/2017 – 6/30/2017

Work Complete

Appreview

  • New feature to document expected Washington state certification and endorsements during the application review process. This feature ties into prerequisites reviewed by subject matter advisors. It sets up data that populates the student database when a student enrolls including expected certification and tracked issues (contingencies). 
  • Built configuration management system for endorsements, their prerequisites, and expected endorsement by COE program.
  • Updated manage material tools user interface.

Recruitment

  • Escaped URLs submitted in Ask a Question form. These have been occasionally used by spammers to link to malicious sites.
  • Updated how student services notification emails are sent to prevent spam warnings.

Student

  • Fix to the Grad School doctoral committee import to correctly handle removed committee members.
  • Break views that appear as a single long menu list into multiple columns for better display on desktop screens.
  • Style box buttons on student home page to look clickable.

Infrastructure

  • Ran automated accessibility audit on EDUC project. Fixed some immediate issues and sketch out plan for long term fixes and accessible new development.

Cycle 59

6/5/2017 – 6/16/2017

Work Complete

Appreview

  • Logging for updates from MyGrad applicant data now has a pruning routine.

Student

  • Added logging for all user instigated changes to student record. New logging model stores compiled message for simpler review. Log view available from student detail under page level menu (Student… upper right).
  • New "typeahead" search for students. As user types in search field matching students are suggested. Suggestions include student name, email, program, and status. Back end includes a search optimized index and maintenance routines to keep the index updated.
  • Edit placement form uses pointer mouse cursor hint to indicated mentors can be clicked (add mentor to placement).
  • Nightly import process that brings advisor assignments from Appreview to Student database. Student database is the authoritative home for advisor assignments, so this import only creates advisors records when the student has no advisor in Student database. Import matches on student, program, and start quarter.
  • Created a new home page for Student Database with intention to make system more approachable. Emphasize search, highlight the most useful views, make all the features more discoverable. (Currently in test environment getting user feedback. Will be promoted to production soon.)

Test Scores

  • Fixed certificate name not being displayed in views. Model property name change had not been fully updated.

Infrastructure

  • The system context menu (upper right corner, switch from Student to Appreview, Tech Support, etc) is now fixed to the view port instead of the top of page. This resolves an issue where scrolling down a page, then activating the context menu presented a seemingly empty menu.
  • Fixed issue where URLs with trailing slashes ("https://educ.uw.edu/students/") would incorrect result in a "Page Not Found" message.
  • Major restructuring of client side JavaScripts and style sheets. Reorganized these component files to make them better labeled and locatable during developement. Cleaned out code inherited from previous projects, no longer used. Implemented a strategy to keep vendor libraries up to date. Created automated build pipelines to assembly production builds.
  • Updated authorization notifications. We use the Person database to monitor user authorizations. Other college systems send notifications to Person, when a user's authorization is modified. These API clients needed to be updated for token API authentication.

Cycle 58

5/22/17 – 6/2/17

Long Term Planning

As the academic year wraps up and we work through the Student database punch list we are also working on long term planning for information system development. So far we have met this Undergrad team and Carlson Center to plan for undergraduate placements, certification team to plan for filling in test score data, and grants support team to review the Grants database. As long term plans are drafted they will be posted on this blog.

Work Complete

Person

  • Incorportated new student related tables into the person merge process. This included new routines for the 20 or so tables with person references in student. Rebuild of person merge to increase its modularity while decoupling it from some external dependencies.
  • Utility that can re-apply historic person merges using current merge logic.

Infrastructure

  • Update the EDUC project (Appreview, Student, Testscores, etc) to use lazy UW login. This allows the local application policies to dictate when a user needs to be authenticated and sends them away to UW login page only when needed.
  • Removed the /a/ and /b/ from EDUC project URLs. These were needed because previously it was web server (Apache) configuration determining when a user needed to be logged in.
  • Web service token authentication. When College of Education applications request data from each other (example Faculty Merit Report in Courses asks Student database for advising data) it passes a token which authorizes this inter-application API access.
  • Upgraded application framework and vendor packages for EDUC (Laravel 5.4).
  • Migrated JavaScript build utility to Webpack. This allows for more sophisticated client side application development using latest features while maintaing backward compatibility with the most common browsers.
  • Re-organized style-sheets to create a more concise and intuitive layout.
  • Prototyped a new application UI. This UI makes better use of browser viewport space, is more friendly on smaller mobile screens, accomodates large menu layouts, and makes UI components (e.g. Search) more obvious.

Workday 101 Instructional Videos

Training Everyone Should View

Everyone at the UW who will use Workday should view these Workday 101 Instructional Videos.

Please plan to view these instructional videos before Workday goes live in June.

The Workday 101 instructional video series includes:

  1. Navigating in Workday
  2. Updating Personal Information
  3. Enter Time
  4. Request Absence (Time Off)
  5. Inbox and Notifications
  6. Accessing Benefits
  7. Accessing Pay Information

This series is targeted for those individuals who were NOT assigned one of the specific security roles included in classroom style or seminar style training, but is relevant for all faculty, staff, and student employees at the University of Washington.

View Workday 101 Instructional Videos now