Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like you are catering for a corpus with searches that you need to match very loosely?</p> <p>If you are doing that you will want to choose your fields and set different boosts to rank your results.</p> <p>So have separate "copied" fields in solr:</p> <ul> <li>one field for exact full name (with filters) </li> <li>multivalued field with filters ASCIIFolding, Lowercase... </li> <li>multivalued field with the SynonymFilterFactory ASCIIFolding, Lowercase... </li> <li>PhoneticFilterFactory (with <a href="http://en.wikipedia.org/wiki/Caverphone" rel="nofollow noreferrer">Caverphone</a> or <a href="http://en.wikipedia.org/wiki/Double_Metaphone#Double_Metaphone" rel="nofollow noreferrer">Double-Metaphone</a>)</li> </ul> <p><a href="https://stackoverflow.com/questions/1419882/enabling-soundex-metaphone-for-non-english-characters">See Also: more non-english Soundex discussion</a></p> <p>Synonyms for names, I don't know if there is a public synonym db available.</p> <p>Fuzzy searching, I've not found it useful, it uses Levenshtein Distance. </p> <p>Other filters and indexing get more superior "search relevant" results.</p> <p>Unicode characters in names can be handled with the <a href="http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.ASCIIFoldingFilterFactory" rel="nofollow noreferrer">ASCIIFoldingFilterFactory</a></p> <p>You are describing solutions up front for expected use cases.</p> <p>If you want quality results, plan on tuning your <a href="http://www.lucidimagination.com/Community/Hear-from-the-Experts/Articles/Search-Application-Relevance-Issues" rel="nofollow noreferrer">Search Relevance</a></p> <p>This tuning will be especially valuable, when attempting to match on synonyms, like MacDonald and McDonald (which has a larger Levenshtein distance than Carl and Karl).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload