FRBRization of a Public Library

1. FRBRization of a Public Library April 27, 2007 Northern California Technical Processes Group

2. Suggested Reading • “How OPACs Suck, Part 2: The Checklist of Shame.” Posted on ALA TechSource Online, 4/3/06 • Karen Calhoun’s The Changing Nature of the Catalog and Its Integration with Other Discovery Tools. Prepared for the Library Congress, draft 2B, 2/21/06

3. BACKGROUND • Why FRBR in a public library • Enhance searching and browsing / Guided navigation – Endeca • Federated searching • FRBR

4. BACKGROUND(continued) • A system of 14 branches (soon to 16) and a large central library • Serving a population of 1.5 million • Circulating 13+ million items per year • Collection of 2.2 million items • 4+ million visits per year • 13+ millionelectronic visits per year

5. Why FRBR for a Public Library • Phoenix Pubic Library stepped into the world of commercial websites in 2003 • Re-developed the online catalog using CARL APIs – Quick Search • by Author keyword • Exact Title • Exact Author (LN,FN) • by Title keyword • for Audio Books • for Arizona Images

6. Why FRBR for a Public Library (continued) • for Book on CD - Search Database • for Children’s Materials - Find a Database • for DVDs • for Large Type - Online Magazines • for Braille - Online Newspapers • for Print Magazines • for Print Newspapers - Library Event Calendar • for Videos (VHS) - Library Website

7. Why FRBR for a Public Library (continued) • Created an environment that would constantly evolve to continuously meet customer expectations • Created Online Account Registration for • My bookshelf • My Searches • My Favorites • My Events • Update My profile • Update My Events

8. Why FRBR for a Public Library (continued) • Created Online Account Registration for • Email Notices and Library Newsletters • Library Courtesy, Holds, Overdues Notification • Part-time Employment Notification • General Newsletter • Business Newsletter • Children’s Newsletter • Calendar of Events • Promotional e-mails

9. Why FRBR for a Public Library (continued) • Most common public complaints received: • Why don’t you have a copy of … to check out • They only looked at the first, second, or third bibliographic records and everything was checked out, while there were 30 copies available under other bib. records farther down the results list • I did not place a hold on this copy of this title! • 1st title in results list was “on order record” or large type, etc. because they were listed in reverse chronological order

10. Why FRBR for a Public Library (continued) • Bottom line, in an environment of evolution to meet customer needs • Get the patron / end user to the information they need by making it • Fast • Easy • Convenient • Be in total control of the end user experience to meet their needs !!! FRBR was a natural !!!

11. Next Steps • Developed a 3 pronged approach to controlling the end user experience • Implement Endeca to enhance searching, browsing, and provide guided navigation – live on 3/12/07 • Incorporate federated searching into the new environment • FRBRize the bibliographic database

12. Prong #1 Implemented Endeca to enhance searching, browsing, and provide guided navigation. In addition to searching by traditional means (author, title, etc.), searching in Endeca works by a process of elimination called “guided navigation.” For example searching “Phoenix” will display 11,964 results. Endeca allows users to group the results in similar characteristics like: topical subject / format / age level / languages / fiction / non-fiction / region / era / author names / etc. 2 click later <book> <labor market> takes the user to Arizona Occupation Employment Forecasts.

13. Prong #1(continued) • Endeca is ILS independent • Endeca and its tools can be applied to a Library’s entire website • Operates on a “snapshot” of the catalog for searching

14. Prong #1(continued)

15. Prong #1(continued)

16. Prong #1(continued)

17. Prong #2 • Incorporate WebFeat federated searching into the Endeca searching environment both as: • A stand alone option to just search databases • Or as part of catalog searching retrieving relevant articles from subscription databases related to type of search chosen Example: Search by subject would not only result in a list of books, but relevant articles from subscription databases. PPL would control the default, serving up a small subset of results and further enabling the end user to expand the results. Implementation in planned for FY 2007/08.

18. Prong #3 • FRBR • Made decision in July 2004 to begin process to FRBRize the online catalog • Put together a team - Library Services Administrator, Bibliographic Services Manager, Bibliographic Enhancement Supervisor, and Web Manager • Background Research

19. Prong #3(continued) • Extensive literature and Internet search to • Learn all facets of FRBR • See if other libraries had plans to implement FRBR • Learn what ILS systems are supporting FRBR • Examine plans for incorporating FRBR into AACR3/RDA

20. Prong #3(continued) • Convinced OCLC Research to help with our project – Special thanks to George Needham • PPL created a subset of our database of selected popular / high circulating titles in : • fiction • non-fiction • Spanish fiction • classic works in English

21. Prong #3(continued) b. OCLC Research (Thom Hickey) applied FRBR to these titles • Results output in an Excel spreadsheet • Converted to Access to display in a clearer manner • Participated in OCLC WorldCat Pilot Project • Didn’t like interface, but results were almost what we were looking for

22. Marching Forward with FRBRIssues to Consider Our current ILS vendor does not support FRBR, nor is it developing anything. So – Phoenix Public Library decided to: • Increase authority / bibliographic controls • Implement a process to insert uniform titles in “on order” records in the online catalog @ the time of downloading to the bib. database • Resolve the issue of Movies and uniform titles or author main entries

23. FRBRImplementation Question: How much of the database needs to be FRBRized? Answer: Of the 800,000 bibliographic records, less than 20% (160,000) need uniform titles. Of those, approx. 12-15,000 will actually be FRBRized = less than 2% of the database.

24. FRBRImplementation Phase #1 . Implemented uniform title and author main entry model • Identified bibliographic records that need uniform titles • Updating bibliographic records

25. FRBRImplementation Phase #1 . Updating authority files (currently in process) • Testing uniform titles in Endeca to see the extent to which aggregation (Endeca term = roll-up) can be utilized to FRBRize (to begin in July)

26. FRBRImplementation Phase #2 . Preliminary testing indicates that Endeca’s aggregation functionality can automatically FRBRize the search, resulting in the display of one record with all of the items from the aggregated records based on the search rules the Library applied in Endeca. • Bibliographic Enhancement Team is developing “exceptions list” to distinguish those records we do not want to aggregate (e.g., large type, different translation, special illustrated edition, etc.)

27. FRBRImplementation Phase #2 . If Endeca hadn’t not worked, what was our plan? • Create a “master record” in the bibliographic database for each group of bib. records with the same uniform title that we wanted to group together. • Add all of the items from the subordinate records to the “master record.” • Determine how only the “master record” would be searched and displayed in Endeca.

28. What about movies? • Add uniform title and author main entry in a specific field (currently testing 5xx and 9xx) and teach Endeca to search that field. • Apply the uniform title / author main entry only to movies of literary classics (e.g., Treasure Island, To Kill a Mockingbird, Pride and Prejudice, For Whom the Bell Tolls, etc.)

29. Conclusion It’s a Work in Progress! Watch our Website www.phxoenixpubliclibrary.org

30. © Phoenix Public Library2006 Ross McLachlan ross.mclachlan@phoenix.gov