JSTOR Not Working (January 2015)
Over the last few weeks Zotero Standalone (4.0.23) hasn't been able to grab citation information from JSTOR, even in cases when the article I'm trying to save includes a DOI (for an example, see http://www.jstor.org/stable/info/10.1525/jams.2013.66.1.129). I get a message that the article is being added to my library, but nothing happens. Zotero seems to be working nicely with other providers, so this appears to be an issue specific to JSTOR. I've done some searching on the forums to see if anyone else is reporting this, but I've mostly found older discussions.
I'm using Safari 7.1.2 and Zotero Connector 4.0.21.
I'm using Safari 7.1.2 and Zotero Connector 4.0.21.
The translator in question can be found at https://github.com/zotero/translators/blob/4e4907551c68a06f3c482908c03a8cc65a266a2c/JSTOR.js
It can be added to the Zotero Library translators folder (I just overwrote the newer version).
With Zotero 4.0 built from source (fa75be), accessing JSTOR via our University proxy, translation fails without issuing an error. The Debug ID is D86936079.
When JSTOR is accessed without the proxy, translation succeeds.
I'm not sure what to make of the self-signed certificate error. If the certificate is the problem, should I complain (1) to our Uni computing office, (2) to the resolver service, or (3) to JSTOR themselves? (Sorry to be clueless.)
If this should go in a separate thread, just say the word.
Anything in jws's debug that'd be helpful?
fbennett: Your IT department, I guess. I've never seen an institution use a self-signed cert for a proxy — seems like a strange choice. You could whitelist the cert on a common domain, I guess (though I don't actually know if wildcard self-signed certs work). But I think your case is specific to your network.
I'm using Chrome on Windows with Zotero standalone on a uni network. It was working perfectly just a few days ago but yesterday stopped. I need this to import dozens of papers and citations at the moment so it's a bit of hindrance to say the least.
The debug ID is D2114274435
http://www.jstor.org.connect.nls.uk/stable/1800252?seq=1#page_scan_tab_contents
I'm connecting through the National Library of Scotland. Always worked perfectly before.
UPDATE: the plugin now works fully (citation and pdf import) on the pages it previously failed on (but this isn't going through https). What's going on there, then?!
In any case, this is not an acceptable solution and I will be reverting it shortly. We'll have to come up with something better for the original issue.
http://www.nul.nagoya-u.ac.jp/db/DBannai/ezproxy/index_e.html#faq5
The link was accompanied by an apologetic note saying that they would like to set up a proper signed certificate on the proxy service, but that there is no timetable in place for making that happen.
So ... well, yeah.
Since for most people here switching to Chrome fixed this, any issue that exists on Chrome is by definition not the same.