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.
Thank you for posting this idea. The direction that we are thinking to implement is to highlight at the top of the list of versions the record that user came from. so users will have the same context of their search when they are viewing the entire list of versions.
"tentatively planned to be fixed on Primo VE August 2023" (06359614)
Thank you for the update, Yael
There's an additional UX aspect to it:
Our default sort is 'Relevance'
Once the patron clicks on the first title, the sort changes to 'Date - newest' without the patron actively changing the setting – this should just not happen.
(Also wrong: why do I see the author's name three times?)
> 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, [...] Lattimore is nowhere in the top 50 results.
I search for his terms, with the additional step to re-sort the list of versions to 'Relevance' -> what he's looking for is shown as hit number 10.
=> But when I switch from FRBR Generic to FRBR Preferred *, Primo VE is perfectly able to show the work the patron is looking for, see screenshot.
* we probably won't do that, because it's confusing in other ways
Only made it to rank 60 in NERS 2022.
If you have a case open with Ex Libris about this, please add that it's a parity issue and needs to be fixed for Primo VE.
NERS 7843, open for voting now.
In Primo VE there is no option to sort the FRBR versions by Relevancy
> I believe this a flaw in Primo VE design
I completely agree.
If I switch from FRBR Generic to FRBR Preferred, I get to see "the highest ranked record from the results set" in the short title list.
This is the record that should be the FIRST title in the list of versions, also with the Generic setting.
This is very much not the case.
> An alternate approach to this might be to enable "search within" the FRBR group titles,
> with results limited to those matching terms
I 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.
> 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.
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!
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