Friday, June 26, 2009
For those of you who are, like myself, following the work of Bibliocommons, I bring to your attention that Knowledge Ontario has recently announced that they will be shortly approaching libraries in Ontario with the opportunity to implement the Bibliocommons interface as part of an early adopters program.
Wednesday, April 22, 2009
How to reduce the number of missing books on my library lists
We all look at problems from different distances. For me, I tend to look at library things from the network level (far away) or at the user level (close up, but not too close up) and then I try to fit the two perspectives together.
Even though I blather on about grandiose big-picture library ideas in this blog, my library thoughts are also consumed by the minutia of the library experience. For example, it still grates me that its so very hard to create a simple 'shopping list' of titles, call numbers, and floor numbers (!) from the library catalogue that I can print out at home to take with me to the library.
My other complaint I have is that (at least at the libraries that I have recently visited) there is a disturbing number of books on my home-made cobbled book list that should be on the shelf but can't be found. What's particularly troubling, is that I haven't even bothered to approach library staff to fill out the requisite 'Item Missing' forms, and I'm a librarian. Just imagine what percentage of our users take this extra and effort to fix a problem that won't help them with their own immediate needs.
So here's my wish.
I would like a library catalogue to effortlessly let the user create a list of items for retrieval from the library shelves (this will come in handy in the future when our libraries become closed-stacks again, but that topic is another post). AND on this list, I would like a checkbox beside each item that reads something along the lines of "couldn't find this on the shelf". Now the user can check off the items she couldn't find and drop off the list at the front desk (with or without a contact email address for follow-up) and the cycle of missing books on the shelf is closer to closing.
Even though I blather on about grandiose big-picture library ideas in this blog, my library thoughts are also consumed by the minutia of the library experience. For example, it still grates me that its so very hard to create a simple 'shopping list' of titles, call numbers, and floor numbers (!) from the library catalogue that I can print out at home to take with me to the library.
My other complaint I have is that (at least at the libraries that I have recently visited) there is a disturbing number of books on my home-made cobbled book list that should be on the shelf but can't be found. What's particularly troubling, is that I haven't even bothered to approach library staff to fill out the requisite 'Item Missing' forms, and I'm a librarian. Just imagine what percentage of our users take this extra and effort to fix a problem that won't help them with their own immediate needs.
So here's my wish.
I would like a library catalogue to effortlessly let the user create a list of items for retrieval from the library shelves (this will come in handy in the future when our libraries become closed-stacks again, but that topic is another post). AND on this list, I would like a checkbox beside each item that reads something along the lines of "couldn't find this on the shelf". Now the user can check off the items she couldn't find and drop off the list at the front desk (with or without a contact email address for follow-up) and the cycle of missing books on the shelf is closer to closing.
Labels: catalogue
Saturday, August 30, 2008
The forcast is getting more cloudy all the time
Lots of different thoughts flooded my brain as I watched the introduction video to Ubiquity for Firefox. This video should be required viewing for librarians because its a proof of concept that illustrates what 'web 2.0' or 'cloud computing' can be: the user makes use of a website's services without even visiting that site.
The obvious question is how do we integrate the local library into this new ecology? I've been mulling it over and on first glance, I think that answer might be that we don't because we can't. I came to this conclusion after trying to envision a user trying to add a book or an article that they wanted to recommend to a friend. The most likely scenario is that this is an item in that user's own collection. To this end, I suspect that the most natural fit for this space is a web-based citation service such as Zotero 2.0 or newly released Mendeley. LibraryThing could work for books.
If we do want libraries to provide this service to our users (and I do), I think at a minimum, our library catalogue has to provide a means for a user to create their own virtual collections of books that include items from their library and from their own shelves . From my understanding, Bibliocommons is the only library catalogue service that can do this.
The obvious question is how do we integrate the local library into this new ecology? I've been mulling it over and on first glance, I think that answer might be that we don't because we can't. I came to this conclusion after trying to envision a user trying to add a book or an article that they wanted to recommend to a friend. The most likely scenario is that this is an item in that user's own collection. To this end, I suspect that the most natural fit for this space is a web-based citation service such as Zotero 2.0 or newly released Mendeley. LibraryThing could work for books.
If we do want libraries to provide this service to our users (and I do), I think at a minimum, our library catalogue has to provide a means for a user to create their own virtual collections of books that include items from their library and from their own shelves . From my understanding, Bibliocommons is the only library catalogue service that can do this.
Friday, August 22, 2008
On my list for next generation library catalogues - lists
One crucial feature that is missing by most library catalogues (and LibraryThing, to boot) is the ability to make and share lists of books. I consider it a crucial feature because I have this notion that most of our formal education consists of actively learning through works of text.
But there are other more subtle reasons why a listing making function is important for a library catalogue. For example, allowing users to create public lists of books is one of the few ways that readers can be connected with each other in a way that they can control.
Lists, I believe, are also an untried means by which collections librarians could share the reasons why they have selected some of their choices for the library. For example, some time ago the English Literature librarian at MPOW added We need to talk about Kevin, Vernon God Little, and Elephant (and others that I have forgotten - natch) to our collection because they were all cultural responses to the Columbine shootings. When I was collecting for science at MPOW, I actively sought out and acquired books on a number of topics (such as works about Tallgrass Prairie) that would be too narrow to properly represented in any of the traditional collection development policies. If I had the ability to create lists, I could group material together that were related but not necessarily represented by the same formalized subject heading.
Biblicommons does a fabulous job of providing users with the ability to create and share lists and does one better by automatically creating a "For later" list for each registered user. This will hopefully cut down on the inevitable "toread" tags. Although seeing a library catalogue filled with toread tags wouldn't necessarily be a sad sight to see.
But there are other more subtle reasons why a listing making function is important for a library catalogue. For example, allowing users to create public lists of books is one of the few ways that readers can be connected with each other in a way that they can control.
Lists, I believe, are also an untried means by which collections librarians could share the reasons why they have selected some of their choices for the library. For example, some time ago the English Literature librarian at MPOW added We need to talk about Kevin, Vernon God Little, and Elephant (and others that I have forgotten - natch) to our collection because they were all cultural responses to the Columbine shootings. When I was collecting for science at MPOW, I actively sought out and acquired books on a number of topics (such as works about Tallgrass Prairie) that would be too narrow to properly represented in any of the traditional collection development policies. If I had the ability to create lists, I could group material together that were related but not necessarily represented by the same formalized subject heading.
Biblicommons does a fabulous job of providing users with the ability to create and share lists and does one better by automatically creating a "For later" list for each registered user. This will hopefully cut down on the inevitable "toread" tags. Although seeing a library catalogue filled with toread tags wouldn't necessarily be a sad sight to see.
Labels: catalogue, collections

