Google Search Appliance dynamic results cluster

[madhavsinghk]

Hi,
We want to provide query suggestion as the user starts typing. From
the documentaion, I get the idea that dynamic results cluster is the
answer. But there is no option to enable dynamic results clustering
through Admin GUI or by changing the underlying stylesheet as
suggested in the tutorial?

Appreciate any input?
Thanks

[timhall]

are you referring to the search as you type tool?

[madhav singh]

I want to implement something search as you type tool, but this tool reads from static file.
How can i provide query suggest (auto-complete) words that have been index by crawler?
Thanks,
Venu

[Joe D'Andrea]

Greetings!

On Nov 14, 1:28 pm, "madhav singh" <madhavsin...@gmail.com> wrote:

> I want to implement something search as you type tool, but this tool reads
> from static file.

Aye.

> How can i provide query suggest (auto-complete) words that have been index
> by crawler?

I believe that one is what they call an "exercise left to the
reader." ;)

Seriously though, there's a subtle-but-important difference here,
which you drew a bead on in your initial post. "Search-as-you-type" is
indeed _not_ the same as "query suggest." The former provides results
while the latter provides queries.

WIth that, dynamic results clustering _might_ be the closest thing to
query suggestion on the GSA.

In this case, you'll need to get familiar with the /cluster service on
your GSA (vs. /search). It works just like a search query (same
params), but with two important differences:

1. There's a new parameter, coutput (cluster output?). Set to xml or
json.
2. If using json, HTTP POST must be used (though the query string
remains).

To experiment, try a search directly on the GSA, then change this part
of the search URI:
/search?

... to this instead:
/cluster?coutput=xml&

View source (it may appear to be an empty page depending on your
browser) and you'll see the XML.

As an aside, notice this part:
<algorithm data="Concepts"/>

(I wonder if there might be other algorithms lurking within? Hmm!)

If you want to see the JSON response, use coutput=json instead, then
use a helper app (e.g., wget) that lets you issue a POST request.
Again, keep the query string as-is. No need to turn the params into a
POST-style payload.

Have a look at /cluster.js on the root of your GSA for the JSON format
(which, in turn, gives you insight into the XML as well).

Hope this helps!

--
Joe D'Andrea
Liquid Joe LLC
www.liquidjoe.biz
+1 (908) 781-0323

[Joe D'Andrea]

On Nov 18, 8:36 am, "Joe D'Andrea" <jdand...@gmail.com> wrote:

> WIth that, dynamic results clustering _might_ be the closest thing to
> query suggestion on the GSA.

As I think about this some more, I feel I should add a caveat here.
DRC is probably not what you ultimately want, since it takes a query,
not the beginnings of a query. For instance, if I was typing "wid"
perhaps it would be nice to get back "widgets" and other proposed
queries right away, but I don't think DRC works that way.

I mention this because the user expectation will likely be for this
kind of behavior in the response, especially if they have seen it
elsewhere (e.g., Google Labs[1]).

This is also why I mentioned the algorithm element earlier. Perhaps
there _is_ some other query string param (calgorithm??) to instigate
this kind of response, but I have no idea. If it exists at all, it
certainly isn't documented, so it may not be ready for prime time
anyway. "Webeat emptor!"

--
Joe D'Andrea
Liquid Joe LLC
www.liquidjoe.biz
+1 (908) 781-0323

[1] http://www.google.com/webhp?complete=1

[madhavsinghk]

Thank you verymuch for sharing your thoughts.

Thanks.
Venu

[srikanth vm]

Thanks ! :)