#community-help

Comparing Text Match Scores Across Separate Collections

TLDR Maximilian inquired about comparing text matching scores between collections. Kishore Nallan explained that scores are based on string similarity. They acknowledged an issue with scoring inflation and are working on a solution.

19mo

Join the chat

Mar 30, 2022 (19 months ago)

Photo of md5-d866f36ff951bfe0aae996ac8a2a5024

Maximilian

09:20 AM

Hi, I have a question about matching score. Let's say I have two collections, categories and brands. Is there a way to know in which collection the same word has higher matching score / relevance? Or if I have a collection of products and every product has a category and a brand, is there a way to know in which field the searched word has higher score?
Thanks

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

09:37 AM

You can compare the text match score returned for each result across two different searches, one searching category and the other brand.

09:38

Kishore Nallan

09:38 AM

And re-sort results client side using that.

Maximilian

09:41 AM

ok so the matching score is reliable when comparing two different collections?

Kishore Nallan

10:11 AM

Yes it is computed on string similarity so can be used.

Maximilian

10:17 AM

ok. I see that if I include two fields and the searched text is present on both fields, the score is much higher. So maybe it's better to compare only one field at a time.

When there are more words, it would be very useful to know which word matched what.

If I search for a category and a brand, it would be useful to know if a word is matched as a category or as a brand. At the moment we have the snippet that shows what was matched, but if the word is different (like plurals or a typo) it's impossible to get the matching word.

10:19

Maximilian

10:19 AM

so for instance "smartphone apple iphone" could be matched as
smartphone => category field
apple => brand
iphone => product name

Kishore Nallan

10:40 AM

I'm actually fixing this issue of score inflation caused by the same word matching multiple times, which will help here. I'll have a preview to show next week.

Maximilian

10:43 AM

great!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2786 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Issues With `text_match` Scoring for Search Queries in Typesense

Colin encountered issues with the `text_match` scoring on Typesense v0.23.1. Jason and Kishore Nallan identified a potential issue with numeric overflow in the text match score and applied an unverified patch. The final resolution is unclear.

15mo

Understanding Rank Fusion Score in Typesense's Multi-Search

Ayush had queries about comparing `rank_fusion_score` across collections in Typesense's hybrid search. They were explained and clarified by Kishore Nallan on how the score works and how it could be manipulated for their use-case.

1mo

Collating Search Results from Different Collections.

Patrick inquired about collating search results on different collections based on text_match value. Jason confirmed it's possible, but must be done client-side.

16mo

Discussing Schema Design Best Practices and Splitting Collections

Janaka inquired about resources for schema design and collection splitting. Kishore Nallan advised that splitting should occur for distinct entities and recommended client-side merging and sorting using text match score.

26mo

Combining and Sorting Search Results from Two Collections

Toyin asked about combining and sorting search results from two collections. Kishore Nallan confirmed that `text_match` could be used for this purpose.

30mo