Guests are allowed to search through parts of the Suda that have been translated and stored in the database so far. Searches are currently limited to text phrases, but will be enhanced to allow Boolean combinations of phrases and searches restricted to particular keywords.
SOL keeps two versions of the translation database, the test version and the production version. The test version allows translators to experiment with data entry and to see the results without committing their work as finished. This version is erased periodically. The production version is meant to be permanent.
We use an idiosyncratic markup scheme at this point, but we intend to transform it to a TEI-conformant SGML/XML tag organization [Ini94]. A sample markup can be found at http://php.indiana.edu/~rchavez/sudadtd3.html. We use tags to delimit head-words, the English translation of the head word, the time the translation was entered, the identifier of the translator, the translation itself, notes to the translation, keywords appropriate to the translation, bibliographic citations of interest to the reader, pointers to related Web sites, and a quick classification of the entry.
When a particular entry is returned by the search engine, some of these fields are formatted and rearranged for readability; we call that appearance ``output format''. In output format, the identifier of the translator is converted to the translator's name and becomes a mailto link so the guest performing the search can contact the translator. Output format also includes the Greek head word in Beta code. Alternative viewing styles are also available, including Unicode [Con96], GIF images, and Java applets capable of displaying Greek. Because the TLG text of the Suda is protected by copyright, we do not include the original contents in the output format.
Guests may view the current state of the translation effort. A graphical picture is produced showing what parts of the range of each letter has been assigned to be translated (red) or has been translated (green); other parts (grey) have not been assigned yet.
In addition to viewing the global state of the translation effort, guests can also see the roster of registered participants, which is a list of names, affiliations, and e-mail addresses. (The names are also mailto links.)
A guest can seek to increase the level of engagement either by registering as a participant or, if already registered, by logging in.
Registration involves filling out a form giving those particulars that we store in the participant database, including the desired level of engagement, the desired participant identifier, and a password. Registration does not automatically confer approval. Instead, it generates mail to the community of managing editors informing them that a new participant has asked to join. Until a managing editor accepts this registration, it remains pending. When a managing editor either accepts or rejects the registration, mail is generated informing the guest trying to register of the outcome of the request.
A guest logs in by presenting a participant identifier (like samuel) and a password. If login is successful, the participant is presented with choices appropriate for the recorded level of engagement for that participant. If the login fails because the password is incorrect, the participant is given the option of receiving registration confirmation (which includes the password) re-sent through e-mail to the address on record.