Open KarlLevik opened 7 years ago
Some further additions to this:
ALTER TABLE BLSample_has_DataCollectionPlan
DROP `order`;
ALTER TABLE ScanParametersModel
DROP duration;
ALTER TABLE BLSample_has_DataCollectionPlan
ADD `order` tinyint unsigned;
ALTER TABLE ScanParametersModel
ADD duration mediumint unsigned COMMENT 'Duration for parameter change in seconds';
As discussed at the ISPyB meeting at Soliel earlier this week, Diamond has made some recent database schema developments to support our XPDF (pair distribution function) beamline.
While these schema changes have been "live" at Diamond for a little while now, we are happy to make changes to this if anyone finds a problem with it.
A few words about the schema changes
In the tables and columns you'll see the words DataCollectionPlan and Component. These are what we would like to rename the current DiffractionPlan and Protein tables to, respectively, in the future. This is to make the schema less MX specific.
packingFraction was previously erroneously added to Crystal, so we've now moved it to BLSample.
The table _DataCollectionPlan_hasDetector allows us to have multiple Detectors for each DC plan, and to use the same plan for multiple detectors.
The table _BLSample_hasDataCollectionPlan allows us to have multiple DC plans for each BLSample and also to use the same plan on multiple samples.
The enums DiffractionPlan.experimentKind and DataCollectionGroup.experimentType have to be extended to allow for XPDF data collection types.
Each DiffractionPlan needs to have a name to make them more easily recognizable by humans.
_DataCollection_hasScanParametersModel allows us to say that a DC was done using a set of scan parameters.
_DataCollectionPlan_hasDetector allows each DC to be associated with more than one Detector.
I would have attached a diagram to show the changes, but alas, it's not possible.
The SQL statements
Can these changes be merged into the official database schema?