{"id":2158,"date":"2007-09-26T22:37:49","date_gmt":"2007-09-27T03:37:49","guid":{"rendered":"http:\/\/blog.librarysupportstaff.org\/?p=411"},"modified":"2007-09-26T22:37:49","modified_gmt":"2007-09-27T03:37:49","slug":"libguides","status":"publish","type":"post","link":"https:\/\/www.libology.com\/blog\/2007\/09\/26\/libguides.html","title":{"rendered":"LibGuides"},"content":{"rendered":"

(Note regarding this post:\u00a0 When you read this post, be sure to read the comments as well.\u00a0 I did not\u00a0state my case as well as\u00a0I should, and end up\u00a0sounding as though\u00a0I don’t feel that LibGuides\u00a0has\u00a0as much value for libraries as they\u00a0obviously do.)<\/em>\u00a0<\/p>\n

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.<\/p>\n

LibGuides<\/a> 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.<\/p>\n

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.<\/p>\n

Why am I not happy with this offering? Two reasons.<\/p>\n

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?<\/p>\n

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.<\/p>\n

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).<\/p>\n

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.<\/p>\n

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.<\/p>\n

Reason two, for those of you who are still with me, is their license agreement<\/a> (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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

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.<\/p>\n

And if you want to see a positive review of LibGuides, which highlights the great points of the site, check out BiblioTech Web<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

(Note regarding this post:\u00a0 When you read this post, be sure to read the comments as well.\u00a0 I did not\u00a0state my case as well as\u00a0I should, and end up\u00a0sounding as though\u00a0I don’t feel that LibGuides\u00a0has\u00a0as much value for libraries as … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[2920,2943,2944,2952,2982,2966,2977,2979],"tags":[2985,3604,3497,4674,3605,4673,3948,3606,3607,3608,3483,3609,3610,3611,3021,3612,3613,3432,3614,5387],"class_list":["post-2158","post","type-post","status-publish","format-standard","hentry","category-blogs","category-libraries","category-library-20","category-online-services","category-open-source","category-software","category-web-design","category-wiki","tag-20-technology","tag-annual-web-hosting-fee","tag-blog-software","tag-consultant","tag-content-management-system","tag-e-mail-management","tag-facebook","tag-few-built-in-tools","tag-hosted-web-server","tag-hosted-web-service","tag-instant-messaging","tag-paid-solutions","tag-search-pages","tag-shared-group-calendar-software","tag-usd","tag-virtual-server","tag-web-design-instructors","tag-web-presence","tag-web-server","tag-xml"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pSU5g-yO","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts\/2158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/comments?post=2158"}],"version-history":[{"count":0,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts\/2158\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/media?parent=2158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/categories?post=2158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/tags?post=2158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}