nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Searchservice and Score problems

Peter Forsbom

I am using the C# Search Service sample on a 9.7.1. server (keep in mind that the server has never been patched .....)

It looks like ResultOrderSpec is messing with the Score result.

                query.DataCollectionSpec = "'LES Enterprise Search'"; // use the first search slice in the list
                query.QueryLanguage = "Livelink Search API V1";         // use the Search API for queries
                query.FirstResultToRetrieve = 1;                        // start retrieving results at Result #1
                query.NumResultsToRetrieve = 100;                         // retrieve up to 5 search results
                query.ResultOrderSpec = "sortByRegion=OTCreatedBy";     // sort by the OTCreatedBy region
                query.ResultSetSpec = "where1=" + whereClause;          // set the where clause of the query
                query.ResultTransformationSpec = new string[] { "Score", "OTName", "OTLocation" };      // set the displayed/retrieved regions

This returns 100% Score results on all hits. If I remove the line : query.ResultOrderSpec = .... then the result set contains proper Scores.

If I try changing the ResultOrderSpec to order by OTName : query.ResultOrderSpec = "sortByRegion=OTName"; then all the scores are set to 0!

As I said earlier the Livelink installation has never been patched so this may be fixed a long time ago. If that is the case, please provide me with the patch # I need so I can push my customer to upgrade the Livelink installation :-)

thanks

Peter

Find more posts tagged with

Comments

Steve Brezina

Hi Peter,

You should push to get on the latest 9.7.1 cumulative patch. Update 5 is the most recent.

We made a number of fixes to score handling and included a major update to the search engine since 9.7.1 was initially released. When updated, you will find that Score is the value of the query sort expression. Only when sorting by relevance is it an integer between 0-100. When sorting by OTCreatedBy, it will be the OTCreatedBy user id values.

Regards,

Steve