Micah, I think I may have explained poorly. This is essentially what I'm doing -- Docs are, generally, like this:
<doc> <search-meta/> <p>...<cite><search-meta/></cite>...</p> <section> <p>...<cite><search-meta/></cite>...</p> ... </section> </doc> Searches operate over //doc by default, but if you add the operator/state "select:cite" it changes the searchable expression to //cite. The results are correct, but the problem is that the facet counts appear to be for *both* doc and cite metadata, and thus do not change when toggling searchable-expressions via operator/state. This won't make any sense to our users, who will expect the facet counts to match what they think they're searching for. -W -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Micah Dubinko Sent: Tuesday, October 18, 2011 6:56 PM To: General MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] How to get different facet counts for different searchable-expression in Search API Hi Will, Everything you want to search exists in document fragments (not properties) right? What would happen if you switched in a different searchable-expression via operator and state? The combined query is taken into account by faceting, but the searchable-expression is not. -m On Oct 18, 2011, at 4:42 PM, Will Thompson wrote: > Our app has typically searched only document-type elements, but I recently > added metadata to citation elements (contained within and scattered about > document elements) so that they can be optionally searched using an operator. > i.e.: "term1 term2 select:citations" The operator changes the > searchable-expression and transform-results to search only citation elements > and return citation-specific snippets. > > However, I need the facet counts to reflect the search being performed - > i.e.: only show estimates for document element direct-child metadata during > normal search, and only for citations when that is toggled using the > operator. > > My first thought was to use different names or namespace for the citation > metadata and have the operator toggle a separate set of constraints > associated with those names. But constraints are not supported children of > search:state under search:operator. > > Any ideas on how to accomplish this with Search API? > > Thanks! > > -Will > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
