Hi,
well one of the coolest thing is that unlike DB-level proprietary full text engines you can tune your own notion of what "Relevance" should mean with quite a lot of flexibility. The default relevante is very nice, but in this applications you want to be able to hint the system about what you think your particular use case should return, what your users are expecting to find.
The default "Relevance" concept is not about the position of the terms being at the beginning of the text nor about lexicographical ordering, it's about the terms you are searching for are more frequently used in one text, how good they match, how far they are from each other (supposing larger natural text sentences); in case of more than one search term, you will get first the results containing most frequently both terms, and even a better score if the two terms are used near each other.
In the book you really want to take a look to chapter 12: scoring and boosting of results. It has code examples and lots of good explanations about how it's done and how to best tune it to your needs.
_________________ Sanne http://in.relation.to/
|