Freeware isn’t free. Nor is open source software. Yet, I often use those terms in describing social software solutions to libraries as cost-effective communication, marketing, or customer service tools for their libraries. I (as well as others) am intrigued by the implementation of open source library automation software by some pioneering library system, most notably the Georgia PINES (Public Information Network for Electronic Services) library system, which migrated in September 2006 from a commercial ILS system to an in-house developed, open-source platform, named “Evergreen.”
Wow, it’s so cool to be able to access or download software like Blogger or pbwiki (“make a free wiki as easily as a peanut butter sandwich”) and in a short time display a product that simulates the online presence of big library technology gurus. Trouble is, we’re seldom cognizant of the true cost in development and customization time involved in getting the product on the virtual street.
Open source software refers to an application that is derived from a freely accessed basic code and developed through a collaborative effort by multiple users in an environment dispersed both through time and space. Note: no record is kept of the value of the time of all those IT gurus (not insignificant).
Karen Schneider draws a really relevant metaphor in her posting on ALA TechSource, IT and Sympathy.
. . . remember nothing is “free,” even if it didn’t come with a price tag. Second Life isn’t “free.” Instant messaging isn’t “free.” WordPress isn’t “free.” (In fact, that sucking sound you hear may be your RSS feeds dragging down that server hosting your blogs.) Or, more correctly, all of these technologies are “free” as in “free kittens,” not free as in “free beer.” They come with maintenance and deployment issues, from opening ports on a secure network, to how much bandwidth they will use, to how much time IT personnel need to devote to deploying and maintaining the “free” software.