Since the range of topics covered by the Suda goes far beyond the expertise of any individual scholar, we depend on the wisdom and specialized knowledge of a diverse group of editors. We encourage our editors not only to vet translations, but also to share with us ideas for improving SOL. Please send any comments, criticisms, problems and new ideas to the senior editor (see the home page for a link to his address).

When you are ready to begin editing

First of all, log in with your username and password (if you have forgotten these, contact the managing editors)

If you know the Adler number of an entry you would like to edit, access the entry via the list of all entries (also accessible from the home page).

If you don’t have in mind a particular entry or don’t know the Adler number of the entry you’re interested in, you can find entries you would like to edit using any of the searching and browsing methods available on the home page and in the list of search options you find when you log in.

Once a particular entry appears on your computer screen, scroll down to the bottom of the display and you should see a button inviting you to “Vet this entry”.

vet this entry

Clicking this button takes you to the Vetting Page that looks something like this:

vetting page

Editable boxes present you all the different categories of information in the entry (Headword, Translation, Notes, Bibliography). You can change or add to the information in these boxes as you see fit.

Further down the page, there is a box in which you can enter or edit the URLs (web addresses) for associated web pages, with a line break between each URL. Below that is a scrollable menu with standard keywords that you can click to associate them with the entry (ctrl-click or command-click to select more than one keyword). Keywords give users an easy way to find entries relating to topics that often show up in the Suda.

keyword entry

At the bottom of the page is a button inviting you to “Click here to see the new work”. Before clicking this button, briefly describe the editorial actions you have performed in the “Vetting Comments” box, as in the following example:

vetting comments

When you click this button, your browser displays the work as you have edited it. If you see something else that needs to be added or changed you can use the Back key on your browser to return to the Vetting Page as many times as you like.

When you are done editing, be sure to click the “CONFIRM TO SAVE” button at the bottom of the display that shows your edits. Otherwise none of your changes will be saved to the database:

confirm to save

Be bold in editing! Even if you screw up very badly, the database retains all the previous versions of the entry, so restoring the entry to a previous form is not difficult (do contact the managing editors if you need to restore an entry).

You can come back to the same entry and make changes as many times as you think necessary. You do not have to do all your editing of an entry in one sitting. But please try to leave the entry in a presentable form when you take a temporary break from it.

Like translating, editing is never proprietary on SOL. After you have edited an entry, other editors can (and will) come by later and re-edit the same entry. Your name will remain attached to the entry as editor, however, in perpetuity. See this page on how to cite your own work in SOL.

Your goals as an editor

Your aim is to improve the translation and annotation of each entry in as many ways as you can. Here are some suggestions:

Please do not think that this list is exhaustive. If you see another way to improve an entry that is not listed here, don’t hesitate to do it.

Guidelines for Style and Content


The standard text for the Suda is that of A. Adler's Teubner edition (Leipzig 1928-35). Please note any deviations from Adler’s text that you follow in your translation in the footnotes. References to other entries in the Suda should use Adler’s reference numbers (see the citation form below).


Imagine as your ideal audience advanced undergraduate students who have some knowledge of ancient history and literature but little or no knowledge of ancient languages. Err on the side of giving too much information in your annotations (within reason), rather than too little.

Format and Punctuation

Greek words and names


In general, you should avoid abbreviations apart from common and standard ones like ‘etc.’, ‘cf.’, ‘e.g.’ and so on. Write out grammatical characteristics rather than abbreviating them (nominative singular rather than n.s. or nom. sing.). Do not abbreviate names of ancient authors or titles of works (Homer, <t>Iliad</t>, rather than Hom. Il.).

Tagging and character formatting

The Editing page does not recognize most standard HTML tags; nor does it recognize the sorts of character formatting (italic, bold, etc.) that your word processor can produce. The following three are the only tags that the software recognizes and accepts:

Citations and Bibliography

Citations of other entries in the Suda

Cross-references to other Suda entries should cite the reference numbers in Adler’s edition. To refer to the entry on ‘kottabos’, for instance, you should cite kappa 2154 rather than (for instance) s.v. ‘kottabos’. Please note the format of the reference (kappa 2154): lower case, with a single space and no punctuation between the letter and the number. Giving the Suda citation in this precise format allows the software to generate an automatic hyperlink to the referenced entry.

Citations of other ancient lexica

Some standard editions of ancient lexica use reference numbers similar to the Suda’s Adler numbers, and you should cite those editions in preference to others if they are available to you. Three such editions of lexica that are frequently cited as sources or parallels to the Suda are the following:

If you have access to these editions (and all but the third volume of Theodoridis’ Photius are currently in the on-line TLG), you should cite entries in them as follows:

The lack of a space between the letter and the number in these citations is not a typo. These lexica (and others using this reference system) must be cited in this fashion to keep the software from creating an automatic link to the Suda. For instance, the citation Hesychius alpha 2127 would generate an automatic hyperlink to the Suda entry alpha 2127.

References to ancient sources in general

These references should be written out rather than abbreviated, e.g. Homer <t>Iliad</t> 3.227 rather than Hom. Il. 3.227, and should be put in the footnotes, not in the translation field or in the bibliography. There is no need to cite the edition of the ancient text you have consulted unless you are discussing a particular editor’s reading or recension. If you do need to give full bibliographical information for a particular edition, put that in the bibliography rather than in the footnotes.

References to modern scholarship

These references should receive abbreviated parenthetical citations in the footnotes, e.g. (Traill 1975), (Whitehead 2002: 179-80), with full bibliographical information relegated to the bibliography field.

Use the following as models for listing works in the bibliography/reference field:

Please observe the following in the bibliography:

References to on-line resources

You should not put the full URLs (web addresses) to on-line resources (articles, texts, etc.) in the translation, footnotes, or bibliography fields. Instead put them in the box for web addresses near the bottom of the Vetting Page, each one on a separate line. Then refer to these addresses in the notes in parenthetical citations in the following format: (web address 1), (web address 2), etc. The software reads what you put in the web address field and converts each URL into a hyperlink labelled “web address 1”, “web address 2” etc., based on the order in which your URLs are listed in the web address field. You do not need to write “web address 1”, etc. in the web address field yourself. In fact, the software will not work properly if you do.

Try to find the most brief and stable URL for any on-line link you refer to. Many web pages will offer a ‘URL for citation’, or a button to click that will copy the URL to your clipboard, which you can then paste into the web address field.

The Perseus Digital Library has many useful resources you can link to, including an on-line copy of the LSJ lexicon and a large number of Greek and Latin texts with English translations. If you are looking at a text on the Perseus site, the bottom right-hand corner of each page has a listing for a “Citation URI” that you can copy and paste into the web address box to provide a link to the precise location in the text to which you wish to refer the reader.

When you enter the URL in the web address field, be sure to give the entire URL, including the http:// or https:// at the beginning.

Before saving your edits, it’s a good idea to check any links that you have generated (as well as any that were there before), and fix or remove any that don’t work. If you can’t figure out why the link won’t work, the Managing Editors might be able to help.

As always, if you run into issues not covered in this overview, please ask the managing editors about it. Many thanks in advance for your contributions to the improvement of SOL!