Congratulations : ye have overcome the wiki one*

26 February 2008

Task 19 of the 23 Things program requires me to put a photo of my pet on the library staff wiki. My lilac Burmese cat Lily is already there, in excellent company with 77 other pets:


I regret that this was quite a difficult task for those who don’t have pets, those who have recently lost their pets, and those who struggle with the wiki software.

I’m not going to go into too much detail about the origin of the wiki; my colleague Dana gives an excellent linguistic rundown on her post so I’ll save myself the time. But I think I’ve made it clear in a previous post that I like the idea of wikis as a means of keeping as much of our corporate work accessible, transparent and current as possible.

There are many reasons why wikis are better than intranets in our setting. For starters, intranets tend to be a top-down method of communication where senior levels of management deposit policy documents and statements to trickle down to their underlings. There is usually little or no encouragement for contributions from further down the food chain. That’s not how we want communicate in a library. Libraries are spaces for learning, creativity and collaboration at all levels of scholarship; that should include the library staff.

Secondly, intranets are usually maintained by a single administrator who uses complex HTML and stylesheets to build pages. While our web managers are quite capable of running a system like that, it defeats the purpose of a horizontal communication tool if we have to email them every time we want to make a change. Documents on intranets tend to go out of date very quickly and become redundant when an administrator has to see to other tasks; staff members are unlikely to pay attention to an internal method of communication if it’s perceived to be constantly out-of-date.

Many of my colleagues seem to have found using the staff wiki quite stressful. I agree with Dana that remembering the special wiki markup language is actually very difficult for those schooled in the HTML encoding used in websites; it’s like learning Dutch after learning German — the languages are similar on the surface, but sometimes their similarity is actively misleading.

For me, learning to use our Swinburne Library MediaWiki software has been a process of trial and error (lots of errors and quite a trial at times). I’d never used a wiki before June last year, but I found many of the help manuals on Wikipedia very useful for both basic and more advanced skills.

Library staff will have noticed that it’s particularly difficult to upload documents to a wiki. This is because wikis can’t really compute the concept of a word processed document; the software makes the assumption (whether good or bad) that if you’re adding textual content, you’ll do it in wiki markup. Uploading images is not an easy task, either.

I was disappointed that my idealistic viewpoint on democratic flows of information is hampered by my pedantry. I found it difficult to search for specific pages on the wiki; no matter which keywords I used, I often couldn’t find the page I was looking for. So I made a decision to introduce categories to our wiki, so that it’s easier to browse by topic, unit or campus for pages of interest. Every time someone adds a page to the wiki, the software sends me an email so I can log in to add the page to a category. This might appear a little intrusive, so please let me know what you think in the comments or on my talk page.

The other problem I discovered with wikis is that attempting to navigate around them can lead users into a bit of an abyss. It’s especially difficult to go backwards. You can click the Main Page link on the left-hand side panel to return to the homepage, but if you’ve come across a page purely by chance you’ll struggle to ever find it again. My response to this problem is to add breadcrumbs to each wiki page in the hope that it’s easier to feel my way around. On our Online Services and Strategies pages, I’ve also added a section for related links at the base of each page to help users find more information or return to an area of interest. If you’d like to do this to your own pages, please feel free. I think it’s a handy trick. Again, please let me know what you think in the comments.

*’ I write unto you, young men, because ye have overcome the wicked one.’ (1 John 2:13)


How libraries are using RSS

21 January 2008

I’m beginning to wonder if I’m a lousy blogger. Surely blogging is meant to be about frequent updating of content in a short, sharp conversational style? My posts are more like essays. Maybe I should stick to scholarly literature, although of course that actually has word limits …

Despite the length of my previous post on RSS, I still have something to say about the topic. As this post from the Official Google Reader Blog points out, there are feeds for almost everything, including weather, fashion, and social networking. The news you receive from Facebook about your friends’ activities uses RSS; if you click on the little RSS button (normally orange, this time blue), you can subscribe to friends’ updates in your feed reader.

That’s of course if you want to lose even more time …

Those of you who work at Swinburne Library with me might remember the presentation that Dana and I gave at the staff development day last year. We talked about using technology to reform library collections, and yes, I’m the one who couldn’t work out where the port was for my flash drive … embarrassing.

Although the newly-named Online Services and Strategies Unit hasn’t started a Facebook group for lovers of online research repositories yet (ok, ever), we do find that there are a number of ways we can integrate Web 2.0 functions into our work to make our lives easier. So I thought I’d give an insight into how we use RSS to help with Swinburne Research Bank.

Part of our workflow for creating content for the repository involves running regular searches on bibliographic databases such as Scopus, Web of Knowledge, EBSCOhost and Informit. Most of these services allow users to save a search string, for example ‘Swinburne AND University’, provided they have registered user accounts. Scopus allows this saved information to be converted to an RSS feed. I can then subscribe to that feed, and be alerted every time a publication is added to the database that contains both the words ‘Swinburne’ and ‘University’. I imagine that the liaison librarians do something similar within their own disciplines.

The University of South Australia Library thinks this is such a good idea that they have made these RSS feeds easily accessible to their users. They also provide a subscription link for library users to easily discover new additions to the collection. I think this is a great way to communicate with library users, both staff and students. Bond University‘s research repository, ePublications@bond, provides a similar service to alert staff and students when new papers are added to the collection. These are just some of the ways that Australian university librarians are beginning to use RSS to make their users’ (and sometimes their own) lives easier.

It’s worth mentioning, though, that feeds can get out of control. I don’t know how it happened, but I now have so many unread items (well over 1000) that Google Reader is starting to … well … devour them.

(‘2 PM @ San Francisco Zoo = Big Cats Feeding Time!’, from Minuk’s Flickr photos and reproduced under a Creative Commons License)

Poor bunny.

Update: Those following this discussion might be interested in this post from iLibrarian on creative uses for RSS feeds.