Confusion about 'Token Equals' in Matching Rules

[former_member496675]

Hi,

I am creating a rule that matches values of a single field. I have set this rule to 'Token Equals' function. However, interstingly if this field has numbers like

10-31860

31860-10

the matching strategy does NOT return a matched result.

But if the field has values like

UPC-OSD

OSD-UPC

the matching strategy returns PERFECT match.

What's going on here. Why 'Token Equals' treating numeric values differently than the text values? How can we change this behavior if possible?

Regards,

-Y

[former_member189059]

hello

this is what i can get about token equals

1. Token comparison (word order not important)

2. Fuzzy match on each of the tokens of the field

3. Returns Success, Partial Success, Failure or Undefined score

a Uses the keyword parsing, which enables matching to use existing keyword indexes

b Score = Success * Number of Unique Matching Tokens / Total Number of Unique Tokens