Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Support multiple items per citation-number (for chemistry journals) #36

bdarcus opened this Issue · 7 comments

3 participants


We need to be able to support compound reference styles with output like:

(21) (a) Childs, A. F.; Goldsworthy, L. J.; Harding, G. F.; King, F. E.; 
Nineham, A. W.; Norris, W. L.; Plant, S. G. P.; Selton, B.; Tompsett, 
A. L. L. J. Chem. Soc. 1948, 2174–2177. (b) Chase, B. H.; Downes, 
A. M. J. Chem. Soc. 1953, 3874–3877.

My understanding is this conceptually like a footnote citation, where the individual references simply get labeled based on their position in the list.

If I understand that right, then all we need to be able to get the index number for the position within the citation, and then format that using cs:number. Does that mean we need to add something like reference-in-citation-index to the cs-numbers pattern?

Aside: we have first-reference-note-number as a simple variable (not on number). Two things:

  1. well, should it have been under number?
  2. we probably need to establish consistent naming of three things:
    • the full citation as a whole
    • the individual references within the full citation
    • the item in the bibliography

This is doable, but it's not going to be trivial to implement. In-text references have to be able to target individual references embedded within a citation, and discriminate back-reference groups that list all of the references in a citation from those that consist of only a limited selection. The latter need to be rendered with their position numbers (possibly with collapsing?), and the former need to be rendered as bare numbers (also with collapsing?). Past discussion is here:

@fbennett fbennett closed this
@fbennett fbennett reopened this

I forgot about that thread. It sounds like your original optimism in that has given way to a greater pessimism?

I'm getting a bit confused by the jargon though. It seems like if we do tackle this, the easiest way is to formalize it in both spec language, and one or more tests. But it also seems like we shouldn't do this anytime soon.


I'm still optimistic, but with Zotero 2.1 going final, I need to focus on bug fixes and stability for the time being. Implementing the grouping logic for this will involve some internal changes that might affect stability in the short term, so I'd like to hold off for a bit until things settle down.

@fbennett fbennett closed this
@rmzelle rmzelle reopened this

A question raised by a student at a writing workshop here has gotten me to take a more sympathetic view of this category of styles. When a particular discovery arises from a chain of smaller innovations, the grouped treatment provides a concise expression of their interconnection, for purposes of the immediate discussion.

I'll try to put some time in on this during the summer.


Hmm. There is a problem with this. The Wiley guide contains this example (ellipsis added):

[1] ... b) H. J. Ache, Angew. Chem. 1989,101, 1–21; Angew. Chem. Int. Ed. Engl. 1989, 28, 1–20; ...

Rintze pointed out (three years ago) that this collapsing of two cites within a composite citation will make implementation particularly tricky. Tricky but doable, I thought; but looking now at the Wiley guide again, I'm realizing that this is even more idiosyncratic than we have assumed:

When citing publications from Angewandte Chemie, please quote both German and International Editions. The page numbers of the German version can be found at the end of the article itself and in the annual index of the International Editions.

So the collapsing is not based on common authorship alone, but on the identity between two manifestations of the same work published in two specific journals.

I had just opened a development branch in the citeproc-js repo for this feature, but after reading that, I'm tempted to close it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.