- Free redistribution - the software’s license allows for redistribution without fees
- Source code -the software’s source code is available to developers
- Derived works - the license lets users modify the software’s source code
- Integrity of the author’s source code - some licenses may require that modifications to the original source code be renamed or distributed through patches
- No discrimination against patrons/groups - inclusion maximizes user diversity, which brings more benefits to the open source process
- No discrimination against fields of endeavor - the software may be used by any organization: commercial, nonprofit, etc.
- Distribution of license - the software’s license must transfer along with the software
- License must not be specific to a product ? the software cannot be tied to a specific software distribution
- License must not restrict other software - no restrictions can be placed on other software that comes with the open source software
- License must be technology neutral - the software can be used on different operating systems and platforms
Customization is another useful feature of OSS. Because users have access to the source code, they can tailor the software to their specific needs. “Open source software works from the idea that you can use and develop the software as you need it…Potentially you can customize it how best suits you.” (Routt, 2008) Unlike proprietary software, OSS users can take an active role in developing it or improving it. As Amy Begg De Groff, IT director of the Howard County Library, noted, “[W]hen you want a change to open source software, you make the change. Or, as we’ve found a few times, you search and find out that someone has already done what you want, and you merely use their code and credit their idea.” (De Groff, 2008)
Another challenge that proponents of OSS face is the perception that OSS does not offer the same kind of value as proprietary software. Unlike proprietary software, OSS usually does not have any kind of tech support call center. “Free and open source software application users, on the other hand, must rely on development communities for support.” (Colford, 2009) For library staff who may not have the programming skills or confidence, this lack of formal support can be daunting.
While most libraries have not adopted OSS to the same extent as the Howard County Library, most have already integrated some OSS tools into their arsenal. As Scot Colford stated, “Realizing that your organization is already a hybrid environment helps administrators and staff realize that a relationship with open source can be more like a respectful, close friendship than a toxic, codependent marriage.” (Colford, 2008) In Connecticut, the Darien Library uses Innovative Interface’s Millennium, a proprietary-based ILS, along with Drupal, an open source CMS, to create a dynamic, interactive library Web site.
Evergreen, an open source ILS, was developed for and is used by PINES (Public Information Network for Electronic Services), a consortium of over 275 public libraries in Georgia. Since its launch, it has been installed in a variety of libraries around the world, including shared catalogs administered by the Indiana State Library, which has fifty-three public libraries using Evergreen, and the Michigan Library Consortium, which currently has seven libraries sharing the system.
Colford, Scot (2009). Explaining Free and Open Source Software. Bulletin of the American Society for Information Science and Technology, 35(2), 10-14.
Georgia Public Library Service (n.d.). Retrieved July 15, 2009, from http://www.georgialibraries.org/public/pines.php
Gordon, Rachel Singer & West, Jessamyn (2008). What Can Open Source Do for You? Computers in Libraries, 28(44-45).
Groff, Amy Begg De (2008). Using Open Source to Give Patrons What They Want. Computers in Libraries, 28(3), 6-10.
Indiana State Library (n.d.). Retrieved July 15, 2009, from http://www.in.gov/library/evergreen.htm
Open Source Initiative (n.d.). Retrieved July 14, 2009, from http://www.opensource.org/docs/osd
Michigan Evergreen (n.d.). Retrieved July 15, 2009, from http://www.mlcnet.org/evergreen/
Molyneux, Robert E. (2009). Evergreen in Context. Bulletin of the American Society for Information Science and Technology, 35(2), 26-30.
Routt, Deidre (2008). The Open Source Task Force. Nebraska Library Association Quarterly, 39(4), 3-5.
West, Jessamyn (2009). Ten Open Source Tools. Computers in Libraries, 29(2), 44-45.
6 comments:
I think OSS is great if you have the technological savvy to work with them. My library director is considering moving to Evergreen (ILS); however, there are many features that do not currently exist in it (like serials) which would make it more problematic than the ILS we currently have. I think if you have the staff to help maintain the OSS (in terms of ILS), things will run more smoothly. I worry though about libraries with very minimal staffing and lack of tech savvy folks who want to use an OSS ILS and, it will end up costing them more money and problems in the long run!
I have heard quite a bit about OSS but never the challenges that this type of freeware can bring. The need to be quite tech savvy is one area where this may not be the best option for smaller libraries without internal tech support.
I like the quote, "free as in free kittens." Buyer beware when things say they are free as hidden costs, not just financial, will probably arise.
Thanks for the great information!
Hi Sarah,
There should be a serials module released for Evergreen in 2010. Here is the link to Evergreen's product roadmap: http://evergreen-ils.org/dokuwiki/doku.php?id=faqs:evergreen_roadmap
Ashley,
Thanks for the link! My boss will be excited to hear serials are going to be on Evergreen at some point in the near future.
This is really cool! I can see how for some libraries this could really make a difference. I would admit that I would be terrified to not have any kind of formal tech support, though. I wonder if that deters potential users?
You mention the administrative costs of open source software. We looked at some open source solutions this year, but often times the cost of the hardware required to store and run the software was offputting, or the necessary hardware or operating system (Linux, Unix, etc.) was not supported on our campus.
However, there are some great opportunities with OSS -- I'm still amazed with the Open Office suite I learned about in 6080. What a great solution for cash-strapped libraries; they can offer a full office productivity suite without any licensing costs.
Post a Comment