I checked it now with Zotero 2.1.10 again, and nothing changed. Some weeks ago I made a diff between your git-Version and the shipped version, there was nearly no difference. Other suggestions?

@ajlyon:
your fix didn't worked. I checked the fieldTypes in the database and the line

JF:"publicationTitle"

in the bookChapterFieldMap section helped.

So maybe there is some confusion between proceedingsTitle and publicationTitle somewhere in the ZoteroCode.

Let me know if you choose JF or T2 for the corresponding RIS-line.

Thank you for your help

Hello,
I had a similar problem, as a conference paper reference exported with the default RIS.js (and also with the one downloaded from the link above) did not completely import to Endnote.
I modified the RIS.js so that it now imports to Endnote and also completely imports back to Zotero.
I uploaded it to
http://www.filefactory.com/file/1qkiu9vbw85/n/RIS_js
Please have a look at it and tell me whether it is OK.
Wilfried

I agree with noksagt, Zotero should export strictly (unless there's no appropriate field at all) in the written RIS specification. We can, however, accommodate a lot deviations from the spec when importing. If EndNote cannot import RIS spec properly, that an EndNote bug and we can possibly provide an EndNote-specific export style.

Edit: Having said that, I am getting close to adding a lot of accommodations for RIS files exported from ProCite and once that is done, I will revise our export code. Unless someone else tackles that before hand.

@adamsmith:
The RIS specification was revised last October...perhaps to document the behaviour that Endnote has evolved fairly organically:
http://www.refman.com/support/risformat_intro.asp

Somewhere else on the forum, someone has consolidated the multi-sheet spreadsheet into a single table that maps the type-dependent specs.

Thanks for the comments.
The current RIS.js handles a conference proceedings equal to book section, while the Zotero program handles them differently, so I think there is a need to modify RIS.js.
My first intention was to change as little as necessary.
With respect to the RIS specification consolidated table, proceedings title should go to C3 instead of JF.
JF isn't defined in the specification at all, so I wonder why it is used in RIS.js. To maximize backward compatibility, I suggest only to change the handling of proceedings (that's what I did). The current RIS.js export has two assignments to T2, first from publicationTitle, second from bookTitle, but the exported file contains neither of both. It seems that although publicationTitle is defined in the proceedings record, the T2 output is subsequently deleted because bookTitle is undefined. If I exchange the order of both, T2 gets output, its contents being taken from "Proceedings Title". But according to the RIS specs (and also Endnote import), T2 should be "Conference Name". So the proceedings type needs to be handled separately.

With respect to DOI, I did not change it because DOI import/export works as it is now, with several webpages offering RIS export (e.g. some Elsevier journals and ieeexplore) and also Endnote import/export.
Similarly, in the ReferBibIX format the DOI output does not conform to the specs listed in
http://savanna.lternet.edu/reports/endnotetags.php
So I do not want to start a discussion on meeting the specifications here, I only want to modify RIS.js so that it works with what we get.

I modified RIS.js to use T2 for "Conference Name" and C3 for "Proceedings Title", which is consistent with both the specification and Endnote import/export.
Please get RIS.js from
http://www.filefactory.com/file/68s1t6zhgtuv/n/RIS.js
Wilfried

I'm not sure what a CPAPER would be - if it's a paper given at a conferences, but not published in proceedings, it should map to presentation in Zotero.