Settings and activity
25 results found
-
1 vote
Kara Reuter
shared this idea
·
-
7 votesKara Reuter
supported this idea
·
-
11 votesKara Reuter
supported this idea
·
-
5 votesKara Reuter
supported this idea
·
-
18 votesKara Reuter
supported this idea
·
-
13 votesKara Reuter
supported this idea
·
-
28 votesKara Reuter
supported this idea
·
-
18 votesKara Reuter
supported this idea
·
-
18 votesKara Reuter
supported this idea
·
-
4 votesKara Reuter
supported this idea
·
-
4 votesKara Reuter
supported this idea
·
-
9 votesKara Reuter
supported this idea
·
-
8 votes
An error occurred while saving the comment Kara Reuter
supported this idea
·
-
7 votes
The default sort is relevance based on hits in key indexes on the search terms. It would be a confusing experience for the end user if their search results were automatically sorted by 'most popular' by default. A post search sort for 'most popular' however would make sense and can be explored.
An error occurred while saving the comment Kara Reuter
commented
Yes, Margaret sums up the issue very nicely! For us, the Most Popular sort addresses this issue by surfacing the mainstream items that most people are mostly likely to be searching for.
An error occurred while saving the comment Kara Reuter
commented
Polaris PAC allows you to set your default sort order, and ours is set to Most Popular. Therefore, it's actually MORE confusing for our patrons who might do a search in our PAC and then get different results if they do the same search in our app. My goal is to provide a consistent user experience across all our library channels.
Ideally, the app would inherit configurations such as this from the PAC. Alternatively, it would be nice for the same configurations to be available in the app as are in the PAC.
Kara Reuter
shared this idea
·
-
23 votesKara Reuter
supported this idea
·
-
13 votesKara Reuter
supported this idea
·
-
7 votesKara Reuter
supported this idea
·
-
9 votesKara Reuter
supported this idea
·
-
32 votesKara Reuter
supported this idea
·
-
18 votes
An integration with Stripe Connect is planned.
Kara Reuter
supported this idea
·
.jpg){kind=link}
We are in a large consortium and sorting by location is actually quite helpful. But, when you toggle off sort by location, it appears that the fallback sort is by organization ID. This is completely opaque to patrons-- there's no way to infer the sort order from the list itself. Plus, sometimes branches for library systems are not adjacent / in sequence in the organization ID list, so this sort also ends up separating branches of library systems. An alphabetical sort would be immediately obvious to patrons and keep each system's branches together.