I’ve said I wouldn’t do as much cross-posting, now that we have a combined blog feed (see over on the right). But I thought I’d mention it here, and explain a bit about what it means for LibraryThing.
For those concerned about development time, I want to emphasize that LibraryThing for Libraries is good for LibraryThing. On the most basic level, it’s going to help our bottom line. That means more programmers making features and fixing bugs. Conceivably, it could mean cheaper accounts.
It also deepens our relationship with libraries, and returns a favor. LibraryThing was built on library data, and we’ve been graciously invited into the library conversation. We are charging for LibraryThing for Libraries, but our prices are in an entirely different league from what libraries are accustomed to pay for their online catalog software. And as these catalogs add “social” features, LibraryThing for Libraries will exert powerful downward pressure on prices. Ultimately, the industry needs a newcomer to take a huge slice of a smaller market. We’re not going to be that company, but we can push the trend along.
LibraryThing for Libraries has also taught us a lot about library catalogs. These are some thorny, mysterious systems! Until now, we’ve relied exclusively on the simplicity of Z39.50 connections, which most libraries don’t have. But we can do more. With out new-found experience, we can start connecting to the remaining 95%. If nothing else, this should help our language reach.