The microcomputer in the library: VI. Implementation and future development
| Published date | 01 June 1986 |
| Pages | 332-343 |
| DOI | https://doi.org/10.1108/eb044722 |
| Date | 01 June 1986 |
| Author | Peter Leggate,Hilary Dyer |
| Subject Matter | Information & knowledge management,Library & information science |
ARTICLES
The
microcomputer in
the
library:
VI.
Implementation and
future development
PETER
LEGGATE
Regional Librarian
Oxford Regional
Health
Authority
Cairns Library
John Radcliffe
Hospital
Oxford
HILARY
DYER
Lecturer
Department
of Library
and
Information Studies
Loughborough University
Loughborough
Leicestershire
Abstract: After
selecting hardware
and
software,
consideration needs
to be
given to
their
installation.
This
includes
any necessary
cabling and
the design of
the
vdu workstation(s) for staff
well-being.
Important decisions also need to be
made about data
security.
The software may need to be tailored to meet library
requirements
and staff and
readers trained
in
its
use.
Automation changes
the
nature
of a job and
consequently
will have an
impact on
job
design
and on
library
procedures.
These
effects,
as well as the
software
itself,
need to be
evaluated after
the system has been
operating for
some
time,
both with a view to
improving the existing system
and considering possible future
developments.
Introduction
T
he previous five articles in this
series have offered an introduction
to microcomputer hardware and
operating systems and to the main
characteristics of software for
library applications. The objective has been
to provide some guidance to the librarian in
choosing a microcomputer system.
1.
Choice of system
The first step on the road to automation
is
the
same for all libraries, whether they require
the simplest single-user micro or a 100-
terminal mini: the functions which need
automating must be defined. Restrictions on
choice must also be noted, e.g. funding avail-
able,
the need for software to run on a
machine already installed in the library.
Needs and resources must then be matched
against available packages with regard to
function, capacity and price. To do this, the
librarian must decide the questions to be
asked:
— does the machine have the capacity to
store, sort and index a file of 20,000
records with an average length of 250
characters?
— may all fields in the catalogue be searched
for complete words, word stems, or com-
binations of words anded together?
— will the system produce letters reminding
readers of overdue loans?
— can the wording of these letters be
changed at the discretion of the librarian?
—■
how easily can such changes be made?
— is the vdu display easy to read?
— and so on
It is hoped that these articles will help the
librarian to decide which questions to ask —
and whether the answers given by suppliers
make sense.
The more complex are a library's require-
ments, the more questions will need to be
asked, but the less certain will be the choice
of the system. If
a
multi-functional package
is sought, no one system will be the 'best' for
all the functions to be performed. For
example, a package with an excellent
catalogue search module may not offer a
sufficient number of fields for the catalogue
record, or may have inadequate budgeting
facilities in an acquisitions module. The
librarian must, therefore, devote time to
identifying the really important questions.
What features are essential? What de-
ficiencies are unacceptable? It remains a
difficult task to choose between competing
packages on the basis of demonstrations by
the supplier or in someone else's library. As
an alternative, some suppliers offer 'samples'
of their software, usually restricted by the
number of records that can be handled, to
allow evaluation in-house. The cost of such
samples is usually low
(c £50)
and can usually
be credited against the price of the full
package if it is purchased. If a library has a
machine on which sample software can be
run, full advantage should be taken of such
offers.
2.
Planning for implementation
Once hardware and software have been
chosen — and even before — attention must
be turned to planning for the implementation
of the configuration in the library. After
fighting to get the necessary funding,
trudging round exhibitions and other
people's libraries, fending off over-
enthusiastic salespeople, and evaluating
options which do not provide the basis for
clear-cut decisions, the librarian may be
forgiven for wishing to forget the whole
business for the few weeks before the equip-
ment arrives. Nevertheless, successful intro-
duction of an automated system requires
planning for its implementation. The factors
to be considered include:
1.
installation of equipment
2.
workstation design and location
3.
scheduling of software implementation
332 The Electronic Library, December 1986.
Vol.
4, No. 6.
To continue reading
Request your trial