Skip to content

EWS EVAL Release 16 is Now Available

Enterprise Web Services (EWS) has released an update in EVAL for multiple web services in support of UW Finance Transformation (UWFT). For an overview of how EWS is adapting to support UWFT, refer to EWS for Finance Transformation.

Monthly Scheduled Releases

  • EVAL: Updates to EVAL environments for all EWS services are released on the same monthly schedule. This allows us to better synchronize with Enterprise Data Platform’s release schedule for Finance Transformation. For more information, refer to the Data Availability Timeline.
  • PROD: Updates to PROD environments for all EWS services now reflect changes from the previous month’s EVAL release (for example, if EVAL reflects Release R16, then PROD will reflect Release R15).

What’s New in EWS Release 16

Web Service Overview of Release
FWS v2 (Outbound)
  • Introduced a Breaking Change by removing PayrollProcessingID from the /PayrollJournal resource.
  • Updated the /PayrollJournal resource by updating the data source, removing some search parameters, and renaming a search parameter.
  • Updated the /Journal resource by removing one search parameter and renaming another.
  • Fixed bugs for the following resources:
    • /BillingSchedule
    • /ReferenceType
    • /WorkdayHierarchy
    • All FWS v2 resources with an active_status search parameter.
  • Added the /CustomListValue resource.

For more information, refer to FWS Reference Data (Outbound) – Release 16. For support, refer to Support | FWS.

FWS v2 (Inbound)
  • Restricted the length for the DocumentId field to 100 characters to avoid truncation by Workday and specified allowable characters: alphanumeric, dashes, and underscores.

For more information, refer to FWS Common Transactions (Inbound) – Release 16. For support, refer to Support | FWS.

HRPWS v3
  • Introduced a Breaking Change by removing PayrollProcessingID from the /PayrollResult resource.
  • Fixed a bug related to the changed_since_date and changed_to_date search parameters in the /PayrollResult resource.
  • Fixed a bug for all HRPWS v3 resources with the active_status search parameter.

For more information, refer to HRPWS v3 – Release 16. For support, refer to Support | HRPWS.

SpaceWS v2 There were no customer-facing changes for SpaceWS v2 included in this release.

Reminder for HRPWS v2 and SpaceWS v1 Users

HRPWS v2 and SpaceWS v1 are ready to retire. If you have not transitioned to the new version(s) and need additional time, please submit an extension request ASAP:

  • HRPWS v2 – Email hrpws-support@uw.edu with subject line: “HRPWS v2 extension request”. Include the following:
    • Certificate you are using for PROD.
    • Name of application/service you are integrating.
    • Estimated date your transition to HRPWS v3 PROD will be complete.
  • SpaceWS v1 – Email spacews-support@uw.edu with subject line: “SpaceWS v1 extension request”. Include the following:
    • Certificate you are using for PROD.
    • Name of application/service you are integrating.
    • Estimated date your transition to SpaceWS v2 PROD will be complete.

EDW for Finance Transformation Release 15 is Now Available

Enterprise Data Warehouse (EDW) has released an update in UWODS and WDFinDataMart in support of UW Finance Transformation (UWFT). For an overview of how EDW is adapting to support UWFT, refer to EDW for Finance Transformation.

Reminder for ODS users: When UW Finance Transformation (UWFT) goes live, the current state ODS database will be frozen and the UWODS database will be introducedFor more information, refer to Transitioning HR Data from ODS to UWODS.

Monthly Scheduled Releases

Updates to UWODS and WDFinDataMart are released on the same monthly schedule. This allows us to better synchronize with Enterprise Data Platform’s release schedule for Finance Transformation. For more information, refer to the Data Availability Timeline.

What’s New in EDW for Finance Transformation Release 15

Database

Overview of Release

UWODS
  • This release includes 29 new tables. An additional 18 columns were added to existing tables with 14 column name changes.
  • Introduced Breaking changes by renaming and removing fields in multiple tables.

Known Data Issues are as follows:

    • Some Tables are missing data. See: UWODS Tables Missing Data
    • Truncated data due to bad test data not following expected standards 
    • Some definitions are unknown

For more information, refer to UWODS EDW Release 15. For support, refer to Support | UWODS. Refer to FAQ | UWODS for frequently asked questions by UWODS users.

WDFinDataMart

There were no customer-facing changes for WDFinDataMart introduced in this release.

Known Data Issues

For more information, refer to WDFinDataMart. For support, refer to Support l WDFinDataMart. Refer to FAQ l WDFinDataMart for frequently asked questions by WDFinDataMart users.

EDW Release Schedule for the Holidays

The UWODS and WDFinDataMart December releases are moving to early January to accommodate for Christmas and New Year holidays:

  • Release 16 – 01/09/2023.

EWS EVAL Release 15 is Now Available

Enterprise Web Services (EWS) has released an update in EVAL for multiple web services in support of UW Finance Transformation (UWFT). For an overview of how EWS is adapting to support UWFT, refer to EWS for Finance Transformation.

Monthly Scheduled Releases

  • EVAL: Updates to EVAL environments for all EWS services are released on the same monthly schedule. This allows us to better synchronize with Enterprise Data Platform’s release schedule for Finance Transformation. For more information, refer to the Data Availability Timeline.
  • PROD: Updates to PROD environments for all EWS services now reflect changes from the previous month’s EVAL release (for example, if EVAL reflects Release R15, then PROD will reflect Release R14).

What’s New in EWS Release 15

Web Service Overview of Release
FWS v2 (Outbound)
  • Introduced Breaking Changes by renaming or removing fields in the following resources:
    • /Customer
    • /Journal
    • /PayrollJournal
    • /Supplier
  • Introduced Breaking Changes by fixing data types across various resources that previously required values when they should be nullable.
  • Added search parameters to most FWS v2 resources.
  • Updated and renamed multiple fields in the /SearchID resource.
  • Updated a majority of FWS v2 resources to return active values only by default.

For more information, refer to FWS Reference Data (Outbound) – Release 15. For support, refer to Support | FWS.

FWS v2 (Inbound) There were no customer-facing changes for FWS v2 (Inbound) introduced in this release.
HRPWS v3
  • Added search parameters to most HRPWS v3 resources.

For more information, refer to HRPWS v3 – Release 15. For support, refer to Support | HRPWS.

Reminder for HRPWS v2 users: HRPWS v2 is scheduled to retire at the end of 2022. For more information, refer to Transitioning from HRPWS v2 to v3.

SpaceWS v2 There were no customer-facing changes for SpaceWS v2 included in this release.

Reminder for SpaceWS v1 users: SpaceWS v1 is scheduled to retire at the end of 2022. For more information, refer to Transitioning from SpaceWS v1 to v2.

EWS Release Schedule for the Holidays

The December EWS releases will occur the week between Christmas and the New Year:

12/27/22 – EWS Production Release (includes updates from EWS EVAL Release R15)
12/29/22 – EWS R16 EVAL Release

Support Available to Transition Human Resource/Payroll Data from ODS to UWODS

The Enterprise Data Warehouse (EDW) recently introduced two new databases to support UW Finance Transformation (UWFT): UWODS and WDFinDataMart. For more information, refer to EDW Databases and Resources Available to Support Finance Transformation.

The UWODS database, which goes live with UWFT, will enable EDW users to access Finance and Human Resource/Payroll (HRP) data from Workday. The UWODS will replace the current ODS database as the EDW resource for this data.

In the UWODS, the HRP data model is different than in the current ODS database. This change better reflects Workday’s HRP data structure and creates better parity between the UWODS and HRP Web Service (HRPWS). This better alignment allows the EDW to quickly adapt to future changes and provide more clarity and consistency to users who leverage this data.

Watch this short video for an introduction to how HRP data is changing in the UWODS:

Transition Support is Available

Documentation is available to help users transition from the ODS to UWODS for HRP data. Refer to the following pages to get started:

  • Transitioning HR Data from ODS to UWODS – This resource guides users through the transition from ODS to UWODS, which includes:
    • Mapping tables and columns from current to future state.
    • Reviewing new HRP tables.
    • Exploring HR Data Domain concepts and associated sample queries to help answer common questions.
  • UWODS Customer Portal – This page provides additional information on this new database, including the different environments available and how to get started.

Additional Resources for Support

Join Us for Office Hours

EDW Subject Matter Experts are now available during the Enterprise Reporting and Analytics (ERA) Office Hours every Friday from 9 to 10. Please drop by to ask your UWODS questions.

You can either sign up ahead of time or drop by during the session:

Sign up – Trumba

Drop by – Zoom (During session only) 

Subscribe to Our Email List

When you request access to UWODS, you are automatically added to the respective mailman list(s) to receive periodic communications related to these databases.

If you are not ready to get access, but want to stay in the loop, we encourage you to sign up for the following list today: uwods-ft-users

Email Us

If you have questions or would like to provide feedback, please write to edw-help@uw.edu with “UWODS” in the subject line.

EDW Databases and Resources Available to Support Finance Transformation

The Enterprise Data Warehouse (EDW) is a secure central repository that integrates data from many sources across the University. It stores current and historical data that are used to support operational reporting and strategic analysis. The goal of the EDW is to support better and faster data-informed decision making. For more information about the EDW and how it fits within the Enterprise Data Platform, refer to Enterprise Data Platform.

EDW and UW Finance Transformation (UWFT)

UW Finance Transformation (UWFT) is much more than a system update – it is a redesign of our finance-related policies and processes, with the help of new technology. The EDW is supporting UWFT with the introduction of two new databases: UWODS and WDFinDataMart. These databases, which are under development and provision data from Workday, are currently available to help users prepare for UWFT go live.

For more information on how the EDW is supporting Finance Transformation, including planned dispositions for affected databases, refer to EDW for Finance Transformation.

New UWODS Database

When UWFT goes live, the EDW’s current state Operational Data Store (ODS) will freeze, and the new UW Operational Data Store (UWODS) will be introduced. This new database reflects the Foundation Data Model (FDM), which is the technical framework that organizes financial data in Workday. This new database will support reporting for the following:

  • Workday Foundation Data Model (FDM) and Financial Reference Data
  • Remediated HR/Payroll Data

To learn more about UWODS, request access, or get support, refer to the UWODS Customer Portal.

New WDFinDataMart Database

When UWFT goes live, the EDW’s current state FinancialSumMart will freeze, and the new Workday Financial Data Mart (WDFinDataMart) will be introduced. This new database will support reporting for the following:

  • Accounting & Operational Journal Transactions
  • Grant & Financial Budgets
  • Current Budget Balances
  • Payroll Journal Line Detail

To learn more about WDFinDataMart, request access, or get support, refer to the WDFinDataMart Customer Portal.

Additional Resources for Support

In addition to the customer portals noted above, there are a number of resources available to help users stay informed, ask questions, and get support with these new databases.

Reach Out to UWFT

Reach out to your FT Unit Readiness Lead or submit a request to uwftask@uw.edu for guidance.

Tip: To identify your Unit Readiness Lead, go to the UWFT System Remediation & Retirement Portal, locate your unit, and then click the information icon next to the unit name. For example, .

An Information/Overview page displays for your unit, which includes the name of your assigned Unit Readiness Lead.

Join Us for Office Hours

EDW Subject Matter Experts are now available during the Enterprise Reporting and Analytics (ERA) Office Hours every Friday from 9 to 10. Please drop in to ask your UWODS and WDFinDataMart questions.

You can either sign up ahead of time or drop by during the session:

Sign up – Trumba

Drop by – Zoom (During session only) 

Subscribe to Our Email Lists

When you request access to UWODS or WDFinDataMart, you are automatically added to the respective mailman list(s) to receive periodic communications related to these databases.

If you are not ready to get access, but want to stay in the loop, we encourage you to sign up for the following lists today:

Email Us

If you have questions or would like to provide feedback, please write to edw-help@uw.edu with “UWODS” or “WDFinDataMart” in the subject line.

How To: URM Status SQL Function in the EDW

Do you get tired of maintaining the same business logic in many data products and spending too much time updating the logic in all those products?

Are you looking for one version of the truth across all your academic reports, data cubes, and dashboards?

The BI Team has great news for you. The EDW supports the first academic data-related SQL function, URM (Underrepresented Minority) Status, to help you reduce business logic maintenance, improve code readability, and keep one version of the truth for Underrepresented Minority students. Imagine that instead of spending time on updating, let’s say, 12 academic reports with the new URM logic, the EDW team can apply the URM Status SQL function logic just once and this modification will propagate to all 12 academic reports at the same time.

This function is most helpful to SQL developers working on academic reports, cubes, and dashboards that use students’ demographic data.

Context:

In SQL or any other programming language, a function is a program that takes some input and generates an output value. SQL has many built-in functions that you get out of the box. For example, one of the built-in system functions is REPLACE(), which expects to have three inputs:

  1. The expression you want to search (i.e. column or field),
  2. what you are searching for, and
  3. what you want to replace it with.

The EDW team has recently added the first academic data-related scalar SQL function called [dbo].[URMStatus] to the UWSDBDataStore] database in the EDW. A scalar SQL function returns a single value as opposed to a table of values.

By definition, a SQL scalar function takes one or more parameters in a SELECT statement and returns a single value, which in our case is one of the following: “International,” “URM” or “Not URM.”

How To Use the New Function:

The [dbo].[URMStatus] function takes four parameters:

  1. @underrepflag – an integer value of 9 represents that a student belongs a URM group
  2. @hispaniccode – an integer value of 7xx indicates a hispanic student
  3. @ethnicity  – a string value that could be one of the following: AFRO-AM, AMER-IND, ASIAN, CAUCASN, HAW/PAC, NOT IND
  4. @residency  – an integer value ranging from 0 – 6. If a value is 5 or 6, a function is going to return a value of “International”

The SQL code below provides an example of how ethnicity/race data is staged and then used in the [dbo].[URMStatus] function:

----------------------------------------------------------------------------- 
-- Race/Ethnicity temporary table 
-----------------------------------------------------------------------------
USE [UWSDBDataStore];
SELECT DISTINCT t.system_key,
    Race_Ethnicity = CASE 
        WHEN s1.resident IN (5, 6) THEN 'INTERNATIONAL'
        WHEN COUNT(DISTINCT et2.ethnic_group) >= 2 THEN 'TWO OR MORE'
        WHEN s1.hispanic_code <> 999 THEN 'HISPANIC'
        ELSE RTRIM(et.ethnic_desc)
        END
     , MAX(et2.ethnic_under_rep) AS ethnic_under_rep
    , MAX(sh.hispanic) AS Hispanic_Ethnic_Code
    , s1.resident
    , RTRIM(et.ethnic_desc) AS ethnic_desc
    , CAST(NULL AS CHAR(255)) AS  Hispanic 
    , CAST(NULL AS  CHAR(20)) AS Underrepresented
    , CAST(NULL AS CHAR(255)) AS Ethnic_Long_Description
INTO  #teth
FROM #t t  -- this your temp table with you an initial students’ population
INNER JOIN sec.student_1 s1 ON s1.system_key = t.system_key
LEFT JOIN sec.student_1_ethnic et1 ON et1.system_key = t.system_key
LEFT JOIN sec.sys_tbl_21_ethnic et2 ON et2.table_key = et1.ethnic
LEFT JOIN sec.sys_tbl_21_ethnic et ON et.table_key = s1.ethnic_code
LEFT JOIN sec.student_1_hispanic sh ON sh.system_key = t.system_key-- AND sh.hispanic &lt;&gt; 999
GROUP BY t.system_key
    , s1.resident
    , s1.hispanic_code
    , et.ethnic_desc   
    , s1.resident
-----------------------------------------------------------------------------
-- dbo.[URMStatus]  function call with parameters passed to this function
-----------------------------------------------------------------------------
;WITH UnderCTE AS
(
SELECT system_key
, Underrepresented = [UWSDBDataStore].[dbo].[URMStatus] 
    (
     REPLACE(ethnic_under_rep,0,99)     /* @underrepflag - a function validation outputs an error if an input value is 0 which is unexpected.
                                              so I replace 0 with 99 to pass a function validation for @underrepflag */
  , ISNULL(Hispanic_Ethnic_Code,999)    /* @hispaniccode - there are some NULL values in hispanic data source so we are passing 999 value that 
                                              is ignored in the function "WHEN @hispaniccode is 999" */
  , ethnic_desc                        /* @ethnicity */  
  , resident                           /* @residency */  
    )
FROM #teth
)

UPDATE t
SET t.Underrepresented = f.Underrepresented
FROM #teth t INNER JOIN UnderCTE f
ON t.system_key = f.system_key

Please Note:

The [dbo].[URMStatus] function has been implemented in 12 academic reports so far. Please check a SQL tab in the BI Portal for almost any academic report to see the function implementation.

Questions:

If you have questions about this function or how to use it in your solutions, please write to help@uw.edu and put “EDW Feature: URM Status Function” in the subject line.

EWS EVAL Release 14 is Now Available

Enterprise Web Services (EWS) has just released an update in EVAL for multiple web services in support of UW Finance Transformation (UWFT). For an overview of how EWS is adapting to support UWFT, refer to EWS for Finance Transformation.

Monthly Scheduled Releases

  • EVAL: Updates to EVAL environments for all EWS services are now released on the same monthly schedule. This allows us to better synchronize with Enterprise Data Platform’s release schedule for Finance Transformation. For more information, refer to the Data Availability Timeline.
  • PROD: Updates to PROD environments for all EWS services now reflect changes from the previous month’s EVAL release (for example, if EVAL reflects Release R14, then PROD will reflect Release R13).

What’s New in EWS Release 14

Web Service Overview of Release
FWS v2 (Outbound)
  • Introduced Breaking Changes by adding, renaming, or updating fields (including changes to some XML or JSON paths) in the following resources:
    •  /Award
    • /BillingSchedule
    • /Customer
    • /CustomerPayment
    • /FacilitiesAndAdministrationRateAgreement
    • /Gift
    • /Grant
    • /InternalServiceProvider
    • /Journal
    • /LedgerAccountSummary
    • /PayrollJournal
    • /Plan
    • /Project
    • /ProjectHierarchy
    • /Supplier
    • /SupplierContract
  • Introduced Breaking Changes by removing the following resources:
    • /ReferenceType/{ReferenceIDType}
    • /Resource/{RefID|WID}/ResourceHierarchy
    • /ResourceHierarchy/{RefID|WID}/Resource
    • /Gift/{RefID|WID}/GiftHierarchy
  • Added or updated fields in multiple resources in addition to those listed under breaking changes above.
  • Added HREFs to multiple resources.
  • Updated the formatting of Swagger metadata for multiple resources.
  • Fixed bugs that impact fields and search parameters for multiple resources.

For more information, refer to FWS Reference Data (Outbound) – Release 14. For support, refer to Support | FWS.

FWS v2 (Inbound) There were no customer-facing changes for FWS v2 (Inbound) introduced in this release.
HRPWS v3
  • Introduced a Breaking Change, which impacts fields for the /JobProfile resource.
  • Added and updated fields in multiple resources.
  • Updated multiple resources to display Active values by default.
  • Removed the /PayrollResult by Name search parameter.
  • Fixed bugs related to HREFs for multiple resources.

For more information, refer to HRPWS v3 – Release 14. For support, refer to Support | HRPWS.

Reminder for HRPWS v2 users: HRPWS v2 is scheduled to retire at the end of 2022. For more information, refer to Transitioning from HRPWS v2 to v3.

Check Out Knowledge Navigator!

Knowledge Navigator is a web-based application that allows UW enterprise data users to explore key concepts from subject areas including Student, Finance, HR/Payroll, and Research Administration. The tool also visually demonstrates how key concepts are linked to physical data objects like reports, databases, and APIs.

FWS v2 has been available in Knowledge Navigator for a while, but now HRPWS v3 is available as well. You can access links to applicable sections of Knowledge Navigator from the customer support portals:

EWS Release Schedule for the Holidays

The November EWS releases will occur the week after Thanksgiving:

  • 11/29/22 – EWS Production Release (includes updates from EWS EVAL Release R14)
  • 12/1/22 – EWS R15 EVAL Release

The December EWS releases will occur the week between Christmas and the New Year:

  • 12/27/22 – EWS Production Release (includes updates from EWS EVAL Release R15)
  • 12/29/22 – EWS R16 EVAL Release

Support Available for SpaceWS v1 to v2 Transition

 

We are making some changes to the Space Web Service (SpaceWS). Current users must take action before SpaceWS v1 retires—scheduled for the end of 2022.

The purpose of these changes is to align better with the new InVision source system and remove some legacy financial elements in preparation to support UW Finance Transformation (UWFT).

These changes will mainly involve a direct mapping relationship from one resource to another or field mapping changes within the same resource.

We have also introduced a new ‘Floor’ Resource, plus HREFs for Space and FloorID. We encourage you to explore RESTful API Documentation v2 | SpaceWS to learn more about these new resources.

Transition Support is Available!

Documentation is available to support this transition work. Refer to the following pages to get started:

Transitioning from SpaceWS v1 to v2 – This resource guides users through the transition from v1 to v2, which includes:

  • Key Concepts
  • Search parameter mapping
  • Search results mapping
  • HREF results mapping

We want to hear your questions, comments, and solutions! Please engage with us via the following channels:

  • SpaceWS for Finance Transformation – We’re always looking to improve our documentation. Please use the page comment feature to provide feedback on any page within this space.
  • Support | SpaceWS – Refer to this page for guidance on who to contact for various support scenarios.

UW GL Cube undergoes redesign

We’re happy to announce the release of the newly redesigned UW GL (General Ledger) Cube. Kicked off in February 2021, the project is now completed and ready for use. Thanks to all the hard work of our developers from the DATAGroup and UW-IT ERA (Enterprise Reporting and Analytics), we updated the cube’s schema, making it easier to maintain, and making it more intuitive for finance users at all levels. 

Why was the UW GL Cube redesigned?

  • To attain increased cost efficiency
  • To facilitate UW Finance Transformation
  • To make general ledger data accessible across the UW

Users can expect the redesigned UW GL Cube and its predecessor to run in parallel until October 30 2022, at which point we will retire the older cube. Users can expect to find the same data elements and will have the same levels of access as in the previous version, but will need to rebuild their existing workbooks using new dimensions and renamed attributes.

What will it take to switch from the old cube to the new?

To support flexibility and ease of maintenance, we’ve worked very hard with users to update the schema making it more intuitive. 

But you’re not on your own. We have support documentation, and in addition, every Friday at 9am the BI team hosts BI Office Hours where you can ask questions and get answers.

Additional resources

To learn more about the new design, how to connect to the cube, and what changed and how, please visit our UW GL Cube Resources wiki page. 

To learn more about the new schema and attributes, please visit Knowledge Navigator: UW GL Cube

UW-IT’s Enterprise Reporting and Analytics (ERA) will continue supporting users as needed. We’re here to help:

  • Email us at help@uw.edu with “reports, cubes and dashboards” in the subject line.

Thank you!

We also want to express our gratitude to all of you who contributed your time, expertise, and feedback during our design and requirements sessions, as well as performed User Acceptance Testing (UAT). This release could not have been possible or on time without your dedication. We really appreciate all of your help and enjoyed working with you! 

If you have any questions, any trouble connecting, or any input, please don’t hesitate to write to us at help@uw.edu with “UW GL  Cube” in the subject line.

RPG New Dashboard Release: Time Schedule Course Enrollment Trends and Details

The Enterprise Reporting and Analytics team with the collaboration of the Report Prioritization Group released the newest addition to the BI Portal: Time Schedule Course Enrollment Trends

What is the Time Schedule?

The UW Time Schedule application lists credit classes offered at the University of Washington. The UW Time Schedule is updated daily and includes the following information and more:

  • Status of courses
  • Times, days, or locations of courses
  • Instructors for all courses
  • Section types (Lecture; Lab; Quiz; etc.)
  • Learning types (Hybrid; All On-Line; No On-Line Learning)

The Enterprise Data Warehouse (EDW) imports data from the UW Time Schedule system into the [UWSDBDataStore] database. From here the data is used to support the Time Schedule Information report, Time Schedule Enrollment by Day and Time dashboard, and this most recent dashboard, Time Schedule Course Enrollment Trends, on the BI Portal. All data is refreshed daily.

How-To:

First, use the Select Measure: filter to choose a statistic that you want to analyze:

When selecting  data in any of the multi-select filters, select a value(s) of your choice and click the Apply button to execute the filter:

For additional information visit the Interpretation tab for the Time Schedule Course Enrollment Trends dashboard.

Optimization hint: To improve page load time, pre-select the lower level filters (Campus, College, Department, etc.) first before selecting the (All) value under the Year Quarter filter.

Users and Use Cases:

The primary users of  Time Schedule data  are  the Registrar’s Office, Time Schedule “Constructors,” the academic advising community, Program Coordinators, and department administrators working on faculties’ tenure reviews. The Time Schedule dashboards facilitate answering many  business questions. Following are real business questions from our data user community:

Student Enrollment / Credit Hours:

  1. For any course section, what do the current student enrollment / student credit hours counts look like for x number of years?
  2. For any course section, what do the census enrollment / student credit hours counts look like for x number of years?

Course:

  1. For any course section, can you display its School / Department / Curriculum (Responsible Curriculum Dept.) / Course Title / Course Section and Course Credits data elements?
  2. What is the section type for a given course section e.g. ‘Lecture” , “Independent Study” etc.?
  3. Is the course section instruction delivered on-line? If so, does it belong to one of the categories such as: ‘All Online’, ‘Hybrid’, ‘Enhanced’, ‘No Online Learning’?
  4. Is the course section instruction delivered as distant learning? If so, does it belong to one of the categories such as: ‘Pre-Recorded (not Internet courses)’, ‘Correspondence (Print)’, ‘Internet’ ,’Interactive Television Technologies (not Internet courses) ‘, ‘Broadcast (not Internet courses)’ , ‘No Distance Learning’?
  5. Is there a course fee required for a given course section, and what type it is?
  6. What is a course’s enrollment status? Is it ‘Open, ‘Closed, ‘Withdrawn’, ‘Suspended’?

Space:

  1. For any course section, what is its time schedule limit estimated enrollment?
  2. For any course section, what is its space availability (the difference between joint enrollment limit and current enrollment)?
  3. For any course section, what is its space availability (ratio: current enrollment / joint enrollment limit)?
  4. What is the unmet course section request, meaning, how many students are denied registration entry into the course section due to space availability or for any other reason?

Instruction Time:

  1. When does a course section occur during a week (for instance: ‘Monday’, ‘Wednesday’)?
  2. At what time does a course section start and end, and at what location?

Questions?

If you have questions about the meaning of any of the business terms in these questions, or other business terms, you can explore these terms and get more information in Knowledge Navigator.

As always, if you have any questions, please write to help@uw.edu with  “BI Portal: Time Schedule Trends and Details Dashboards” in the subject line.

Thank you

Thank you to all those with the ERA team and the RPG who made this release possible. In particular, the following UAT (user acceptance testing) users from the RPG contributed their valuable feedback and Time Schedule expertise.

  • Nell Gross – Geography department academic adviser
  • Joe Kobayashi – Marine Biology department academic adviser
  • Dori Bloom – analyst in the College of Arts and Sciences, Dean: Business Office
  • Matt Winslow – Sr. Associate Registrar in the University Registrar Office