Announcement

**Ray** · Jun-10-2015, 03:47 AM

Difficult to comment without knowing:

1) Which version and build number you are using
2) Which script platform you are using
3) What the rest of your indexer configuration is (are you indexing 2 letter words such as "on"? what words are in the skip list? etc.)

So I'd say, to begin with, look at the above. Make sure you're at least using the final V6 release.

If there is any legitimate bug/problem (and not a configuration issue), then it would either be fixed in the V6 final release, or in V7. We won't be going back to the V6 code to fix any further issues. So if you still have problems, we would suggest upgrading to V7.

If the problem persists in V7 and we can verify that it is a bug, we would definitely look into fixing it with enough information to replicate the problem.

**voidinutah** · Jun-10-2015, 01:24 PM

1. We are using Version 6.0 Build 1029. Which looks like the final build.
2. We are using the CGI platform
3. The skip list is the default list and setting. Thus on, it, in, and, etc. are on the list. And the "Skip words less than:" is set to 2.

We're working on getting V7 set up.

**voidinutah** · Jul-20-2015, 09:15 PM

I wanted to give an update on this thread since we are now testing V7 Build 1023.

One of the configuration items to note is that we do have "Substring match for all searches" enabled.

If we disable this feature, which is the default for Zoom, then all skip words are ignored. But since our client wanted data returned when users typed partial words, such as "mult" for "multiple", we needed to enabled the substring matching feature. At that point skip words are no longer ignored when doing searches. It is at this point that the problem appears.

When the substring match is enabled and skip words are used, they need to be part of a string for the search to find matches. If you content index has only "and" and you search string contains "and" then nothing will be returned. But if the same content happens to have, maybe. the word "understand" and you search on "and", you will get results, because "and" is a substring in "understand".

However, I believe the issue I outlined above was a bug in V6 like Ray eluded to. Because even though there were words that contained the substring of skip word(s), it did not always bring back results.

In V7, this is functioning as expected. But now this can causes confusion. If some one has a specific statement to search for, with one of the words being a skip word, and there is no text on the page containing a substring of that skip word, you'll get no results. Such as "research and development" in V7 will return no results when no words contain "and" as a substring.

Now that we understand how the search works when substring match feature is enabled and that the bug has been fixed in V7, we can go back to our client with possible changes to configuration or adding work arounds.

Announcement

Search Term with Skip Words Result Not Consistent

Search Term with Skip Words Result Not Consistent

Comment

Comment

Comment