@adamsmith: Is the deepdyve line in the source of the Emerald page for you? The way it's written, the DOI translator should be misparsing that DOI and breaking.
After fixing that so that only the correct DOI (10.1108/EUM0000000006098) is found, I still run into errors, but those ones are linked to changes in 2.1b2. Since I've been putting too much developer stuff on the forum, I'm moving that part of the conversation to zotero-dev.
Bugs are eradicated over time, but site translators are an ongoing battle, since site layouts can change and break them.
The last day or two was particularly bad, with a couple of high-profile translator issues. Usually things are pretty stable and sites work correctly for months or years at a time.
Is the deepdyve line in the source of the Emerald page for you?
yes, it's in there. Not sure why that's not a problem in my case - maybe it's the <meta name="citation_doi" content="10.1108/EUM0000000006098"> line that gets parsed in my case?
@adamsmith: I have that line too. It looks to me like the translator finds all of the DOI-like things and runs them through CrossRef. When the deepdyve one (which is misread) goes to CrossRef, it triggers an error and the translation fails. Do you have a single article icon or a folder icon on the Emerald page?
(3)(+0000252): Translate: Could not find a result using CrossRef: thrown exception => url => undefined downloadAssociatedFiles => true automaticSnapshots => true
(5)(+0000000): Translate: running handler 0 for done
Google Scholar is now working just fine. Thanks very much for the fix! This has been of immense help to both my students and myself. Again many thanks for your quick response.
Upgrade Storage
After fixing that so that only the correct DOI (10.1108/EUM0000000006098) is found, I still run into errors, but those ones are linked to changes in 2.1b2. Since I've been putting too much developer stuff on the forum, I'm moving that part of the conversation to zotero-dev.
The last day or two was particularly bad, with a couple of high-profile translator issues. Usually things are pretty stable and sites work correctly for months or years at a time.
maybe it's the
<meta name="citation_doi" content="10.1108/EUM0000000006098">line that gets parsed in my case?
You can click Update Translators Now in the Zotero preferences to get the fixed files.
(4)(+0000002): Translate: Binding sandbox to http://partneraccess.oclc.org/
(4)(+0000000): Translate: Parsing code for CrossRef
(3)(+0000002): HTTP GET http://www.crossref.org/openurl/?pid=zter:zter321&url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&rft_id=info:doi/10.1108/EUM0000000006098&fieldName=journal_doi&journal=0887-6045&affiliateId=emerald&format=jsonp&callback&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&noredirect=true&format=unixref
(3)(+0000252): Translate: Could not find a result using CrossRef:
thrown exception =>
url => undefined
downloadAssociatedFiles => true
automaticSnapshots => true
(5)(+0000000): Translate: running handler 0 for done
(4)(+0000001): Translate: Binding sandbox to http://partneraccess.oclc.org/
(4)(+0000000): Translate: Parsing code for CrossRef
(3)(+0000015): HTTP GET http://www.crossref.org/openurl/?pid=zter:zter321&url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&rft_id=info:doi/10.1108/EUM0000000006098&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&noredirect=true&format=unixref