Y26-127 - As a manager in short read in charge of billing, I want the billing report to correctly handle Bioscan samples.
@dn10-sanger ci sta già lavorando.
Dal 9/4/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
User Story
As a manager in Short Read in charge of billing, I want the billing report to correctly handle BioScan samples, so that lane proportions and totals are accurate when ToL begin using the billing report.
Acceptance Criteria
TBD pending stakeholder input
Who the primary contacts are for this work
Tom W
Ivy T
Laura H
Rich R
Dikshita N
Context
The billing report joins stock_resource to retrieve stock plate barcodes. For Bioscan samples, a single sample can be associated with more than one stock plate (e.g. both a LILYS plate and a Lysate plate are registered as stock plates in stock_resource)- see https://github.com/sanger/sequencescape/issues/4706 for where it was implemented. This causes the sample to appear multiple times in the sample_lanes CTE, which inflates the COUNT(*) used to calculate lane proportions resulting in incorrect total values for Bioscan runs.
This is a known limitation and was flagged during development of https://github.com/sanger/sample-tracking/issues/51. ToL are not currently using the billing report so this is not urgent, but it must be resolved before they do.
Suggested two possible approaches
- Show one row per sample and choose the stock plate barcode most useful for billing.
- Show one row per sample and concatenate multiple stock plate barcodes into one field.
Known Bioscan pipeline routes:
- Extraction performed in SeqOps :
Service user provides the LILYS-96 plate to SeqOps, and SeqOps perform the extraction and produce the Lysate
plate -> two stock plates expected since https://github.com/sanger/sequencescape/issues/4706. Only one (LILYS) expected before that, unless data was back-filled. - Extraction performed in programmes :
Faculty perform the extraction themselves and provide the Lysate plate to SeqOps - > one stock plate expected (Lysate)
Research Task
- Inspect Bioscan sample data in
stock_resourceto understand how often samples have one vs multiple stock plates. - Review examples covering the two known pipeline routes.
- Confirm with stakeholders whether to pick one stock plate or concatenate multiple barcodes.
- Use findings to define the implementation approach and write acceptance criteria for the fix.
Reference
sanger/ sample-tracking https://github.com/sanger/sample-tracking/issues/51
- Lingua principale
- Python
- Stelle
- 0
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di sanger/sample-tracking
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 38/100
sanger/sample-tracking#11 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
sanger/sample-tracking#9 · 1 commento ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
sanger/sample-tracking#7 · 3 commenti ·
-
ST0011—Deployment processAperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
Tutte le issue di sanger/sample-tracking
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
BasedHardware/omi#20271 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 92/100
openai/openai-cookbook#3153 ·
I maintainer di solito rispondono entro 1 giorno
-
cvss-severity:high devguard l3montree-cybersecurity/devguard/devguard pkg:golang/github.com/l3montree-dev/devguard risk:low state:open
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
l3montree-dev/devguard#3146 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
bug confirmed issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
open-webui/open-webui#31849 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno