The document discusses different ways libraries can customize services for patrons using technologies like RSS, widgets, and mashups. It provides examples of how some universities and public libraries have implemented these technologies. The goals are to make access to information more seamless, relevant, and personalized for users. However, challenges include privacy, development costs, and technical issues. The document predicts these customization methods will become more popular and collaborative as security improves.

1. Customization for Libraries GROUP F LIS 652 INFORMATION SERVICES & RESOURCES

2. The Beginning

3. Reasons for Implementation A new generation of library patrons The need to be forward-thinking and user-driven Identifying customers’ preferences

4. Goals “ Libraries and universities have to make access to information seamless, relevant, and personally useful to clients and stakeholders -- while at the same time competing with new information providers” -Lakos and Gray

5. Issues Facing Libraries Privacy Development Cost Tradition

6. What is RSS? Rich Site Summary RSS Feeds Feed Reader

7. How do Libraries Incorporate RSS?

8. RSS: University of British Columbia

9. RSS: University of Oklahoma

10. Issues with RSS Cons: Can be overwhelming for some, "too geeky" Requires a separate tool Server or spyware problems Pros: Simple for the average Internet user Customized information Feed readers are free Independent of email

11. What is a Widget? Some Popular Examples: Dashboard Widgets (Mac/OSX) Facebook Apps Google Gadgets (iGoogle) Third-party applications that companies build to embed into major content platforms (Scott 2008)

12. Usage in Libraries Catalog Integration Chat Reference (Meebo, QuestionPoint, AOL Wizmi) Social Networking (Facebook, Twitter)

13. Widgets: Catalog Integration In-Website/Portal, Browser Add-on (i.e. Firefox)

14. Widgets: Chat Reference MeeboMe, QuestionPoint, AOL Wizmi

15. Widgets: Social Networking Facebook, Twitter

16. Widgets: University of Texas at Austin

17. Issues with Widgets Evaluation for Users and Libraries: Point-of-need / Access vs. Determining usefulness / Delivery method (Platform)

18. What are Mashups? “ A mashup is a web application that uses content from more than one source to create a single new service displayed in a single graphical interface” -Darlene Fichter, “Library Mashups”

19. Anatomy of a Mashup Content host and provider Application Programming Interface (API) Use web protocols such as REST and SOAP Mashup Site/Host Web Browser

20. Library Mashups: Maps Uses Google Maps Includes branch details, hours Brooklyn Public Library

21. Library Mashups: Multimedia National Library of Australia Flickr hosts photos, allows users to upload photos Users can search archives through library website

22. Library Mashups: Catalog Uses NY Times Bestsellers API Users can find bestsellers in library catalog Dallas Public Library

23. Issues with Mashups Cons: No control over how content made available through API is used Protection of intellectual property Data security OPAC’s Search API is only for member institutions Pros: Easy to create Yahoo Pipes Added value to library websites Greater user interactivity with library content OPAC has released basic API for general use

24. Customization Trend Predictions RSS More expansive Going to become more popular and easier to use Widgets Increased mobility associated with Reference Services Mashups More organizations will provide API’s Become more collaborative (users make content) Security will increase to protect data

25. THANKS! GLENDA BARAHONA RYAN BREAUX SARAH LYON ANDREA MULLEN