You also have those of us whose libraries unfortunately are not
automated... but because the vast majority of libraries are, we have
students who come in and can't find a book and say "I can't find this
book, but the catalog says its not checked out!" (to which I want to
laugh - the catalog doesn't say one way or the other! - but they assume,
even though it doesn't say "checked in" that it means it is!) I have to
admit, being a younger librarian myself (I'm 24) that I was quite
shocked to get here and have to learn about circulation the "old way" -
because I was in elementary school the last time I even used a library
that was not automated! So I certainly can't blame the students that
are even younger than me for assuming that's the way all libraries work
- but again, its another point that the catalog doesn't completely tell
you what is available.
Alison Jones
Public Services Librarian
Baptist College of Florida
-----Original Message-----
From: Next generation catalogs for libraries
[mailto:NGC4LIB_at_listserv.nd.edu] On Behalf Of Thomas Dowling
Sent: Wednesday, June 07, 2006 10:04 AM
To: NGC4LIB_at_listserv.nd.edu
Subject: Re: [NGC4LIB] Define catalog!
On 6/7/2006 10:33 AM, Scott Warren wrote:
> ...If it is in the catalog, you
> have access to it, period.
Er, let's say "ellipsis" there. It is a source of constant frustration
for users that they search for a popular topic or item and hit after hit
is checked out and the user does not have access in any satisfying way.
[A local public library leaves catalog records for lost items with a
holdings note of "The library owns zero copies". Gee, thanks.]
This came up at a brainstorming session we held earlier this year - a
next gen function that could earn us a lot of good will would be a way
to limit searching to items that are actually available, or to
circulating items that are actually available. (Or to items actually
available in my branch or location). Apologies to anyone whose system
currently offers that, but it's unknown around here.
Thomas Dowling
tdowling_at_ohiolink.edu
Received on Wed Jun 07 2006 - 11:35:39 EDT