Hi Jeffrey:
The test I did was to type in a whole bunch of events and type text
into the text control at the bottom of the detail view. I don't
remember exactly how many Items I tested, but it was less than 10
events. I just tried it again with different text. I created the
following items in the following order:
1 John 2 Anderson 3
John Anderson2
asdf asd fasd John asdf asdfasdf Anderson aasdf asdf asfd sadf
test 2 John Anderson test 3
John Anderson
Lucene returns them in the following order:
John Anderson
1 John 2 Anderson 3
test 2 John Anderson test 3
asdf asd fasd John asdf asdfasdf Anderson aasdf asdf asfd sadf
John Anderson2
So in my two trivial tests it seemed useful. Maybe we index titles
differently from the body text. But like I said earlier, I'm not sure
we should conclude the general usefulness or complete lack of it by
such small tests. Leaving it in for Preview would let us get feedback
from users about it's usefulness, and it doesn't get in the way of
using Chandler.
John
On Feb 7, 2007, at 12:12 PM, Jeffrey Harris wrote:
Hi John,
Consider this situation: Suppose you are looking for items by
searching
for "/Search John Anderson". Lucene returns all the items with the
word
John followed by the work Anderson with a higher rank than all the
items
with words between John and Anderson. This can be a really handy
feature.
If this worked well, I'd be in favor of having relevance sort in
Preview. I tried the specific use case you mention, though, and found
that the search results continue to defy my expectations, which I
think
undermines the argument.
If this is easy to fix, great, but if it's not, lets get it working
well
after Preview.
Sincerely,
Jeffrey
<find_results.PNG>
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
