Week Fourteen : The end isn't near, it's here

I can't believe the end is here.  Once I've finished this post, I'll be done all of the coursework for my MLIS.  I guess I should get it over with.  I've left a discussion of best practices and how I think social software can be best used in libraries until last, but I've been thinking about it all semester, with each week's topic.

I discussed my personal favourite social software tools last week, and this week I'm looking at which ones I think have the most potential for use in a library environment.  I think in terms of ease of use, implementation, and adoption, a blog is a great tool to ease any user group into using social software.  The blog could initially be used internally, or used as a component to keep the website updated more frequently (like a news feature).  People may not even realize that it's a blog, but it will improve library service.  I think the tool with the potential to have the biggest impact is RSS feeds, especially customizable catalogue search RSS like we saw at some libraries and with some online journals.  The problem with this kind of service is that RSS still isn't widely used, and users may not be aware of the benefits associated with RSS, or how to use it effectively, to be able to take advantage of it.  I think tagging also has great potential to enhance a user's experience of an OPAC, but it requires a significant technological change, and a great deal of user input to be effective.  I also like what the Library of Congress has done with Flickr, posting archival photos and having users help them identify people, places, and things.

On to best practices - I'm going to limit myself to one overarching best practice.  I think the best practice when implementing any new software, program, or service in a library is to look before you leap.  Do your research - see what other libraries and businesses are doing, see what your patrons think, and see what your staff thinks.  Think about it thoroughly before jumping in with both feet - dip a big toe in first.  I'm not necessarily saying not to use social software, but it's so vital to make sure you're using the right tool (as we've mentioned again and again), and not wasting time making the most beautiful FAQ wiki that no one besides library staff and a handful of users looks at.

 I've learned so much about social software in this course, and I feel completely equipped to implement one of these services in a library.  But I know for sure I'll be doing research, talking to people, and seeing what else is out there before I commit any long-term woman hours and effort to the project.  It would be so easy to hop on the social software bandwagon and bring in blogs, RSS feeds, tagging, and media sharing, but are all of these activities sustainable?  Will they be used and appreciated by your patrons?  It may sound callous and like I don't believe in the great potential these tools have for enhancing service, but that's not true.  I just have a healthy sense of skepticism and doubt, and want to err on the side of caution before committing a vast amount of time and resources to a project that may have been doomed to fail before it began.

So there it is.  Look before you leap.  Research and contemplate before you launch a blog, wiki, or start a gaming program.  That doesn't mean that these social software tools shouldn't be used, and this new technology shouldn't be taken advantage of.  It just means that the implementation of any new service should receive the same kind of consideration.  Just because a blog is "free" up front, it doesn't mean that it's actually free.  The success of social software in libraries depends on us using it responsibly, and ensuring it can be used sustainably.

Thanks to this course, I feel like I might have a chance at doing just that.  Thanks everyone.