#community-help

Customizing Count References and Range Boundaries in Instantsearch

TLDR Vishal asked how to change count references and implement range bounds in Instantsearch. Jason suggested custom widgets and setting up attributes during indexing for these tasks.

3mo

Join the chat

Jun 26, 2023 (3 months ago)

Photo of md5-178450ab9171fe1c7eba3a5eb7e1a312

Vishal

03:50 PM

For your demos I noticed that the counts are all consistent with the primary search term, in this case commits, is there a way to make the count reference something other than the primary search?

Image 1 for For your demos I noticed that the counts are all consistent with the primary search term, in this case commits, is there a way to make the count reference something other than the primary search?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:05 PM

If you’re using Instantsearch UI library, I don’t believe this is possible to do. But if you’re building your UI, then you can facet on any field as needed

Vishal

04:07 PM

I'm using Instantsearch -- ok

04:27

Vishal

04:27 PM

do you know if you can easily range bound it?

Jason

04:27 PM

May be there’s a way to build a custom widget to do that… and also make it a static bounded list if needed

04:28

Jason

04:28 PM

https://www.algolia.com/doc/guides/building-search-ui/widgets/create-your-own-widgets/js/

Vishal

04:28 PM

eg lets say you want the various sort choices to be ranges rather than values

Jason

04:28 PM

Ah that type of range… for that you would have to setup an attribute which defines the range in your dataset at indexing time

Vishal

04:29 PM

ok -- can't bucketize in the ui layer?

Jason

04:29 PM

No unfortunately

04:29

Jason

04:29 PM

For, eg in this demo: https://songs-search.typesense.org/?s%5Bquery%5D=Annie%27s%20song%20Denver

Notice how the release year shows up in the UI, and in the dataset (browser dev console network tab - look for multi_search). There’s both a Unix timestamp and also a release_decade

Vishal

04:30 PM

ahh

04:31

Vishal

04:31 PM

Typesense

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

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Resolving Issue with Instantsearch Sort_by in React

Edward had a problem with sorting functionality in a React component using Algolia's InstantSearch. Jason recommended a potential solution for specifying index names which resolved the issue.

15mo

Troubleshooting Typesense Setup and Understanding Facets and Keywords

Demitri encountered errors when exploring Typesense for the first time. Jason guided them through troubleshooting and discussed facets, keyword settings, and widget configurations. Helin shared a Python demo app and its source code to help Demitri with their project.

18mo

React Instant Search Range Slider Issue and Alternative Solutions

Lukas voiced concerns and issues regarding React instant search range slider. Jason suggested a custom range slider, custom code, and using typesense-js directly as potential alternatives and solutions.

16mo

Resolving 'stores_count' field sorting issue in Schema

em1nos encountered an issue sorting the 'stores_count' field, which was due to a field disparity in multiple collections. Upon resolving that, a subsequent issue with instant search internally managing sorting came up, which Jason addressed by releasing an updated version of the adapter.

26mo

Resolve Facets and Sorting Issues with Typesense

Ethan needed assistance with getting all facet values and sorting results by date using Typesense. Jason provided guidance on how to use Typesense properties to accomplish these tasks, and resolved issues related to specific use-cases provided by Ethan and Rushil.

2mo