Result Curations and facets

gavin1211 2016-03-05 12:34:23 UTC #1

We use result curation to boost some urls of specific courses to the top of search results for certain keywords.

This is ok when just using a query, but when a facet is applied, the result curations are not honoured, and the results seem very wrong. We need to be able to control the result set when a facet is applied.

For example, this query works great, thanks to result curation: http://www.ulster.ac.uk/courses/course-finder?query=management

All of our management courses appear at top of results.

But when a facet is applied, http://www.ulster.ac.uk/courses/course-finder?query=management&f.Campus|campus=Jordanstown

The management courses disappear.

Is there a way to control results when query and facets are applied using result curations?

msheppard 2016-03-06 23:05:14 UTC #2

Can we see the curator config in question @gavin1211?

gavin1211 2016-03-07 09:20:07 UTC #3

[ {

"name" : "To Top Management (Jordanstown campus)",

"enabled" : true,

"trigger" : {

"type" : "And",

"triggers" : [ {

"type" : "Or",

"triggers" : [ {

"type" : "AllQueryWords",

"triggerWords" : [ "management" ]

} ]

"actions" : [ {

"type" : "PromoteUrls",

"urlsToPromote" : [ "http://www.ulster.ac.uk/courses/course-finder/201617/management-8922" ]

}, {

"type" : "PromoteUrls",

"urlsToPromote" : [ "http://www.ulster.ac.uk/courses/course-finder/201617/management-8921" ]

} ],

"id" : "0d40fd70-8af3-4d41-b1ab-3619f005a9ce"

} ]

msheppard 2016-03-15 22:27:52 UTC #4

Ah, so 8922 and 8921 seem to be at the top of the results for http://www.ulster.ac.uk/courses/course-finder?query=management&f.Campus|campus=Jordanstownand http://www.ulster.ac.uk/courses/course-finder?query=management , just in different orders - When multiple actions are used, I don't think we guarantee anything about the order those actions apply (though perhaps we should in a future version).

Something you could try is combining the two PromoteUrls actions into one which lists two URLs to promote. That may make the ordering consistent (or it may be that the ordering is in fact not retained further down the stack as well).