I’d note one more thing I’m troubled by: Google’s share of revenue from book sale links on a GBS page means it is NOT in Google’s interest to provide openurl links back to user’s local library catalogs for google books material. Many of these books can be obtained by our users for free from our libraries (many of them were digitized from our catalogs in the first place!).
We’d like to let our users to easily discover this about a given book (and easily access ILL services, if desired), before deciding to purchase the book. An OpenURL link to our institutional link resolver would do that.
But it’s in Google’s interest to have users in fact NOT discover local library availability, and instead choose to purchase the book.
Interestingly, Google does offer OpenURL links in Google Scholar, I wonder how they decided this was a good idea for them despite their commercial interests. But I don’t expect to see it showing up in GBS anytime soon, and wouldn’t be surprised to see it dissapear from Scholar.
Interestingly, Google does provide a link to Worldcat—as a result of a deal made with OCLC. I suppose eventually that might lead the user to her own library, but not very easily for them. There are a number of problems with this user work-flow, I could get into details. So we have OCLC making a deal to trade metadata largely contributed by US (what OCLC offered Google), for access to and visibility on GBS, consisting of text largely digitized from US (what Google offered OCLC)—with our actual individual library interests (that is, the proxied interests of our patrons) left out of the equation altogether, while other organizations benefit from our assets freely shared.
I still wonder if the particular deals libraries made with Google for digitizing books were really in our libraries’ long-term best interests.
What can we do?
But I can think of two main technical solutions for us to give our users easy access to library availability information and services (ILL) for materials they find in GBS:
1) LibX or similar browser plugins can be developed to add links to our library openurl link resolvers, or catalogs. Link resolver is better as it typically provides ILL service, but you’d need a link resolver like Umlaut that actually has useful catalog integration built in. Then we aggressively market LibX to our patrons. It’s a last resort to rely on a browser plug-in like this, but I think we’re in last resort territory.
2) Using the GBS data API, we could develop a seperate “front end’ for GBS which is essentially a proxy. It gives the users pretty much the same things that are in the actual GBS results, except with a link resolver link. We could encourage our users to use this search, to get library availability and services, instead of GBS native interface. This is something which easily could be deployed in a central shared way, by a library consortium or vendor (OCLC?) such that we can all share it, and it will direct each of our individual users to our individual library link resolver (using OCLC Registry; using ‘preferences’ in cookie as per Google Scholar; or using a directive given in a URL used to access. I wish worldcat would add this last method, so my off-campus users could get the link resolver links worldcat currently gives on-campus users).
I’m not sure if these would be allowed by GBS API terms of service, which are confusing and ambiguous. For that matter, whether or not it’s allowed now, if something like this were developed and it did hurt Google’s interests, they could change their terms at any time.
I hope libraries are finally getting over trusting Google to act in our interests, instead of theirs, or assuming these interests never conflict.