What is Metasearch?

• More than Federated Search– Federated Search– Local, Harvested Data– Customizable– Flexible– Adjustable

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.ppt

Data Layer

Application Layer

Presentation Layer

Typical Application

Data Layer

Application Layer

XML-based Application

Data Layer

Application Layer

XML layer

XML-based Application

Data Layer

Application Layer

XML layer

Custom Presentation Layer

What is the Metalib X-Server?

What is Metasearch?

• Metasearch is research and development of both:– Backend (Data Layer, Application Layer,

XML Layer)– User Interface (Custom Presentation

Layor)

• And more…

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

Backend Features

• Standard API / Web Service Interface

• Ability to harvest and index metadata

• Relevancy ranking

• Search caching

• Use Data (comprehensive logging)

• More…

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.

Timeline

• First instance for public consumption available by March 15

• Anticipate new updates every six weeks in the first year (approximately 8 updates)

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

W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12

Development Testing R Development Testing R

User Testing User Testing

Developm

ent Planning

Developm

ent Planning

Data Gathering (logs, etc.)

(R=Release)

Timeline for 2 six-week cycles

Resources

• Project Team– Jeremy, Terry, LSTA Programmer, Tami

Herlocker, Graduate Student, Ryan

• Usability Team– Members from Public Services / Reference

Services, Tami, Graduate Student

Resources

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

Resources

• Usability Team– 5 Members, including Tami and GRA– 3 Public Services Reps, .15 FTE each (5

hours/wk)