Try our conversational search powered by Generative AI!
AI OnAI Off
AutoBoost and the "Age" property used in Decay?
Hi Magnus,
I found when using this myself the Published Date seems to be the property that affects auto boosting, which would make sense as its boosting the "freshness"of content.
Oct 12, 2017 18:06
Hi
And thanks to finally get some answer in this thread :)
Since we didn't get an answer we wen't along and skipped the autoboost and went with a multiple sorting algorithm instead which works OK for now, but good to know if we need to look at this again.
Best Regards Magnus
Edited,
Oct 12, 2017 21:41
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
In the documentation for AutoBoosting (http://world.episerver.com/documentation/developer-guides/find/NET-Client-API/searching/auto-boosting/) it states that a document is Decayed using the Age of the document.
"Normally, the date value is the document age or updated date value, and the fixed point in time is the search time."
My question here is, since the whole feature of Decay is based on this value, what actual property of the Content is read? Is it the SavedDate, or ChangeDate or CreatedDate? Or even PublishedDate?
In our solution we have a custom Content object that implements the two IContent, IChangeTrackable and currently I am setting the "CreatedDate" but not seeing any difference in scoreing. Do I also need to .Track() when using decay? Or do I need to implement and set some other interface on my custom indexed object?