Gravatar for slangevin@coveo.com

Question by Simon, Jul 1, 2014 1:55 PM

Affecting relevance with Sitecore date field instead of Coveo sysdate field.

Hi,

Using Coveo for Sitecore, what would be the best way to ensure that the relevance score of a document is based on the Sitecore date field instead of the Coveo sysdate. I want to make sure that a fresh document, modified recently by my Sitecore author, is at the top of the pile.

Thank you,

Gravatar for mlaporte@coveo.com

Comment by Martin Laporte, Jul 2, 2014 3:24 AM

And why would the @sysdate field be set to any other value than the last modification date in Sitecore?

Gravatar for slangevin@coveo.com

Comment by Simon, Jul 2, 2014 2:54 PM

It is not, you are correct, but I wanted to add my own custom date.

1 Reply
Gravatar for lbergeron@coveo.com

Answer by Luc Bergeron, Jul 2, 2014 1:42 PM

I double checked this and the value of the @sysdate field corresponds exactly to the update date of the Sitecore item. Even if the index is rebuilt, the @sysdate field value doesn't change.

Is it possible that some custom processor updates the item during rebuild index/publish?

If you really want to set the @sysdate, you can implement a custom processor in the CoveoPostItemProcessingPipeline to override the ModifiedDate property of the CoveoItem.

Gravatar for slangevin@coveo.com

Comment by Simon, Jul 2, 2014 2:51 PM

To answer your first question. It is indeed the update date of the Sitecore item, not the crawling. I double checked after I saw your answer. I will try with the documentation here: https://developers.coveo.com/display/public/SC201406/Using+the+Coveo+Pipelines

Gravatar for klutz@absolute.com

Comment by krislutz, Feb 4, 2015 1:30 PM

which of these fields affects the relevance sorting? We have a pipeline that writes our custom date field to the coveoitem modified date, and to the sysdate however neither of these seem to affect the ranking. If we write the custom field to the updated meta (sitecore updated date) the format gets messed up as it seems to expect a different format then the other date fields.

Gravatar for slangevin@coveo.com

Comment by Simon, Feb 6, 2015 9:44 AM

Hi Kris,

The relevancy is not a field in such, but a combination of factors. Karel, product specialist of the platform core, wrote two great blogs about it:

http://source.coveo.com/2014/09/26/getting-the-most-out-of-relevancy/
http://source.coveo.com/2014/10/15/customize-ranking-with-qre/

Gravatar for klutz@absolute.com

Comment by krislutz, Feb 11, 2015 7:45 PM

I have seen both of those documents. querying for enablerankinginformation has never worked for us, maybe a limitation of the sitecore free version of coveo?

I could likely alter the results to suit our needs using a QRE to boost our custom date field and decrease the updated date field that coveo uses by defualt, however I was hoping there was just a way to tell coveo which date field should be used by devault when calculating relevancy rankings.

Ask a question