Monthly Archives: April 2009

A nicely implemented webservice

I’d be very surprised if the developers of Timetric didn’t work straight out of Richardson and Ruby’s RESTful Web Services just as many of us did. They offer a webservice that lets you upload time-series data in a file, creating a resource from it with an overloaded POST in place of the expected PUT. On success, a 303 is returned with the URI of your new resource in the Location header. Do a GET on it, and you see it beautifully plotted, get an embeddable URL for the graph, and even get your original data back. Use POST to add to or change your data, and DELETE to remove your resource. They adhere to R&R’s gold-standard as closely as could be expected.

Editorializing for a moment, the best reason to check them out is to have a look at their API documentation. It is the paragon of elegant simplicity and I only wish the Unix man pages were as easily digested. Requiring neither flash nor javascript, they render as sensibly on my Treo as they do on my twin 17″ monitors.

UserVoice – Tell us what services you need

You know best about what services we need at the UW. So tell us about it.

We have link from this blog to a uservoice feedback site that we are trying out. Using the tool you can:

  • post your idea
  • check out other people’s idea and vote on them
  • talk about those ideas
  • see which ideas were the most popular and watch as we take action on the feedback

Even though we are trying this tool out; the feedback you submit today is being taken seriously by the developers building web services at the UW. You will find several ideas that I have seeded already from various forums such as providing a course url in SWS which we have already have taken action upon.

We hope to hear your feedback soon.

Financial Web Service development status

Work continues on the Financial Web Service targeting “summer” for release. There will be six resources that comprise v1: budget, budget search, organization, organization search, vendor and vendor search; inquiry only. A data dictionary will be provided within the resource representations. The service will be publicly available. A couple of clients have already signed up to start using the service. If you are interested in using the service or reviewing the proposed representation attributes, let us know!