Reviewing for BMCR
Publishers may send books for review to:
Bryn Mawr Classical Review
Thomas Library, Bryn Mawr College
101 N. Merion Ave.
Bryn Mawr, PA 19010
See here for updated lists of books available: Books Currently Available for Review
BMCR is a peer-reviewed journal. Books are assigned to reviewers with the help of the editorial board. Books unassigned at the end of each month are published as an email to all BMCR subscribers and to our website. Reviews, once received, are divided between senior and associate editors, depending on subject and language, who then send them to members of the editorial board, thus ensuring that most reviews are edited by at least two people. Unless editorial intervention is significant, reviews will be published as the editorial process is completed. The entire process can take as long as three months, but most reviews are published more quickly. If you have submitted a review and it has not been published within three months, please contact us at firstname.lastname@example.org.
BMCR accepts any American or European style for references and punctuation. However, we do ask that you italicize all book and journal titles both in your text and notes, and please follow the more specific instructions below.
Please send your review or response of no more than 2000 words (including text and footnotes) as an email attachment in .doc, .docx, .txt, or .rtf format to email@example.com within four months. Reviews or responses that are too long or do not follow these formatting guidelines will be returned for revision. Once we’ve received your review, it should be published within three months; if it is not, ask us why. *See below for a note on our editorial process.
Rolando Ferri, firstname.lastname@example.org
Richard Hamilton, email@example.com
Camilla MacKay, firstname.lastname@example.org
Heading (ignore this section for responses)
- In the heading, please include the information about the book that we published in our monthly Books Received list (search the website if you no longer have that information).
- Please give YOUR name, institution, and email address.
- Check Google Books for a Limited Preview or Full View of the book (not a snippet view). If a preview or full view exists, insert a link in the review (see below for more on URLs):
- If there is no Google Books link, please include the table of contents, in one of the following forms. A table of contents should be included for volumes of collected studies but can be omitted where it provides little
information to the reader.
1. Search the LC catalogue (http://catalog.loc.gov/), the Deutsche Nationalbibliothek (https://portal.d-
nb.de/opac.htm), or other library catalogue to see whether there is a link to an html or PDF table of contents in the book record, which can then be inserted into the BMCR review below the reviewer's name in the form: <u n=http://www.loc.gov/ [etc.]>Table of Contents</u>. A link to a publisher's website can also be used, but is less desirable because the URL may change.
2. Insert the table of contents at the end of your review, noting at the beginning of the review: “[Authors and titles are listed at the end of the review.]” (You may be able to copy the TOC from the publisher’s website.)
Review or Response Body
- Please do not abbreviate names of authors.
- Follow each paragraph with an empty line . DO NOT indent or use tabs.
- DO NOT use italics, bold-face, or underlining. Please tag titles or anything else that should appear in italics with <i>...</i>, e.g., <i>nomen</i>. Bold and underlining is not possible with our system..
- DO NOT use footnotes. Both the note and the reference to the note should be numbered [] [] [] etc. (that is, the number of the note in double square brackets). References in the text must be made manually: type [] [] [] etc., where you would otherwise place the footnote marks, e.g. “in the earlier book,[] …” (i.e., after any punctuation, with no space). The notes themselves should go at the end of the text, numbered [], [], [] etc.
- To insert a link, tag it like this example: <u n=http://bmcr.brynmawr.edu>Bryn Mawr Classical Review</u>, with the link you wish to appear between the <u>...</u> tags. Links to BMCR reviews only should be encoded BMCR <b>2009.01.01</b>. (In our system, <b> is not code for bold text; rather, it automatically generates a link to the BMCR site.)
- If you wish to indent a long quotation (i.e., more than seven lines), please use <q>...</q>. Otherwise use quotation marks.
- Single line breaks must be tagged. Separate lines of verse or any lines that should be single-spaced with <v> before and </v> after each line. (A paragraph return will not work.)
- Superscript and subscript characters are coded <sup>…</sup> and <sub>…</sub> (e.g., IG II<sup>2</sup>
Languages, accents, and symbols
- Any characters in any language (including Greek) and any symbols can be used in your review, but they must be Unicode.
We expect that reviews will have:
- A a brief summary of the book's content and purpose, indicating its major sections;
- an assessment of the argument and the use of evidence;
- a discussion of its place in current scholarship, i.e., aspects of the book which the reviewer thinks are important and innovative or of doubtful success or value;
- notice of factual errors and their gravity (presentation or appearance should generally be ascribed to the press, and content to the author).
We expect that reviews will not have:
- ad hominem arguments;
- longwindedness or excessive detail (you're judging the author's case, not re-making it);
- excessive quotation, either of the book or of primary sources;
- attacks for not being the book you would have written.
For collected essays, since it will often be impossible within the assigned word limit to discuss all contributions one by one, we recommend beginning with an overview of the book with a summary evaluation, and then discussing some interesting, outstanding, or problematic contributions.
A note on the editorial process: Reviews are collected each month. At the beginning of the following month, the reviews from the previous month are divided up among the Associate Editors by subject, who then distribute them to members of the editorial board. These two editors read the review for content and for grammar, spelling, and typos. Reviews that require minimal correction (typos or spelling) are not returned to the reviewers before publication. Reviews are returned to reviewers only if substantive changes are needed. While every effort is made to work with reviewers to improve problematic reviews, reviews are occasionally rejected on the recommendation of the associate editor, with the agreement of the senior editors. Reviews are normally published within one to two months of receipt, but please allow three months before contacting us (and at that point, please do contact us if your review has not been published or if you have not heard from us).
Authors retain copyright in their reviews, and are welcome to archive copies of their reviews on their own or institutional websites or repositories. We prefer that authors archive the final version of the review (the review we published), and include the link for the review on this website, the blog, or both.
Bryn Mawr Classical Review is committed to upholding the highest standards of publication ethics and takes all possible measures against any publication malpractices. All authors submitting reviews to BMCR for publication as original articles attest that the submitted works represent their authors’ contributions and have not been copied or plagiarized in whole or in part from other works. The authors acknowledge that they have disclosed all and any actual or potential conflicts of interest with their work or partial benefits associated with it. BMCR is committed to objective and fair peer-review of the works submitted for publication and to the prevention of any actual or potential conflict of interests between the editorial and review personnel and the reviewed authors. Any departures from the above-defined rules should be reported directly to the senior editors, who are committed to providing swift resolutions to such problems.