nice!  yeah, I was thinking of something along those lines.
…adam

On Nov 7, 2013, at 9:56 AM, Chris Fitzpatrick <[email protected]> wrote:

> Hi,
>
>
> I think you can do this all with JS or Coffeescript.
>
> Here's a fiddle :
>
> http://jsfiddle.net/chrisfitzpat/t69Xs/
>
>
>
>
> On Tue, Nov 5, 2013 at 10:12 PM, Daryl Grenz <[email protected]> wrote:
>
>> Powell's Books provides an API (http://api.powells.com/stable) and direct
>> links to their book covers by ISBN13 only.
>> Regarding the limit on daily use of the Google Books API, I think from
>> when I used it before that if you access cover links through the Dynamic
>> Links API (https://developers.google.com/books/docs/dynamic-links) there
>> is no daily limit.
>> - Daryl
>>
>>> Date: Tue, 5 Nov 2013 15:13:35 +0000
>>> From: [email protected]
>>> Subject: [CODE4LIB] display book covers
>>> To: [email protected]
>>>
>>> Hi all,
>>>
>>> Anyone have some good resources about tools for gathering book cover
>> images?  I'm building that into our next catalog update, which uses
>> Blacklight, but I'm not necessarily looking for Rails-only approaches.  My
>> questions are more general:
>>>
>>> What sources are out there?  (ex. Google Books, amazon)
>>>
>>> Making it work?
>>> I'm trying out Google Books at the moment, just making a call to their
>> API.  This can be asynchronously and loaded after the rest of the page, or
>> cached, perhaps even store the url in solr or a database table?
>>>
>>> Tools?
>>> I am trying out a Google Books gem[1], which is just a wrapper for the
>> api.
>>>
>>> Other thoughts?
>>>
>>> Thanks in advance,
>>>
>>> …adam
>>>
>>> ______________________________
>>> Adam Wead
>>> Systems and Digital Collections Librarian
>>> Library + Archives
>>> Rock and Roll Hall of Fame and Museum
>>> 216.515.1960
>>> [email protected]
>>>
>>> [1] https://github.com/zeantsoi/GoogleBooks
>>> This communication is a confidential and proprietary business
>> communication. It is intended solely for the use of the designated
>> recipient(s). If this communication is received in error, please contact
>> the sender and delete this communication.
>>
>>

This communication is a confidential and proprietary business communication. It 
is intended solely for the use of the designated recipient(s). If this 
communication is received in error, please contact the sender and delete this 
communication.

Reply via email to