Planning for Integrated Systems and Technologies: A How‐to‐Do‐it Manual for Librarians (2nd rev. ed.)

Richard Biddiscombe (Team Leader for Arts, Social Sciences and Law, Information Services, University of Birmingham, UK)

Program: electronic library and information systems

ISSN: 0033-0337

Article publication date: 1 March 2003

84

Keywords

Citation

Biddiscombe, R. (2003), "Planning for Integrated Systems and Technologies: A How‐to‐Do‐it Manual for Librarians (2nd rev. ed.)", Program: electronic library and information systems, Vol. 37 No. 1, pp. 59-60. https://doi.org/10.1108/00330330310460608

Publisher

:

Emerald Group Publishing Limited

Copyright © 2003, MCB UP Limited


The preface of this “hands‐on” book says it is aimed at the working librarian in a small or medium‐sized library who is “planning for the introduction of an integrated library system or migrating from an existing system to a new one”. It goes on to say that the book is designed “to be current, useful and simple to use” while claiming to provide practical advice on planning for the evolution of integrated systems that are now enabled to access the World Wide Web. It promises to outline changes in technology, system migration and possibilities such as the “application service provider” model.

At this introductory stage therefore I thought I understood what the book was about, but further delving proved me wrong. I had always understood an “integrated library system” to be about circulation systems, interlibrary loans automation and book and periodical ordering as well as cataloguing. Alas, either I have been wrong in my assumption or the book has a misleading title, for it restricts itself solely to the problems of cataloguing systems. A third of the book is taken up by issues such as retrospective conversion, barcoding, and MARC and other standards. There is no reference to other processes or library services. Some way into the book a brief justification is given: “Throughout this book, we use the phrase ‘integrated library system’. Some think ‘integrated’ implies completeness – that today’s systems offer everything that a library needs to automate its functions and services. In fact, the term really means to co‐ordinate or blend into a functioning whole.”

So there you have their scope note somewhat belatedly languishing on page 57. If you are able to refocus your expectations on this sole aspect, then essentially the authors have achieved what they set out to do.

The sub‐title is accurate in describing the book as a “how‐to‐do‐it manual” for it is full of practical advice on planning, inviting the user to make use of the various worksheets that are provided. Annotated lists of references are also included to guide the reader further into the topics covered. There are some useful things here and some parts of the book could help assist in the planning of other aspects of library‐based activity. The authors believe that technical problems, however daunting, can become demystified and manageable once one has understood the issues and prepared a blueprint for action. This book is more to do with the latter than the former, though some basic explanations about technical matters are included.

It is evident that, as the book outlines, the old idea of “automating” an individual library no longer makes much sense. It is now essential for libraries to plug in to larger systems that will give them access to a whole new world of products, services and information. For librarians the process should not be about finding original solutions to local problems but about choosing which off‐the‐shelf system will both provide for most of their needs and integrate easily with the technology that the organisation already has. Costs of course are a third factor and there is some brief guidance on planning for these.

Part 1 of the book deals with the initial planning stage for implementing projects. It runs though various initial considerations in a methodical way. At the heart of this section there is a chapter dealing with the need to create a strategic plan. This shows how you can go about outlining your objectives even if you do not at that stage know how you are going to achieve them. To help with this, the chapter describes how to set up a model for a two‐day planning meeting that would include “all those who have a stake in the outcome of your automation efforts”. As further guidance this chapter offers possible brainstorming exercises, a hand‐out entitled “40 phrases that kill creativity”, help on SWOT (Strengths, Weaknesses, Opportunities and Threats) analysis and further reading. This is typical of the sort of practical help that is available in many parts of the book.

Part 2 moves on to developing and sustaining a technology plan. Chapters here deal with the considerations necessary for evaluating and selecting a system that meets the criteria and then implementing it once it has been installed. Finally this part covers the training necessary to ensure that the system can be used effectively by both the staff and users. The chapter excitingly headed “Training! Training! Training!” is, however, mainly concerned with staff training. User training gets little coverage and there is no suggestion that other library staff may have more experience here and could be involved.

Part 3 covers, as indicated above, the planning of in‐house collection databases with detailed coverage of retrospective conversion, barcoding and cataloguing standards. A useful appendix covers the process of “working with consultants”.

For me it would have been really helpful if the title of the book had more accurately described its coverage. I believe it is misleading to imply that there is more inside the cover than there actually is. I found the book was useful for some of the practical tips it gave on planning, a number of which could be used in other project management situations. Those involved in cataloguing in small to medium‐sized libraries should get a lot more out of it, but how many are concerned with just having an isolated cataloguing module? In deliberately ring‐fencing this facet the authors have missed an opportunity to include links to other operations and wider agendas. They seem to be implying that cataloguers are interested only in their own patch. They are not are they?

Related articles