Page 51 - DLIS007_LIBRARY AUTOMATION

Library Automation

Notes 1. Authority Control: The LMS must be capable of incorporating the following features:
Support for MARC authority format for personal, corporate and topical name
headings in a name authority file; title, uniform title and series entries in a title
authority file, and subject headings in a subject authority file;
Provision for generation of SEE, SEE ALSO references and Narrow Term-Broad
Term-Related Term relationships network from authority records and link these
references to matching access points in OPAC;
Must allow any bibliographic field to be authority controlled, and include facilities
to search, retrieve, and display print and global editing of authority records by
authorised operators; and

Must include provision for multiple thesauri with the ability to produce a list of all
citations with authority file violations.
2. Bibliographic Control: The master bibliographic record of the LMS should extend support
for:
MARC 21 (Machine-Readable Cataloguing) bibliographic and authority record
formats;
MARC record loader that can accept records input from various sources and from
various media like tape, diskette or over network;

Global editing utility that can find and replace data within specified fields;
Data format validation during input of bibliographic information;
MARC 21 format for holding and display of holding on the basis of ANSI Z39.44
serials holdings display format;
Import and export of bibliographic data through Z39.50 compliant catalogue;
Interoperability and crosswalk through incorporation of XML, RDF and metadata
schemas (e.g. Dublin Core Metadata).
3. Online Public Access Catalogue (OPAC): Following are the features of OPAC:
OPAC must be fully integrated with other modules and accessible through web-
based client;
OPAC should provide browse indexes for author, title, and series and browse index
combining all four indexes;

It should allow combined, specific and field level searching for all formats along
with phrase searching, nested searching and truncated searching;
It must enable searching by using Boolean operators (OR, XOR, NOT, AND),
positional operators (SAME, WITH, NEAR, ADJ) and relational operators (‘greater
than’, ‘less than’, ‘equal to’, etc.) within and across all fields;

It should provide facility to see processing status (fully catalogued, in process, lost,
withdrawn etc.) and circulation status (in transit, reserve, recalled, on-hold etc.);

OPAC should support full, brief, standard and customised display of records including
relevancy ranking of search results;
OPAC should also support bulletin board, information desk and gateway services
(to access external databases) along with patron self-service options (e.g. holds,
renewals etc.);

46 LOVELY PROFESSIONAL UNIVERSITY