Add Jump to Last & Specific Page Options to Primo Search Results Paging Bar
Our users are asking for the option to jump to the last page of the search results in Primo. They would also like to get to a specific page number in the Primo search results paging bar by typing the number in there. First and last page options are basic functionalities of pagers and users expect those.
This idea was reviewed and discussed in the past also as part of the NERS evaluation. In the last few years we did few improvements to the pagination area to increase the visibility of the results. We do support now option to jump to specific page number up to the limitation of number of results to show, however the ability to jump to the last page is not in our roadmap.
therefore we have decided to close this idea and release your votes.
-
Susan Chakmakian commented
We would still be interested in the option to type in a specific page number in order to jump directly to that page of search results in Primo VE (and that exact capability is currently available for navigating search results in Alma).
-
Manu Schwendener commented
NERS 7987, open for voting now
-
Lydia Herring commented
The recent changes to paging haven't addressed two main issues. We would like the ability to jump to a specific page of search results. Currently, users can only select pages in a five-page range around the current page of search results. It would be much more useful to be able to select a specific page of search results and to be able to go to the first and last pages of results. Paging forward and back a page or two at a time is extremely cumbersome.
-
Manu Schwendener commented
> Allow libraries to increase the results displayed to load 25 or 50 results at a time.
-
Manu Schwendener commented
While some (but not all) of the points mentioned here are solved by now, I'd also like to point to https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/42566068-add-very-compact-display-option-1-row-per-title
If there was a much more compact additional display option, a lot of the problems with getting through long result lists would be less painful.
-
Anonymous commented
Any comments from Ex Libris on this? status has not changed for 3 years now...
This feature is especially necessary now since there are currently severe performance problems with the paging functionality and loading of results takes very long after page 4.
If users want to go through e.g. 300 results, this is almost not possible without crashing tabs/Browser. -
Anonymous commented
Our users would like this functionality for skipping through saved searches.
-
Katey commented
I'm also interested in having page numbers instead of "Load more results".
-
Anonymous commented
Related - Allow libraries to increase the results displayed to load 25 or 50 results at a time.
-
Anonymous commented
I can't vote anymore so am leaving comment. I LIKE this idea.
-
nst commented
Hi, Nili
You asked for a usecase:
Since we have no option to sort authors descending' (Z-A) it would be really helpful for the user instead of paging through many pages.Best regards, nst
-
Ann Kucera - Central Michigan University commented
I can see this being useful for a certain type of search. If there are 17 million results retrieved, however, I don't see the point. What if only searches with 1,000? or 10,000 or less results had the capability for this type of navigation?
-
Stacey van Groll commented
The biggest use case for me for improving the pagination functionality is simply speeding up navigation through a list of results in the UI.
As Blake has noted, we're currently limited to jumping 2 pages at a time in either direction at most.
If you're reviewing a list sorted by Date-newest, and you want to skip through some content quickly, it would improve the user experience to offer the ability to click on the Page circle in the widget and, instead of the current X, have a text field where you can type a page number such as 10, to immediately go to Page 10.
The X is irrelevant anyway given the display closes itself if you click anywhere else on the screen.
At the moment, if you're on Page 1, you have 1st click on the circle, 2nd click on Page 5, 3rd click on the circle, 4th click on Page 7, 5th click on the circle, 6th click on Page 9, 7th click on the circle, and finally 8th click on Page 10.
And, yes, you could also use the Date Range filter, but until you start doing a quick review of the results, you might not have a sense yet of what sort of date range you're looking at with the results of your search query. Our stats show that most users only use a couple of filters per session as well, and there should be other options (such as a good and useful pagination widget), over many facet selections.
Improving the pagination widget to offer better page jumping functions would also help the performance of page loading in general. If users ignore the widget and click many times instead on Load More Results, by the time you get to page 10 or so, the speed of navigation and jerkiness of display starts to be obvious, because Primo is displaying so many results on screen at once and it simply can't handle it well.
This is a prime benefit of using the pagination widget instead, as it loads the one page of content and starts the user off again at that point, which Primo clearly can handle better.
I have noted that many of our staff don't even know that there is an option to click on the Page Number circle by the way, and are missing even the existing jumping options, so better indicative design there would be a good thing also. -
Blake Galbreath commented
One use case might be that a patron has a long list of results that they can't check all in one go. So, they look at results 1-100 today, 101-200 tomorrow, 201-300 the next day, etc. No one wants to scroll through every page, or use the awkward skip-2-pages-at-a-time method that Primo currently offers, to get farther into the results list.
Also, you can sort by Relevance, but not Non-Relevance, Author AtoZ, but not Author ZtoA, Title AtoZ, but not Title ZtoA. There are times when a patron would want to start at the end of a list and work their way to the beginning.
Another way to look at this: this functionality already exists in Alma, and it is super helpful!
-
We would like to understand better the use cases of jumping to the last page. can you please be more specific with the needs and user workflow.
-
Anonymous commented
Yes, please! It's one of the biggests issues users have with Primo.
-
Kitty Mackey commented
This is a very, very basic feature! Please add it!