Relevancy sorting in FRBR version list display should use terms searched
FRBR groups and the display of versions within them does not consider the relevancy of the terms searched. Often a user is searching for a specific version within the FRBR group (ex: Homer's Iliad translated by Richmond Lattimore) but there is no way to focus in on this version within the list of FRBR versions. Even when users search specifically for terms: Iliad Lattimore, Lattimore is hidden within search results. Within the list of FRBR versions, sorting by Relevancy should use the terms searched by the user -- this should enable the works of a single translator (like Lattimore) to rise to the top of the list of results when that translator's name is explicitly included in the search, greatly improving discoverability and access.
In this enhancement, Primo VE will highlight the selected record on top of the list of FRBR versions, only for the preferred record mode.
We understand from the comments here that there is also a request to add this option for Generic mode, however in the generic mode we only show a link to the list of versions and not pointing for a specific record. In Generic mode we don't show any actions or availability status, and there is no option to open a full mode as this is not a specific representation of the record.
This is why we have chosen to implement this only for preferred mode.
Please provide some more clarifications for the generic mode request in a dedicated idea.
Best regards
-
Manu Schwendener commented
> An alternate approach to this might be to enable "search within" the FRBR group titles,
> with results limited to those matching termsI do not agree. I search for something = I only want to see results that contain my search terms.
There should not be an additional step "now show me the things I actually was searching for".
-
Stacey van Groll commented
I believe this a flaw in Primo VE design. If you search for Iliad Lattimore in a Back Office site, open the FRBR group, and change the results sort to be by Relevance, then the Lattimore versions will be right at the top of the list. If you do the same thing in a Primo VE site, the results ranking is clearly changed somehow, but there is no obvious meaning to this change. It is not by relevance to the term searched, as a meaning known and expected through all of queries searched in Primo, as Lattimore is nowhere in the top 50 results.
We have almost 90,000 FRBR groups for important works, some with over 100 titles.
Our users need to be able to search quickly and easily for known items, and it should not require disabling FRBR to ensure relevance ranking works as expected in a discovery layer.
It is just these sorts of unexplained and inexplicable behaviours, which completely undermine the fundamental workings of the UI, that mean that we are are not wanting to move to VE. -
Manu Schwendener commented
> FRBR groups and the display of versions within them does not consider the relevancy of
> the terms searched.
This makes our catalog basically a joke. We are a university library and you can't search for an exact title. -
Manu Schwendener commented
I think the way FRBR groups work at the moment is not logical and should be changed.
> a user is searching for ... Homer's Iliad translated by Richmond Lattimore
114 versions found.
It's ok to bundle different versions in a FRBR group, but only those works that contain the search terms.
Even advanced search isn't helping.
And the author facet isn't helping because it can't show more than 50 entries and Lattimore is not among them.
-
Erica Nutzman commented
We have had the same problem. A search term hits on one record in a FRBR set and the whole set is displayed every time, so a patron has to look through all of the records to figure out which one actually had a match. It's very frustrating.
-
Cheryl Grubb commented
This would be very helpful!
-
Manu Schwendener commented
Related: Allow patrons to disable FRBR https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/42531016-allow-patrons-to-disable-frbr-disable-frbr-in-ad
-
Nancy Babb commented
An alternate approach to this might be to enable "search within" the FRBR group titles, with results limited to those matching terms