Hi, Steven.
My experience tells me that new GSA suggest feature does not
distinguish between site-specific requests. What I had to do to solve
the problem was to append site name to visitor's requests, so I would
have:
summer site:
first.foo.com
summer site:
second.foo.com
etc.
Then I had to create a suggestions proxy which would: fetch requests
from my more than 200 web sites; deliver requests to GSA/suggest on
each visitor's keystroke; fetch 300 suggestions (key_matches=300);
filter out those not related to the requesting web site; deliver top
ten suggestions back to the client.
In my scenario, I have only one (default) collection and only one
front end so I don't know for sure how GSA/suggest handles multiple
collections. Maybe we should add our request for site-specific/
collection-specific suggestions delivery to the GSA Feature Request
List. A couple of new GSA/suggest parameters would be very useful.
My next step will be to get rid of GSA/suggest alltogether and build
my own, database-driven, solution.
Hope this helps