BIOXHIT/CCP4: Overview Plan for 2007

What we will do in 2007

This is intended to give a brief overview of what we aim to do in the coming year with the project.

Our immediate priority is to complete the overdue deliverables from 2006. In order to do this we will make a first public release of the dbccp4i files which will include the handler and API codes, database schemas, visualiser and documentation. This will form deliverables D5.2.5, D5.2.6 and D5.2.7.

We will also produce a small client application that can generate an XML description of a project history, conforming to the XML schema developed with Avi Naim and Graeme Winter. This will form deliverable D5.1.4.

Once a public release of dbccp4i has been made, PJB will begin work on making an initial version of CCP4i that can use the handler. This version of CCP4i will be made publically available and will be deliverable D 5.2.4.

After the release of dbccp4i, feedback from users and developers will be gathered to inform the next steps. This feedback will be gathered into reports for milestones M07/1, M07/2 and M07/3 (which are concerned with additional functionality for the tracking database, defining the knowledge base contents, and new functions for the visualiser.

• Feedback for the tracking and knowledge databases can be gathered by talking to developers who are interested in using the database: Graeme Winter for XIA2, Liz Potterton for CCP4mg and Paul Emsley for Coot. Also BIOXHIT partners could be approached.
• Feedback for the visualiser should be gathered by demonstrating the program to users, and encouraging them to try it. This could be done in various ways, for example via site visits and conferences.

Once feedback has been gathered for the milestones, a subset of features will be identified and implemented.

This still needs to be completed - PJB

How to manage the project in 2007

Some suggestions:

• Weekly meetings to discuss the progress on the current tasks, review outstanding bugs and issues, and to consider any new actions due to upcoming deadlines. Wendy to summarise these meetings and make a list of actions from these meetings.
• Schedule monthly reviews of progress towards the deliverables, and update the documents afterwards
• Put the tasklists and other documents in a shared location
• Make regular releases of the dbccp4i code

[Index] [Deliverables]