You mentioned you are on Koha 3.0.5. For Amazon reviews etc to be accessible (but not for cover displays), the key which Amazon calls Secret, and Koha calls Private, has to be entered into Koha system prefs (in addition to AmazonAssocTag and AWSAccessKey). And there's no place to enter this in the system prefs in Koha 3.0 or 3.1 (at least, not in the 3.01.00.032 which is mounted as the Liblime demo system). But in Koha 3.2, there is a system pref entry for "AWSPrivateKey". I think we can't get Amazon reviews etc until we get a stable release of Koha 3.2 and upgrade to that. Mike At Saturday 13/02/2010, you wrote:
To the best of my knowledge, the associate key and the private key are both correct. I also have the secret key set up as well. Still no reviews or "Look Inside" (although, again, I do get the image on the detailed view; that didn't work until I had got the keys right).
On Fri, Feb 12, 2010 at 7:46 PM, <<mailto:m.mason@ytu.edu.au>m.mason@ytu.edu.au> wrote: Amazon now requires the SECRET /Private key for all except covers. But there does not seem to be a Koha System preference for this until version 3.2. From Koha 3.2 manual:
Why do I need a AWSPrivateKey for Amazon Content?
This FAQ applies to: 3.2 Why do I need the AWSPrivateKey as well as the AWSAccessKeyID to use Amazon Content? After 2009-08-15, Amazon Web Services will expect that all requests to the Product Advertising API, which is what Koha uses for retrieving reviews and other enhanced content from Amazon, include signatures. This patch and subsequenct patches implement this functionality. What this means in practice (assuming the user has elected to use any enhanced content from Amazon) is that The user must get a Amazon Secret Access Key. This can be done by logging in to the user's AWS account at (e.g.) <http://aws.amazon.com/>http://aws.amazon.com/, going to the 'Access Identifiers' page, and from there retrieving and/or creating a new Secret Access Key. The contents of the Secret Access Key should then be entered into the new AWSPrivateKey system preference. Once that is done, grabbing reviews and table of contents from Amazon should work as normal. If the user doesn't do this before 2009-08-15, reviews and TOCs will no longer be supplied from Amazon, although there should be no crashes - the content will simply not show up. Note that the requirement to sign requests does *NOT* appear to apply to simply displaying book covers from Amazon.
At Saturday 13/02/2010, you wrote:
Hi! Do you have appropriate values for both AWSAccessKeyID and AWSPrivateKey? I think covers without reviews is symptomatic of a missing AWSPrivateKey. Regards, Magnus Enger <http://libriotech.no>libriotech.no 2010/2/12 Chris Morrison <<mailto:cmm1005@gmail.com>cmm1005@gmail.com>:
Our recent upgrade to 3.0.05 went smoothly (thanks for helping us with the label problem we had), and pretty much everything works now except the Amazon reviews. We get jacket covers both in the results page and detailed views, but the reviews tab isn't displaying. Further, when we click the image in the detailed view, we get a "page not found" error. For example, see this record:
But the image tries to take you to this page:
Which obviously doesn't work. Actually, it looks like it would need to go to:
Associate tags and AWS key are both filled in and it looks like all appropriate switches are turned on (AmazonContent, AmazonSimilarItems, OPACAmazonContent, OPACSimilarItmes). I searched the lists and didn't see this answered yet--just one person who couldn't get the covers to display and needed a patch (for 3.0.04).
Thoughts?
Michael Mason Librarian & Director of I.T. Redemptorist Seminary Library 10 Majella Ct. Kew, Vic. 3101 Phone: +61 3 9817 9758 Fax: +61 3 9816 9805 Email: <mailto:M.Mason@ytu.edu.au>M.Mason@ytu.edu.au
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha