Allow users to choose how many results to see
With a lot of online retail sites, users are able to choose how many search hits they see per page.
Would this be a helpful addition to Primo?
After all, since the new UI was introduced, the subject of infinite-scrolling vs paging has been contentious amongst Ex Libris customers. It has already led to the addition of the 'Next Page' widget.
Allowing users to choose how many hits they would like to see might take a lot of the debate from us, and put the decision directly into the hands of the end user.
Thank you for this idea, we plan to let the user set the number of results to see per page and in addition to replace the behavior of the “Load More Results” in the brief results with pagination. With this – the more results per page and the pagination we will make sure to keep the performance.
On the roadmap for 2021H1
Katie Utschig, SWITCH Library Consortium commented
I would also request that this behavior affect the My Favorites page. I just recently heard someone complain about having to page through their pinned results and opine how much nicer it would be if they could just have more of them load from the start.
François Renaville commented
Great! Will the new feature only be effective for search results? It would be nice if Ex Libris would consider this globally and make it also working for Collection Discovery, eShelf, Journal Search and Database Search records, if the setting for the number of records would be effective everywhere, whatever the Primo page/context...
> We're looking forward to seeing the new Roadmap for 2021 in January.
Me too ;-)
But will the browser icon remain?
Hi Lars, Nili explains more about it starting around 38:30.
A user will be able to personalise results at 10, 25 or 50.
At the moment, choosing Load More Results adds more results to the bottom of the list, and keeps all results on screen, which affects performance.
Instead, the next load of results will replace the current set.
So, if a user has the page load set to 50, then initially they will see No.1 to No.50.
If they go to the next page, then the results will show No.51 to No.100.
In the sneak peak for Primo BO and VE Q2 2021 it says: "Increase numbers of results per page and replace Load More results with pagination":
I wonder what this update exactly will include? At least this idea is not Under review yet, so I don't know what to expect. Will infinite scrolling really disappear?
M Schewender - A few items were pushed back for 2020. We're looking forward to seeing the new Roadmap for 2021 in January.
'Enable user to set default number of results per page' is/was planned for 2020H2
I do agree with you. The possibility with pagination to set 10, 20, 30 hits etc as a default by adm and configurable by the user should also be considered here.
I also support more options in this area.
It was quite a loss of personalisation on the New UI, whereas the Classic UI gave the configuration option to set number of results per page (we had 20), and then users could set themselves in their My Account settings to 10, 20, 30, 40, or 50.
We get comments from users pretty often that they hate having to click Load More Results constantly, and that 10 is much too few a number.
There is the real performance issue though that the New UI slows down so considerably once there are a few hundred results on screen, so loading more endlessly may not be a good solution (unless this performance can be improved of course).
The only way to jump pages now is by changing the offset in the URL, but there is a limit of 2,000 in a blended search, and it will sometimes error out.
We had a client query just last week asking after any options in this area, because they had painstakingly worked through a results set up to Page 80, and then accidentally clicked a feature which reset the search back to Page 1. It is extremely limiting that the pagination widget only allows for advance 5 pages from Page 1, but then only 2 pages once you're past page 1.
Lisa Hatt commented
This should always be an option controllable by the user, whether because of a simple preference or because the device/browser they are using can't cope with a page that grows and grows. (In other words, an admin may choose a default, but the user should be able to choose otherwise.) Infinite-scroll-only cuts off access to later search results.
If I am thinking of the correct page element by the "scroll button" (because it is on the right for me - probably depends on positioning of the sidebar?), this does not provide adequate access to pagination, because you cannot enter an arbitrary page number and can only navigate in two-page jumps in either direction. Probably most users would not really page (or scroll) through all the results in a very large set, but what about simply jumping to the end? Currently can't be done.
Infinite scrolling (with or without load more) is not a good solution from a stricter accessibility perspective and certainly not in combination with the scroll button. Primo has both infinite scrolling from the bottom search result list with the button "Load more results" and a scroll button in left bottom. That scroll button doesn't work in Safari with newer MacOS and it's registered as a bug.
1. Make it optional to the library administrator to choose between: infinite scrolling or scrolling by pagination (with option of number of hits per page) and with or without scrolling button to the left.
2. Make it optional to the user in the account settings to choose between: infinite scrolling or scrolling by pagination (with option of number of hits per page) and with or without scrolling button to the left.
Some make a difference between infinite scrolling and a load more button. Here, wether you agree or not, I treat Load more button as a type of infinite scrolling.
Natasha Stephan commented
That idea has a number of votes as well...
Moved to second half of 2020, see PDF link here https://knowledge.exlibrisgroup.com/Primo/Product_Materials/Roadmap
Shanyun Zhang commented
What is the status for this? Is this available to Primo VE users as well? It is January of 2020 now, but I don't see this option for our users.
Is on the Roadmap for second half of 2019.