Gulp. My mistake. Not appears to be completely broken for me.
RankScheme(0) just moved the erroneous results further down the pile.
Has anyone else experienced a broken NOT when indexing XML and using
MetaNames to query?
On Fri, 2005-02-11 at 13:09 -0800, Mark Maunder wrote:
> Firstly tip of the hat to the swish team - the new site rocks, and as
> usual so does the little miracle that it supports.
> I'm indexing using XML with metanames and
> IgnoreTotalWordCountWhenRanking no
> So when I do a query I'll do something like:
> job=(CEO not assistant)
> It looks like NOT is not notting when using RankScheme(1). I'm switching
> back to RankScheme(0) for now but I'm going to miss RankScheme(1)
> because the sizes of the chunks of text that I index vary wildly and I
> find that the larger chunks float to the top with (0).
Received on Fri Feb 11 13:22:59 2005