Comments on: CUIPID 4: Building a faceted searching and browsing interface for your library catalog http://litablog.org/2006/10/cuipid-4-building-a-faceted-searching-and-browsing-interface-for-your-library-catalog/ Library and Information Technology Association Fri, 20 Jan 2012 19:19:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Genny http://litablog.org/2006/10/cuipid-4-building-a-faceted-searching-and-browsing-interface-for-your-library-catalog/comment-page-1/#comment-25168 Genny Sun, 29 Oct 2006 01:47:29 +0000 http://litablog.org/2006/10/28/cuipid-4-building-a-faceted-searching-and-browsing-interface-for-your-library-catalog/#comment-25168 Well, isn't this an interesting counterpoint to the faceted search based on a vendor product, Endeca, as used at NCSU and described in earlier sessions at LITA Forum. What this has in common with their solution is a lot of technical staff, compared to my library (we have one person responsible for the public web site and the staff site -- that would be me; and one person responsible for the ILS -- that would be my cubemate Mike). By public library standards, we already have a huge systems staff. Granted, it's way smaller than Seattle's or even San Jose's, but most public libraries have even less to work with -- both in terms of staff, and in terms of budget. So I'm glad to see this move towards making advanced features available via open source! And beyond that, I think we need to start considering how to make these solutions not only available but install-out-of-the-box easy for many of our colleagues at smaller libraries. How can we take the next step to make every library patron have as easy a search experience as the undergrads at these academic libraries? Well, isn’t this an interesting counterpoint to the faceted search based on a vendor product, Endeca, as used at NCSU and described in earlier sessions at LITA Forum.

What this has in common with their solution is a lot of technical staff, compared to my library (we have one person responsible for the public web site and the staff site — that would be me; and one person responsible for the ILS — that would be my cubemate Mike). By public library standards, we already have a huge systems staff. Granted, it’s way smaller than Seattle’s or even San Jose’s, but most public libraries have even less to work with — both in terms of staff, and in terms of budget.

So I’m glad to see this move towards making advanced features available via open source! And beyond that, I think we need to start considering how to make these solutions not only available but install-out-of-the-box easy for many of our colleagues at smaller libraries. How can we take the next step to make every library patron have as easy a search experience as the undergrads at these academic libraries?

]]>