So Google Scholar lets institutions register their OpenURL link resolver details. And this lets those institutions show up in the Google Scholar preferences. And if a user chooses that institution from the preferences, then they’ll get links to that institutions link resolver on most Google Scholar hits. Which is great, among other reasons for integrating institutional access and delivery options into the excellent Scholar search.
However, many developers have wanted to find a way to set preferences for users. Whether actually setting persistent preferences in a cookie, or instead just embedding in a link to Google Scholar to set them for the current search — seems better than having to give users multi-step instructions, which many users will never see or read, for setting their own preferences.
I had never seen anyone figure out a good way to do that before. I had noticed some libraries using a kind of hacky way (I think LibX sometimes uses this hacky way too) — and I had noticed even that hacky way had stopped working last time I checked, as Google had changed their interface in some way that broke the hacky screen-scrapey way that was too sensitive to implementation details.
However, Jim Pitman just brought to my attention that some Sakai installations seem to be using a method of specifying an openURL base URL in a ‘deep link’ to Google Scholar. Check this out:
That linking specification for including an “import to bspace” link does seem to be “sticky”, if you change your search criteria, you still get the link, by those extra URL parameters staying with you. (They are not set in cookies, if you start over with a fresh URL, you lose the link).
I had no idea that was possible, and don’t entirely understand how it works. I see the linkurl_id and linkurl_base parameters, but specifying your own arbitrary values there doesn’t seem to work. And the actual link text, in this case “import into bspace” isn’t specified there — so it would seem to be referencing some registration on file with Google Scholar already. My institution has a registration on file for ordinary Google Scholar preferences, but I haven’t been able to figure out how to use it for this kind of ‘deep link’, I don’t know what the “linkurl_id’ would be. I am not sure if you instead need some kind of special relationship/arrangement with Google Scholar.
Anyone seen this before? Anyone know anything about it? Anyone have any ideas for where to go to get more information? Google ‘support’ is generally not so much. Jim Pitman says this is the project page where the Sakai plugin that provides this Google Scholar connectivity is found, but that emails to the contact addresses there have gone unanswered.
Seems like a feature a lot of people would be interested in using, if we could figure out how it can be used.
Update Feb 2 2011
Jon Dunn, who was involved in the Sakai/Scholar plugin, helpfully writes:
We (IU and Michigan) worked directly with Google back in 2007 to accomplish this. Their requirement at the time was that, for the callback, we take exactly the same parameter format that they pass to RefWorks. The linkurl_id value that we pass to Google Scholar is used to look up the correct name (e.g. bSpace, Oncourse, CTools, etc.) of the institution’s Sakai instance in a registry hosted at sakaiproject.org so that the correct label can be displayed for “Import into ____”.
I think that Google has set up similar linkages with Blackboard and perhaps some other CMSes. I don’t know how open they are to doing this in general, though. The people we worked with were [omitted] on the Google Scholar team, but the best way to contact them may be through the general scholar-library google.com mailbox.
This is interesting, but I’m thinking, geez, I don’t need any setup as complicated as that. All I need is the exact same institutional link registration that Google already has (no need for a seperate registry), but the ability to pass in an ID in the URL refering to that registration, the way they can with their “seperate” registries.
That feature would make a lot of sense, and is consistent with what Google is already doing, but more sensible — but I’m not sure there’s any way Google is going to develop any new features for Scholar to serve libraries, no matter how small. My impression in the past has been that there is essentially no development work going on on Scholar right now. So when I’ve tried to communicate these thigns with Google contacts before, it takes a lot of back and forth to even succesfully explain what I’m talking about, and then they say “Okay, we’re probably not going to do that.” Guess it doesn’t hurt to email that email address, which I’ll do when I have some time for some back-and-forth. But if anyone else wants to, feel free!