Last changed: February 28, 2001      

Here are the improvements recently completed or still in prospect: blue means we'll get there eventually; purple means completed work). If you want a quick peek at how search results in our new version look, here's a screen capture. (NB buttons for pop-up Greek source text window and edit mode, bright red to indicate vetting status, yellow to highlight the search term in the text, linked keywords, translator's name as an e-mail link.)

1. Fix remaining problems with Greek display. Javascript popup windows delete grave accents from text shown to users with betacode or SGreek selected because betacode and SGreek use the backslash for the grave but that's the escape character for javascript.
2. Consolidate overlapping data files.
3. Add a "senior editor" user level who can: Assign entries (to self only?), check status of entries/contributors, send mail....(?)
4. Increase visual distinction of draft entries.
5. Make it possible to unassign entries (retire professor Outis)
6. Make it possible to browse Suda entries: Add option on searches "Browse translated entries beginning with [Adler number]? Add "See Next/Previous Translated entry" buttons to display.
7. Fix problem of when you hit "back" before confirming an entry it destroys any automatic links you put in.
8. Generate list of entries assigned and translated that all users can see.
9. Consider making it possible to transfer an entry from the 'draft database' to the real database with one click (and encourage more use of draft database?)
10. Make the generated pages look the same as the shtml (SSI) pages.
11. Add to user-defined profile the choice of a particular Perseus mirror.
12. Feature Extraction/Automatic Tagging:
    • filter data against authority tables of authors' names, place names, etc. and automatically insert TEI-style tags to facilitate automatic linking to useful resources for such entities
    • likewise, develop ways to identify and automatically tag citations that can become hypertext links.
    • It might be nice to supplement the feature-extraction programs with a java-based "select and tag" editorial system that lets editors add tags to various items manually.
    • we also need to identify, tag, and implement links for internal cross-references (the notes to alpha 1298 for example refer to alpha 1300).
13. Improve display of records: enable the managing editors to generate a table for each contributor of entries assigned and work completed (with dates).
14. Regularize appearance of site by calling standard CSS, headers, and footers from all scripts.
15. Run progress.pl and stabilization of qddb as nightly CRON job.
16. Clean up the list of translated and assigned entries at the end of the "recent activity" page (where, for instance, alpha 1 to something like 1200 are assigned, but the list has something like 1, 1, 1, 1, 5, 9, etc.
17. Change the assignment of entries page so that managing editors can assign more than one range of entries at a time.
18. Highlight search terms in search results with green font.
19. Add a button for every item in search results for those with editorial status to open a "modify entry" form.
20. Add a button for every item in search results for "show the Greek original" (javascript popup window showing Adler number plus entire Greek passage)
21. Make listed keywords hotlinks to searches of those keywords (be sure to preserve user preferences by passing along authentication)
22. Include a search box for new searches before and/or after search results so people don't have to back up
23. Fonts: enable Unicode Extended Greek (the filter is now available, at /export5/httpd/cgi-bin/Progs/GreekFilters/UTF8)
24. Use CSS to change the vetting status to different colors of text as a stronger visual cue to reliability
25. Fix any remaining uninitialized values in PERL code generating error messages
26. Suppress the invitation to search in other resources in the case of Adler numbers
27. Include the user's e-mail address in translation assignment requests that are e-mailed to the managing editors
28. Align the buttons properly!!
29. Add a text-entry box to the page for requesting to be registered as a translator or editor. Introduce the box with the following text: "Although no official credentials are required for participation in SOL as an editor or translator, competence in ancient Greek is a necessity. Please indicate briefly here your background and experience in reading and/or translating ancient Greek:" Mail contents of that box along with the name and e-mail of the person making the request to the managing editors.
30. Move the list of assigned and translated entries to the end of the page that you get when you click on "vet entries" (generated by edit_entry.pl). We've already done this for the "translate entries" page.
31. Proofread the English on all user-accessible pages
32. Fix the mangled headword for alpha 1! It ought to be *)\a )/a
33. Delete the Ismini Greek choice from the various Greek display selection menus
34. In the display of each translation, make the names of translators and editors mailto links so that any user can suggest additions or improvements to any entry
35. Repopulate done.dat and trans_done.dat from the trans.dat master file because inaccuracies have crept into the former.
36. Enable easier upgrading of users' status by adding the ability to modify profiles of all registered editors, translators, guests to the "Update Profile" feature (I.e., for managing editors only, user_profile.pl should generate a third option in addition to the two already there, and it should say "Modify the profile of" followed by a pull-down menu showing the names of all registered users.)
37. Suppress the user-supplied tags for italics, Greek, and titles in display of search results for now (later we'll do more interesting things: font conversion, links)
38. Fix the translation entry script so it preserves line breaks (two problems: %% not being converted to <br>, and in recent entries, %% not being added at all)
39. Automatically update a text file (progress.dat) containing totals (assigned to date, translated to date, vetted to date), so we can then grab that data with an SSI directive and display it on whatever pages we want