The following table may clarify things further. (I apologize for not having secured access to CMOS 18e yet, but I believe the principles we’re discussing here haven’t changed much from the 17e.)
|
book, sv/mv |
vol. in mvbook 1 |
vol. in mvbook 2 |
chapter in svbook |
chapter in mvbook |
CSL type |
book |
book |
book |
chapter |
chapter |
title of chapter |
– |
– |
– |
title |
title |
title of volume |
– |
volume-title |
title |
– |
volume-title |
title of book (sv/mv) |
title |
title |
container-title |
container-title |
container-title |
title of series |
collection-title |
collection-title |
collection-title |
collection-title |
collection-title |
CMOS 17e |
mv: 14.117 |
14.118–9 |
14.118–9 |
14.107 |
14.120 |
sv: single-volume, svbook: single-volume book
mv: multi-volume, mvbook: multi-volume book
The table illustrates which variables can be used for the different title levels of various types of single or multi-volume books and chapters within such books. It demonstrates that within the CSL framework, not one but two combinations of variables are suitable for the case of volumes in multi-volume books. Additionally, it shows that collection-title
is relatively independent of the others.
The columns ‘vol. in mvbook 1’ and ‘vol. in mvbook 2’ illustrate two different methods of representing the two levels of titles involved. If title
is considered the one that is emphasised relative to the other, this distinction somewhat mirrors those made in CMOS 17e, 14.119 (also 14.121 and 14.122).
Examining the Armstrong and Böll entries from https://www.zotero.org/groups/2205533/test_items_library/collections/5V67EPX3 reveals that they use title
and volume-title
as in my ‘vol. in mvbook 1’ column (and not title
and container-title
as in my ‘vol. in mvbook 2’ column).
On the other hand, Euripides, Orestes (from the same Zotero group) has title
, container-title
and collection-title
, matching my ‘vol. in mvbook 2’ …
It would seem that either ‘vol. in mvbook 1’ or ‘vol. in mvbook 2’ could, in principle, be used for coding CSL styles. If both are implemented, it would be possible to generate either of the two different versions outlined in CMOS 17e, section 14.119, in the formatted output, depending on the variables included in the user’s data. However, I am uncertain whether the effort of implementing both versions in CSL style files would be justified. Nevertheless, if CSL styles were limited to implementing only one of these versions, users should be clearly informed which one is supported and which variables they should use in their Zotero or CSL-JSON data.
Regarding the handling of ‘chapter in mvbook’, there seems to be only one possible option, which is to use container-title
for the title of the multi-volume book. This led me to consider that container-date
might be the most useful new date variable. I had assumed that for a volume within a multi-volume book, the ‘vol. in mvbook 2’ option would be the most straightforward choice. However, upon designing the table, I recognized that this is not the sole option and that ‘vol. in mvbook 1’ can be expected to work just as well.
If ‘vol. in mvbook 1’ remains the preferred approach, we are left with the question of which date variable would be most appropriate in this context. Should we use container-date
regardless? Or would it be more sensible to introduce volume-date
for this case?
I believe that collection-date
would not be a good choice. If used at all, it should be reserved for specifying the date(s) associated with collection-title
, not with any of the other title variables discussed here.
In particular, collection-title
(and a possible collection-date
variable) should not be confounded with container-title
(and a possible container-date
variable). Within the context of CSL, a multi-volume title, as defined by CMOS, is either a title
or a container-title
, whereas a series title, also as defined by CMOS, is a collection-title
.