#community-help

Promoting Curated Products Across Pages with Filtering

TLDR Stefan wants to promote 1-2 curated products per page while filtering user facets. Kishore Nallan suggests using pinned hits and confirms their non-duplication in results. Stefan considers a second request to show the best matching product.

Powered by Struct AI

1

Mar 14, 2023 (9 months ago)
Stefan
Photo of md5-d6c265b4792dbf0a1d6ae378f39d8736
Stefan
02:45 PM
Assuming you'd want to promote 200 products, but you only want to have 1 or 2 curated results per result page (chosen randomly). What would be the best way to approach this?

I think curation doesn't support this use case right now. I guess I will have send a second query and pull the result out like that?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
02:46 PM
You can use pinned hits if you want more flexibility?
Stefan
Photo of md5-d6c265b4792dbf0a1d6ae378f39d8736
Stefan
02:47 PM
I'd still want them to be filtered out in case the user selects facets
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
02:48 PM
Ok got it, it will be an interesting to see if we should support filtering on pinned hits as well.

> but you only want to have 1 or 2 curated results per result page (chosen randomly)
The random part is the one that is not possible right now? Otherwise if you know your pagination order, you can still choose results at positions across pages.
Stefan
Photo of md5-d6c265b4792dbf0a1d6ae378f39d8736
Stefan
02:50 PM
Hmm didn't think about that, I can just spread them randomly across pages.

Could it then happen that let's say product X is the best token match, but I randomly assigned it position 100, will it be shown twice or on page 10?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
02:51 PM
We currently have a "slide up" behavior where if you set position 100 but only 50 results are found, then it will just appear at the end.
02:52
Kishore Nallan
02:52 PM
Products that are in curated list is guaranteed not to duplicate in results even if that hit is picked naturally.
Stefan
Photo of md5-d6c265b4792dbf0a1d6ae378f39d8736
Stefan
02:56 PM
hmm so I might "mess up" my search results doing it like that, for example I search for "ITEM XX"

user searches for "ITEM XX", but it's pinned at pos 20

then "ITEM XX" would be shown at position 20 and before it would be:

"ITEM XA", "ITEM XB" etc.., correct?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
02:57 PM
If you pin an item at position X then yes it won't appear higher even if the original ordering places it higher in the hits.
Stefan
Photo of md5-d6c265b4792dbf0a1d6ae378f39d8736
Stefan
03:01 PM
feels like a second request makes more sense, this way I can always choose the best matching product

1

Typesense

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

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Implementing Result Pinning in Typesense Product

Sai questioned about implementing result pinning in Typesense for a product. Kishore Nallan provided several resources and explanations to assist, ultimately suggesting the use of 'sort_by' to promote groups of objects based on an attribute.

1

15
30mo

User-Specific Tagging and Filtering in UI

bnfd asked for the best way to create user-specific tags available on the UI. Jason suggested using personalized filters and creating a separate collection for each user's movies. The duo clarified the use of 'tags' in schemas and the refinementList widget in instantsearch. They also discussed various approaches to import and search large document collections.

1

46
29mo

Resolving Typesense Result Issue in Document Collection Queries

Mike was encountering errors when searching for specific query in their Typesense document collection. Jason suggested it may be due to the `drop_tokens_threshold` setting. There was a misunderstanding but after further explanation from Jason, Mike understood and decided to continue the conversation via email.

1

19
22mo

Performance Characteristics of Filtering Search Results

Oskar queries the performance difference in filtering search results. Jason clarifies how filters work and provides performance improvement suggestions like increasing vCPUs and sharding the collection. Kishore Nallan explains filter IDs and document ID matching. The thread concludes with discussions on performance tradeoffs in filter implementation.

33
15mo

Implementation and Optimization of 'Similar Products' Feature

Stefan is considering using "curation" for pre-calculating similar products. Kishore Nallan suggests using preset API, but Stefan raised an issue with sorting based on non-stored values. The issue remains open for resolution.

3

26
18mo