sanger / sequencescape

Web based LIMS
MIT License
85 stars 33 forks source link

DPL-913 Submit banked PBMC tubes for cDNA prep #3900

Closed KatyTaylor closed 7 months ago

KatyTaylor commented 1 year ago

User story As an SSR, I would like to be able to submit a collection of tubes containing banked PBMCs for cDNA prep, as part of the "scRNA Core" pipeline.

Who are the primary contacts for this story Katy, Lesley, Abby, Liz H

Who is the nominated tester for UAT Abby, Liz H

Acceptance criteria To be considered successful the solution must allow:

Additional Information We will use the HT library types added for 'bespoke' activities in https://github.com/sanger/sequencescape/issues/3883:

Lesley84 commented 11 months ago

1) How will the communication happen here? e.g. When they determine there are enough banked cells in storage to go down the pipeline, BioResource team create an RT ticket for the SSR, listing out the tubes? To be determined for the SSRs and BioResource

2) Who knows / how do they know which cost code (Sequencescape "Project") is relevant for each tube? (Study should be known as it was specified on the manifest, when the samples were first uploaded prior to cell extraction). To be determined for the SSRs and BioResource

3) OK if this is a normal "manual" submission, managed by SSRs? To be determined for the SSRs and BioResource

4) Should the submission be just for the thawing step (before the 2nd entry point to the pipeline), or for the whole of the cDNA preparation step? Needs stakeholder and dev agreement. Considerations: what chunks billing will happen in; whether pool plates from SeqOps-banked cells will ever be combined with pool plates from faculty. If there is just one submission and the cell count is poor post-thawing and as a consequence, it doesn't move forward for cDNA prep will the customer still be billed for cDNA prep (assuming contingency also fails)? Also, how would this look if we had to use contingency samples? Can we discuss combining with SeqOps and faculty plates when we meet on Monday it will be useful to have the process map alongside and there are multiple considerations. The risk of cross-study swaps is high.

5) Should it have a "library type"? Assume no, as we are not creating "libraries". Library type will come in in the next submission - when enters the existing 5' Chromium pipeline. There are alternative protocols for cDNA prep which will need to be defined here. e.g. 5' or 3' for example

6) How should we refer to the "middle" section of the pipeline - is "cDNA prep" OK? (as opposed to the first section, "cell extraction", and the final section, "library prep" or currently "Bespoke Chromium 5 prime") 'cDNA prep' is fine

KatyTaylor commented 11 months ago

More thoughts on q4 above:

KatyTaylor commented 11 months ago

Notes from meeting yesterday:

Library types:

Submissions / selecting samples to go onto the 10X chip together:

KatyTaylor commented 11 months ago

In meeting 25/10/23 with R&D we discussed library types. Decision confirmed by Lesley today:

These library types are the best placed to align with the 007C project. As discussed previously, in the early days of the project there will be cross-over with what were bespoke activities and 007C until the point at which they are aligned. However, in the interim we can filter by date and/or study.

Chromium single cell 5 prime HT v2 will the library type we immediately require for 007C.

  • Chromium single cell 3 prime HT v3
  • Chromium single cell 5 prime HT v2
  • Chromium single cell BCR HT
  • Chromium single cell TCR HT
yoldas commented 7 months ago

Added Integration Suite DPL-913 MR on GitLab .

yoldas commented 7 months ago

Updated the documentation with the Submitting banked PBMC tubes for Donor Pooling and cDNA Prep section.

yoldas commented 7 months ago

Gist: Running integration suite locally for the 'scRNA Core entry point 1 - blood' scenario

yoldas commented 7 months ago

Gist: Database Inspection for Donor Pooling and cDNA Prep submission

yoldas commented 7 months ago

Deployment note: To enable WIP when we deploy Sequencescape to UAT, we need the following executed on the host:

WIP=011_scrna_core_cdna_prep_submission_templates,014_limber_scrna_core_cdna_prep_request_types,011_scrna_core_cdna_prep_plate_purposes,008_scrna_core_cdna_prep_tube_purposes,011_scrna_core_catalogue bundle exec rake record_loader:all