Enhancing Library Operations with Computerized Subsystems: Acquisition, Cataloguing, Circulation, and Serials

Walk into any modern college or university library and you will rarely see a card catalogue cabinet or a hand-written ledger at the issue counter. Behind the smooth experience of searching for a book and getting it stamped in seconds sits an Integrated Library System (ILS), a set of interlinked software modules that automate the day-to-day work of a library. These modules, often called subsystems, share a single central database so that an action in one place automatically updates records everywhere else. Four of these subsystems carry most of the load: acquisition, cataloguing, serials control, and circulation. Understanding how each one works is essential for anyone studying library automation, because together they form the operational backbone of nearly every functioning library today.

What computerized subsystems actually are 🔗

A library, regardless of size, depends on the close collaboration of three elements: the documents, the users, and the staff. The routine, repetitive tasks that keep these three connected are called housekeeping operations. Traditionally these were done by hand, which made them slow and error-prone. The spread of Information and Communication Technology led to software systems that perform these tasks faster and more accurately.

A typical ILS includes acquisition, document processing, serials control, and circulation as its core modules, alongside managerial functions like backup, configuration, and report generation. The defining feature is integration. When a new book is received in the acquisition module, that record can flow straight into cataloguing without re-entry. This shared-database design removes duplicate work and keeps information consistent across the whole system. In India, software such as SOUL (Software for University Libraries) developed by INFLIBNET and the open-source package Koha are the most widely used examples of such integrated systems.

Computerized acquisition subsystem 🔗

Acquisition is one of the basic functions of any library. A library must obtain relevant documents for its users within budgetary limits, and the acquisition subsystem performs four core operations: selection, ordering, receiving, and accessioning of documents. Computerization improves every one of these stages.

Selection and pre-order searching 🔗

The process begins with pre-order searching, which checks existing holdings and pending orders to avoid buying duplicates. In a manual system this meant flipping through registers; in an automated one, a quick database query confirms whether the title is already held or on order. Selection decisions are then recorded digitally and can be linked to specialist files of publishers, suppliers, budget heads, and currency rates.

Ordering and receiving 🔗

Once a title is approved, the system generates purchase orders automatically and tracks them against vendor records. When the material arrives, staff register its receipt, and the system can generate invoices in real time so that financial records update instantly. Because these files are maintained in machine-readable form, the same data feeds the library’s fund-accounting and reporting functions without re-typing.

Accessioning and reports 🔗

Each document received is given a unique accession number and entered into the accession register, historically one of the most important records of a library. An automated acquisition module produces a range of outputs, including outstanding-order lists, budget-utilisation statements, and vendor-performance reports. These reports give the librarian a clear, current picture of spending and pending deliveries, which would be tedious to compile by hand.

Cataloguing and system integration 🔗

Cataloguing is arguably the most critical function in a library, because it organises resources so users can find them. In traditional libraries this meant creating index cards by hand, a slow and repetitive task. Computerized cataloguing replaced those cards with structured electronic records that can be searched, shared, and reused.

MARC and UNIMARC: the language of catalogue records 🔗

For computers to exchange catalogue data, the records need a common structure. This is where MARC (Machine-Readable Cataloging) comes in. MARC was developed in the 1960s by Henriette Avram at the Library of Congress to create records that machines could read and libraries could share. By 1971 MARC had become the US national standard and two years later an international one, and several versions are now in use worldwide.

The two most prominent today are MARC 21, created in 1999 by harmonising the US and Canadian formats, and UNIMARC. UNIMARC was created by the International Federation of Library Associations and Institutions (IFLA) and is widely used in parts of Europe, where it acts as a bridge to map divergent national formats. A single MARC record is built from three elements: the record structure, the content designation (tags, indicators, and subfields), and the data content itself. The underlying record structure follows the ISO 2709 standard, which governs how the data is encoded for interchange.

OPAC: the user’s window into the catalogue 🔗

The catalogue data becomes useful to readers through the Online Public Access Catalogue (OPAC). The OPAC is the search interface where users look up titles, authors, and subjects, and see whether a copy is available or on loan. A computer-based catalogue can also export bibliographic data of its own collection to other library systems, which is what makes shared cataloguing and union catalogues possible. In India, networks such as INFLIBNET and DELNET run union catalogues that let one library reuse records created by another, saving enormous duplication of effort. Modern systems like SOUL are built to be compliant with MARC21, AACR-2, MARCXML, and the ISO-2709 data-exchange standard, ensuring their records remain interoperable.

Serials control subsystem 🔗

Periodicals, journals, and magazines behave very differently from books. They arrive in regular instalments, subscriptions must be renewed, and missing issues have to be chased. This repetitive, ongoing work makes serials an especially strong candidate for automation. As one IGNOU study material notes, the procedures related to serials control require frequent and repetitive record addition or amendment, which makes computerisation an attractive proposition.

The master database 🔗

At the heart of a serials module is a master database of serial titles and vendor information. Any addition, modification, or deletion made here is automatically reflected across all sub-modules. This reduces data-entry work and enforces standardisation, so a change made once is correct everywhere.

Subscription, check-in, and claims 🔗

The system manages the entire lifecycle of a serial: placing and renewing subscriptions, tracking payments against budget heads, and registering each issue as it arrives, often through a digital version of the traditional Kardex card. A particularly useful feature is its predictive capability. The software can anticipate when the next issue is due and automatically generate claim notices for issues that fail to arrive. It also handles binding of completed volumes and controls routing slips that circulate journals among staff. The result is fewer missed issues, tighter budget tracking, and far less manual chasing.

Circulation subsystem 🔗

The circulation subsystem is the part of the ILS that most users interact with directly. It automates the issuing and returning of documents, the calculation of fines, and the generation of activity reports.

How circulation works 🔗

A circulation system draws on three linked files: the document file from the catalogue, the borrower file from membership registration, and a transaction file that records every loan. When a member borrows a book, the system reads the borrower’s ID and the item’s barcode, checks borrowing entitlements, records the loan, and sets a due date in seconds. The same speed applies to returns and renewals.

Barcode and RFID technology 🔗

The data needed for issue and return is read using scanning devices. The bar-coded data elements can be read through a portable light-scanning device such as a barcode reader. A more recent trend is RFID (Radio Frequency Identification), where a thin chip storing bibliographic data is fixed inside each document. RFID enables self-checkout kiosks, faster stock verification, and built-in security. Indian institutions have adopted this widely; for instance, several college libraries have moved from barcode-based to RFID-based self-circulation systems running on Koha, improving both speed and security at the counter.

Fines, reports, and member cards 🔗

Overdue fines are calculated automatically based on preset rules, removing arithmetic errors and disputes. The system also produces valuable reports, and can print member ID cards carrying the member’s name, category, photo, and barcode. Other typical outputs include overdue lists, most-issued titles, and category-wise usage statistics, all of which help librarians plan collections and services.

Why integration matters 🔗

The real power of these subsystems comes from working together rather than in isolation. Because acquisition, cataloguing, serials, and circulation share one database, a single piece of data entered once flows through the whole system. This cuts duplicate effort, reduces the human errors common in manual entry, and frees staff to spend time on research help and user services instead of paperwork. Cost-effective options like the open-source Koha and the affordable, INFLIBNET-supported SOUL have made this level of automation realistic even for small and medium libraries that cannot afford expensive commercial packages.

What do you think? If your college library were upgrading its system today, which subsystem would deliver the biggest improvement for students first – a smarter OPAC for searching, or a faster RFID circulation counter? And as more resources go digital, how do you think the role of these traditional subsystems will change?

References

1. https://egyankosh.ac.in/bitstream/123456789/35927/5/Unit-2.pdf
2. https://egyankosh.ac.in/bitstream/123456789/34867/1/Unit-3.pdf
3. https://en.wikipedia.org/wiki/MARC_standards
4. https://www.librarianshipstudies.com/2017/10/marc-21.html
5. https://soul.inflibnet.ac.in/
6. https://ebooks.inflibnet.ac.in/lisp5/chapter/library-automation-circulation/