CONF - conference paper vs conference proceeding
Zotero interprets the RIS field "CONF" as an item type of "Conference paper", but the RIS spec says it's "conference proceeding" and has the field "CPAPER" for "conference paper".
Is there a further nuance that I'm missing or is Zotero doing it wrong?
Is there a further nuance that I'm missing or is Zotero doing it wrong?
There CONF = Conference Proceedings and CPAPER = Conference Paper. So having Zotero do CONF = Conference Paper is wrong (again, if I read the spec correctly).
The conference paper item type in Zotero is principally intended for papers published in proceedings. CPAPER in RIS doesn't even have a field for a proceedings title, so just mapping that would lead to data loss.
CONF on the other hand doesn't just have a mapping for proceedings title (C3), but also one for title (the standard TI). If it's just intended for the entire proceedings, what would TI be for? So I think it's not unreasonable to understand CONF as "paper published in conference proceedings" and CPAPER as "unpublished paper given at a conference". And if that's the case the current mappings are the best we can do. If anything we could consider mapping CPAPER to presentation.
For example, CONF has fields like "Number of volumes", "Edition", and "ISBN" that would seem to belong to a book-like thing, more than just a single paper.
I would agree that CPAPER seems to be meant for papers that are not in proceedings, but they are perhaps published, as it does include PB, SP, VL and other fields that suggest a publication in some form.
It's also the case that I got on this by downloading an RIS from WorldCat for a book of conference proceedings that had the type CONF. WorldCat isn't great at implementing RIS, of course.
I suppose in the end Zotero should have a good conference paper type, but not interpret CONF to be that. What is the conference-proceeding type in Zotero then?
which, as he says, Worldcat e.g. has as CONF
It seems pretty clear that CONF is principally meant for papers in proceedings. (the fact that it includes ISBN, # of Vols. and editions doesn't speak against that. So does CHAP)
https://github.com/ajlyon/zotero-bits/issues/23
On the other hand, is there something specific about citing a conference paper published in a periodical vs. citing a journal article? Same for book section. I'd have the same comment as I did above. I can't imagine someone citing the periodical as a whole. I looked thorough some of the referenced threads in the proposal, but I didn't really see a very compelling reason besides categorization within Zotero library.
You can update your translators via Preferences -> General -> Update Now. The update will not affect importing RIS files directly, so you will have to use the URL bar icon to import these correctly.
I don't mind turning WorldCat's CONF into BOOK (that's what I've done in Zotero), but the reality is that proceedings have fields that books don't, like "date of conference" and treating CONF as BOOK throws out that information (or puts it into a note of fields not found in Zotero).
I also remain unconvinced that CONF is intended for papers. That CHAP contains book-related info is likely to allow citation of the chapter in the context of the book, no? That is, I might have a chapter specifically cited and also provide enough book info for the book to be found, and in fact the type CHAP has T2 for book title. Chapter citations will normally include info on the book. Likewise CONF has the same info because proceedings may be published as books.
In the end this isn't a great set-up in RIS. CONF and CPAPER clearly don't have the same relationship as BOOK and CHAP, even though one might expect that.
I think we're beginning to spend time over a inadequately explained standard no one here is responsible for. I appreciate the attention and the change to the translator.
"But a) are those ever cited as a whole? and b) if so are those citations different from regular edited book citations?"
which is relevant for how we deal with this in Zotero
The difference to my mind lies in the book vs. the proceedings, not the smaller pieces. The conference has place and date info that a book does not. CONF allows this info, but BOOK doesn't. Overall I'd say CONF *is* very similar to book. Here's a list of the fields CONF has, but BOOK doesn't:
A4 - Sponsor
C1 - Place Published
C2 - Year Published
C3 - Proceedings Title
C5 - Packaging Method
CY - Conference Location
M1 - Issue
PY - Year of Conference
T2 - Conference Name
Obviously C1 and C2 do appear in BOOK in different fields (which I don't understand the reason for), but the rest are specific to conferences.
Looking the other way, CONF lacks the following BOOK fields:
A4 - Translator
C3 - Title Prefix
C4 - Reviewer
CY - City
J2 - Abbreviation
M1 - Series Volume
M3 - Type of Work
OP - Original Publication
PY - Year
RP - Reprint Edition
SP - Number of Pages
Year does appear in CONF, but in a different field, but arguably very few others would be necessary.
In short - despite my nolo above - I'd still hold that CONF looks like it would be the place for a book of conference proceedings.
http://libguides.reynolds.edu/content.php?pid=143373&sid=1220383
So the discussion is now focused on how to best import CONF in general. If citing a section of conference proceedings in some citation style requires including conference title or conference date or location, then we would probably want to stick to "Conference Paper" and expand some of the available fields. If nothing special is required, then we can import it as a "Book Section" or "Journal Article" depending on whether an ISBN or ISSN (or some other criteria) is specified. If we need to cite the proceedings as a whole (and again, I do not think that CONF refers to the whole collection of proceedings), it would probably have to be imported as a Book or (the possibly upcoming) Periodical. I would argue, however, that it is always safer to import something as a section (of book or journal), because this retains the most information.
And my argument against CONF referring to the entire collection of proceedings stems from the fact that CONF has fields for Author (AU) in addition to Editor (A2), Pages (SP) instead of Number of Pages that we would see for a book, and Title (TI) in addition to Proceedings Title (C3)
For me the only remaining question is we need to worry about citing entire proceedings in a way that Book doesn't capture.
Again, I think the RIS standard is poor here and we're arguing over imprecision in someone else's work. For example, is it "Conference Proceedings" in the plural, as in the spreadsheet, or "Proceeding" in the singular, as in their accompanying pdf?
And what in the end is supposed to be the difference between CPAPER and CONF, if both are meant to be conference papers? CPAPER has "SP pages", so the idea that it's meant for unpublished content seems odd.
I see a need to have something like a type of "book", which includes conference date and place info. Despite some oddities (like SP = "pages" and not "number of pages") CONF looks to me like the right RIS type. WorldCat seems to agree, but they're not a stickler for detail in RIS , it seems, so I'm not sure that agreement means much.
Edit:
FWIW, NLM style guide also gives a large number of examples where the entire book is cited ( http://www.ncbi.nlm.nih.gov/books/NBK7272/ ). We may be unable to avoid adding a conference proceedings item type. It would essentially be a book/periodical with 3 additional fields, so perhaps as far as maintenance is concerned, this wouldn't be a huge deal for Zotero. A bigger problem is the corresponding CSL mapping. I'd still like to find real life examples of where such citations actually occur though.
On the CSL side we don't need an item type. We can just treat this as a book and add event place and date when it exists in the data.
Which leaves us with the representation of this in Zotero. Adding conference data to the book item type seems odd to me, but so does adding a very rarely cited type as a new item type - we'll have too many of those anyway. If we had hierarchical item types this would be a no brainer, but those are a long way out. So I'm not sure how best to solve this.