Knowing how to find out
Many librarians, when asked what is involved in being a librarian besides checking out books, will say something to the effect of, “I don’t know the answers, but I know how to look them up.” Where a doctor has knowledge of medicine, a librarian has knowledge of how to find out knowledge of medicine. (Or how to organize and store knowledge of medicine for later retrieval, and how to connect people with the medical knowledge they need.)
An overarching problem in LIS, as I’ve said before in different ways, is that we have confused “knowing how to look it up” with technical knowledge of tools.
Knowledge of the tools is important, but is worth nothing without knowledge of the materials on which the tools operate. By analogy, knowing how to drive a car is of little value when you don’t know where you are and have no map and don’t know how to read one anyway, and you’re late to an appointment. To extend the analogy, it solves nothing in that situation to make technical improvements to the car, regardless of how fast you can make it go.
We are making vast technical improvements to the tools we use to find things, making them more powerful (in some respects) and easier to use. At the same time, however, we are gradually forgetting – by way of de-emphasis and de-prioritization – the general knowledge and domain-specific knowledge that enables us to do what we do at the reference desk.
If you’re a reference librarian, consider the thought-processes that are involved in answering a challenging reference question. Knowing the tools is helpful, obviously. But knowing what to do with them, based on your knowledge of the question’s subject area, is what gives you abilities that your patrons couldn’t pick up so easily. The knowledge that enables us to find things is knowledge of what Paul Otlet theorized as “the biblion,” the bibliographically interconnected world of information in documents and books. (The knowledge that enables us to interpret users’ information needs hermeneutically is another kind of knowledge altogether, but I won’t go into it here.) We can start with a couple of clues, infer a couple of different clues, and move from there into a rich inroad of relevant material, because we have knowledge of the field and the historical and conceptual relationships within it.
Actually, the initial exposition of the idea of knowledge of something versus knowledge of how to find something out, or at least the one our tradition goes back to, had nothing to do with knowledge of tools and was all about bibliographic knowledge, the ability to follow a thread from one place to another in the web of science and culture. It was a conversation between Samuel Johnson, James Boswell, Sir Joshua Reynolds, and Samuel Taylor Coleridge, in 1775. As well as we know it, it went like this:
“No sooner,” says Boswell, “had we made our bow to Mr. Cambridge, in his library, than Johnson ran eagerly to one side of the room, intent on poring over the backs of the books. Sir Joshua observed (aside) ‘He runs to the books, as I do to the pictures; but I have the advantage. I can see much more of the pictures than he can of the books.’ Mr. Cambridge, upon this, politely said, ‘Dr. Johnson, I am going, with your pardon, to accuse myself, for I have the same custom which I perceive you have. But it seems odd that one should have such a desire to look at the backs of books.’ Johnson, ever ready for contest, instantly started from his reverie, wheeled about, and answered, ‘Sir, the reason is very plain. Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information upon it. When we enquire into any subject, the first thing we have to do is to know what books have treated of it.”
(This conversation was quoted by Andrew Keogh in his address to the American Library Association Annual Conference in Asheville, North Carolina, in 1907, and is reprinted in Speaking of Information: The Library Juice Quotation Book.)
I have an ambition to do some research that lays out the thought processes involved in answering complex reference questions, the knowledge and creativity that we bring to the table, over and above our understanding of search interfaces and index structures. If you would be interested in helping with research along these lines, please let me know.