[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [search-ws] faceted search
Ok. Then I think we have two possible approaches: 1. Via scan: We would want to consider eliminating the scan clause, add a query parameter (already mentioned), and enrich the scan response as Ralph suggests. 2. Via searchRetrieve: First, would we want to get back regular result set records along with facet results, or just the facet results? If the latter, maybe we could just come up with a "facet" record schema. If we want both, and assuming we don't want this relegated to an extension (in 2.0) then we need an additional parameter in the response, something like "facetResults" or something more general, "additionalSearchInfo". (That was a joke, of course. A Z39.50 relic. But you get the point.) --Ray ----- Original Message ----- From: "LeVan,Ralph" <levan@oclc.org> To: "Ray Denenberg, Library of Congress" <rden@loc.gov>; <search-ws@lists.oasis-open.org> Sent: Friday, September 19, 2008 4:02 PM Subject: RE: [search-ws] faceted search Scan doesn't work. A scan response assumes that all the terms returned are from the index in the request. So, there is no indication of the source index for the individual terms. Facets can come from many indexes. Languages are popular facets and they'd come from a language index. Similarly for dates. We need a response richer than scan. In addition, the current proposal would require 2 interactions with the server; once to do the search and once to get back the facets. My proposal returns the facets with the search response. My response goes into the extraResponseData and looks like this: <facetReport> <facets index="indexName" count="numberOfFacets"> <facet count="numberOfMatchingDocuments">term</facet> </facets> </facetReport> As you can see, I clump my facets by index. If you prefer to have a flatter response and leave the clumping to the client, then the response could be: <facets count="numberOfFacets"> <facet index="indexName" count="numberOfMatchingDocuments>term</facet> </facets> The count on the facets element could be omitted. Some applications prefer not to have to count the number of subelements. Ralph > -----Original Message----- > From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov] > Sent: Friday, September 19, 2008 3:41 PM > To: search-ws@lists.oasis-open.org > Subject: Re: [search-ws] faceted search > > Ralph: > > "How about a flag on the request that says that you want facets > returned > in the search response?" > > But how would they be presented in a search response? I think the > reason for > suggesting scan is that the scan response is essentially how you want > the > facets presented. > > --Ray > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]