Can't save item from ScienceDirect
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
D1108499460
http://sciverse-shindig.elsevier.com/gadgets/ifr?container=default&mid=0&nocache=1&country=ALL&lang=ALL&view=profile&parent=http://www.sciencedirect.com/science/article/pii/S1053810011002674://www.sciencedirect.com [...]
Just to confirm, in the address bar you see direct ScienceDirect URLs? The main article URL doesn't appear at all in the debug output you submitted. (If it did, Zotero would use that, since it has a higher priority than DOI.)
Also, that URL above appears to have something to do with Refinder service—is that something you've explicitly enabled?
I'm still having problems saving items from SD.
I submitted an error report, ID: 817236697
I'm on campus so I'm logged in. I also tried logging in, but no luck either.
Just to recap, I updated the translator yesterday and I do see Sciencedirect when I hover over the URL icon.
Let me know if you need anything else
Much thanks,
Example URLs that are not working:
http://www.sciencedirect.com/science/article/pii/0378874183900363
http://www.sciencedirect.com/science/article/pii/0378874183900296
Should I submit an error report?
mark: Please do submit an error report if things are not working when you are not in guest mode.
I'll proceed with a hack to DOI, then, so we can fix this quickly.
http://www.sciencedirect.com.libraryproxy.griffith.edu.au/science/article/pii/S002192901100618X
I know that there is a library proxy in this url, but I have no trouble saving files from wiley with the same type of url.
I hope this makes sense. I'm not sure if I am missing something or not.
Thanks, Peter.
i was describing problems with sciencedirect a few posts up.
Apparently my debug code showed the url i was trying to save as:
http://sciverse-shindig.elsevier.com/gadgets/ifr?container=default&mid=0&nocache=1&country=ALL&lang=ALL&view=profile&parent=http%3A%2F%2Fwww.sciencedirect.com%2Fscience%2Farticle%2Fpii%2FS1053810011002674%3A%2F%2Fwww.sciencedirect.com
that is definately not what i see in the address bar. I have all proxies disabled (including in zotero).
I had never heard of 'refinder' but looking in my account details in sciencedirect I can see this is an application that has been enabled by my institution. I am not able to remove it. Is there something else I can try?
Thank you.
prjohnston: Thanks.
ajlyon: Zotero is still trying to save the wrong iframe. The advertising frame needs to be blacklisted from the SD translator, not the DOI one—sorry if I wasn't clear. vpolito's "shindig" URL is what's being used by the DOI translator (due to the frames bug that Simon has fixed).
Many thanks guys for all the work and help!
Thanks.
Example URL: http://www.sciencedirect.com.libproxy.ucl.ac.uk/science/article/pii/S107476130800112X
Error report: 2093980715 (although it doesn't seem to contain any Zotero errors, even though it was submitted immediately after triggering a failed item addition).
Details: Zotero 3.0b3 for Firefox on OSX 10.6
If this is fixed in the next release don't worry about it - the workarounds are relatively painless. Let me know if you need any further information or if I can help you with any (non-coding) troubleshooting steps.
http://www.sciencedirect.com/science/article/pii/S107476130800112X
and see if the Zotero translator detects that?
@Dan - debug output is here: D382799133 I had a quick look at the output and it does indeed seem to be picking up an advertisement frame - I didn't realise that this was only fixed in the dev XPI, and not in a translator update. I'll pass on installing the dev XPI for now as I'm about 80% of the way through a reasonably large project with Zotero and I don't want to risk breaking anything. If it would still be useful I'd be happy to install the dev version after my manuscript is submitted on the 24th January. I'm quite happy to work around this for now (Zotero has so many good ways to grab metadata these days that one way breaking almost never presents a major problem).
Thanks for your help.
The proper fix is in the dev XPI.