Could not save item: JSTOR and Wiley Library

jwbaker
Report ID: 621365106

Examples URLS: http://dx.doi.org/10.1111/j.1468-2281.2007.00457.x ; http://dx.doi.org/10.1525/rep.2014.128.1.1

Getting a 'Could not Save Item' error. Seems to only be happening for journal content. Not sure how long problem has been there, but a couple of weeks at least.

Tried steps at https://www.zotero.org/support/troubleshooting_translator_issues with no resolution.

Setup:
Windows 7
Firefox 34.0
Zotero 4.0.23.1

Thanks for your help,
James
  • adamsmith
    Firefox 34 is the issue here. Won't come out of beta until Friday, Zotero isn't compatible with it yet.
  • jwbaker
    Ah. Thanks for your help. The perils of being on the beta stream!
  • adamsmith
    (@Dan, Aurimas - can you think of a simple way we could dynamically show current Zotero and Firefox versions? I've been doing a lot of "Update Zotero" and "downgrade Firefox" recently, and it'd be nice if instead of the generic advice on the troubleshooting page, we could be specific without having to update it with every new release of Zotero and Firefox).
  • RintzeRintze
    @adamsmith, might be doable with a dokuwiki plugin, like https://www.dokuwiki.org/plugin:fields.
  • dstillman
    Firefox 34 is the issue here. Won't come out of beta until Friday, Zotero isn't compatible with it yet.
    Monday, December 1st, actually. (Friday is the merge date.)
    (@Dan, Aurimas - can you think of a simple way we could dynamically show current Zotero and Firefox versions? I've been doing a lot of "Update Zotero" and "downgrade Firefox" recently, and it'd be nice if instead of the generic advice on the troubleshooting page, we could be specific without having to update it with every new release of Zotero and Firefox).
    I don't think showing the versions would be particularly useful, but I could see something like this:

    1) We set up a cron script that pulls the latest Fx version from Mozilla daily and saves it.

    2) We have some PHP code that generates an appropriate HTML message based on the user agent and Zotero version header, advising the user to upgrade or downgrade Firefox/Zotero as appropriate, and stuff it into a DokuWiki variable of some sort. (Won't help with Standalone version unless the connectors get in on the action.)

    3) We include that message in some of the troubleshooting pages.
  • adamsmith
    that'd be great -- with re recent issues with FF beta and pre 31 versions, I feel like this is 80% of all translator troubleshooting I do.
  • twwey
    Hello,

    I'm still having a similar issue today(Dec 21, 2014) with an article on JSTOR, where I see a Zotero icon for save to Zotero using DOI but cannot save the metadata ("could not save item" error). I have access to the pdf and can enter information and attach the pdf manually. Firefox 34.0, Windows 7, browsers and Zotero up to date. Just curious if this is a more or less permanent issue with JSTOR, or if there is a known fix. Thank you!

    Tina
  • dstillman
    Tina: Report ID?
  • twwey
    Oops, I hadn't generated a separate report yet, but here is the info:

    Report ID: 1512295357

    I was trying to import this paper: http://www.jstor.org/stable/2461927
    When I go to that link, I see the icon for downloading the item from DOI, but if I click on that, I get the error message "could not save item".

    I have accepted JSTOR terms and conditions and can download the pdf. Now that I'm looking into it, I've successfully downloaded metadata from JSTOR before, so this is a new issue for me.

    Thanks in advance,
    Tina
  • twwey
    Sorry for the multiple posts, but I just downloaded a more recent article from the same journal on JSTOR without issue, so it turns out this is just a problem with that particular article. I noticed that there was no DOI provided for it.
  • dstillman
    There actually is a DOI, but it's not registered with CrossRef, which is where Zotero looks them up currently. Not sure if it was omitted in error or whether it's in another database — other folks might know the details, but it won't save at the moment.
  • twwey
    Ok, thanks very much for the quick response!
  • aurimas
    That is actually an invalid (unregistered) DOI http://doi.org/10.2307/2461927. JSTOR often issues "DOIs" that are basically just JSTOR IDs affixed to their DOI preffix 10.2307. Then they don't always bother to register them with proper authorities (doi.org).

    The JSTOR translator was ust updated to recognize that page though, so this should no longer be a problem. Update your translators via Preferences -> General -> Update Now, restart the browser, and try again.
  • twwey
    That worked! Thank you so much!
  • RintzeRintze
    ... I could see something like this:

    1) We set up a cron script that pulls the latest Fx version from Mozilla daily and saves it.

    2) We have some PHP code that generates an appropriate HTML message based on the user agent and Zotero version header, advising the user to upgrade or downgrade Firefox/Zotero as appropriate, and stuff it into a DokuWiki variable of some sort. (Won't help with Standalone version unless the connectors get in on the action.)

    3) We include that message in some of the troubleshooting pages.
    Dan, assuming you get the information under 1 and 2, wouldn't it be handier to add a warning to the top of the forum pages, with text like:

    --

    Outdated Zotero version detected

    The latest Zotero version is x.x, but it looks like you have Zotero y.y installed. Updating to the latest version is usually one of the first troubleshooting steps we recommend, so if something is not working, please start by updating Zotero.
Sign In or Register to comment.