#community-help

Adjusting Result Item Numbering Across Pagination

TLDR A asked how to adjust numbering across pages of search results. Kishore Nallan suggested a CSS rule, while Greg advised using array indices or the start attribute. Jason referred to using __hitIndex in instantsearch.

21mo

Join the chat

Feb 05, 2022 (21 months ago)

Photo of md5-fe034fbff44e9cae037b7bb23a5080c4

A

11:35 AM

Q: The hits are always numbered 1..N..is it possible to take the page number into account? 20 hits per page, the first item on page #1 would be “1”, first item on page #2 would be “21" …the current fixed 1..N numbering is counter-intuitive.

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

11:50 AM

👋 We don't number the hits in the API responses. Can you post a snippet or screenshot to show that?

A

01:29 PM

Example: https://github.com/zopyx/zopyx.typesense/blob/master/src/zopyx/typesense/browser/static/app.js

01:30

A

01:30 PM

http://dev2.zopyx.de:8081/Plone/typesense-search

Kishore Nallan

01:30 PM

Ah, you mean the numbers always starting with "1" in the UI even when I click on page 2, 3, etc.?

A

01:31 PM

yes

Kishore Nallan

01:32 PM

I see the HTML is being rendered using <li> -- that explains those 1 to 10 numbering.

A

01:32 PM

using an outer ordered list

Kishore Nallan

01:34 PM

You can probably add a CSS list-style: none rule to remove that numbering, but Jason might have an alternative approach here.

Photo of md5-cc95589a5ca309cc60c36b7e901d749b

Greg

02:52 PM

Or use ul (unordered list) instead of ol (ordered list).

02:54

Greg

02:54 PM

If you retain all the results in memory (page #1, #2, #3, etc) then you could likely use the array index to apply the numbering yourself even with techniques like virtualization (windowing).

02:55

Greg

02:55 PM

(or something like pageNumber + index + 1 if you don't)

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

03:00 PM

It looks like instantsearch might have a way to manage ordering like what Greg mentioned using __hitIndex. Could you try this out: https://www.algolia.com/doc/api-reference/widgets/hits/js/#widget-param-item

Photo of md5-d3a4ca49ba4aeb3b9d0cb7d846eb0989

CaptainCodeman

04:09 PM

if the numbering is coming from an <ol> element there is a start attribute that lets you set the number sequence starting point

Typesense

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

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

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

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.

19mo

Hiding Exact Hits Number in Typesense and Utilizing `out_of` Field

A sought a way to hide exact hits count in Typesense. Kishore Nallan clarified about the `out_of` field, its future use, and suggested using `found` for scrolling. Jason offered a solution to hide the count by modifying the item template.

30mo

Range Filtering and Faceting Discussion

Phil asked about the requirements for range filtering, which Jason explained does not always require faceting. Discussion about different possibilities with Algolia and Typesense ensued, resulting in Phil successfully utilizing the 'Configure' widget.

25mo

Querying with Typesense-Js and Handling Null Values

michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.

15mo