Individual (non-grouped) records lose Search Results Navigation menu when a user uses "Group Formats and Editions" in the OPAC

Bug #1437460 reported by Carrie Curie
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

Evergreen 2.7.4

We just began testing and customizing this release on our development server and noticed that when using the "Group Formats and Editions" option in the OPAC, individual records that are not part of a grouping lose the Search Navigation Menu on the record view page.

The following examples are from Statistics Canada's production catalog.

Record View when not using the "Group Formats and Editions" option: https://statcan.egcatalogue.ca/eg/opac/record/35825?query=harriet;qtype=keyword;locg=1

Recocrd View when using the "Group Formats and Editions" option: http://statcan.egcatalogue.ca/eg/opac/record/35825?query=harriet;qtype=keyword;locg=1;modifier=metabib

The Search Navigation Menu does appear correctly on the record view page for the records that were grouped.

Revision history for this message
Carrie Curie (carrie-curie) wrote :
Revision history for this message
Jason Stephenson (jstephenson) wrote :

Confirmed on our 2.7 production system and on a 2.8 development vm.

It would probably affect 2.6 as well, but I have not confirmed it there.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
tags: added: metabib search
Revision history for this message
Kathy Lussier (klussier) wrote :

Noting that we also lose the results header on the results page for a grouped record. I don't know if this is by design - we might not want the user to click the "Group Formats and Editions" option at this stage - but it does take away the ability to go to the detailed view on this page.

tags: added: metarecords
Revision history for this message
Kathy Lussier (klussier) wrote :

What is the expected behavior here?

On a non-metarecord search, the record navigation menu navigates through the records retrieved on the main search results page.

For a metarecord search where the record is part of a group, the record navigation menu navigates through the records on the grouped record page (i.e. only the records that are part of the metarecord group).

For a metarecord search where the record is not part of a group, then, we can't navigate from one grouped record to another because it wasn't part of a group. Therefore, we would need to navigate through the records retrieved on the Grouped Search results page (the first page that displays during a metarecord search.)

Taking a look at a screenshot from a metarecord search at http://www.screencast.com/t/APj793TnCokU, let's say the user clicks on the first record in the search result set, The world of the Hunger Games, which is not part of a group.

If they start navigating from the record, they would then go to A brief guide to the Hunger Games (also an ungrouped record) and then to the Hunger Games trilogy (another ungrouped record.) The next result is a metarecord group that contains two titles. What happens if we hit 'next' in the record navigation? Should we navigate through each of those individual titles belonging to the group? Or should we see a Grouped Record results page that lists the two titles belonging to that group?

I'm not sure what the best approach would be.

Revision history for this message
Kathy Lussier (klussier) wrote :

A correction to my above example. The first search result is a set of grouped record, so let's pretend instead that the user started with A brief guide to the Hunger Games, which is indeed a single record that's not part of a metarecord group. The question remains. At some point, we'll get to a result that is a set of grouped records, and we'll need to know how to handle these in the navigation.

no longer affects: evergreen/2.6
no longer affects: evergreen/2.7
Andrea Neiman (aneiman)
no longer affects: evergreen/2.8
tags: added: opac
removed: tpac
Revision history for this message
Andrea Neiman (aneiman) wrote :

Noting that this still occurs in 3.12 BOOPAC.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.