translator="Copernicus 3" not working with ZS + ZF

TomRoche
summary: ZF-4.0.8, iceweasel-20.0, ZS-4.0.6 running on debian testing:

http://krugman.blogs.nytimes.com/2013/05/26/reinhart-and-rogoff-are-not-happy/

works but

http://www.geosci-model-dev.net/5/1589/2012/gmd-5-1589-2012.html

fails.

details:

I'm running debian testing, with the correct system-clock time and time zone. On it I installed Zotero Standalone (ZS) package version=4.0.6-6: see

https://forums.zotero.org/discussion/29198/package-available-in-debian/
https://forums.zotero.org/discussion/30252/running-zoterostandalone4x-to-fix-existingbroken-zotero3x/

Installing ZS installed Zotero for Firefox (ZF) 4.0.8 on my iceweasel-20.0 (which is basically firefox, see

http://en.wikipedia.org/wiki/Iceweasel

). I now have both ZS-4.0.6 and iceweasel-20.0 open, and the latter shows button=Zotero @ lower right. When in ZS, I choose mainmenu>Edit>Options, and click button="Update now"; the button then displays "Up to date".

Per http://www.zotero.org/support/troubleshooting_translator_issues , I tried browsing to a nytimes.com page

http://krugman.blogs.nytimes.com/2013/05/26/reinhart-and-rogoff-are-not-happy/

where I see (in the "URL bar") button="Save to Zotero (Embedded Metadata)". When I push that, I get a success message in ZF; and when subsequently I Alt-Tab to ZS, I see that an appropriate new record exists, and is furthermore highlighted.

When I browse to

http://www.geosci-model-dev.net/5/1589/2012/gmd-5-1589-2012.html

I see button="Save to Zotero (Copernicus 3)" in the URL bar. On clicking that, I get the error dialog="Could Not Save Item" @ lower right of iceweasel. In ZS, gear>Report Errors... produces Report ID=606069067 (which appears to reference the successful nytimes.com write, not the failed GMD one). In ZS I do not see an item with either the appropriate first author or the appropriate title.
  • aurimas
    edited June 14, 2013
    There is no "Copernicus 3" translator in Zotero (it's just called Copernicus). In fact, the website you are referring to is only supported by the DOI translator, which finds a DOI on that page, and the Embedded Metadata translator, which looks at the <meta...> tags. Looks like you have a custom version of the Copernicus translator.

    In Iceweasel, you should be able to right-click the URL bar icon and select a different translator to be used (e.g. DOI or Embedded Metadata).

    If you did not add the Copernicus 3 translator yourself (and you don't have any other custom translators), you can try resetting your translators from Preferences... -> Advanced -> Files and Folders -> Reset Translators... Then restart Iceweasel and Update the translators again.
  • TomRoche
    aurimas 14 Jun 2013 ~1800
    > Looks like you have a custom version of the Copernicus translator.

    Doh! Indeed.

    > In Iceweasel, you should be able to right-click the URL bar icon and select a different translator

    Thanks! I didn't know that.

    > you can try resetting your translators from Preferences... -> Advanced -> Files and Folders -> Reset Translators... Then restart Iceweasel and Update the translators again.

    Actually restarting Iceweasel was not required (fortunately--too many tabs), just

    1. (in ZS) ...>Reset Translators
    2. exit and restart ZS
    3. (in iceweasel) reload the journal page

    and now I get translator=DOI, which works (though I hafta fill in some things manually, like the abstract and the journal abbreviation).
  • aurimas
    edited June 14, 2013
    now I get translator=DOI, which works (though I hafta fill in some things manually, like the abstract and the journal abbreviation).
    That's expected for the DOI translator. CrossRef (where DOI lookups are performed) does not serve this kind of metadata. Sometimes Embedded Metadata has abstracts and even links to PDFs (another thing DOI does not), but in this case, I don't think it will produce better data.

    If this is a common front-end for publishers, we would be interested in adding support for it (including abstracts, PDF attachments, etc.) Taking a quick look at it, I can't really tell what publishing system they are using. I found references to CLOCKSS and LOCKSS, which are pretty cool concepts that I didn't know about, but I think they are back-ends. I'll have to look more into this later.

    Edit: nvm, found it. It does seem to be a Copernicus system. We'll take a look at our Copernicus translator and see if we can fix it.
Sign In or Register to comment.