Google Scholar

101james · January 11, 2012

Google Scholar is normally highly reliable for import to Zotero. Just today it is causing Zotero to report translator issues. Is this a short term issue or something that requires resolving. Other attempts at importing the item e.g., from the publishers website - in this Ebsco - are successful.

dstillman · January 11, 2012

You'd have to provide an example URL.

adamsmith · January 11, 2012

seems completely broken
http://scholar.google.com/scholar?q=test
I'll have a quick look now.

ajlyon · January 11, 2012

Please go to http://github.com/ajlyon/translators/raw/master/Google Scholar.js and save the file to the translators directory of your Zotero data directory (http://www.zotero.org/support/zotero_data).

It should start working again. If this works for you, please post here so that I can submit this change to be pushed to all users.

[Sorry, adamsmith, but I had to take a quick look for such a major site.]

adamsmith · January 11, 2012

yeah, looks like we did the same - i just changed one span to div -
works for me.

ajlyon · January 11, 2012

This is now in the main translator repository. The updated Google Scholar translator will be installed automatically in Zotero clients within 24 hours. Click "Update now" from the Zotero preferences to get the new version immediately.

dstillman · January 11, 2012

Thanks, guys.

101james · January 11, 2012

Thanks for the speedy reaction and response. This is such a fantastic features in Zotero. Best for 2012!

caldwelljules · January 17, 2012

This error still occurs in the MLZ client. I have followed the steps above and they seem to solve the problem. Can this change be made to the main translator repository for MLZ as well?

Thanks guys

fbennett · January 17, 2012

It should pull the new GS translator in now, if you update again. The MLZ update mechanism relies on JSON that GitHub generates when changesets are added, and ships to a CGI on the MLZ-specific repository site. The GitHub JSON changed recently to add a tab character after filenames. I'm not sure if that's a bug or a feature, but it broke the CGI update mechanism on the repository site. It's fixed now, and touching the GS translator has triggered an update through the usual channel. I'll work back through recent translator updates soon, and touch other translators that may have been "overlooked".