Recent Topics

Dec. 19, 2009. Does Library Journal dislike my online MLS? After reading John Berry's comments, the question needs to be asked, and we all need to consider what those comments really mean.

Series: Library Web Site a foregone conclusion?

Sept. 14, 2009. Getting Started. Library Web Sites: Positioning, Integration, and Adding value.

Sept. 24, 2009. Backup and push... Libraries without web sites!

Oct. 5, 2009. Do we really need a web site for the rural library? Arguments against a web site, infrastructure and connectivity.

Oct. 17, 2009. Paying the Bills...utilities for the library. Web portals. Costs. Outsourcing=access vs. ownership. Organize to make sense for your public.

Nov. 30, 2009. Competency vs. complexity: win by "picking your battles." Eliminate overhead, leverage library competencies, dotnetnuke, and mystax.

Dec. 6, 2009. Full circle. Arguments against an academic library portal site, positioning, integration, adding value.

Getting started...

Monday, September 14, 2009 at 12:15 PM
The fundamental requisite for anyone that wishes to be read--or heard for that matter-- is to have something to say. That is a sore spot for a lot of libraries. Don't add a blog to the site without having the intention to keep it up by freshening the content regularly, and preferably frequently. [See how I turned my indecision about a topic to my advantage? I suppose I could talk about this...but no... ;^) ] I guess I'll be making at least four entries this semester, however, if people are following and time permits, I will post more.

The point of this blog is to discuss technology for the small and rural library. The emphasis is going to be on eliminating costs, adding features, and improving your computing reliability. I have a few posts planned but let's see what develops.

We'll start off slowly by considering a relatively easy way of providing features and content for patrons. I want to discuss the practice of collecting links. Many libraries do it to some extent or other. Some have gone so far as to catalog them in the ILS. You know how our favories folders are running over, right? Well then it's a natural step to share them, and of course, for the sake of our public, organize them too. This practice is really a throwback to the early days of the public's awareness of the Internet. Back then, it seemed that a web site wasn't complete without a page of links.

Today we find such rich collections of links as the Internet Public Library (IPL - originally a Michigan product, thank you) and the Librarians' Internet Index (LII). With all of that, why bother to collect on your own? Wouldn't it be better to just link to them and be done with it?

That depends, I guess. If you have a web site and some time, I believe it is still worthwhile to collect some links for your website. Why? Integration and positioning. Both of these make the user's life easier. Positioning is setting the object up in a meaningful way that clearly delivers some advantage for your patrons. Integration is achieved when the object is combined with other elements of your site for ease and convenience of use with the other tools in the web site. Both of these concepts are about adding value for the end user.

One of the problems of linking to aggregations is that each aggregator has a different interface and this presents problems for patrons. I have actually heard a patron speaking of our state's online collection saying that he doesn't have time to waste on all of that. In fact there is a lot to choose from there. A case in point is the history section. It contains a lot of digitized works of historical significance for students of state history. Unfortunately it isn't well indexed. This is where a librarian can spend a couple of hours once to save countless hours for patrons. Now all of the state's links to materials that are germane to our county's history have been analyzed and selected and are readily available on our site. This is a perfect example of a repackaged collection of links providing a tangible advantage for patrons.

The trend today is toward big libraries (State library) , big systems (OCLC), big utilities (Google, Ebsco, etc), and even big link collections (IPL, LII). This has a disintegrating effect as the patron now has to deal with all of them, each in its own environment. The library can mitigate this to some extent, as I have demonstrated. It looks to me like an important way to add value, and seems likely to be increasingly so as this paradigm overtakes us. What do you think? ~dd

0 comments

Post a Comment

TOOL BOX

Libweb - find public libraries on the web - benchmark yourself!
http://lists.webjunction.org/libweb/Public_main.html

Well-defined web site goals
http://www.olis.ri.gov/pubs/plstandards/websites.php

Design Strategy
http://www.alistapart.com/articles/homepagegoals/

Writing for the web: a primer for librarians http://bones.med.ohio-state.edu/eric/papers/primer/webdocs.html

A great site for Library Web administrators http://www.libsuccess.org/index.php?title=Website_Design

How to Create your own "hidden web" application pages http://databases.about.com/od/tutorials/ss/dynamicweb.htm

Library webmaster links-- large, old, a bit cluttered, but useful: http://www.librarysupportstaff.com/4libwebmasters.html#content

Learn about how you set up a portal with Dotnetnuke

This short video will give you an idea of what it is like to use a DNN portal. Searching youtube for "dotnetnuke" will turn up many videos, some about using DNN and some about programmng it. The programming is more complicated, but is not required.