Skip to content

Y26-077 - Add Fail Slider for LRC PBMC Aliquot in Limber #2738

@Stan1520

Description

@Stan1520

Context
During the LRC PBMC workflow, users assess sample viability and total cell count when transitioning from the LRC PBMC Defrost PBS 08ml page to the LRC PBMC Aliquot page in Limber. Currently, users must manually check individual cell count files to determine which samples should fail or require dilution. This manual process is time-consuming, error-prone, and inefficient during a time-sensitive step. Introducing fail sliders with predefined thresholds would provide a quick visual check to identify samples that should fail or require manual dilution.

User story
As a user, I want fail sliders for viability and total cell count to appear on the LRC PBMC Aliquot page in Limber, so that I can quickly identify samples that should fail or require dilution without manually checking external cell count files.

Who are the primary contacts for this story
Abby C

Who is the nominated tester for UAT
Abby C

Acceptance criteria

Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:

  • Add sliders / thresholds for cell count and viability onto the LRC PBMC Aliquot plate
  • Remove sliders / thresholds for cell count and viability from the LRC PBMC Defrost PBS 08ml plate
  • The default slider values must be set to 50% viability and 500,000 total cells/ml.
  • The sliders should work as per the other plates in the pipeline that they are currently defined on.

Dependencies

This story is blocked by the following dependencies:

  • #<issue_no.>
  • sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

  • #<issue_no.>
  • sanger/#<issue_no.>

Additional context

Deployment notes

Add any details that should be noted when deploying this feature. For example, is a database migration needed, a specifc rake task or other script that needs to be run, a dependency on another application or service that needs to be released first etc?
These notes are intended to ensure the developers releasing the feature know what needs to be done.

Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

Labels

EnhancementNew feature or requestSize: SSmall - low effort & risk

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions