Chrome Translator Issues in Proquest

hannahsaur · September 16, 2016

I am getting generic item icons (web page link instead of a journal article type) when trying to save an article from Proquest within Chrome.

I had been getting this generic item for a lot of other sites (JSTOR, Pubmed), but I seemed to have resolved that issue by getting the latest update in Standalone.

Are there known Chrome translator issues with Proquest?

Apologies if this has been discussed/resolved in another forum post. Thanks!

adamsmith · September 16, 2016

we'd need to see a URL exactly as you see it.

hannahsaur · September 16, 2016

Does this help?
http://getitatduke.library.duke.edu/?url_ver=Z39.88-2004&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.atitle=Adverse health consequences of the Iraq War&rft.aufirst=Barry S.&rft.aulast=Levy&rft.date=2013&rft.epage=958&rft.genre=article&rft.issn=0140-6736&rft.issue=9870&rft.jtitle=LANCET&rft.pages=949-958&rft.spage=949&rft.stitle=LANCET&rft.volume=381&rfr_id=info:sid/www.isinet.com:WoK:WOS&rft.au=Sidel, Victor W.&rft_id=info:pmid/23499043

adamsmith · September 16, 2016

I'm guessing the problem is that you're looking at the resource inside summons and Zotero doesn't recognize it as proquest. You should be able to look at it outside of the library catalog framework (the way to tell would be that it actually says proquest in the URL).

hannahsaur · September 16, 2016

OK, thanks for the super speedy reply! I see what you mean about the weird URL. It seems to work in Firefox with that referring URL, but not Chrome. It appears when you use our Duke ezproxy link within any database (Web of Science, Scopus, Summon) you're faced with that scenario when using Chrome (see: http://screencast.com/t/ONH90jasf).

I realize this is probably a better question for my library's Web IT. I'm a librarian and a teach with Zotero a lot, so I'm just trying to diagnose what's going on so I can tell students what to do (preference Firefox over Chrome and/or save the citation within original database and add PDF manually). Might not be much we can do given the ezproxy setup that we have, but I'll look into it.

Thanks for your help!

hannahsaur · September 19, 2016

Hi Adam,
I reported the issue to my library's Web IT. They're going to notify Summon/Proquest to see if they can fix the issue on their end.

But my library IT also thought that an update might have to happen on the Zotero (or Chrome) end - updating the translator, so that items in Summon are recognizable/translatable.

The translator does work as you'd expect in Firefox/Standalone, but the translator does not work in Chrome. Another person had posted about this (https://forums.zotero.org/discussion/62418/), so I don't think it's a local issue with my institution. Rather a larger issue between the Chrome extension and Summon/Proquest. According to the other forum poster this change/break in the translator working might've occurred after a recent (August) Summon update. The Chrome/Zotero/Summon translator had been working fine previously.

Thanks for your help!

adamsmith · September 19, 2016

@zuphilip actually reminded me that we worked with Summon on the translator, so we have some hope they'll help us fix it on the Zotero side. It's a bit hard to understand what's going on for us. The ticket is here:
https://github.com/zotero/translators/issues/1148