I like the "matched on" list. I think that could be more useful than individually listing where the terms are located in each record. I definitely agree that more on why an individual record is retrieved will help users, particularly since we are moving away from a display that mimics the old cards.
If the search term is in a field not normally displayed (say the 505 - which I think should be displayed, but that's another topic), is it possible to display that field when the record is retrieved? Elaine J. Elaine Hardy Library Services Manager - Collections & Reference Georgia Public Library Service, A Unit of the University System of Georgia 1800 Century Place, Suite 150 Atlanta, Ga. 30345-4304 404.235-7128 404.235-7201, fax [EMAIL PROTECTED] www.georgialibraries.org -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Etheridge, Jason - Gmail Sent: Thursday, September 13, 2007 11:23 AM To: [email protected] Subject: Re: [OPEN-ILS-DEV] Introduction and Question I do think it would be useful to give more information on how matches are being made, in some generic manner. Not as a snippet of the record with the terms highlighted without any context, but maybe something like "Search terms found in blah and blah", where blah is maybe some friendly description of the pertinent field mapped from MODS or Dublin Core, and not necessarily MARC. So you might get something like: 1) Computers and intractability : a guide to the theory of NP-completeness by Michael R Garey; David S Johnson Search terms found in title, table of contents, and abstract. 2) Np Completeness Comprehensive Reference, Guide And Solution Manual for Pnp. Search terms found in title, subject, user tags, and reviews. Would that be too weird? Another notion is to have a sidebar or summary of the actual match points as facets for the whole result set. Maybe something like... Matched on: Title: 5 hits Subject: 10 hits Table of Contents: 3 hits Reviews: 2 hits Something like that, and then choosing one of those would further constrain your search. Useful? -- Jason
