Evolution of Library Automation: From COBOL to Web-Based Systems

Walk into any modern library in India and you can search the entire collection from your phone, place a hold on a book, and check your borrowing history without speaking to a single staff member. This convenience did not appear overnight. It is the result of more than five decades of steady technological change, beginning with bulky mainframe computers running programs written in COBOL and culminating in today’s web-based and cloud-hosted systems. Understanding how library automation software evolved across distinct generations helps explain why our libraries function the way they do, and where they are heading next.

What library automation software actually does 🔗

Library automation software, commonly called a Library Management System (LMS) or Integrated Library System (ILS), is the digital backbone that handles a library’s core operations. Before computers, libraries relied on the physical card catalogue, where every book was represented by a paper card stored in long wooden drawers. Computers were first used to automate this card catalogue, which is exactly why these early programs came to be known as automation systems.

An LMS typically manages cataloguing, circulation (issue and return of books), acquisitions, serials control, and the public search interface. The story of how this software developed is best understood as a journey through four broad generations, each shaped by the computing power, programming languages, and user expectations of its time.

The four generations of library automation software 🔗

Each generation marks a clear leap in capability. The shifts were driven not only by faster hardware but also by new ways of storing data, friendlier interfaces, and the eventual arrival of the internet.

First generation: COBOL and in-house systems 🔗

The first generation emerged in the 1970s. These systems were often built using low-level languages and, very commonly, COBOL (Common Business-Oriented Language), which dominated business computing at the time. Libraries either purchased a commercial package or had software developed in-house, frequently running on large minicomputers.

These early programs automated basic functions such as circulation, acquisitions, and cataloguing. While they were a huge improvement over manual card systems in terms of speed and accuracy, they had serious limitations. According to a detailed comparison of ILS generations published through IGNOU’s eGyanKosh, first-generation systems used non-standard data formats, offered limited reporting, and were highly machine-dependent and hardware-specific. They were also isolated, meaning sharing records between libraries was extremely difficult. Users interacted through command-line interfaces, which demanded specialised training and memorisation of complex commands.

Second generation: vendor packages and richer databases 🔗

By the 1980s, the second generation arrived alongside the spread of affordable personal computers. Programming expanded beyond COBOL to include languages like PASCAL and C, and systems began running on vendor-specific operating systems. The data models used were typically hierarchical and network models, which allowed somewhat better organisation than the rigid formats of the first generation.

This was also the era when the Online Public Access Catalogue (OPAC) took root. The introduction of OPAC modules in the late 1970s and early 1980s marked the transition from single-purpose circulation systems to genuinely integrated library systems. Patrons could now search the catalogue from a computer terminal instead of flipping through card drawers, though the experience was still menu or command driven and far from intuitive.

Third generation: relational databases and graphical interfaces 🔗

The third generation represents one of the most important turning points in this history, and we will examine it closely in the next section. In short, this generation embraced relational database management systems (RDBMS) and graphical user interfaces, moving library software away from cryptic text commands toward point-and-click operation built on client-server architecture.

Fourth generation: web-based and open-source systems 🔗

The fourth generation is defined by the web. As telecommunication and the World Wide Web matured through the 1990s and 2000s, vendors built systems accessible through ordinary web browsers. Many adopted the Z39.50 standard and created web-based catalogues, which brought uniformity to how different library interfaces handled searching, Boolean operators, and result display. The MARC format was even extended with an Electronic Location and Access field to hold the URL of a digital resource, linking a catalogue record directly to online content.

This generation also saw the rise of powerful open-source software. Koha, the first open-source ILS, was originally developed in New Zealand in 1999 and is now used worldwide. It supports MARC21 cataloguing, the Z39.50 protocol, a web-based OPAC, and multi-branch operations, all without licensing fees.

The development timeline: from the 1970s to today 🔗

Placing these generations on a timeline makes the pace of change clearer. The groundwork was actually laid in the 1960s, when Henriette Avram developed Machine-Readable Cataloging (MARC) at the Library of Congress, and Frederick Kilgour began building an online searchable database for Ohio State University in 1967. The first public-facing OPAC that patrons could search by title, author, or call number was unveiled at Ohio State University in 1975.

The 1970s saw integrated automation packages enter libraries, with minicomputers handling circulation, acquisition, cataloguing, and serials. The 1980s brought cheaper PCs within reach of libraries, expanding adoption dramatically. The 1990s were transformative: the arrival of graphical user interfaces, particularly Windows, had a profound effect, and vendors quickly converted their character-based mainframe systems into Windows-based GUI systems using client-server architecture. Users no longer had to memorise long commands to find and view bibliographic records.

In the Indian context, library automation began in a few special libraries in the late 1970s and gradually spread to university, college, and school libraries. Software packages such as Libsys, SLIM++, and SOUL became familiar names, travelling across operating environments from DOS and UNIX to Windows, LINUX, and finally the web.

The transition to relational databases and GUI 🔗

The single most consequential technical shift in this evolution was the move to relational databases. Earlier systems stored data in rigid, proprietary formats or in hierarchical models that made complex searching awkward. Relational databases, which allow large amounts of data to be stored so that common queries run efficiently, changed everything.

In a relational system, bibliographic information is organised into tables that can be linked through shared fields. This means a single author record can connect to many book records, and a library can run sophisticated queries such as finding every title on a subject published after a certain year, instantly. This flexibility and scalability let third and fourth-generation systems handle vastly larger collections than their predecessors. Modern systems commonly run on RDBMS platforms like MySQL, MariaDB, Oracle, or MS-SQL.

How GUI changed the everyday experience 🔗

Running parallel to the database revolution was the shift from command-line interfaces to graphical user interfaces. First and second-generation systems forced both librarians and patrons to learn specific commands and syntax. A GUI replaced this with menus, buttons, and forms that anyone could navigate after minimal instruction. This lowered the training burden enormously and opened library catalogues to ordinary users who had no technical background.

SOUL: a case study from India 🔗

The Indian experience captures this transition neatly. The INFLIBNET Centre first developed an Integrated Library Management Software with both DOS and UNIX versions for university libraries. But with the arrival of GUI-based systems, INFLIBNET decided to build a modern, user-friendly, Windows-based product. The result was SOUL (Software for University Libraries), designed to run in a client-server environment and compliant with international bibliographic, networking, and circulation standards.

SOUL has tracked the broader technological timeline closely. SOUL 2.0 launched in January 2009, and the most recent version, SOUL 3.0, was released in February 2021. The current version is compatible with modern relational databases such as MS-SQL and MySQL. Although the name suggests it is meant only for universities, it is flexible enough to automate any type or size of library, and it remains one of the most widely deployed library packages in the country, serving thousands of institutions. Alongside SOUL, open-source Koha and the government-supported e-Granthalaya have become popular choices, reflecting the fourth-generation preference for web-based, standards-compliant systems.

Where the journey is heading 🔗

The trajectory from isolated COBOL programs to interconnected web platforms shows a consistent direction: systems have become more open, more user-friendly, and more capable of sharing data. Today’s emerging systems are moving toward cloud hosting and library services platforms that manage both print and electronic resources in a single interface. Features once considered futuristic, such as automated recommendations and analytics, are gradually being built into mainstream products.

For students of Library and Information Science, this history is more than a sequence of dates. It demonstrates how each generation solved the specific limitations of the one before it, and it equips you to evaluate the software a library uses today against the standards and needs of tomorrow.

What do you think? If you were advising a small college library setting up automation for the first time, would you choose a well-established commercial package or a free open-source system like Koha, and why? Looking ahead, which capability do you believe the next generation of library software should prioritise above all others?

References

1. https://en.wikipedia.org/wiki/Integrated_library_system
2. https://socialsci.libretexts.org/Courses/Sacramento_City_College/LIBT_300:_Introduction_to_Library_Services_(Li)/01:_Technical_Services_and_Infrastructures/1.02:_New_Page
3. https://egyankosh.ac.in/bitstream/123456789/35928/5/Unit-3.pdf
4. https://ebooks.inflibnet.ac.in/lisp5/chapter/library-automation-library-automation-definition-need-purpose-and-advantages/
5. https://www.encyclopedia.com/media/encyclopedias-almanacs-transcripts-and-maps/library-automation
6. https://en.wikipedia.org/wiki/Koha_(software)
7. https://study.com/academy/lesson/online-public-access-catalog-definition-usage.html
8. https://wolframalpha.com/docs/timeline/computable-knowledge-history-6.html