(Note regarding this post: When you read this post, be sure to read the comments as well. I did not state my case as well as I should, and end up sounding as though I don’t feel that LibGuides has as much value for libraries as they obviously do.)
I don’t normally post “negative” about web sites or services; if I am not impressed by something being offered, I simply don’t blog about it. However, I have noticed a really interesting Library 2.0-related offering, and feel that it should be mentioned here.
LibGuides is a truly interesting and useful product. It offers a way for a library to implement many Web 2.0 tools via a service that is remotely hosted and configured, with content and features that you select.
It looks great, in many ways. They include tools for Facebook integration (great for academic libraries), showing RSS feeds on LibGuide pages, and built in instant messaging (IM) capabilities.
Why am I not happy with this offering? Two reasons.
Reason one is their pricing model. According to their FAQ page, their “annual license fee ranges from $899 to $2,499”. This, to me, is packaging Library 2.0 like a database subscription. True, they have done some excellent work in setting up page templates and integrating tools, but why should a library spend that amount of money to rent those services?
Let me provide an example. This blog is run on a hosted web server. The annual fee for this server is less than $50. This provides 1 GB of disk space, plus quite a few built-in tools such as a MySQL database, full e-mail management including listservs, site statistics, and a comfortable amount of site traffic. I have run several different websites on this company’s servers, and have been happy with their service.
What have I run on these sites? Standard web sites, wikis, a blog, a content management system (CMS), listservs, discussion forums, and custom search pages. There are only two things that I have wanted to install that I haven’t been able to, based on their security settings: I can’t host a WebDAV calendar (for shared group calendar software), and cannot install a library automation system, like Koha or Evergreen (so I have to play with Evergreen using a virtual server on my home computer).
Most Web 2.0 software has open source options available. This means that I can select a blog software, download it, install it to the web server, configure it, and there it is. Is this easy to do? Yes and no. Configuration, especially the database settings, can be fairly detailed. WordPress has very good instructions, and if you are comfortable with copying files from one place to another, and can follow a written guide you won’t have much trouble getting a blog up and running.
Wiki? Same type of installation. Want to run a listserv? Don’t need to install anything, just go to the sites control panel and set it up. What I am trying to say is that for $50, time, and some effort, your library can create a web presence that is just as rich as what is being offered via LibGuide.
Reason two, for those of you who are still with me, is their license agreement (Pdf). You pay them, they provide the service on their servers for one year. They can change anything about the agreement, and all they have to do to make you comply is notify you. You own your own data, and they will provide it to you within 30 days of cancellation, if you ask.
These are pretty standard clauses for many services and software. It is actually quite mild compared to some. It still doesn’t sit well with me that open and interactive services are packaged and controlled like this.
Sure, you could try them out for a year, decide not to renew, and only have an xml file with your content and data to show for it. Or you could get a hosted site, start a blog and a wiki (or a CMS with both built in) and build your site from scratch, adding content here and there, adding new programs and technologies as you go.
Even if you hire someone as a consultant to do the installation and initial training (find people in your area who do this, or want to learn… try contacting web design instructors at your local community college for potential contacts), you can do a great deal in a relatively short time span. Even if you spent $500 for someone (and you shouldn’t even need to go that high), once set up the software and technology is yours for just the annual web hosting fee. Just be sure to learn as much as you can about how everything works, and learning what your site’s potential can be.
And after all of this, if you don’t want the hassle or cost of the hosted web service, you can still do many Library 2.0 functions through other sites. Blogs are available simply by registering at WordPress or Bloglines. Similar options exist for IM. You can find hosted wiki and CMS sites, but these are mostly paid solutions.
I strongly suggest that every library examine their options for the range of 2.0 technology, and adopt those which will best fit your environment. It doesn’t need to cost much; it doesn’t need a limiting license agreement; it does need to give you the flexibility and the power to connect your services with your customers.
And if you want to see a positive review of LibGuides, which highlights the great points of the site, check out BiblioTech Web
Hi there, thank you very much for mentioning LibGuides on your blog. As a small company, we appreciate any “free press” we can get (there’s no such thing as bad publicity, as the saying goes 🙂
If you allow me, I’d like to point out a few things regarding the issues you take with LibGuides.
1) Pricing model. While it is true that online database subscriptions are priced similarly, LibGuides is not “packaging Library 2.0 like a database subscription.” LibGuides is a piece of software, and we license it on a Software-as-a-service (SaaS) model. This model of “renting” software rather than purchasing is nothing new and, in fact, it is fast becoming a dominant way for organizations to use software. The entire software industry is moving towards the SaaS model, and LibGuides is just one example of an SaaS application.
2) License Agreement. Since LibGuides is SaaS, our license agreement is actually very liberal for an SaaS application. If you could find an SaaS License Agreement that is less restrictive than that of LibGuides, we will modify ours accordingly, to match the less restrictive one. We have looked at a whole lot of SaaS licenses when drafting ours. Please send us the one that you think is less restrictive, and I promise we will change ours accordingly. We’re not out there to play “gotcha” with our clients, or to take advantage of them via our License. Having a license agreement is simply a cost of doing business in our (rather litigious) society. Our agreement is very liberal, as the software license agreements go.
Your most important point, I think, is that libraries can do a lot of “LibGuides stuff” themselves. Absolutely true! In fact, we say that on our “Why LibGuides” page – (http://www.springshare.com/libguides/whylibguides.html). It’s not rocket science, as our webpage points out. LibGuides has only been out for several months and, judging by the overwhelming positive response from libraries to date, there are plenty of them who think LibGuides is a great bargain for the features it offers. These libraries would rather spend a bit of money on a full-featured professionally developed product (that is being worked on and improved, continually), rather than going the DIY route. We don’t pretend to be a “universal” solution for every library, nor do we expect every library to come on board (we won’t turn them back if they do, though 🙂
There is a live, fully-functioning test LibGuides system at http://demo.libguides.com, and we give free accounts to whoever wants to explore the LibGuides features. If, after checking out all that system can do, libraries decide they can do it cheaper and better themselves, we do not mind that all. We’ll even give free advice!
So far, however, the large majority of libraries who spent some time playing with LibGuides have decided that they are better off licensing LibGuides than trying to do it in house.
I’d like to invite the entire LibrarySupportStaff.Org staff to get a free account and check out the features and everything that LibGuides offers. In addition, I’d be more than happy to give you contact info at every client we have – every single one – and if any of them gives us less than a glowing review, I will eat my words right here on this blog 🙂
Thanks very much for your time and attention. I apologize for somewhat lengthy reply, but I hope it was worth your time.
Best,
-Slaven Zivkovic
Chief Springy
http://www.springshare.com
For what it’s worth, sure a blog or wiki can be set up cheaply and get a library using “Web 2.0” technologies, but what LibGuides provides is way beyond implementing 2.0 for its own sake. The system makes it very easy for ANY librarian to create an online resource guide or collection of information on a topic. I’ve been able to take a “generationally challenged” librarian who’s not particularly comfortable with new technologies and help them set up a LibGuide in half an hour.
The best part is that LibGuides interfaces with Facebook, where 90% of our students are already spending a great deal of time. This allows us to go where they are in the virtual world, making the library more ubiquitous for them.
And then there’s the whole community aspect which allows librarians to interact in online forums with other librarians who are also using the system. Sharing ideas with others who have the same subject area responsibilities is a powerful tool. And since we can view the Guides that other libraries have put together, we can get ideas and grow that way also.
The “web 2.0” aspect that makes LibGuides so attractive is that we go to where the students are (virtually), allow them to interact with our materials through ratings and comments, contact us via integrated librarian profiles, and relate ourselves to other librarians in this virtual community.
To me (and to my library staff), that’s DEFINITELY worth paying an amount much less than what we pay for some databases which hardly get used. 🙂
Scott Pfitzinger
Reference Librarian
Butler University
http://bibliotechweb.com
I want to thank both Slavin and Scott for providing detailed and constructive comments.
I didn’t state my ideas all that well, and deserve criticism for how LibGuides comes across in my post. That I get constructive critiques instead of criticism is a credit to each of them.
To summarize what was in my mind when I wrote this post:
1) I feel that libraries, as well as individuals, should examine their tech needs and desires, and find what works best for their situation. If LibGuides’ offerings are a good fit for your organization, and the pricing model fits your budget, I think they are a great service, and would recommend it.
I am at heart a DIY type, and approach technological innovation with “how can we use this?”, which can cause me to forget that many people do better by focusing on developing content and using the technology, rather than building their tech presence.
2) I don’t like some aspects of many license agreements; this is stated in the post. I didn’t mean to imply that LibGuides was in any way attempting to use this to their advantage. In fact, the opposite is true: I was impressed that they had their agreement available on their site. This level of openness is usually a sign of honesty and integrity.
My concern is for license agreements in general, and I didn’t make that clear enough.
I encourage anyone interested in Library 2.0 to check out the entire range of options in order to determine what is best for their situation. This includes Software as a Service as well as Do-It-Yourself.