Koha has long been a consumer of Amazon API data and jacket images. The API has changed previously and Koha has had to keep up. It looks like Amazon has another set of changes in the works, set to take effect in a few months, so we will have to adapt again. <br>
<br>Separately, it is speculated that it might become more difficult to get API keys under the upcoming model, but this has not been confirmed. Koha developers will be following the API migration closely.<br><br>I'm forwarding a message from Jonathan Rochkind of code4lib that describes the upcoming changes.<br>
<br>-- <br>Joe Atzberger<br>LibLime - Open Source Library Solutions<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Jonathan Rochkind</b> <span dir="ltr"><<a href="mailto:rochkind@jhu.edu">rochkind@jhu.edu</a>></span><br>
Date: Mon, May 11, 2009 at 9:40 AM<br>Subject: [CODE4LIB] Amazon product API will require a crypto signature<br><br>The Amazon products API keeps changing it's name, and has just been changed to Amazon "Product Advertising API" -- it's the one you use to look up books in Amazon and get metadata for them, though.<br>
<br>
It looks from an email I got from Amazon that as of August 15th, you'll need to cryptographically sign requests to this API, to have them responded to. It looks like kind of a pain.<br>
<br>
I think a bunch of people on this list may be using this API. Beware. Instructions for how to cryptographically sign requests the way they want can be found here:<br>
<br>
<a href="http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/Query_QueryAuth.html" target="_blank">http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/Query_QueryAuth.html</a><br>
<a href="http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/rest-signature.html" target="_blank">http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/rest-signature.html</a><br>
<br>
Like I said, it's looking like a pain to me. There are lots of details to get right. If you URI-escape not _exactly_ the same way they do, it's not going to work. Etc.<br><font color="#888888">
<br>
Jonathan<br>
</font></div><br>