1. Searching Options and Result Sets Sara Randall Endeavor Information Systems October 30, 2003

2. NISO Metasearch Workshop Topics Searching Result Sets

3. October 30, 2003NISO Metasearch Workshop Search Options Service to promote efficient multi-target and multi-resource searching Fast retrieval Meaningful results

4. October 30, 2003NISO Metasearch Workshop Search Options Criteria Near stateless access Standard query syntax Search multiple resources via a single request Preference Start record and records per request Sort order of result set Record syntax of result set

5. October 30, 2003NISO Metasearch Workshop Search Options Recommendations Search and retrieval Review current practices and make recommendations for best practice and further standards work. Search review to include XML interfaces, SRW/SRU (SOAP-based successor to Z39.50) or other Web services, including standard query syntax and support for integrated relevancy ranking Longer term develop or adopt a standard metasearch search and retrieval protocol

6. October 30, 2003NISO Metasearch Workshop Result Set Management Result set metadatainformation that is valid only in the context of the current result set Record metadata Administrative/control metadata Descriptive

7. October 30, 2003NISO Metasearch Workshop General Recommendations Need a next-generation search protocol based on current technologies As part of search protocol development consideration should be given to providing result set metadata Standard single record metadata, both descriptive and administrative (or small handful) May need a more informal short term process to define metadata needs and review metadata initiatives underway that may be appropriate

8. October 30, 2003NISO Metasearch Workshop Result Set Open Issues How to allow for extension to core metadata so that Information Providers can transmit extra value information If cross database searching allowed in single search, how will variations in the results set metadata be handled on a database level Can result set metadata be overridden at the single record level Tension between the need for a simple to implement protocol and the need for rich metadata to provide advanced features