Below are the deliverables promised in the 3rd Implementation Plan for
the third year of the project. The descriptions try to make more concrete
what they mean, and how they will be delivered in practice.
Number |
Title |
Description |
Due |
Delivered |
D5.1.4 |
Integration of XML schema for messaging within WP5.2 Project Tracking
Database design |
Needs to be clarified |
24 |
. |
D5.2.4 |
Integration of version 1 database handler with CCP4i |
Make a version of CCP4i that runs using the Python database
handler to interact with the data storage for project
tracking, to be released with CCP4 6.1. |
36 |
. |
D5.2.5 |
Specification of version 1 of the Project Tracking Database Design |
Publish a schema and supporting documentation (usage/implementation?)
of the design for the tracking and knowledge base databases. |
36 |
. |
D5.2.6 |
Implementation of version 1 of the Project Tracking Database design |
The design in D5.2.5 will be incorporated into the Python database
handler, and appropriate client APIs will be provided for Python and
Tcl. |
36 |
. |
D5.2.7 |
Visualisation tools integrated with project tracking database |
A "visualiser" client application will be built using one of the
APIs in D5.2.6 to interact with data stored in the database
specified in D5.2.5. |
36 |
. |
D5.3.5 |
Report on the feasibility of an integrated connection between VCS
and CCP4 (WP5.2) Project Tracking Database |
Needs to be clarified |
36 |
. |
Task |
Priority |
Person |
Achieved |
Identify and document features required by python handler from CCP4i
Tcl handler |
HIGH |
. |
. |
Identify and document features not in the Tcl handler but also
required in the "production" handler |
HIGH |
. |
. |
Incorporate these features into python handler |
. |
. |
. |
Develop python code for dealing with CCP4i .def files |
HIGH |
. |
. |
Incorporate CCP4i def file handling code into python handler |
. |
. |
. |
Define/document the XML "language" between the clientAPI and the
handler |
. |
. |
. |
Incorporate Python handler into CCP4i to replace Tcl handler, using
existing dbClientAPI.tcl functions (with minimal modifications) |
. |
. |
. |
Use new dbClientAPI.tcl as basis for specification of def file
API |
. |
. |
. |
Task |
Priority |
Person |
Achieved |
Specify SQL database schema for tracking based on CCP4i def file
contents and additional desirable data |
. |
. |
. |
Make a list of dbAPI commands for the new schema |
. |
. |
. |
Make a list of clientAPI commands for the new schema |
. |
. |
. |
Develop embedded database backend |
. |
. |
. |
Incorporate embedded server functionality into python handler |
. |
. |
. |
Develop "dbAPI" functions (analogous to "clientAPI", but defining
the commands inside the python handler) and incorporate into python
handler. |
. |
. |
. |
Build Tcl clientAPI to complement dbAPI for embedded database |
. |
. |
. |
Incorporate into CCP4i (may also need changes to CCP4i) as version 0.1 |
. |
. |
. |
Document version 0.1 schema, clientAPI and dbAPI |
. |
. |
. |
Task |
Priority |
Person |
Achieved |
Create SQL schemas for the Knowledge Base database based on comments/input
from HAPPy and XIA projects, and incorporating tracking database. |
. |
. |
. |
Incorporate Molecular Replacement knowledge (Garib/Alexei/Fei and Ronan) |
. |
. |
. |
Incorporate Data Harvesting/deposition requirements |
. |
. |
. |
Build/extend the client- and dbAPIs for this, defining the "rich DB API" |
. |
. |
. |
Communicate with potential users (HAPPy, XIA, CRANK, Autorickshaw, Charlie Bond) |
. |
. |
. |