Document relevancy – Google Search Appliance User Experience Guide User Manual
Page 30
![background image](/manuals/552749/30/background.png)
30
How can I see the XML that the Google Search Appliance is sending back before it gets
transformed?
● For
results, remove the proxystylesheet parameter and value. For example:
○
http://GSA_HOSTNAME/search?
q=query&btnG=Google+Search&access=p&client=default_frontend&outpu
t= xml_no_dtd&sort=date:D:L:d1&entqr=0&oe=UTF-8&ie=UTF-
8&ud=1&site=default_collection
● For
dynamic results clustering, you can directly query the Google Search Appliance for the XML
output. For example:
○
http://GSA_HOSTNAME/cluster?q=query&site=default_collection&clien
t=default_frontend&coutput=xml
How can I integrate the Google Search Appliance into a non-web application?
● The
Google Search Appliance accepts HTTP requests, and can return XML (or other formats
after having been transformed by means of an XSLT). The returned results can then be parsed
by an application, written in the language of your choosing, and then used for whatever purpose
the application requires.
Document relevancy
How can the Google Search Appliance sort the results by other criteria than relevancy and date?
● It
is exactly the purpose of a search engine to sort the search result by relevancy. Everything else
is the output of a data base query.
If you need to sort the results by any other numeric value you have, you can make use of the date
sort feature. To do so, convert the value to an ISO-8601 date format (YYYY-MM-DD) and insert it
to a meta tag in your document. You can search any dates between 1900-01-01 and 2079-06-06.
Then set up the respective name of the meta tag in the section "Document Dates" in the admin
console. The Google Search Appliance considers the value of this meta tag as the document
date and can sort it by this value.
Starting in 7.2, it is also possible to sort by metadata.
I want to promote a URL to the top of the results. How can I do this?
● Use
KeyMatches.
● Implement
User Results.
● Create
a result biasing policy, which increases the relevancy of documents based upon the URL,
Collection, Date, or MetaData. Attach this policy to the appropriate front end.