Upgrade Storage"Subsequent" conditional for different items but same container-title or reporter
I'm citing Swiss supreme court cases which are generally cited as "[Reporter] [Year as vol.] [Division] [First Page]", e.g. "BGE 123 II 321".
Subsequent mention of cases within the same citation should drop the reporter, if it's the same. Meaning "BGE 123 II 321; BGE 456 III 654" should actually be "BGE 123 II 321; 456 III 654", omitting the second "BGE". Can this be achieved? As reporters are (AFAIK) not names but container-titles and the items are not identical, the methods I have checked so far fail.
Subsequent mention of cases within the same citation should drop the reporter, if it's the same. Meaning "BGE 123 II 321; BGE 456 III 654" should actually be "BGE 123 II 321; 456 III 654", omitting the second "BGE". Can this be achieved? As reporters are (AFAIK) not names but container-titles and the items are not identical, the methods I have checked so far fail.
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
More generally, you can't test for previous occurrences of any specific element -- subsequent can only test for the entire item and subsequent-author-substitute only applies to the bibliography.
You can improvise chain citations by turning this into a single item with 456 III 654 in "History"
no-repeat(see https://citeproc-js.readthedocs.io/en/latest/csl-m/index.html#no-repeat-extension). It should be implemented in a style-module.For posterity, the code now reads:
<group no-repeat="container-title" suffix=" "><text variable="container-title"/>
</group>
<group delimiter=" ">
<text variable="collection-number"/>
<text variable="division"/>
<text variable="page-first"/>
<text macro="locator-note"/>
</group>
You have to separate the part you want to omit in subsequent cites into its own group, as
no-repeatsuppresses the entire group.@evolin have you seen my private message? I don't mean to push. Just asking as I know from my own experience that those messages are too easily overlooked.