1 / 18

Metasearch

Metasearch. 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)

vince
Télécharger la présentation

Metasearch

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Metasearch

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

  4. Typical Application Data Layer Application Layer Presentation Layer

  5. XML-based Application Data Layer Application Layer

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

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

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

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

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

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

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

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

  14. W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 Development Testing R Development Testing R User Testing User Testing Development Planning Development Planning Data Gathering (logs, etc.) (R=Release) Timeline for 2 six-week cycles

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

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

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

More Related