id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc 1442,BioPlate events,Nicklas Nordborg,Nicklas Nordborg,"The basic idea is that things that are normally done to a single biomaterial at a time (in the gui) or with batch importers should be possible to do with all biomaterials on a plate in a single 'plate event'. For example, it should be possible to take a bioplate with samples and create extracts from them using the web gui. * We need more ""plate types"". The current bio plate implementation allows for biomaterial to be moved around and a single plate can be re-used with other biomaterial some time in the future. This is only true for 'storage'-type plates were the biomaterial is in a test tube. Plates of other types become contaminated when they are used and cannot be re-used. Biomaterial that is put in this type of plate can not be moved. * We need some kind of flags to lock biomaterials to plates. We need a flag to indicate that a plate has been destroyed. We may also need a flag to lock a plate to a specific type of biomaterial (eg. only samples or only extracts are allowed on the plate) * We need some kind of ""event type"" declaration that defines some kind of constraints for an event. For example, - what kind parent plate type is required - what kind of child plates that are created - what type of source biomaterial that is required - what type of child biomaterial that is created - the protocol - a default coordinate mapping (may be locked or open for user modification) - and possible more.... * A ""plate event"" is then used to record the individual details about a single event. The information in the plate event and the rules in the event type are used to create the new plate and the new biomaterials. This ticket may be divided into more tickets as work progress. ",task,closed,critical,,core,,duplicate,,