Once again I’ve broken my golden rule of blogging – “never leave a post in draft for more than 48 hours” – and so I’ve had to prune a few bits that I’d intended to write about. Some of these may – or more likely may not – be covered at a later date.
I’m writing this sat on a plane to Chicago at the start of my holiday – driving across America from San Francisco to New York. But I’m not here to gloat this time! For the last week I’ve been at the University of Essex in Colchester for the Institutional Web Management Workshop – an annual conference for people involved in the web in Higher Education. This was my third IWMW, following on from great events in Aberdeen and York.
This year I’d been asked by the conference chairs – Marieke Guy and Brian Kelly – to be part of the “organising team”. I’m still not entirely sure what this involved but I basically gave my opinions on various aspects of how the workshop runs. I was also asked to chair the Thursday morning session which seemed easy enough!
A few changes were made this year to the structure of the sessions. Following the introduction of “BarCamps” last year, these were expanded to three 30 minute sessions, replacing the discussion group (which never really worked for me). The Wednesday afternoon was split into front- and back-end “tracks”. While one track had a parallel workshop, the other was running a couple of plenary talks. The idea of this structure was to broaden the event to provide more technical and marketing/governance content to those that are interested. Additionally, there was an attempt to “amplify” the event through use of video streaming, a blog and live Twitter updates – I’ll discuss that some more later.
Parallel Session: Mashups Round the Edges – Tony Hirst and Mike Ellis
Mike Ellis from Eduserv and Tony Hirst from the Open University presented an introduction to mashups session. Anyone who follows Tony’s blog, OUseful will know that his work on mashing up various data sources can only be described as prolific. He’s been doing stuff in the HE sector for a while including a page showing how autodiscoverable RSS feeds on HEI websites. Released at last year’s IWMW, the number of sites with at least one feed has now increased to an underwhelming 33%.
Mike’s also been spreading the word recently, promoting linked data. Check out the slides from one of his recent talks to get an idea of some of the things he’s barking on about 😉
Mashups are one of those things that I always intend to do more with especially when Tony Hirst makes it look so easy! I’m not going to write any more now but I’ll try to post some examples of what you can do with the data that we make available.
Making your killer applications… killer! – Paul Boag
A few weeks ago, Paul Boag’s slides for this plenary came up in my Google Reader feed of contacts’ presentations. I had a quick flick through, spotted a screenshot of one of Edge Hill’s course pages, and started to worry! As is the fashion with presentations these days, Paul’s slides contain very little text leaving me to think about all the possible faults he could be picking in our site. Fortunately he was quite positive.
I completely agree with him that the stuff we have in the online prospectus doesn’t go far enough in terms of engagement – there is much more we can do. I hope some of this will happen through the new department and faculty websites. These will provide pages where we can give a richer experience of what it’s like to study a particular subject, leaving course pages to describe the detail.
Parallel Session: Scrum – Andrew Male
Andy Male from University of Bath Web Services ran a workshop in the back-end track about using Scrum techniques in a development team. I’ve spoken to several people from Bath about scrum before but haven’t had the time to invest in working through how it works. Andy’s session gave a very useful introduction to the terminology used and then went hands-on using an accelerated scrum cycle to build a LEGO house. It took our team a couple of cycles to get good at estimating workloads but after that we were knocking out tractor sheds, flowerbeds and lakes left, right and centre!
Seeing scrum in action has motivated me to try the technique at Edge Hill. With a smaller development team, it may not work for all our projects, but I can see it working really well for certain things.
How the BBC make websites – Michael Smethurst and Matthew Wood
Everybody knows the BBC makes good websites. Some may point to the amount of money Auntie receives through the licence fee to explain this but just throwing money at a problem doesn’t make things perfect. I’m sure that every web developer in the country has at some point cited the BBC as a reason for doing something. The day they introduced their first pages designed for 1024 pixel screens I rejoiced as it meant we could finally start thinking about developing fixed with sites that looked good at higher resolutions.
In /programmes, the BBC Audio and Music team have created something capable of scaling to record every TV and radio programme ever broadcast by the BBC. The plenary talk was about “designing and building data driven dynamic web applications the one web, domain driven, RESTful, open, linked data way”. Bit of a mouthful! What I took this to mean was a real interest in the data that they wish to publish well before they look at designs. I suspect a few people in the audience were shocked at their opposition to “PhotoShop mockups” but we’ve sometimes had problems with sites when we’ve designed first, coded second resulting in spaghetti PHP.
I blogged about the BBC’s beautiful URLs last year and since then they’ve implemented the functionality promised and much more. Hackable URLs mean websites work for their users, not forcing users to to work to the website.
Probably the thing that stuck out most for me was their approach isn’t to build content management systems, but to create systems to manage data. You’ll hear me talking about this again.
I mentioned earlier that I’d been asked by Brian and Marieke to chair the Thursday pre-coffee session. I perhaps didn’t fully understand that this also involved co-presenting the 45 minute session following the chaps from the Beeb. The schedule had “Developers Lounge Show and Tell” pencilled in for the slot but the outputs from the developers lounge were – how can I put it – limited! A quick chat with Mike Ellis over a beer at the drinks reception led to a rough plan – we’d talk about some stuff and it’d all be fine.
Mike went for the Just In Time approach to preparing slides and delivered a great talk about becoming more than a day coder. I wholeheartedly agree with this – in the IT industry, and for web professionals in particular, it’s vital to stay current and engaging with the geek community or attending BarCamps or hacking on your own projects in the evening is a great way to do that. I approached my 10-ish minutes like a teacher at the end of term and played a couple of videos. We finished up with debate answering important questions such as “are design agencies a waste of money?” (Paul Boag seemed to think so!) and “is Web 2.0 ‘where it’s at’?”
I’ll let others be the judge of how the session went, but I was glad when it was over!
During his wrap-up session, Brian Kelly mooted the idea of an Institutional Web Management Community – a way for Higher Education web people to continue the conversations that go on at IWMW. Like the JISCmail lists, but better.
After last year’s IWMW I asked why so few web teams have a blog. Twelve months on and what’s the situation now? It appears a couple more have popped up; I’ve heard there are others but limited to internal viewers but should we do more? Brian suggested an aggregator similar to the predominantly US-based BlogHighEd.org and while this may provide some focus it’s not the whole answer. Clearly the US has many more colleges so we’ll never match them in number of active blogs but it could form part of the IWMC. What needs to be done for this to happen? Maybe in the spirit of mashups, all we need is a Google Spreadsheet and a bit of Yahoo! Pipes magic?
I saw one comment on the Twitter stream along the lines of “this year seemed very developer-focused – where was all the discussion about governance?” I was following the backend track so it was likely to be more technical than previous years, but is this a bad thing? If we get too bogged down in policies and strategies then we run the real risk of failing to innovate.