http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7187 Manos PETRIDIS <egpetridis@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |In Discussion --- Comment #16 from Manos PETRIDIS <egpetridis@yahoo.com> --- (In reply to comment #6)
One thing we need to decide on is whether the logic that checks multiple sources should be in JavaScript on the client side or Perl on the server side. I'm leaning towards Perl on the server, for two reasons:
1. Displaying an image could be as simple as this:
<img src="opac-ver.pl?biblionumber=x" />
2. We could cache the results of looking through multiple sources. (Caching might violate the terms of service for e.g. Amazon, but then we could check them last, after we have checked the ones that we can cache.)
Just a comment from an end-user: Could it be that Amazon returns an image, even when no cover image is available in its systems? I'm referring to the "No image available" with a hint of a smile/bent arrow below image. Unless Amazon does provide for an indication that the image it provides is a placeholder for the cover image it does not [yet] have, caching might prove tricky, for it could hinder future [successful] look-ups in Amazon. Furthermore, should Amazon be at the top of the list, successfuly fetching a placeholder image from Amazon would prevent koha from retrieving a correct cover image from some other source down the list. -- You are receiving this mail because: You are watching all bug changes.