Search Service EWS and Hit Highlighting

I need to provide the Search Results with Hit Highlighting information included, ideally in XML format, but can't see if / how the Search Service supports HH, can anyone provide some more detail ?

Find more posts tagged with

Comments

Ferdinand Prantl

I am just an “accidental” user of the XML search,but isn’t the highlighting the default behavior? I got it using thefollowing query:

var rootSlice ="2084|90621|Within SDK Documentation";

var textQuery = "test";

var startItem = 1;

var pageSize = 25;

var urlQuery = “?func=search&lookfor1=allwords&where1="+ encodeURIComponent(textQuery) +

???"&within1=content&slice=" + encodeURIComponent(rootSlice) +

???"&where2=OTMIMEType:text/html&boolean2=and&lookfor2=complexquery"+

???"&outputformat=xml&startat=" + startItem +"&gofor=" + pageSize;

You should see the highlighted words enclosed by inline elements<HH> in the XML search response (element <OTSummary>).

?? --- Ferda

From: eLink Entry:Enterprise Web Services 9.7.1 Forum[mailto:otdnenterprisewebservices971forum@elinkkc.opentext.com]
Sent: 21. ?ervna 2010 17:36
To: eLink Recipient
Subject: Search Service EWS and Hit Highlighting

Search Service EWS and Hit Highlighting

Posted by greg.griffiths@logica.com (Griffiths, Greg) On 2010/06/21 11:35

I need to provide the Search Results with Hit Highlighting information included, ideally in XML format, but can't see if / how the Search Service supports HH, can anyone provide some more detail ?

[To post a comment, use the normal reply function]
Forum:	Enterprise Web Services 9.7.1 Forum
Livelink Server:	knowledge-wlweb01

Greg_Griffiths

Ferda,

Thanks for you post, that is what we currently have, our issue is that callign this URL from an ASP.Net page means that we get into the cycle of challenge / response and the set timezone redirect, we are trying to see if we can do this natively via WebServices, we think that the XMLSearch API may alternatively provide what we need, but at this stage we are trying to get all the interaction done via EWS.

Ferdinand Prantl

Hmm, I took the JavaScript example from a page running on the Livelinkserver itself where it (obviously) works without any problems...For the ASP.NET, the solution based on the EWS would be nicer. Hopefullysomeone who knows the sources of the XMLSearch and the Search WS willpost how to get the highlights there. Good luck! (Or you can plunge intothe OScript sources yourself :-)(We have another component which uses the XMLSearch API from an ASP.NETpage. We set the cookie of the HttpWebRequest to the value obtained by aseparate LAPI call for the currently authentified user. I'm not surewhat you meant about the time zone problem - we convert the date/timevalues from/to the time zone of the client.) --- Ferda

Greg_Griffiths

I managed to solve it by creating a suitable Request object and then directly calling the Search request handlers execute method and setting the fOutputFile parameter to be a file on the server so that the GenerateOutput method dumps to a file rather than streams back, this file is then read into the system and passed back as the output of the EWS.

Evert_Kuiken

Hi Greg and all others,

I have a similar request at this time. In the search results we want to show the text where the search terms were found. We use the Web Service to do the search. Did anyone solve this yet?

Regards, Evert

Kyle_Swidrovich

Hi Evert,

What you’re asking for is different than what was discussed in this thread.

You are asking for dynamic summaries as opposed to static summaries.

Content Server search calculates static summaries.

That is, at the time the document is indexed, we determine the entire summary text.

This text does not change in response to different search terms.

The same summary will be displayed each time the item appears in the search results.

We will highlight search terms in the static summary if they happen to exist in the static summary.

Other search engines calculate dynamic summaries.

That is, the “summary” shown on the results page is a snippet of the document highlighting where one (or more) of the search terms were found.

Content Server provides hit highlighting functionality for the entire document, but it does it on demand.

That is, as a user, you have to click “Hit Highlight” to see where the terms matched in the content of the document.

To change the Content Server search functionality to provide dynamic summaries would result in a huge hit to search performance. As such, we have no current plans to implement it in product. A customization along these lines would probably involve calling out to hit highlight every search result, extract what you deem to be the “most relevant” hit-highlighted segment for each result, then modify the results page to suppress the static summary and show the dynamic summary.

Kyle