I’m attending the NISO forum on collaborative library resource sharing, and heard a cautionary tale about making sure that a software project meant to be open source actually gets there.

Gail Wanner from SirsiDynix spoke today about the Rethinking Resource Sharing Initiative, an effort to revolutionize sharing of materials and services among libraries and their users. One of the products of the initiative was a Firefox plugin called GoGetter (previously known as GET-IT) that could grab information about a book from a web page and give the user a list of ways to get it, including online bookstores, the local library, resource sharing networks, Google Books, and so on.

A proof of concept was ready by June 2007 and was successfully demonstrated. However, work on it stalled — while the plugin was meant to be open source, apparently not all of the institutions involved in writing it (or employing the programmers involved) were prepared to let it go. Over the past year, various institutions have been signing off on releasing it under an open source license; while there’s been progress recently, GoGetter is not yet free. In the meantime, nobody has been able to play with it, improve it, or make it compatible with Firefox 3.

Lesson of the day: if you want to start an open source project, particularly if multiple institutions will be involved in writing it, it’s a good idea to make sure from the beginning that all parties are willing to release their work under an open source license.

Last week I had the chance to get a hardhat tour of the massive renovation project underway at my alma mater’s epicenter, Ohio State University’s (Main) Thompson Library. Lest you get the impression from my Google Books post that physical libraries are passé, the Buckeyes here provide a striking counter-example.

In classic OSU style, the scale of the project is huge, with a cost of over $108 Million and 140 full-time construction staff.

This leads to many questions. What does a hundred million dollar book house look like?  Well, you can see for yourself on this University webcam, right now during daylight hours it looks like a Bob the Builder episode.  Click through the image above or here for the tour photos.

Also, what are the defining requirements of systems that are suitable for use in such a large environment?  How well do their current implementations fulfill them, and how well does Koha compare?

[update] Added links. [/update]