Citation Guidelines

Anyone is welcome to use this project (including the repertory, searchable database, and corpus of transcriptions) for the purposes of teaching and research. If the project proves useful to you, please acknowledge it in any resulting publications in order to spread awareness of it among the broader scholarly community.

Here is a sample citation for referencing the project or database as a whole:

Dorin, Rowan, ed. Corpus Synodalium: Local Ecclesiastical Legislation in Medieval Europe, 30 June 2021, www.corpus-synodalium.com. Accessed DD/MM/YYYY.

To cite the working repertory:

Dorin, Rowan. “A Repertory of Synodal Statutes and Provincial Canons, 1200-1500.” Corpus Synodalium, 30 June 2021, www.corpus-synodalium.com/repertory. Accessed DD/MM/YYYY.

When referencing individual texts that have been located via the searchable database, users should first confirm readings found in the online transcriptions against the sources from which they were drawn (whether printed editions or manuscripts), insofar as this is feasible. These sources are indicated in abbreviated form in both the working repertory and the metadata for each database text, under the headings “Source” (which lists important manuscript versions) and/or “Edition”, along with links to online digital versions where available. For full bibliographic references, consult the Bibliography. Published citations should be made to these originating sources, as appropriate, accompanied by a general acknowledgment of the Corpus Synodalium project.

Should you wish to cite one of the database texts directly (whether because the originating source is inaccessible, or because the transcription is newly created for the project), you are encouraged to include the text’s unique Record ID in the citation. (This is a four-digit number that appears alongside the header information whenever a result from the text is displayed.)

If you have any questions, or need help tracking down a source, please feel free to reach out to the project leader, Rowan Dorin ([email protected]).