It would be helpful if you would decide the contents of PIMS's first
deliverable.
The most urgent requirements I have heard are:
Sample location (Leeds) - not including barcodes at first
Target management (Leeds)
Expression scale-up (OPPF), i.e. simple experiment management
Audit trail (MPSI) - all edits are recorded, but access to the records
will be delivered later
Bioinf (Leeds, OPPF, SPF)
Do you agree this as a list of objectives?
These are arranged with the easiest to deliver first,
and we will provide as much as we can.
Once the list is agreed, we can progress to confirming the use cases to
meet these objectives.
Susy Griffiths has prepared drafts which are available from
http://www.mole.ac.uk/lims/project/use-case-suite.html
This will in fact be PIMS version 0.2.
Version 0.1 will be a development platform only, without user value.
Response to request
I've had some feedback from MPSI investigators on the contents of the 1st
usable version of PIMS (the salient comments are paraphrased below).
MPSI should meet soon - a date in december was mooted. It would be useful if
you could define a cut off date when the content of v0.2 is fixed.
----- Forwarded message from M.J.McPherson@leeds.ac.uk -----
One issue related to quality control and reproducibility, though not
initially specifically PIMS, that should be addressed .....
is the issue of standardising various consumables items so that when an
experiment is performed say in Leeds, and the results are added to the
PIMS system, then by using identical consumables it could be reproduced
elsewhere.....
By standardising on certain supplies from certain companies we should be
able to enhance productivity and the utility of the PIMS system.
See note 1 below
----- Forwarded message from p.bullough@sheffield.ac.uk -----
We will need to be able to add data on 2D trials and images of initial
screens in the EM (both protein preps and screens of 2D crystallisation
trials).
See note 2 below
Follow up and action points
note 1:
In the data model, the "Sample.Sample" class has attributes called
"catalogNum" and "BatchNum"
The "AbstractComponent" class has "catalogNum" attribute