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
Received on Fri May 16 2008 - 07:51:45 EDT