Tech Blog Menu

You probably wondered how come a result is coming first and not the other when performing a query. Why is the search result ranked in a certain way and what can you do about it?

Coveo for Sitecore has been out for a few months now and we had to rethink the way we index search and of course, for us, support and maintenance people, the way we tackle the issues popping here and there.

If you’ve ever written a unit test in Java, you’ve probably used JUnit 4 and done something like this: public class CompanyTest { private Company company; @Before public void setup() { company = new Company(); } @Test public void getEmployees() { company.addEmployee("John"); company.addEmployee("Susan"); assertEquals(company.getEmployees().size(), 2); } } This is okay and gets the job done. However, I think there are some issues with this approach.

Recently, I’ve spent some time adding support for server-side scripts in Coveo’s Search API component. In a Coveo setup, the Search API provides the backend through which our JS UI framework executes queries on the index, using REST requests. Queries go through what we call the Query Pipeline. The Query Pipeline provides various ways to alter the query before it’s finally sent to the index server, and now offers scriptable extension points where you can implement complex custom logic when needed.