In order to support the automatic upload of sequence data from multiplexed high-throughput sequencing (PacBio protocols in our lab specifically) we need to be able to add Multiplex Sequencing Run records that, in addition to some metadata, serve as collections of the PCR products used to prepare the sequencing library. Discovery needs to be done on what metadata is required, apart from the true basics (a scientist ID, an entry date, a name for the run).
Users must be able to create Sequencing Runs, as well as search for PCR products and add them to the run. Metadata display for PCR products in the context of the Sequencing Run display should highlight the original sample and the primer used for RT, which contains the sample barcode for sequence multiplexing.
A sequencing_run table with a many-many join to pcr_product
CRUD for sequencing run records
UI flow for adding PCR products to a sequencing run as "products being sequenced"
Business logic to verify that a sequencing run is "appropriately multiplexed", i.e. each PCR product included has a distinct sample ID primer (such as PB_A1…, PB_A2…)
In order to support the automatic upload of sequence data from multiplexed high-throughput sequencing (PacBio protocols in our lab specifically) we need to be able to add Multiplex Sequencing Run records that, in addition to some metadata, serve as collections of the PCR products used to prepare the sequencing library. Discovery needs to be done on what metadata is required, apart from the true basics (a scientist ID, an entry date, a name for the run).
Users must be able to create Sequencing Runs, as well as search for PCR products and add them to the run. Metadata display for PCR products in the context of the Sequencing Run display should highlight the original sample and the primer used for RT, which contains the sample barcode for sequence multiplexing.