Bug 26933 - Improve handling of multiple covers on catalog search results in the OPAC
Summary: Improve handling of multiple covers on catalog search results in the OPAC
Status: ASSIGNED
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
: 7669 9991 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-11-05 04:30 UTC by David Nind
Modified: 2023-08-05 00:31 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Screenshots - Multiple cover images displayed in the OPAC (327.10 KB, application/pdf)
2020-11-05 04:30 UTC, David Nind
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Nind 2020-11-05 04:30:18 UTC
Created attachment 113028 [details]
Screenshots - Multiple cover images displayed in the OPAC

If multiple cover image sources are enabled for the OPAC, multiple images are displayed in search results and record detail pages.

See the attached examples.

To recreate:

1. Enable Amazon (AmazonCoverImages), Google (GoogleJackets), Open Library (OpenLibraryCovers), and local cover images (LocalCoverImages).
2. Search on the OPAC for perl.
3. Note that on the search results pages and record details pages that multiple images are displayed.

I'm assuming here that it is valid to have multiple cover image sources enabled.
Comment 1 Andrew Fuerste-Henry 2021-10-28 15:58:47 UTC
Bug 25846 establishes a design precedent for this on the staff side.
Comment 2 Owen Leonard 2022-07-11 16:18:15 UTC
Since the OPAC detail page has already been upgraded to handle multiple covers like the staff interface has, I'm re-titling this bug to cover only OPAC search results.
Comment 3 David Cook 2022-08-22 03:15:05 UTC
*** Bug 9991 has been marked as a duplicate of this bug. ***
Comment 4 David Cook 2022-08-22 03:30:19 UTC
*** Bug 7669 has been marked as a duplicate of this bug. ***