2. What is Metasearch? More than Federated Search –Federated Search –Local, Harvested Data –Customizable –Flexible –Adjustable

3. What is Metasearch? The following 5 slides are borrowed from a presentation by David Walker (Cal St. San Marcos) http://smugnet.org/2005intl/Session-2- David-Walker.ppthttp://smugnet.org/2005intl/Session-2- David-Walker.ppt

4. Data Layer Application Layer Presentation Layer Typical Application

5. Data Layer Application Layer XML-based Application

6. Data Layer Application Layer XML layer XML-based Application

8. Data Layer Application Layer XML layer Custom Presentation Layer What is the Metalib X-Server?

9. What is Metasearch? Metasearch is research and development of both: –Backend (Data Layer, Application Layer, XML Layer) –User Interface (Custom Presentation Layor) And more…

10. What is Metasearch? Much greater interface flexibility Increased ability to integrate with other systems New ability to add new services: –Spell checking / recommendations –Personal digital libraries –Citation management

11. Backend Features Standard API / Web Service Interface Ability to harvest and index metadata Relevancy ranking Search caching Use Data (comprehensive logging) More…

12. User Interfaces Backend standard API allows for many different user interfaces Initially developed interfaces –Oregon Explorer –Rochester –A9 Future interfaces –Grokker-like –Others Ability to collaborate on interfaces with other libraries, like CDL, Uminn, NC State, etc.

13. Timeline First instance for public consumption available by March 15 Anticipate new updates every six weeks in the first year (approximately 8 updates)

14. Activities within each 6 week cycle User testing / feedback (Usability group) Use data analysis (Project team) Feature / task prioritization (Project team) Programming / Development (Project team) Testing (non-user) (Project Team) New version moves into production (Library Tech) ALL OF THESE TASKS ARE CONTINUOUS

15. W1W2W3W4W5W6W7W8W9W10W11W12 DevelopmentTestingRDevelopmentTestingR User Testing Development Planning Data Gathering (logs, etc.) (R=Release) Timeline for 2 six-week cycles

16. Resources Project Team –Jeremy, Terry, LSTA Programmer, Tami Herlocker, Graduate Student, Ryan Usability Team –Members from Public Services / Reference Services, Tami, Graduate Student

17. Resources Project Team –Jeremy: 50% –Terry: 25% –Tami:.5 FTE –GRA:.5 FTE –LSTA Programmer: 1 FTE

18. Resources Usability Team –5 Members, including Tami and GRA –3 Public Services Reps,.15 FTE each (5 hours/wk)