- Koha - lists.katipo.co.nz

Re: [Koha] Amazon Secret key used to generate digital signature
by Nicole Engard 15 Feb '10

15 Feb '10

Mike, I've written so much I can't remember it all :) That said - I was able to copy and paste my secret key today using Firefox -- so I'm not sure what you mean about not being able to copy/paste. Nicole On Sat, Feb 13, 2010 at 9:33 PM, <mcmlists(a)people.net.au> wrote: > Hi Nicole, > > Further to my last post, I should have quoted this Koha FAQ, > http://koha.org/documentation/faq/why-do-i-need-a-awsprivatekey-for-amazon-… > which states that the Private Access Key and Secret key are the same. I > assumed you had written the FAQ. > > Why do I need a AWSPrivateKey for Amazon Content? > > Up to Table of Contents > > 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/, 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. > > END OF QUOTE FROM FAQ. > > This won't be so simple to implement because the Secret key is long and > complex and can't be cut and pasted from the Amazon site into the Koha > system prefs. > > Presumably the patch for 3.2 uses the Secret Key to create a digital > signature, as described in the following > Amazon description of access keys at > http://docs.amazonwebservices.com/AWSSecurityCredentials/1.0/AboutAWSCreden… > > Secret Access KeyEach Access Key ID has a Secret Access Key associated with > it. This key is just a long string of characters (and not a file) that you > use to calculate the digital signature that you include in the request. Your > Secret Access Key is a secret, and only you and AWS should have it. Don't > e-mail it to anyone, include it any AWS requests, or post it on the AWS > Discussion Forums. No authorized person from AWS will ever ask for your > Secret Access Key. > > When you create a request, you create a digital signature with your secret > key and include it in the request along with your Access Key ID. When we get > the request, we use your Access Key ID to look up the corresponding Secret > Access Key. We use the key to validate the signature and confirm that you're > the request sender. > > END OF QUOTE FROM AMAZON SITE. > > Mike Mason > > Earlier today, I wrote: > ------------------------------------------------ > My statement that "what we call the Amazon private key is really the Amazon > Secret Access Key" was based on the following: I have just set up my Amazon > associate ID and AWS access keys in Amazon, and the site described two keys > as follows: (this is cut and pasted from Amazon's Associates' "Manage your > account" page:) > You will need access identifiers to call the Product Advertising API, > authenticate requests and identify yourself as the sender of a request. Two > types of identifiers are available: AWS Access Key Identifiers (Public and > Secret Keys) and X.509 Certificates. > > The site guides you to set up the Public and Secret keys. It does not > mention a "Private key". So I assumed that what you referred to in the 3.2 > manual as a "Private Key" was meant to indicate Amazon's "Secret Key". But > perhaps you had something else in mind? > > Unfortunately I can't test this as I'm on Liblime's Koha Express, which is > still back in Koha 3.00.02.012 and has no system preference entries for > Amazon reviews or for the Secret/Private key. > > Mike Mason > > At Sunday 14/02/2010, you wrote: > > Hi all, > > I want to confirm that what we call the Amazon private key is really > the Amazon Secret Access Key. If so I want to update the language in > the manual and the sys prefs page -but I want to be sure before I do > that. > > Nicole > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Koha and Public Access Computers
by Josh Westbrook 14 Feb '10

14 Feb '10

I apologize for being slightly off topic, but does anyone on the list know of any free, inexpensive, or open source tools for managing Public Access Computers? Any that work with Koha to validate patrons? We had used Windows SteadyState previously but it won't be developed for Windows 7 so we need to move to something else fairly quickly. Any help would be appreciated! Thanks, Josh Westbrook Prescott Library Mngr/District Technology Mngr Walla Walla County Rural Library District joshw(a)wwrurallibrary.com http://www.wwrurallibrary.com

5 4

Re: [Koha] Amazon Private Key
by Nicole Engard 14 Feb '10

14 Feb '10

Mike thanks, I had gone to AWS today and saw that there was no 'private key' which is what it used to be called - but that it was now a secret key - so glad that you see the same thing as me. Nicole On Sat, Feb 13, 2010 at 6:54 PM, <mcmlists(a)people.net.au> wrote: > Hi Nicole, > > My statement that "what we call the Amazon private key is really the Amazon > Secret Access Key" was based on the following: I have just set up my Amazon > associate ID and AWS access keys in Amazon, and the site described two keys > as follows: (this is cut and pasted from Amazon's Associates' "Manage your > account" page:) > You will need access identifiers to call the Product Advertising API, > authenticate requests and identify yourself as the sender of a request. Two > types of identifiers are available: AWS Access Key Identifiers (Public and > Secret Keys) and X.509 Certificates. > > The site guides you to set up the Public and Secret keys. It does not > mention a "Private key". So I assumed that what you referred to in the 3.2 > manual as a "Private Key" was meant to indicate Amazon's "Secret Key". But > perhaps you had something else in mind? > > Unfortunately I can't test this as I'm on Liblime's Koha Express, which is > still back in Koha 3.00.02.012 and has no system preference entries for > Amazon reviews or for the Secret/Private key. > > Mike Mason > > At Sunday 14/02/2010, you wrote: > > Hi all, > > I want to confirm that what we call the Amazon private key is really > the Amazon Secret Access Key. If so I want to update the language in > the manual and the sys prefs page -but I want to be sure before I do > that. > > Nicole > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] Amazon Secret key used to generate digital signature
by mcmlists＠people.net.au 14 Feb '10

14 Feb '10

Hi Nicole, Further to my last post, I should have quoted this Koha FAQ, http://koha.org/documentation/faq/why-do-i-need-a-awsprivatekey-for-amazon-… which states that the Private Access Key and Secret key are the same. I assumed you had written the FAQ. Why do I need a AWSPrivateKey for Amazon Content? <http://koha.org/documentation/faq>Up to Table of Contents 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. END OF QUOTE FROM FAQ. This won't be so simple to implement because the Secret key is long and complex and can't be cut and pasted from the Amazon site into the Koha system prefs. Presumably the patch for 3.2 uses the Secret Key to create a digital signature, as described in the following Amazon description of access keys at http://docs.amazonwebservices.com/AWSSecurityCredentials/1.0/AboutAWSCreden… * Secret Access KeyEach Access Key ID has a Secret Access Key associated with it. This key is just a long string of characters (and not a file) that you use to calculate the digital signature that you include in the request. Your Secret Access Key is a secret, and only you and AWS should have it. Don't e-mail it to anyone, include it any AWS requests, or post it on the AWS Discussion Forums. No authorized person from AWS will ever ask for your Secret Access Key. When you create a request, you create a digital signature with your secret key and include it in the request along with your Access Key ID. When we get the request, we use your Access Key ID to look up the corresponding Secret Access Key. We use the key to validate the signature and confirm that you're the request sender. END OF QUOTE FROM AMAZON SITE. Mike Mason Earlier today, I wrote: ------------------------------------------------ My statement that "what we call the Amazon private key is really the Amazon Secret Access Key" was based on the following: I have just set up my Amazon associate ID and AWS access keys in Amazon, and the site described two keys as follows: (this is cut and pasted from Amazon's Associates' "Manage your account" page:) You will need access identifiers to call the Product Advertising API, authenticate requests and identify yourself as the sender of a request. Two types of identifiers are available: AWS Access Key Identifiers (Public and Secret Keys) and X.509 Certificates. The site guides you to set up the Public and Secret keys. It does not mention a "Private key". So I assumed that what you referred to in the 3.2 manual as a "Private Key" was meant to indicate Amazon's "Secret Key". But perhaps you had something else in mind? Unfortunately I can't test this as I'm on Liblime's Koha Express, which is still back in Koha 3.00.02.012 and has no system preference entries for Amazon reviews or for the Secret/Private key. Mike Mason At Sunday 14/02/2010, you wrote: >Hi all, > >I want to confirm that what we call the Amazon private key is really >the Amazon Secret Access Key. If so I want to update the language in >the manual and the sys prefs page -but I want to be sure before I do >that. > >Nicole >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] Amazon Private Key
by mcmlists＠people.net.au 14 Feb '10

14 Feb '10

Hi Nicole, My statement that "what we call the Amazon private key is really the Amazon Secret Access Key" was based on the following: I have just set up my Amazon associate ID and AWS access keys in Amazon, and the site described two keys as follows: (this is cut and pasted from Amazon's Associates' "Manage your account" page:) You will need access identifiers to call the Product Advertising API, authenticate requests and identify yourself as the sender of a request. Two types of identifiers are available: AWS Access Key Identifiers (Public and Secret Keys) and X.509 Certificates. The site guides you to set up the Public and Secret keys. It does not mention a "Private key". So I assumed that what you referred to in the 3.2 manual as a "Private Key" was meant to indicate Amazon's "Secret Key". But perhaps you had something else in mind? Unfortunately I can't test this as I'm on Liblime's Koha Express, which is still back in Koha 3.00.02.012 and has no system preference entries for Amazon reviews or for the Secret/Private key. Mike Mason At Sunday 14/02/2010, you wrote: >Hi all, > >I want to confirm that what we call the Amazon private key is really >the Amazon Secret Access Key. If so I want to update the language in >the manual and the sys prefs page -but I want to be sure before I do >that. > >Nicole >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Amazon Private Key
by Nicole Engard 13 Feb '10

13 Feb '10

Hi all, I want to confirm that what we call the Amazon private key is really the Amazon Secret Access Key. If so I want to update the language in the manual and the sys prefs page -but I want to be sure before I do that. Nicole

1 0

Updating LibXML
by Sven Jankofsky 13 Feb '10

13 Feb '10

Hi, can somebody tell me, how to update (or downgrade) LibXML? Sorry for such a stupid question but I'm pretty new with Linux (Ubuntu 8.10). Got this error: This version of XML::LibXSLT requires XML::LibXML 1.6 (ABI 1), which is incompatible with currently installed XML::LibXML 1.70 (ABI 2). Please upgrade XML::LibXSLT, XML::LibXML, or both! at /usr/local/lib/perl/5.10.0/XML/LibXML.pm line 49. BEGIN failed--compilation aborted at /usr/lib/perl5/XML/LibXSLT.pm line 7. Compilation failed in require at /usr/share/koha/lib/C4/XSLT.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/XSLT.pm line 27. Compilation failed in require at /usr/share/koha/lib/C4/Search.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Search.pm line 27. Compilation failed in require at /usr/share/koha/lib/C4/Heading.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Heading.pm line 25. Compilation failed in require at /usr/share/koha/lib/C4/Biblio.pm line 114. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Biblio.pm line 114. Compilation failed in require at /usr/share/koha/lib/C4/Reserves.pm line 28. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Reserves.pm line 28. Compilation failed in require at /usr/share/koha/lib/C4/Circulation.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Circulation.pm line 25. Compilation failed in require at /usr/share/koha/lib/C4/Overdues.pm line 24. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Overdues.pm line 24. Compilation failed in require at /usr/share/koha/lib/C4/Members.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Members.pm line 27. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 31. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 31. Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22. BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 22. A good weekend for everybody. Sven

1 0

Re: [Koha] Amazon Reviews not displaying
by m.mason＠ytu.edu.au 13 Feb '10

13 Feb '10

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(a)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(a)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: >> > >> > >> <http://koha.lru.edu/cgi-bin/koha/opac-detail.pl?biblionumber=76740>http://koha.lru.edu/cgi-bin/koha/opac-detail.pl?biblionumber=76740 >> >> > >> > But the image tries to take you to this page: >> > >> > >> <http://www.amazon/gp/reader/0805447857/ref=sib_dp_pt/002-7879865-0184864#re…>http://www.amazon/gp/reader/0805447857/ref=sib_dp_pt/002-7879865-0184864#re… >> >> > >> > Which obviously doesn't work. Actually, it looks like it would need to go >> > to: >> > >> > >> <http://www.amazon.com/Killing-Cockroaches-Scattered-Musings-Leadership/dp/0…>http://www.amazon.com/Killing-Cockroaches-Scattered-Musings-Leadership/dp/0… >> >> > >> > 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(a)ytu.edu.au > > >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] Amazon Reviews not displaying
by Chris Morrison 13 Feb '10

13 Feb '10

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, <m.mason(a)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 > > 1. 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/, > going to the 'Access Identifiers' page, and from there retrieving and/or > creating a new Secret Access Key. > 2. 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 > libriotech.no > > 2010/2/12 Chris Morrison <cmm1005(a)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: > > > > http://koha.lru.edu/cgi-bin/koha/opac-detail.pl?biblionumber=76740 > > > > But the image tries to take you to this page: > > > > > http://www.amazon/gp/reader/0805447857/ref=sib_dp_pt/002-7879865-0184864#re… > > > > Which obviously doesn't work. Actually, it looks like it would need to go > > to: > > > > > http://www.amazon.com/Killing-Cockroaches-Scattered-Musings-Leadership/dp/0… > > > > 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: M.Mason(a)ytu.edu.au >

1 0

Re: [Koha] Amazon Reviews not displaying
by m.mason＠ytu.edu.au 13 Feb '10

13 Feb '10

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 >libriotech.no > >2010/2/12 Chris Morrison <cmm1005(a)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: > > > > http://koha.lru.edu/cgi-bin/koha/opac-detail.pl?biblionumber=76740 > > > > But the image tries to take you to this page: > > > > > http://www.amazon/gp/reader/0805447857/ref=sib_dp_pt/002-7879865-0184864#re… > > > > Which obviously doesn't work. Actually, it looks like it would need to go > > to: > > > > > http://www.amazon.com/Killing-Cockroaches-Scattered-Musings-Leadership/dp/0… > > > > 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: M.Mason(a)ytu.edu.au

1 0