Re: SV: Integrating Google Book Search content into OPACs

I can't find who sent the original post, I must have deleted it, but the
Kentlink solution seems elegant to me. The link is:
http://kentlink.kent.edu/search/Xsleepy+hollow

and watch how the google book links load last. I'm trying to figure out how
they do that.

Anyway, a fine implementation at Kent State!

Jim

James Weinheimer  j.weinheimer_at_aur.edu
Director of Library and Information Services
The American University of Rome
via Pietro Roselli, 4
00153 Rome, Italy
voice- 011 39 06 58330919 ext. 327
fax-011 39 06 58330992


> -----Original Message-----
> From: Next generation catalogs for libraries
> [mailto:NGC4LIB_at_LISTSERV.ND.EDU] On Behalf Of Ashley Sanders
> Sent: Friday, May 16, 2008 3:07 PM
> To: NGC4LIB_at_LISTSERV.ND.EDU
> Subject: Re: [NGC4LIB] SV: [NGC4LIB] Integrating Google Book Search
> content into OPACs
>
> Henrik Lindström wrote:
>
> > We also discovered the problem, described by Janes, that the script
> stops
>  > the loading of the page. We tried an AJAX workaround, but that got
>  > stuck in Google's security precautions, resulting in a 401-response.
> The
>  > solution we choose was to make sure that the Google-script is the
>  > last thing to be added to the page when loading.
>
> We've had pretty much the same experiences -- eventually settling on
> an AJAX approach. The way I worked it was that all requests to Google
> went from our machine rather than the users machine. This worked
> for a while, but we have now been blocked by Google. All accesses now
> result in the following message from Google:
>
>       We're sorry...
>       ... but your query looks similar to automated requests from a
>       computer virus or spyware application. To protect our users, we
>       can't process your request right now.
>
> The reason I went for the above approach was that some of our
> users had let it be known that they didn't want information about
> which records they were viewing to be sent to Google.
>
> If you provide access to Google Book Search the way Google suggest then
> Google get to learn the ISBN (and other identifiers you've put in the
> url) of all the books a user is viewing -- all linked by their IP
> address. Which could be valuable marketing information for Google
> and potentially a breach of your users privacy.
>
> So Google Book Search isn't currently working on Copac until we
> decide where to go from here...
>
> Ashley.
> --
> Ashley Sanders               a.sanders_at_manchester.ac.uk
> Copac http://copac.ac.uk A Mimas service funded by JISC