|
Nicholas, D. Assessing information needs: tools and techniques. London: Aslib, 1996. [6], 56 pp. ISBN 0-85142-385-X (Aslib Know-How Guides) [Price not given.]As the series title suggests, this little book is designed mainly for those who manage information services of one kind or another, as a general introduction to the subject. David Nicholas, of City University, is well known for his work on the information needs of journalists and is well able to provide this kind of advice. Nicholas first sets out the rationale for conducting studies of information needs and the reasons for failing to do so, then distiguishes between wants, needs and demands, and goes on to present a framework for assessing information need. This is the core of the book and occupies 24 of the 56 pages. It suggests that information need has eleven major characteristics: subject, function, nature, level, viewpoint, quantity, quality, date, speed of delivery, origin, and processing and packaging. While this is a useful analysis, not all of these can be properly said to be features of information need: some appear to be qualities of the information provided, and other characteristics of the information delivery process. This is a mild criticism, however, since the framework would certainly be useful in drawing attention to the main features of an information service user's needs. Chapter 5 describes five main sets of "obstacles to meeting information needs": personality, time, access to information sources, the availability of information resources, and information overload. Here, as elsewhere, one would have liked to have seen rather more in the way of citation of sources (indeed, the author is guilty of failing to cite when it would be proper to do so). I recognize the view that says, "Practitioners don't want the trappings of academic writing" but I'm not sure that it is correct and, in any event, the publisher claims that this series is also designed for those, "...teaching in the field of library and information services", and in that sector citation is certainly necessary. The final chapter (apart from the conclusion) deals, in a summary fashion with the main ways of collecting data for user studies. From the point of view of what I take to be the primary audience of practitioners, this is probably the least satisfactory part of the book, since it is so slight a treatment of a very complex area. Any practitioner will have to do a great deal more reading, or hire a consultant, before being able to put the main lessons of this book into effect through data collection. In summary, this little book provides a good deal of useful advice for the practitioner on the conduct of user studies, but insufficient guidance on the choice of and details of data collection methods. In education and training, it would be a useful addition to reading lists, but such lists would need to be reinforced by the addition of more comprehensive works. Prof. Tom Wilson
|