Like in bug 31446 libraries should have the option to hide the descriptions displaying under items in the lightbox galleries on the intranet item detail pages. This is particularly useful for libraries that only have one source of images enabled - e.g. Coce - in which case displaying where the item is from when it is the only image displaying on an item detail page, is not always useful.
Some cover services might have the link as a condition to using the service. I wonder if we should investigate this first.
Created attachment 139812 [details] Description hint under image in lightbox gallery on intranet item detail page
(In reply to Katrin Fischer from comment #1) > Some cover services might have the link as a condition to using the service. > I wonder if we should investigate this first. Hi Katrin, Could you please let me know when you refer to the 'link' do you mean the description hint displayed under each image - highlighted yellow in the attached screenshot? Hiding that description hint, rather than the link to the image is the purpose of this bug report. Basically, I'm just trying to check if we're talking about the same thing :) Thanks, Alex
Yes, I mean that text/link below the picture. I know of at least one German provider where a link behind the image was not enough and there was supposed to be text as well (again, this might have changed).
I've quickly looked around a bit: Open Library Covers API (optional?) https://openlibrary.org/dev/docs/api/covers 3) A courtesy link back to Open Library is appreciated, whether it be on each individual book's page (where you can link back to the book's page on Open Library, for example, using the same ISBN https://openlibrary.org/isbn/9780385533225), or on your About page or in your footer. Amazon Cover API https://developers.google.com/books/branding ? Google must be given attribution, using the appropriate text or brand elements, whenever you display Google results, previews, or other content made available through the API. You must maintain prominent links to Google Books pages and features.
(In reply to Katrin Fischer from comment #5) > I've quickly looked around a bit: > > Open Library Covers API (optional?) > https://openlibrary.org/dev/docs/api/covers > > 3) A courtesy link back to Open Library is appreciated, whether it be on > each individual book's page (where you can link back to the book's page on > Open Library, for example, using the same ISBN > https://openlibrary.org/isbn/9780385533225), or on your About page or in > your footer. > > > Amazon Cover API > https://developers.google.com/books/branding ? > > Google must be given attribution, using the appropriate text or brand > elements, whenever you display Google results, previews, or other content > made available through the API. > You must maintain prominent links to Google Books pages and features. Hi Katrin, Thank you for noting this. I think you're right it could be difficult to upstream this change - because of the mandatory attribution requirements of Google. Although, this change is really only giving libraries the option to revert to pre Koha 21.11 behaviour - not displaying text attribution of where an image is from. If libraries want they can hide the text using JavaScript. We think the optimal fix might be to add an ID to the parent div, if one doesn't already exist (i.e. https://github.com/Koha-Community/Koha/blob/master/koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-detail.tt#L66 and https://github.com/Koha-Community/Koha/blob/master/koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-detail.tt#L105 ) to make it easier to hide the hint with JavaScript if necessary. What do you think of that as a solution? Thanks, Alex
Just noting we have decided not to proceed with this fix. As Katrin pointed out in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31456#c5 some content providers look to require text attribution in the Koha OPAC in order for their images to be used, so it is best for these attributions to be retained. If libraries do not use those content providers and want to hide where their cover images are coming from they can already do that using custom JavaScript in the OpacUserJS syspref.