Y25-623 - Enable scRNA Core Users to Cherrypick LRC GEM-X 5p CITE SUP XP/Input Plates

[Stan1520]

Context
Currently, users in the scRNA Core pipeline are unable to properly cherrypick and combine LRC GEM-X 5p CITE SUP XP and/or Input plates within the LIMS to form LRC GEM-X 5p CITE Cherrypick plates. Instead, users manually combine these plates outside the system, leading to discrepancies between LIMS records and the actual lab process.

To accurately reflect the lab workflow and reduce manual effort, LIMS needs to support cherrypicking of these plate types and automate the logical relationships between SUP XP/Input plates, Cherrypick plates, and Ligation plates.

User story
As a user of the scRNA Core pipeline, I want to be able to cherrypick LRC GEM-X 5p CITE SUP XP and/or Input plates together to form LRC GEM-X 5p CITE Cherrypick plates, So that the LIMS accurately reflects the lab process and ensures correct tracking through library preparation and sequencing stages.

Who are the primary contacts for this story
Abby C

Who is the nominated tester for UAT
Abby C

Acceptance criteria
To be considered successful the solution must allow:

• A new plate purpose called “LRC GEM-X 5p CITE Cherrypick” must be added to the LIMS.

• The submission template remains scRNA Core Library Prep - Pool, and the library type remains Chromium Single Cell GEM-X 5p v3 Cell Surface Protein.

• The Cherrypick plate creation page must validate that:
  - All SUP plates requested by the SSR are present in the scanned list.
  - Manual transfer is completed before proceeding.

• LRC GEM-X 5p CITE SUP XP (or Input) plates must be manually transferred to form LRC GEM-X 5p CITE Cherrypick plates ?

• LRC GEM-X 5p CITE Cherrypick plates must then be manually transferred to become LRC GEM-X 5p CITE Ligation plates ?

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.