Upgrade StorageDOI Import Problem from Cambridge University Press
Hello,
Zotero 2.0b6.5, FF 3.5.2
When adding items via DOI from a particular CUP journal (Organised Sound), I'm experiencing two problems:
- Pages sometimes don't seem to get added at all, sometimes just the starting page
- The date doesn't seem to be successfully parsed, insofar as the field appears as an xml fragment in the info pane, with suspicious looking duplication of fields, like
<month>11</month> <month>12</month>/<year>2008</year> <year>2008</year>
and when I export to a bibtex file, the date doesn't appear at all.
Example DOIs
(no pages):
10.1017/S1355771805000622
(start page only):
10.1017/S1355771808000277
Any advice appreciated,
Many thanks,
Owen
Zotero 2.0b6.5, FF 3.5.2
When adding items via DOI from a particular CUP journal (Organised Sound), I'm experiencing two problems:
- Pages sometimes don't seem to get added at all, sometimes just the starting page
- The date doesn't seem to be successfully parsed, insofar as the field appears as an xml fragment in the info pane, with suspicious looking duplication of fields, like
<month>11</month> <month>12</month>/<year>2008</year> <year>2008</year>
and when I export to a bibtex file, the date doesn't appear at all.
Example DOIs
(no pages):
10.1017/S1355771805000622
(start page only):
10.1017/S1355771808000277
Any advice appreciated,
Many thanks,
Owen
This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
The date issue should be fixable. Thanks for mentioning it.
For those with CrossRef accounts, you can modify the below URLs to check the data:
http://www.crossref.org/openurl/?id=doi:10.1017/S1355771805000622&noredirect=true&format=unixref&pid=INSERT_USER:PASS
http://www.crossref.org/openurl/?id=doi:10.1017/S1355771808000277&noredirect=true&format=unixref&pid=INSERT_USER:PASS
Glad to hear the date thing should be fixable though.
Thanks for the swift response.