Kevin Gilbertson - Web Services Librarian Jean-Paul Bessou - Systems Librarian Z. Smith Reynolds Library Wake Forest University Growing Your Own Next-Gen Catalog: ZSR flickr.com/photos/samcatchesides/ /

Our Approach Your Next-Gen Catalog MotivationsInvestmentService issues Technical issues Political issues Sustainability

Agenda Successes, compromises, next steps Why we like VuFind and what our next steps will be Why did we want a new catalog? What essential features and services must it have? How will your constituents accept or adopt to this change? How do you implement, improve and sustain the system over time?

VuFind.org Villanova.edu Project manager Demian Katz Faceted search Supports multiple metadata formats SOLR, PHP, Java

Custom skin Localized facets Pre-processing of MARC records Voyager integration Custom user services

1. Why did we want a new catalog?

Many reasons Separation from ILS Adoption of open source Flexibility Faceted search Integrated digital resources More extensible interface New services Appeal to sophisticated patrons Satisfy basic patron needs

Taxonomy of services and features Use casesExampleImpact Simple but customizable faceted search Easy but persistent limiting of locations, resource types and subject matter Allows patrons and libraries to create ‘custom views’ of data Shift in resource investment Investment in personnel and community Open systems allow libraries to internalize and sustain expertise Support for multiple resource types and services MARC, Dublin Core, EAD Allows library to customize and host a variety of local data

Recognize needs, encourage change “I have used Endeca and I know what it is capable of. This system is NOT Endeca” --Visiting faculty member “I never understood what all of those links on the page were, I just ignored them” -- Faculty member on faceted browsing “You mean that we can use this link to show books that are located just in the Education Library!?” -- Staff member on persistent facets

Beta, Replace, Compromise Beta Low use Focus on hypothetical issues Perpetual delay of ‘go live’ Replace Massive feedback Real world success or failure Commit to rapid improvement Compromise Top ten complaints and compliments Accept limitationsRisk lack of use

Killer features, problems Quick open-ended search Interactive, extensible ‘Web 2.0’ functionality Cross-device support Locally customizable Complex searches, browsing failure Customizations block upgradability Local IT resources required

2. Successes, compromises, next steps

Success: Improved experience Solution: Ability to use facets after search, light weight services, content integration Next steps: Improve quality of facets through pre-processing of records “The new catalog lets me find new books and videos easily’

Compromise: Advanced searching Solution: Re-introduction of classic catalog for specific services Next steps: Depends on new release of VuFind. Focus on slowly minimizing need for other system “I want to browse by call numbers or be able to search specific indexes”

Next Steps: Digital collections Solution: Add resources from multiple locations (catalog, DAMS, OAI) into VuFind Next steps: Employ multi-record driver and OAI harvesting features in VuFind 1.1, load HathiTrust records directly in VuFind “How do we get our special collections indexed? What about public domain e-books?”

Sustainability Localize expertise: Preserve local IT expertise Focus on best practices Contribute back to community Limited customization: Skinning, indexing, service linking Develop with focus on integration with core system Automate and distribute: Automate loading, deleting, updating Develop expertise in IT staff, catalogers and public service Employ IT service life cycle approach

Want to try it out? ZSR maintains a current AMI (Amazon Machine Image) for testing, teaching Register, launch, and load a free Amazon micro-server for new EC2 users