Author Archives: pschurr

SWS Section Status by Course

We released a new build of SWS last week which adds a new resource, Section Status by Course. You can now get Add Code Requirements, Space Available, Section Status (open/closed), and more for all of the sections in a given course.

Single section:,summer,ANTH,322/A/status

All sections in a given course:,summer,ANTH,322/status

This resource requires a separate authorization from the Office of the Registrar. Write to sws-support to request access.

Last week’s deployment also included enhancements to the Degree Audit resources and numerous bug fixes. See Production Release Log for more details.

SWS Section Updates

Updated today, blogging today!

We released an update to Student Web Service this morning.  It fixes several bugs and adds attributes to the Section resource, including Final Exam information, Section Start and End dates, Institute Name, and Student Credit Hours.

FWS has been Updated!

Way back in early April we released an update to the Financial Web Service and I volunteered to blog about it. Several reminders later, head hanging in shame, I’m finally getting it done.

We made some exciting additions to the web service. There are new resources for Biennium and Biennium Search. You can search for bienniums (that’s correct, btw, I looked it up, so there) or call biennium/current, biennium/next, or biennium/previous to get the current, next, or previous biennium.

There are new resources for the Account based information in FIN:

  1. Fund
  2. Fund Search
  3. General Ledger Account
  4. General Ledger Account Search
  5. Revenue
  6. Revenue Search
  7. Expenditure
  8. Expenditure Search
  9. Account Search (which returns links to Fund, General Ledger Account, Revenue, and Expenditure resources)

The new resources are all available in xml, json, or xhtml.

We also did a few bug fixes and some more of the enhancements that you requested. For instance, we increased the maximum size of a search result set from 200 to 500.

Since the changes were all additions rather than modifications of existing elements, we kept the major version at v1.

Next time I pledge to blog sooner!

Simple C# .Net Rest Client


I’ve posted some simple C# sample code for accessing RESTful UW web services. It takes advantage of the Microsoft WCF REST Starter Kit Preview 2 which makes the client code very simple. It covers using X509 certificates and processing xhtml responses.

This is just a first iteration and I would welcome any feedback or contributions.

You just need a UW netid for access:


IdCard Photo Service Gets an EARful

The Idcard Photo service has a new client!

Photos are now available in the Electronic Academic Records System (EARS). This means that advisors and administrators who are working with students can see photos along with academic records.

The advisers are thrilled and, according to Patricia Greer of the Student Team, calling the photo service from her application was easy.

Other Clients Coming on Board Soon

The College of Education is in the process of adding photos to the STEP advisors application and Catalyst Tools will soon be adding photos to GoPost.

Interested in Getting Access?

The registrar’s office has determined that access to the photos will be governed by the same Memorandum of Understanding that covers access to the Student Web Service data. If you have signed the MOU, contact Matt Winslow to get your application’s certificate authorized.

New Version Coming Soon

A new version that will allow clients to request custom sizes is in the works and will be released soon.

Breaking News – Id Card Service Beta Launched!

Id Card Service Beta Launched

We launched a new service last week. The Id Card Service exposes data associated with the Husky Id Card, the card that students, faculty, and staff alike use for identification.

Even more exciting, the Student Team launched a web application to consume the service. The application grabs a piece of the data exposed by the service (the id card photo) and mashes it up with data from another source (the student class list from uwsdb). The result is something that instructors have been clamoring for for years – Photo Class Lists. Now instructors can log on to MyUW, click a link in the My Class Resources portlet, and see their class list – with photos!

The Biology department is one of several that have been photographing students each quarter in order to produce their own photo class lists. Biology Professor Mary Pat Wenderoth tells us that the photos make a big difference in her ability to connect with students. When the instructor learns the students’ names, the atmosphere in a big lecture is much more conducive to learning, she says. And having the photo available obviously makes the task of learning names much easier.

About the Service

This is the first service to be built with the web services framework that we extracted from all the great work that went into building the Student Web Service (SWS). The framework is a work in progress but it has already paid off. The IdCard Service was built in a tiny fraction of the time that it took to build SWS and that is partly a result of the fact that most of the hard stuff was already done by the framework. Of course, it is also due to the fact that the id card data is a lot simpler than the student data, but still…

We only started working on the service in mid-February, squeezing it in between other projects. Getting it (and a consuming app) launched in time for Spring quarter is pretty sweet. Things don’t usually move that fast around here 🙂 It makes me excited about our prospects for moving quickly on building out a whole series of RESTful data services in the future.

We also broke a little new ground with this service. The photos don’t change very often so we had a chance to experiment with caching. We set up a caching layer that allows us to check authorizations and log access but avoid the rest of the processing. We learned how to serve binary data from a Windows Communication Foundation (WCF) service and wrote code to produce and save thumbnails of various sizes too.

Next Steps

Our main issue is to identify data stewards who can authorize applications to use the id card data. The registrar’s office authorized access to student photos for the purpose of photo class lists but that still leaves questions around what other uses will be allowed and who will authorize use of faculty and staff photos.

We will also be working with developers to gather requirements for exposing more of the id card data in the service, for exposing photos of various sizes, and to determine what sort of performance will be necessary to serve many clients.

Hopefully soon we can look forward to UW developers mashing up this data with other information to solve all sorts of current business problems.

Onward and upward!