| exact string search vs neighbouring words with FoxtrotPro Version 6.6 build 1926 [message #824] |
Tue, 27 November 2018 05:38  |
kridrD
Messages: 10
Registered: September 2015
|
Junior Member |
|
|
Hi All,
Has anyone noticed that the exact string search does not necessarily
deliver?
When I search my archive for a two word string, a consecutive word search
gives 135 hits, one for neighbouring words set to the stringest condition
yields 144 hits, while a search for exact string only results in 45 hits
while throwing up an error message "The index does not store document
textual contents". All indices are set to store document textual contents,
I checked them again to make sure.
Consecutive word search 135
Neighbouring words 144
exact string 45
Has anyone noticed any problems with the exact string search?
Kind regards
Dirk
|
|
|
|
| Re: exact string search vs neighbouring words with FoxtrotPro Version 6.6 build 1926 [message #825 is a reply to message #824] |
Tue, 27 November 2018 09:36  |
FoxTrot Engineering
Messages: 384
Registered: April 2020
|
Senior Member |
|
|
kridrD wrote:
> When I search my archive for a two word string, a consecutive word search
> gives 135 hits, one for neighbouring words set to the stringest condition
> yields 144 hits
This is normal, as searching for neighboring words [foo bar] with the smallest distance may find "foo bar" as well as "bar foo".
> while a search for exact string only results in 45 hits
This may also be correct, if not set to ignore case, punctuation etc.
> while throwing up an error message "The index does not store document
> textual contents". All indices are set to store document textual contents,
> I checked them again to make sure.
You may search each of your indices, one by one, until you find which one(s) produce this error; then you can try rebuilding this index. Let me know if that does not fix the problem.
Jérôme - CTM Engineering
------------------------------------------------------------ ---------
"I want to thank you for writing FoxTrot Pro and Personal; they are
fabulous applications. I use Professional, but I demoed Personal
to my wife last night; after less than 30 seconds, she said "I'll
buy it."
FoxTrot Professional Search user comment
Download a demo version from www.foxtrot.ch
------------------------------------------------------------ ---------
Jérôme - FoxTrot Engineering
|
|
|
|
| Re: exact string search vs neighbouring words with FoxtrotPro Version 6.6 build 1926 [message #826 is a reply to message #825] |
Tue, 04 December 2018 23:16 |
kridrD
Messages: 10
Registered: September 2015
|
Junior Member |
|
|
Hi Jerome,
I found the index and rebuilt it, which took about a week. It is 11 GB.
There no interruptions at all while rebuilding ie. the machine kept running
day and night until finished.
The problem persists. The error message pops up when searching for an exact
string and it is the same index again, as it does not pop up when that
particular index is not selected.
Search Results for a species name as genus species, which should always be
in that sequence
Exact string 646
Consecutive words 1482
Neighbouring words 1486
All the other indices are smaller, the largest of these being 3.6 GB
Has the size of the index something to do with it?
Kind regards
Dirk
On Tuesday, November 27, 2018 at 7:06:53 PM UTC+10:30, FoxTrot Engineering
wrote:
>
> kridrD wrote:
>
>> When I search my archive for a two word string, a consecutive word search
>> gives 135 hits, one for neighbouring words set to the stringest condition
>> yields 144 hits
>
> This is normal, as searching for neighboring words [foo bar] with the
> smallest distance may find "foo bar" as well as "bar foo".
>
>> while a search for exact string only results in 45 hits
>
> This may also be correct, if not set to ignore case, punctuation etc.
>
>> while throwing up an error message "The index does not store document
>> textual contents". All indices are set to store document textual
> contents,
>> I checked them again to make sure.
>
> You may search each of your indices, one by one, until you find which
> one(s) produce this error; then you can try rebuilding this index. Let me
> know if that does not fix the problem.
>
>
> Jérôme - CTM Engineering
>
>
> "I want to thank you for writing FoxTrot Pro and Personal; they are
> fabulous applications. I use Professional, but I demoed Personal
> to my wife last night; after less than 30 seconds, she said "I'll
> buy it."
> FoxTrot Professional Search user comment
>
> Download a demo version from www.foxtrot.ch
>
>
>
>
|
|
|
|
] 
FoxTrot Search Forum
Search
Help
Members
Register
Login
Home
