<html><head></head><body>I'll have a look on the plugin. For testing purposes I disabled tf/idf by changing the scoring method to replace (instead of multiply). Results were good but maybe I is not that, anyway I need a closer look on it.<br>
<br>
I will work on a fuzzyless version next week then and add German test cases step by step. Would be helpful if I can get your advice when I need some help. Maybe that's possible?<br>
<br>
If it is tricky and complex to summarise fuzzy and fuzzless results in one es query, maybe it is worth to try an alternative approach that came up in my mind: we can first query without fuzzy then with fuzzy and merge both results to a final result list. Nonfuzzy results in first, third, fifth place whist fuzzy results in second, fourth ... I'll give it a try. Same could be done with location bias.<br>
<br>
I would like to join you that weekend and it would definitely make sense, but exactly this weekend is difficult for me ;-(<br><br><div class="gmail_quote">Yohan Boniface <ybon@enix.org> schrieb am 09.06.2014:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k10mail">On 06/09/2014 03:15 PM, Christoph Lingg [mobil] wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">#2 search logic<br />This is a little bit a black box for me as I am not aware of the current state of yohan's work. Can you give an update and an outlook? How can one support you? I thought we might make a small sprint (1-2 days) so we can work on it together? Some komoot background: in komoot we still use a very old version of photon (still solr) and have some severe bugs (even some big cities cannot be found) I am keen to work on a search logic that resolves those bugs (a basic version is already satisfying in the first step maybe without fuzzy). So I can easily justify towards komoot to work on this some days.</blockquote><br />I'm in two weeks of Mozilla sprint, so no time at all until next <br />week-end for me.<br />Code side, the summary is that <br /><a
href="https://github.com/komoot/photon/tree/positivescoring">https://github.com/komoot/photon/tree/positivescoring</a> is the best search <br />logic we had.<br />But custom similarity is still not working.<br />And I think we will want it in any case.<br />So one think that you can do to help is to make the plugin work <br />(<a href="https://github.com/yohanboniface/elasticsearch-photon-similarity">https://github.com/yohanboniface/elasticsearch-photon-similarity</a>), <br />because we will need to take control of TF/IDF (basically, we don't want <br />it I think).<br />The other think is to add many search tests for Germany.<br />If there is hurry in the air, you can still remove the fuzzy part from <br />any of the branches, and the good results will magically grow ;) But <br />fuzzy is the current challenge ;)<br />I'm not sure I will work on photon next week-end, but for sure next week.<br />I'm planning a new sprint on photon in Paris on June 28/29th, on Mozilla <br />office,
could you join maybe?<br /></pre></blockquote></div></body></html>