I was reading a story last week about the Linux Foundation‘s third annual report [PDF] of the Linux kernel, and in it was a section that talked about the affiliation of the programmers that contributed to the development of the kernel. This got me thinking about the affiliation of programmers in the library open source community. More on that after a brief detour to explain what the “kernel” is.
Schemes to add functionality to the web OPAC fall into four categories: web OPAC enhancements, web OPAC wrappers, web OPAC replacements, and integrated library system replacements. I’m outlining these four techniques in a report I’m editing for an OhioLINK strategic task force and a bit of a reality check on this categorization is desired, so if I’m missing anything big (conceptually or announcements of projects/products that fall into these categories), please let me know in the comments. Generally speaking, this list is ordered by cost/complexity to implement — from lowest to highest — as well as the ability to offer the described enhanced services from least likely to most likely.
This started out as a comment to a posting by Chris Coppola, president and co-founder of rSmart Group. The comment got longer and threaded with yesterday’s posting about the nature of BioMed Central, so I moved it to this posting on DLTJ. For those in the library community who are not familiar with rSmart, it provides commercial support for the Sakai collaboration and learning environment and the Kuali administrative systems suite. rSmart is somewhat equivalent to Equinox Software and LibLime in the library automation arena.