Archive for October, 2008

We now have 27 sites being served out of the CMS, with 7 being developed (HSS, Computer Science, Management, Physics, Pharmacy and Pharmacology, Education, Mathematical Sciences) and 2 not yet started (ESML and ACE).

The 27 live sites are:

Two months ago we undertook the task of creating an application from concept to launch in a single week.  During the aptly named Get Creative Week, the team designed, implemented and launched Flat Out, an application allowing University of Bath students to search for rooms and properties on Facebook.

The app hasn’t had any attention from us since then, so how is it doing and is anyone actually using it?

According to the statistics there are currently 47 active users which was as high as 65 at the beginning of the month.  An active user is someone who has used the app in the last 30 days, so the 65 covers the beginning of term in September.    Whilst this isn’t a huge number, it does show it is being used especially given that the app got no promotion, other than a link on the University’s online notice board.

Can we just release an application and then move on to something else or do we need to support, maintain and promote it?  I think it depends on the nature of the application and how worried we are about whether people are using it or not.   The purpose of Get Creative Week was to investigate the creative process, so the use of the application wasn’t as important.  Although it is still nice to see that people are using it.

It is clear from the stats that new applications do get noticed by at least a few people but how many does it take before it becomes the popular, “must use” application we would like all our creations to be.   Obviously, the more fun and useful it is the more likely people are to use it, and some people will seek out new things to help make their life / job easier.  However, I think, as with any large community, to get everyone using it requires a lot more effort.

There are many different types of people each requiring a different approach to help them understand that your application is the one they need.

I think it would be nice to think an application would become popular on its own and we could just sit back and watch, but in reality it isn’t that simple.

Something we’re very keen on in Web Services is contributing back to the open source community that we base so much of our work on.

With that in mind, we’re excited to be able to say that we followed the guidelines provided by OSS Watch and the University’s Legal Advisers have approved our use of the Apache License v2.0 to release code we’ve written back to the community!

The Apache License v2.0 is OSI-approved and allows us to release both source and binary versions of our software, which we’ve promptly done.

Hungrybot is a Jabber/XMPP bot, written in Ruby by Web Services developer Tom Natt, which sits in your roster, listening for commands and telling you about updates to feeds you’re subscribed to. We find it massively useful for letting us know when other team members have added a new bookmark to delicious, searching our website, finding out more information about someone at the University and what events are going on (some of these are inspired by the work of those good people at the University of Warwick). Click on the screenshots to see some of this in action!

As of today Hungrybot is open source. Download the source code here (we don’t currently have anonymous access to the Subversion repositories where we keep our code, so we’re providing a Zip file produced by our project management tool, Trac – this may change over time as we come to a better arrangement).

In the future we’d also like to release some of the custom plugins we’ve created for our CMS, OpenCms, and a range of other things we use on a regular basis (update: Andy Savin has released our first OpenCms module! Download it here and check out the README).

For other universities looking to do something similar please feel free to look at the Web Services Open Source page on our wiki and ask questions in blog or wiki comments or by mailing web-support@bath.ac.uk. If you’re on a Jabber/XMPP network, feel free to add me – pgw22@bath.ac.uk!

Alrighty then.

Firstly, many thanks to Alison for thrusting me into the limelit microscope that is this blog :)

As some of you may know, I have worked as a web designer for almost 10 years now – in fact for those of you interested this is my very first professional website (circa 1999).

Yes, it’s terrible - I was young, I needed the money.

Thankfully, times have moved on and my current portfolio is – hopefully – a little more illustrious (and sans nested tables).

Continue Reading

Today we welcomed a new addition to our team; Liam McMurray joined us as our new Web Designer.

A former freelancer Liam is an experienced Interactive Designer and Producer with a keen interest in typography. His portfolio includes work for BANES (Youth Matters) and EduServ (MyAthens).

We are pleased to welcome Liam on board and look forward to working with him on our exciting new developments.

We have created a new improved interface for inserting PersonFinder details, with more display options than before.  You can see some examples of what is available by visiting the sandbox example page.

You can

  • specify what resource you want the person’s name to link to:
    • PersonFinder page
    • PIP profilepersonal home pageor a
    • profile page on your site, which must be located in
      /[department]/people/[initial(s)][surname].html, e.g. /oenology/people/jdbloggs.html
  • select which contact details you want to display (name, role, phone, email)
  • display details as a bulleted list, a table, a table row, or a normal paragraph
  • restrict department lists by job title and by person type
  • display a group (using the group short name, e.g. DEPT-ADMINS) that has been created in GroupManager.
  • combine any of this information with details from PIP, or with included biographical information (for example, creating a short biography for each staff member and include it on multiple otherpages in your site; then it only needs to be updated once).

The old PersonFinder macro will still work in any existing pages that use it.

© Copyright University of Bath. All Rights Reserved.