the first of, I suspect, many ILS lawsuits

“The Queens Borough Public Library, one of the largest and busiest libraries in the United States, has filed a major lawsuit against Sirsi Corporation, which currently does business as SirsiDynix.”

You can read the complaint here. Even though it’s 193 points long, I suggest some browsing. The basic issue is that Queens Borough was looking for an ILS, got bids from both Sirsi and Dynix, chose Dynix and then because of the “merger” actually got Sirsi who were a little jerkish. The library spent a lot of time and money on this process and wound up with the product they had not chosen. I’ll be interested to see where this goes. As someone who is often privy to a lot of “we have been having nearly-legal fights with our ILS vendor” stories, I’m glad to see one break through the light of day. [gwasdin]

errors, on fixing

I read with interest this blog post over on Freedom to Tinker about the Google Book Search folks talking about finding and fixing errors in their giant catalog, metadata errors especially. The conversation seems to have largely started at this post on LanguageLog and gotten more interesting with follow-up comments from folks at Google. One of the things we have all learned in libraryland is that the ability to trawl through our data with computers means that we can find errors that might have otherwise stayed buried for years, or perhaps forever. Of course computers also help us create these errors in the first place.

What’s most interesting to me is a seeming difference in mindset between critics like Nunberg on the one hand, and Google on the other. Nunberg thinks of Google’s metadata catalog as a fixed product that has some (unfortunately large) number of errors, whereas Google sees the catalog as a work in progress, subject to continual improvement. Even calling Google’s metadata a “catalog” seems to connote a level of completion and immutability that Google might not assert. An electronic “card catalog” can change every day — a good thing if the changes are strict improvements such as error fixes — in a way that a traditional card catalog wouldn’t.

Note: thanks to people who let me know that one link was wrong, and that I managed to typo both “computers” and “interesting” in this post.

dad using his library card

This is the second and last part of the Jessamyn’s Dad’s Library Card story. I went home yesterday. I got a phone call from my Dad.

Dad: So I clicked the link in that email the library sent?
Me: Yeah? Good.
Dad: It connects me to “iBistro on the go…” what is that?
Me: That’s the library’s online catalog. The library is supposed to type their name at the top there but it looks like they didn’t.
Dad: It’s hard to read.
Me: Yeah it sure is isn’t it? [explains how to make font bigger]
Dad: How do I look for a book, do I really have to log in first?
Me: You shouldn’t have to, but maybe, it depends how it’s configured.
Dad: My login number is fourteen digits long! Why is that?
Me: Good question. You can probably set the browser to remember it. Your PIN is probably the last four digits of your phone number
Dad: It is. Why do I have to log in here?
Me: Well you can reserve books and check your account and there are privacy laws about that information.
Dad: Where does this catalog live?
Me: Depends on the library, many libraries run it off of servers in their basement. Some use hosted versions of the catalog. The consortium probably hosts this one.
Dad: And this iBistro thing is something they buy?
Me: Yeah and they pay a lot of money for it.
Dad: It sucks.
Me: Yeah. It’s sort of useful for consortiums [explains consortiums] so libraries can do interlibrary loan and stuff.
Dad: Okay I searched for sailing and I get 1500 hits. How do I search for the most popular books?
Me: I don’t know if you can, you can redo your search and sort by relevance.
Dad: Amazon lets me search by popularity. I like that.
Me: Yeah I do too. Can you sort the search you have?
Dad: No, it says there’s more than 500 records so I can’t search.
Me: You may be able to search by subject heading and get a shorter list.
Dad: Didn’t I do that?
Me: No, you searched by keyword [explains difference] or you can search just the books in your library.
Dad: I’m not already doing that?
Me: No, you’re searching the whole SAILS network.
Dad: How can you tell?
Me: Because on the search page next to where it says library, is says ALL.
Dad: Okay I’ll find my library. There are like 100 libraries on this list!
Me: I know, you can borrow books from any of those libraries.
Dad: I just want to know if there’s a book at my library.
Me: Yeah, that should be easier.
Dad: What are these libraries at the bottom of this list just called zddd and zddddd?
Me: That’s probably some kludge that the libraries are using to put books in a category or location that isn’t available in the regular catalog.
Dad: Okay thanks for the tutorial. I’ll try again tomorrow.
Me: You’re welcome. It’s not you, it’s them.

just to make sure we’re all on the same page here

“A team from Google interviewed dozens of people in Times Square the other day, asking a simple question: What’s a browser? This was in an effort to understand and improve the customer experience of Google’s own browser, called Chrome.

Turns out that over 90% of the people interviewed could not describe what a Web browser is.”

Don’t believe me? Watch the video. Granted, this comes from Google, but while we’re all being “blah blah Firefox, etc” there are many people who just see what happens when you “click the e” and go forward from there.

Website 2.0 – why a cms is in your future

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.