How the custom rankingexpression work internally
Hi, Can some one explain how the custom rankingexpression work internally in the following scenarios? I am applying custom ranking based on @syscollection and @sysfiletype using script inside CoveoSearch.ascx.
Scenario #1: Same document gets higher rank (+100) based on the @syscollection , but gets smaller rank (-90) based on @sysfiletype attribute. Now what will be the final rank of this document?
Scenario #2: Same document exists in two collections (due to some requirements) and the same document gets higher rank based on one collection, but gets less rank based on another collection. Now what will be the final rank of this document as duplicates are removed, which document will be removed?
For scenario #1, the modifiers for a QRE are added, so the final "score" or your document would end up being 10. That's only a part of the final score used for ranking when using default Relevancy sorting, though. Other factors such as query keywords might impact ranking.
For scenario #2, the duplicate filtering feature always keeps the highest ranking result, so that's the one you should see.
Hi, Thanks for the reply. What if the same page gets rankings like 100 and 80. will the final ranking be 180? What is the range for ranking?