1 Introduction

 

Learning Objectives

  • To understand the role of technology in libraries
  • To understand the background and history of Open Source Technology
  • To understand the unique role of Open Source Technology in libraries

Introduction

Technology touches almost every part of a patron’s experience of a library. The simple act of finding resources is just the surface level activity above a vast network of technology both library-specific and general. Understanding how the various technologies converge to the library and its services and how those technologies and services are affected by Open Source Software will greatly help librarians troubleshoot problems, plan for the future, and serve their patrons.

 Focus Questions

  1. As you read the following chapter, think about what technology you have taken for granted.
  2. In what ways does the Open Source movement and library science goals match? In what ways do they resemble each other?
  3. How successful has open-source software been for libraries? In what ways does it succeed and in what ways does it still need to develop?

Section 1: Technology in Libraries

Section Summary

This section talks about the history of technology in libraries and how that history informs the current state of libraries in general.

Library Technology History

Libraries, from their earliest inceptions, have always used the technology available to get information to their patrons. Sometimes that technology took the form of processes and organizations, but starting in the 1960s, the concept of computers as a part of library technology emerged [1]. In 1965, the Library of Congress released a report that “concluded that in bibliographic processing, catalog searching, and document retrieval was technically and economically feasible”[2].  What was needed still were systems designed for libraries, and for libraries to have their data in formats easily machine-readable. From this need emerged the standard. The format was designed to not only be read by a computer but also shareable so that many libraries could get the benefit of one library’s cataloging work.  The creation of a sharable standard meant that a central repository of cataloging could be maintained, and that made the , a non-profit organization whose mission is to make the technological cost of libraries lower,  possible. As technology advanced, libraries were able to connect their resources using a network, and in 1971 the Alden Library at Ohio University became the first to do online cataloging [3].

This is a theme that will reoccur. Technology not only lets new and interesting things happen but in the case of software and data, it allows cooperation. It allows many organizations to benefit from the work of a few.

This caused librarians to realize the potential of , which is the act of converting a physical item into an electronic or digital item. In the 1980s, the library of congress started their American Memory pilot project, with the goal of making “5 million items accessible electronically to the nation by the year 2000” [4]. If cataloging could be made more efficient with technology and shared resources, so could books and other items. Also around this time libraries developed the , which allowed patrons to search the catalog easier and faster using text-based searching.

In the ’90s, the idea of a library website as a portal to the library’s services and resources was starting to take form. CD-ROMS were being sold with , and those developed into the databases that libraries subscribe to today.

The 2000s have been marked by rapid growth in internet technologies, computer languages, and other tools that have helped libraries change rapidly. Caught in the middle of this change are library staff who have to balance traditional tasks and goals with a rapidly changing information environment.

Most modern libraries have a strong foundation of library technology. Most of the technologies that the library science world focused on for the past 60 years are now so commonplace as to be nearly invisible to patrons.  Computers are expected. On those computers, patrons expect the internet. They expect to be able to search and find resources from around the world easily.  This seamless experience for the patron comes at a technological cost for the library.  Efforts must be made to break down barriers and create seamless experiences. Library employees are hired to work with vendors or to maintain servers and software, prevent downtime, and upgrade as new and better technologies are developed.  The traditional focus of the librarian as an organizer of information has shifted to include organizer and maintainer of information systems. Many new job postings require applicants to stay abreast of future trends, and many are looking for librarians who can be relied on to do the work those future trends require.

The challenge to new librarians is quickly developing the technology competencies that they will need in their future jobs to be flexible [5].

In addition to that, Librarians are at the forefront of spreading digital fluency, fighting for user-centric design, fighting for patron privacy in a world of large companies that sell user’s data. Librarians are at the crossroads where technology and evolving information landscapes converge. It is vital that librarians, in whatever capacity they can, to be well versed in how the technology works and interacts with both patrons and library and information policy. Practice and experimentation are two great ways to become familiar with these concepts.  The Open Source Movement provides a backdrop on which librarian practice and experimentation can happen.

Reflection Exercise

Think back on the last time you visited a library in person and the technology that was present that you may have taken for granted. Did you walk through an alarm system that would go off if someone stole a book? Did the circulation desk have barcode scanners? Does the library have a self-checkout machine? How many other patrons were there using the computers for something other than looking up books in a catalog? Were other patrons charging their phones? What technology education opportunities did the library provide? What services and events would be impossible if the electricity went out because of an emergency?

Section 2: The Open Source Movement

Section Summary

In this section, the core aspects of what open source software is and why it exists will be discussed.

Open vs Free

Before talking about the movement it is important to understand the difference between the words “open” and “free”. They are not interchangeable when it comes to . Open means that people are allowed to see the and edit it, but it doesn’t necessarily mean that the software is free. A good example of this is the operating system Linux. While the software is open, and you can get a version of it for free, some companies have developed their own versions of the software that you have to pay to get. Free software, on the other hand, might be available at no cost but the code isn’t open so it can’t be edited and re-used. Some people talk about free software and what they mean is software that is both open and free from cost to use. When software is not free from costs, and it is not open, it is called . Companies are usually disinclined to allow other people to see their source code, let alone edit it.

Some people feel that software should be free speech and they feel locking it down or making it proprietary is ethically wrong.  Those people belong to the which started in the early ’80s. The free here stands for both free from costs and open to be edited and remixed. The was a branch of the Free Software Movement and consisted of people who believed that proprietary software was fine but still wanted to advocate for open options.

The Open Source Movement is about creating software that allows anyone to edit, remix, or reuse all or part of the software.  The movement has more to do with licensing, permissions, and organization of than it does the actual programming. In much the same way as allows creators and authors to expand on copyright to allow for different uses, the Open Source Movement has recommended licensing for software projects to allow people the legal permissions to edit software [6].  The licenses used are typically the , but there are other free software licenses out there [7]. The foundation of the license is that the software is free to be used for any purpose, to be changed for your needs, the freedom to be shared, and the freedom to share your changes. Software created with Open Source or free licensing is known as .

A lot of the benefits that libraries found for shared cataloging can also be found in OSS. A few developers can create software that the whole community can use, and if someone wants a new feature they can program it and release it back to the community. Just like how OCLC came about to organize all this shared cataloging, organizations developed to organize shared OSS programming projects.  is a very popular software organization platform that provides some features for free and some for a fee. GitHub is based on and uses the standard which is used for of source code. Git itself is a OSS. Because OSS software is open, it can usually be run for low cost or free, but this is not always the case. The openness of OSS software projects also means that there is potential for a diverse developer community which means many different developers can look at the same code and see different ways to fix problems. It also means there’s the opportunity to be more flexible than other software because anyone can submit changes.

Wikipedia: An Example

The Open Source Movement, and the communities within in, are developing and figuring out how better to run projects and maintain documentation.  A great example is Wikipedia. Wikipedia is an online encyclopedia that launched in 2001, and is run off of the software Mediawiki [8] which is an OSS, which means it was developed and is currently maintained by developers from around the world and from many different backgrounds. This has resulted in a well maintained and secure software that is used for projects even outside of Wikipedia. Mediawiki is a good example of how OSS can work well within an open-source environment. Some librarians have taken up Wikipedia as a tool to help people find reliable and open information and have created library programming to help librarians understand how to use it [9]. Librarians do this because patrons often go to Wikipedia first when formulating their search strategy when they are looking up terms to use in a library system search [10]. This is an example of how an OSS outside of libraries can affect librarians and library patron search behavior.

Reflection Exercise

Have you used Wikipedia in the last week? Were you aware that it was an open-source software project developed by both paid and volunteer developers? Do you have an android phone? Have you ever used the Firefox internet browser? Have you ever had a WordPress website or blog? The internet itself is based on open-source software like Apache, MySQL, PHP, and JAVA.  These are all examples of open source software that you might have used without really thinking about where the software came from or whether you could access and edit the source code.

Section 3: Open Source Technology in Libraries

Section Summary

This section is an overview of open source technology in libraries and the potential benefits it has for librarians.

Open Source Technology in Libraries

“The principles and practices of open source software are very similar to the principles and practices of modern librarianship. Both value-free and equal access to data, information, and knowledge. Both value the peer review process. Both advocate open standards. Both strive to promote human [understanding] and to make our lives better. Both make efforts to improve society as a whole assuming the sum is greater than the parts.”

– Eric Lease Morgan [11]

There is an abundance of open-source software for use in libraries. This ranges from common technology that everyone shares, to specific library technology developed for a specific purpose.

Libraries are moving towards open-source software for a variety of reasons [12]. Some libraries see open-source software to control the “speed and direction of their library migrations”, or to have modern functionalities in systems that were more recently created with newer technologies in mind. Some libraries have moved to open source software so that they could own and maintain the data of their systems. In proprietary systems, this data is sometimes owned by the company. Some libraries move to OSS because it is more flexible and changeable for their local developers to make it work the way they want. Other libraries have moved to OSS because of how closely OSS matches with the library profession in general like in the quote at the beginning of this section.

Other libraries specifically avoid OSS because they are concerned about legal issues or having no control about the external development of the software. Maybe they worry it’s not as safe as proprietary software [13]. Or perhaps they are dubious of the idea that the software might be cheaper than proprietary software. Others avoid it because OSS software often doesn’t have the professional look that proprietary software have, and that patrons are expecting. Other libraries don’t like the do-it-yourself nature of OSS, and prefer to have a company to call for problems and feature requests.

 

There are levels of technology, as well as levels of technology adoption and there are benefits for librarians at all levels. The adoption of an open-source Integrated Library System (ILS) is a massive undertaking that may not fit all institutions. More approachable is the idea of providing open-source software to patrons on the computers they use.  Even more approachable is the single librarian toying around with open source software to get experience and try new things without ever having to bring the software to the public or request software to be purchased.

Within the realm of public-facing software, there are also levels of involvement. A library can use open source software that functions in almost every way like proprietary software by hiring a company to run and maintain the software for them. Or, libraries can join that run OSS as a part of the member benefits, so that the group gets the benefits of the software and the benefits of the built-in . On the other end of the spectrum, the library can hire staff to maintain the software and the servers . The aspects that go into this choice will be discussed in Chapter 3: Moving to Open Source Software.

The Dilemma of Collective Action and the 2.5% Proposal

In February of 2017 John Wenzler wrote about the dilemma of collective action which is that for libraries to reap the benefits and savings of new technologies, it requires a level of coordination that is impossible no matter how obvious the benefits are [14]. It is difficult for libraries to argue that money or time should be diverted away from local needs, which hinders their abilities to work toward collective action.  OSS, however, is an example of how the “dilemma of collective action” can be overcome, at least in specific circumstances. In a perfect world, libraries that could develop would group together to develop the perfect library software that other libraries would use.  They would all choose one project and put all their efforts on it, make it work for the whole community, and make it as cheap and easy to run as possible.  To support this, David Lewis wrote a response that suggests every academic library put 2.5% of their budget toward the development of open-source software to create a common infrastructure [15]. It remains to be seen if this approach is the best solution for libraries, but it does show that open source software still holds some potential to be a conduit for change in the library world.

Why Librarians Should play with Open Source Software

With most technologies librarians interact with, especially software, it can be like a black box. You provide some input or a command, and something happens inside the box and a result comes out.  OSS, on the other hand, can be pulled apart and examined. Looked at through a microscope and studied. The algorithms at play can be inspected for bias, or you can simply try it out without having to contact an IT person. For library science students, open-source software provides a playground for getting experience in parts of systems that are normally locked away such as the back end of library systems.

Even if you never program a single line of code, knowing how a system works and how the development of OSS works, can better prepare you for writing documentation, coordinating with IT staff, and maybe running other kinds of projects.

When you look at a problem in your daily work, and you realize you might have a need for software, just knowing that there is free and open software you can dip into is an incredible boon.  The library employee that can look at a problem and quickly download and run software to solve it is a valuable employee that can fill in technological gaps in a library workforce. When you see a metadata problem, you see a data problem, and you can pull out tools like OpenRefine (an open-source desktop application for data cleanup and transformation). You have a patron with a need to convert an audio file, but your library doesn’t have the software. You know you can go get Audacity (which is a OSS platform for audio manipulation and editing). Maybe someone wants to have a knowledge base for their work, and you know how to run and maintain Mediawiki. Maybe your team wants to create a mind map but there’s no budget for software, you can get Freemind installed on everyone’s computer without a single penny. Maybe you have been put in charge of a large project for the first time, and you find GanttPV (an open-source project management tool). Maybe you need to create a website from scratch, and you know to look for Drupal (an open-source website management software). The examples could go on, but in general, if you find a piece of software you need you can usually find OSS versions to play with.

Build a Tool Box of Open Source Software

In my entire career, I’ve found multiple times where I was able to dip into OSS to complete a task quickly where another employee would have had to do it by hand. I once had to re-name hundreds of files, and I was able to download Ant Renamer and do the work in a few minutes instead of weeks. Other times I’ve had to edit metadata and I’ve used OpenRefine to do what MS Excel couldn’t. I’ve used MediaWiki, and open-source server software to run projects and prototype ideas without having to spend a dime.

If anything, for me, OSS brings a certain freedom to experiment without having to worry about cost. If it’s a software I can download to a computer, I can play with it.

I think it’s important for every modern librarian to develop a toolbox of OSS that they are familiar with that they can bring to various library problems.

This book will introduce you to various OSS projects, explain how to manage the adoption of OSS in libraries, and talk about further contributing to the OSS community, and how to develop your own developer skills.

Reflection Exercise

Of the examples of OSS projects listed, did any of them pique your interest? Dive further by looking into the software that you thought was most interesting and look at the features available. Does knowing that these software projects support the open exchange of ideas make you feel differently about them? Do you think libraries should be using at least some OSS? What do you think are the barriers to libraries using OSS besides the ones listed in this section?

Review Focus Questions

  1. As you read the following chapter, think about what technology you have taken for granted.

 

Did you find yourself thinking more about the technology you use day to day while reading this chapter? Has any of the knowledge changed the way you feel about the software on your computer, your phone, or on the computers at your local library?

 

  1. In what ways does the Open Source movement and library science goals match? In what ways do they resemble each other?

 

The quote at the beginning of section 3 does a great job of summarizing how OSS and libraries share common goals.  Are there any other ways that they are similar? Do you think there are ways that each community could support the other?

 

  1. How successful has open-source software been for libraries? In what ways does it succeed and in what ways does it still need to develop?

This will be discussed more in the next chapter, so if you don’t have a clear view of this yet that is ok. Maybe you understand that some OSS software is difficult to implement while others are easy. This question is one we will return to at the end of chapter 2.

Chapter Summary

In this chapter, we went through a short review of the history of technology in libraries so that we could gain context of how open-source software may fit in. It then discussed the Open Source Software Movement and the reasons and motivations for the movement to have started. It then talked about how Open Source Software has potential for libraries and librarians.


  1. https://www.ifla.org/files/assets/information-technology/publications/40-years-of-its.pdf
  2. https://web.archive.org/web/20140305103046/https://blogs.loc.gov/loc/2014/01/a-half-century-of-library-computing/
  3. https://web.archive.org/web/20121004135231/http://www.oclc.org/us/en/about/history/beginning.htm
  4. https://web.archive.org/web/20140305103046/https://blogs.loc.gov/loc/2014/01/a-half-century-of-library-computing/
  5. https://www.sciencedirect.com/sdfe/pdf/download/eid/1-s2.0-S0099133318301848/first-page-pdf
  6. https://www.gnu.org/licenses/licenses.html
  7. https://www.gnu.org/licenses/licenses.html
  8. https://www.mediawiki.org/wiki/MediaWiki
  9. https://meta.wikimedia.org/wiki/The_Wikipedia_Library/1Lib1Ref
  10. http://www.washington.edu/news/2010/03/18/uw-study-finds-wikipedia-first-stop-for-many-student-researchers/
  11. http://infomotions.com/musings/biblioacid/
  12. https://timreview.ca/article/177
  13. https://timreview.ca/article/177
  14. https://crl.acrl.org/index.php/crl/article/view/16581
  15. http://hdl.handle.net/1805/14063

License

Icon for the Creative Commons Attribution 4.0 International License

Open Source Software in Libraries by Joy Perrin is licensed under a Creative Commons Attribution 4.0 International License, except where otherwise noted.

Share This Book

Feedback/Errata

Leave a Reply

Your email address will not be published. Required fields are marked *