Adding &filter=0 as default for search

[scatter]

hello

i'm a non-techy type but our IT department are busy so it's fallen to
me to ask this. so please be kind and have patience...:)

We have a GSA searching through a small database of XML files which are
very similar. when you enter a search term it *always* returns only 2
hits (whether it's 2 of 3 or 2 of 300).

The GSA thinks all the other XML files are too similar so filters them
out. you can click on "repeat the search with the omitted results
included" and get the rest but is it possible to include the &filter=0
command in the initial search?

i.e. when you click on the search button for the first time it should
show all results and not just these two.

any help greatly appreciated!

cheers
jamie

[ctr...@firstam.com]

This is a part of the explanation of the current behavior with filter
setting of "1" "Duplicate Directory Filter - If there are many results
in a single web directory, then only the two most relevant results for
that directory are displayed. An output flag indicates that more
results are available from that directory. "

I am guessing all of your xml files are located in the same directory?
Review the filter settngs in your documentaiton. I would recommend a
filter setting of "p"

This will filter duplicate snippets only. and the snippets will be
different depending on what was searched.

[Jeff Ragusa]

Right, filter=p might be better. Here's the documentation link:
http://code.google.com/enterprise/documentation/xml_reference.html#request_filter_auto

As for how to do it in a persistent way, I believe there's 2 things
you'd need to do.

First you need to add the filter parameter to the default base url that
the search appliance redirects to when users hit
http://<gsaservername>/. For this you need to add filter=p to the
Default Search URL on the System Settings page of the Administration
section of you GSA admin UI. See the context sensitive help there.

Secondly you need to enable it so that the parameter is carried forward
on each search (rather than just the initial search screen). For this
you'll need to edit the XSL in your frontend. Look for the the
form_params template and remove the line where filter is excluded from
the carried on search input form.

For others thinking about doing this, keep in mind that Google
generally recommends against it since for most uses, the filters help
users find what they want.

-Jeff

[scatter]

this sounds very hepful guys. many thanks! i shall pass this on and
let you know how it goes.

[RichD]

I was also looking for functionality like this.

> First you need to add the filter parameter to the default base url that
> the search appliance redirects to when users hit
> http://<gsaservername>/. For this you need to add filter=p to the
> Default Search URL on the System Settings page of the Administration
> section of you GSA admin UI. See the context sensitive help there.

Simply adding the "filter=p" to that field will not work. You need to
provide a complete URL to redirect to such as
http://<domain_name>/search?filter=p&site=default_collection&client=default_frontend&output=xml_no_dtd&proxystylesheet=default_frontend

> Secondly you need to enable it so that the parameter is carried forward
> on each search (rather than just the initial search screen). For this
> you'll need to edit the XSL in your frontend. Look for the the
> form_params template and remove the line where filter is excluded from
> the carried on search input form.

Yeap, once that was completed and you wait long enough it worked.

Good tip.

-Rich

[scatter]

thanks Rich. Still not managed to get an IT guy to help me with this
:( gonna have to start hassling them....

On Oct 4, 9:41 pm, "RichD" <reefl...@gmail.com> wrote:
> I was also looking for functionality like this.
>
> > First you need to add the filter parameter to the default base url that
> > the search appliance redirects to when users hit
> > http://<gsaservername>/. For this you need to add filter=p to the
> > Default Search URL on the System Settings page of the Administration

> > section of you GSA admin UI. See the context sensitive help there.Simply adding the "filter=p" to that field will not work. You need to

> provide a complete URL to redirect to such as

> http://<domain_name>/search?filter=p&site=default_collection&client=default­_frontend&output=xml_no_dtd&proxystylesheet=default_frontend

>
> > Secondly you need to enable it so that the parameter is carried forward
> > on each search (rather than just the initial search screen). For this
> > you'll need to edit the XSL in your frontend. Look for the the
> > form_params template and remove the line where filter is excluded from

> > the carried on search input form.Yeap, once that was completed and you wait long enough it worked.
>
> Good tip.
>
> -Rich

[scatter]

well at last we got someone on the case (don't ask!) and it worked like
a charm. Many thanks to all involved! 8-)

> > -Rich- Hide quoted text -- Show quoted text -