I spent Friday at the NELA-ITS CMS Day. I gave the keynote in the morning, just talking about what CMSes are and why they’re useful with a little overview of a few, and then hung out to see other librarians talk about how they’re using their CMSes. It was a great day. We had a wonderful, if chilly, room at the lovely Portsmouth Public Library and I learned a lot about how some New England area libraries are running their library websites with Drupal, Joomla, Plone and WordPress.
Having the actual people behind these websites talking about what worked and what didn’t work — and people were very candid about what was good and bad about these CMSes — made for a fascinating day of show and tell. Add to this the fact that all the software demonstrated was free and open source and I really think we sent people away with some great ideas on how to save money and still deliver good web content. Not having the chilling effect of a vendor’s stink-eye [or lawsuit threat] was also delightful. I’m now done with public speaking stuff until October I believe. Glad to end this season on such an up note. Thanks to NELA-ITS and Brian Herzog for coming up with the idea in the first place. Notes for my talks — links to slides and a page of links to what i was talking about, are here: Website 2.0! why there is a CMS in your future. Thanks to everyone for showing up. Here are the links to other people’s presentations and websites.
One of the problems that library consortiums have frequently solved is technology centralization. While I am not denying that consortiums have caused other problems, having one central go-to technology platform, software set, team of trainers and help desk has made many non-tech savvy librarians able to provide a higher level of service to their customers. For tech savvy librarians, this has sometimes come with a downside of lack of control of their own technology, or dumbed down interfaces to robust tools. We’ve been looking for a happy medium solution.
Two newish projects have been getting talked about lately in the states of Iowa and Oregon. Oregon is using Plinkit, a web authoring tool that is built on an open source CMS called Plone. This tool allows libraries to create nice looking professional websites with some standard modules (calendar, lists of links, links to electronic resources) and some standards compliance. Here is a list of libraries using it. Iowa got money from the Gates Foundation and is using it to provide web hosting for libraries along with an email hosting service (please don’t let it be an Exchange server) and a helpdesk person available by email and phone (and I bet chat by the end of the grant period) for all state libraries. One of the best things the Vermont Department of Libraries has done is to make sure every library in Vermont has a fixed and memorable email address that either forwards or links to an easy to use webmail interface. They have had this for years and it’s done a lot to help libraries stay connected and feel like part of the larger library system, even when they’re up a mountain serving 600 people. I’m not usually one to jump on the “technology builds community” bandwagon, because I think there are certain irreplacable virtues to face to face interactions. However when done properly and effectively, technology can help support communities that are already built, and help them put their best face forward.