Ronan reported the problem he has got when using dbviewer in MrBump.
When taskname is set to a string containing space, then if open the project in CCP4i, the taskname will be lost and become empty string.
MrBump loses the writing permission randomly during the running. The handler returns message that 'database is accessed by other process, database is read only'. However acturally there is no other processes that access to the database. PJB suggested that using DbReacquire would help MrBump grab back the lock. But this is not an ideal solution. Upgrade current CCP4i will be the solution.
Ronan asked for the feature of highlighting the quality of job. Mark it as 'good', 'bad' or 'marginal' solution.
Review the extending of tracking database.
WY suggested that whether database.def could contain an item which application can define what it is, and what does it mean. So different applications can use it for their own purpose.
Store substeps is very useful. That is the next development we will focus on.
Knowledge base is used to store crystallographic data which can be shared within various applications. PJB suggested that use CCP4 Mlphare as a candidate to use knowledge base. In this way, we can test SQLite infrustrcuture.
PJB is going to attend ACA. We need a poster for ACA. PJB and WY plan to go to BSR and present a poster. The poster should make change on the previous one. We could add new information about MrBump using dbviewer. Emphasis could be in dbviewer.
PJB talked about broadcast issues. We should re-define the broadcast message.
Documentation of dbClientAPI should use pydoc to generate to keep it up-to-date.
Change commands in handler & API: for example, Database -> project, Record->job, Link->JobLink.
There was a dicussion of implemenation of subjob in ccp4i.py. Subjob could be made a sub class of database class. So many codes could be reused.
There was a dicussion of implementation of extra items in database.def. db handler could copy the file before it manipulate it.
Action Items
WY: write a client application to reproduce the problem that Ronan mentioned. Then investigate the bug.