Developer forum

Hi Kurt,

Does your search parameter take a string[] (array) or a string? What you show on the setup seems accurate, and you can definately do that with Lucene.

I am assuming that "fitting with safeseal" is the Product Name or Synonym field.

Best Regards,

Nuno Aguiar

Hi Nuno,

My search parameter takes a string array (string[]).

I haven't got any products with the product name "fittings with safeseal" though - only "fittings, safeseal".

Best regards
Kurt

Hi Nuno,

Regarding search variations, I also need the search to return the product number 71.9923.610, when searching for 719923610 or 71 9923 610.

I've looked into the ability to create my own list of stop-words (with the file stopwords.txt in the Repository-folder), but don't know if that's the way to go.

/Kurt

Hi Nuno,

No, it doesn't work with a single word either, but will try your suggestions.

Regarding your suggestion with the IndexBuilderExtender, it sounds like the way to go.

Thank you very much.

--
Best regards
Kurt

I've made the changes, but without any luck.

I've searched for "fittings with safeseal" and the query is like this: +Active:True +((+Freetext:fittings* +Freetext:safeseal*)) +(+*:* -(+(+ID:prod*)))

The site-language is Danish though and when making a search for the danish terms "fittings med safeseal", the word "med" is added to the query too, as this is not a stopword.

/Kurt

So you are trying to find products that does not have a product id that starts with "prod" and that is case sensitive...?

with is left out of the search becauase it is a stopword.

Yes, correct Nikolai - don't see the case-sensitive part though

Well, got it working now, if I use my own file stopwords.txt containing "med".

@Nikolaj, if I want to use a custom list of stopwords like above, do I need to include the default ones as well or are they implicit?

/Kurt

Hi Nuno,

Do you have an example of how to use the IndexBuilderExtender?

I cannot find any examples in the community or the docs.

/Kurt

Perfect, thanks :)

/Kurt

I've made an IndexBuilderExtender, compiled it and put it into the bin-folder. After building the index, the new field is not present in the index, if I inspect it in Luke. Shouldn't it be?

My code is show below:

    public class ProductIndexExtender : IIndexBuilderExtender<ProductIndexBuilder>
    {
        public void ExtendDocument(IndexDocument indexDocument)
        {
            if (indexDocument.ContainsKey("Number"))
            {
                string productNumber = (string)indexDocument["Number"];

                productNumber = productNumber.Replace(".", "");

                if (!indexDocument.ContainsKey("ProductNumberCustom"))
                {
                    indexDocument.Add("ProductNumberCustom", productNumber);
                }
                else
                {
                    indexDocument["ProductNumberCustom"] = productNumber;
                }
            }
        }
    }

Well, it doesn't change much, I'm afraid - the field is still not present in the index shown in Luke.

Maybe you placed the dll in the wrong /bin?

Just checked again to be certain, but it is the correct folder :)

Hi Kurt,

You have to manually add a field in the index. Here's how to do it

https://www.screencast.com/t/UupG8NPgRaJi

Best Regards,

Nuno Aguiar

A strange thing is, that if I omit the check for the key "Number" in the IndexDocument, the field is populated into the index:

           if (!indexDocument.ContainsKey("ProductNumberCustom"))
            {
                indexDocument.Add("ProductNumberCustom", "1234");
            }
            else
            {
                indexDocument["ProductNumberCustom"] = "1234";
            }

But as soon as I add the check for the Number-field in the IndexDocument, it is not populated:

            if (indexDocument.ContainsKey("Number"))

Hi Nuno,

I've already done this :)

/Kurt

Well, I've found the reason for this. The "Number" field is not called this, but instead called "ProductNumber" :)

/Kurt

I see, on the IndexBuilderExtender. Good catch. Hope the next ones are easier