Tasklist for release 0.1 of dbccp4i, database and visualiser

Description	Make an initial public release (version 0.1 "Rabbit") of dbccp4i which consists of the handler, the various database schemas, and the visualiser, to satisfy deliverables D 5.2.6 ("Implementation of version 1 of the Project Tracking Database design") and D 5.2.7 ("Visualisation tools integrated with project tracking database").
Date due	31/12/2006
Depends on
Assigned to
Estimated time

Make the first release of the handler by 12th March
Determine which bugs need to be fixed before releasing:
- #2089 (implement "compatibility mode" so that dbCCP4i can work ok in parallel with existing CCP4i)
Tidy up the code:
- Tidy up the directory structure: move dotgraph into its own directory
- Fix the licence banners (bug #1861)
Check the installation instructions for third parties
Get some people to try out the installation and usage
- Liz Potterton could do this for us

We must be very careful that the underlying code does not in any way corrupt someone's existing database.
- Put tests in place to verify correct behaviour
- Include PJB's db_recover.tcl script (or equivalent) in dbccp4i (now flagged for 0.2 release, see below)

Fixed socket-size and communication issues in client APIs (bugs #1921, #2004 and #2025)
Fixed bugs #2051 (Tcl client API should escape special XML characters), #1889 (SetData issues) and #2055 (disconnection from handler is slow/buggy)
Setup file moved from bin/ and put into etc/
Missed original target release date of 19th February (BIOXHIT meeting at DIAMOND). Instead, a set of deliverables were made available via the CCP4 BIOXHIT public pages.
Fixed bug #1985 (resizing issues in the dbviewer)
Put the python console into application directory
Fixed bug #2154 (dbsocket.py return error when running starKey or dbconsole.py)
Fixed bug #2121 (bubble help left behind when loading another projects)
Reviewed the visualiser to identify issues to be addressed for release - identified and fixed an number of these
Updated the client APIs to include all the available commands implemented in the handler.

db_recover.tcl functionality (regenerates a new database.def file for a project based only on the files that are found in the project directories; can't recover data from other sources e.g. dbconsole).
Testing under Windows (will be required for CCP4i integration)
Setting up tests for each component (what do we need? Can we run them frequently? might help define the API?)
Review the client APIs to see if we can standardise the return values.
Review the documentation