Historical addressCatalogue Software for Church Libraries

Think of the setup as an enterprise resource planning system designed for libraries. It tracks items owned by the library, orders placed, invoices paid, and patrons who have borrowed materials. For you, that means the VBS kit on the closet shelf, the replacement workbook you ordered, the invoice from the supplier, and the volunteer who borrowed the box last summer can belong to the same record family. The wider definition also uses another name for the same idea, a library management system, and both names point to one database rather than four notebooks.

The design is typically composed of three components. There is a relational database, software for interacting with that database, and two graphical user interfaces, one for patrons and one for staff. In parish terms, your volunteers work on the staff side when they check a kit in or fix a title entry, while teachers and parents would use the patron side to look up what is available. You see different screens, but you work from the same data. If you already keep cataloging basics for congregational shelves in a separate file, this is the point where that file stops standing alone.

Most systems separate software functions into discrete programs, known as modules, with each module integrated with a unified interface. That split lets a small team learn one task at a time without losing the link to the rest. You open the piece you need, and the unified interface keeps the title, the order, and the loan connected behind it. The five examples named on the integrated system for libraries page show how the work divides, and each one maps to a job you already do by hand.

Acquisitions covers ordering, receiving, and invoicing materials. Cataloging covers classifying and indexing materials. Circulation covers lending materials to patrons and receiving them back. Serials covers tracking magazine, journal, and newspaper holdings. The online public access catalog, or OPAC, is the public user interface. If you translate that to a parish shelf, acquisitions holds the order and the invoice for a new Bible study set, cataloging holds the classification that puts it on the right shelf, circulation holds the loan and the return, serials holds the run of a quarterly devotional, and the OPAC is what a volunteer checks on Sunday morning.

Each patron and each item have a unique ID in the database that allows the system to track their activity. That ID is what ties a borrower to a specific copy and to a specific loan period. You do not rely on memory or on a name scribbled inside a cover. You scan or type two IDs, one for the person and one for the copy, and the database keeps the link. When the same Advent kit goes out to three households across three seasons, the copy keeps its identity while the borrower IDs change around it.

Prior to computerization, library tasks were performed manually and independently of one another. Selectors ordered materials with ordering slips, catalogers manually cataloged sources and indexed them with the card catalog system, in which all bibliographic data was kept on a single index card, fines were collected by local bailiffs, and users signed books out manually, indicating their name on clue cards, which were then kept at the circulation desk. Your parish version of that stage is familiar. One person keeps order slips in a drawer, another types a title list, and a third keeps a sign-out sheet on a clipboard. Early mechanization came in 1936, when the University of Texas began using a punch card system to manage library circulation. While the punch card system allowed for more efficient tracking of loans, library services were far from being integrated, and no other library task was affected by this change.

The next big innovation came with the advent of MARC standards in the 1960s, which coincided with the growth of computer technology. From this point onward, libraries began experimenting with computers, and, starting in the late 1960s and continuing into the 1970s, bibliographic services utilizing new online technology and the shared MARC vocabulary entered the market. These included OCLC from 1967, Research Libraries Group, which has since merged with OCLC, and the Washington Library Network, which became Western Library Network and is also now part of OCLC. For a small congregation, the practical point is shared vocabulary. When libraries describe titles the same way, you can copy a reliable record instead of typing every field yourself. An experimental project from the same period shows how new the idea was. The Intrex Retrieval System ran on CTSS starting in the late 1960s as an experimental, pilot model machine-oriented bibliographic storage and retrieval system with a database that stored a catalog of roughly 15,000 journal articles. It was used to develop and test concepts for library automation. A deployment of three Intrex BRISC CRT consoles for testing at the MIT Engineering Library in 1972 showed that it was preferred over two other systems, ARDS and DATEL.

The 1970s can be characterized by improvements in computer storage, as well as in telecommunications. As a result of these advances, turnkey systems on microcomputers, known more commonly as integrated library management systems, finally appeared. These systems included necessary hardware and software that allowed the connection of major circulation tasks, including circulation control and overdue notices. As the technology developed, other library tasks could be accomplished as well, including acquisition, cataloging, reservation of titles, and monitoring of serials. If you lend kits between Sundays, the reservation of titles is the piece to notice. It lets a teacher claim the next use of a Lenten set while the current borrower still has it, and the overdue notice gives you a plain way to ask for it back.

With the evolution of the Internet throughout the 1990s and into the 2000s, systems began allowing users to more actively engage with their libraries through OPACs and online web-based portals. Users could log into their library accounts to reserve or renew books, as well as authenticate themselves for access to library-subscribed online databases. Education for librarians responded with a new focus on systems analysis. During this time, the market grew exponentially. By 2002, the industry averaged sales of approximately 500 million US dollars annually, compared to just 50 million US dollars in 1982. Your volunteers feel the same shift on a smaller scale when they move from a paper sign-out sheet to an account where a borrower can renew a study without calling the church office.

By the mid- to late 2000s, vendors had increased not only the number of services offered but also their prices, leading to some dissatisfaction among many smaller libraries. At the same time, open-source tools were in early stages of testing. Some libraries began turning to such open-source options as Koha and Evergreen. Common reasons noted were to avoid vendor lock-in, avoid license fees, and participate in software development. Freedom from vendors also allowed libraries to prioritize needs according to urgency, as opposed to what their vendor can offer. Libraries that moved to open-source tools found that vendors were now more likely to provide quality service in order to continue a partnership since they no longer had the power of owning the software and tying down libraries to strict contracts. One named case is the SCLENDS consortium. Following the success of Evergreen for the Georgia PINES library consortium, the South Carolina State Library along with some local public libraries formed the SCLENDS consortium in order to share resources and to take advantage of the open-source nature of the Evergreen system to meet their specific needs. By October 2011, just two years after SCLENDS began operations, 13 public library systems across 15 counties had already joined the consortium, in addition to the South Carolina State Library. A survey series from Librarytechnology.org, which polls over 2,400 libraries each year, put open-source use at 2 percent in 2008, 8 percent in 2009, 12 percent in 2010, 11 percent in 2011, and 14 percent in the survey published in April 2013. That 2013 report noted 113 support contracts for open-source systems out of 794 contracts in the public and academic arena.

Library computer systems tend to fall into two categories of software, those purchased on a perpetual license and those purchased as a subscription service. With distributed software, the customer can choose to self-install or to have the system installed by the vendor on its own hardware. The customer can be responsible for the operation and maintenance of the application and the data, or the customer can choose to be supported by the vendor with an annual maintenance contract. Some vendors charge for upgrades to the software. Customers who subscribe to a web-hosted service upload data to the vendor's remote server through the Internet and may pay a periodic fee to access their data. Cloud-based library management systems have increased drastically since the rise of cloud technology started. The cited NIST description says cloud computing can include characteristics such as self-service, resource pooling, and elasticity, management models such as service, platform, or infrastructure focus, and deployment models such as public or private, and the same range applies to cloud-based library systems. Compare that choice with how congregations lend ministry kits to each other before you decide where your borrower list should live.

Many applications can reduce a major portion of manual data entry by populating data fields based on the entered ISBN using MARC standards technology via the Internet. With most software, users can eliminate some manual entry by using a barcode scanner. Some software is designed, or can be extended with an additional module, to integrate scanner functionality. Most software vendors provide some type of scanner integration, and some print barcode labels. On a parish shelf, that means you type the ISBN from the back of a study guide once, accept the title and edition fields that fill in, then stick a barcode inside the front cover and scan it at checkout. The named open examples use the same building blocks. Koha from the Koha Community dates to 2000 with a stable release in 2024, written in Perl for ILS use under GPL 3.0 or later. PMB from the PMB development team dates to 2002 with a stable release in 2024, written in PHP for ILS use under CECILL 2.0. NewGenLib from Verus Solutions dates to 2005 with a stable release in 2024.

Pick a study that circulates well and follow its paper trail for one full cycle. Find the acquisitions entry that shows the order and the invoice, open the cataloging entry that shows the classification, then open the circulation history that shows each borrower ID linked to that copy. Note where serials would sit if the resource were a periodical rather than a single kit, and ask a volunteer to find the same copy through the OPAC without help.