Y26-075 - Inactivate Legacy LRC Bank Input Tube Purpose

[Stan1520]

Context
A recent update to the scRNA Core cDNA Prep pipeline introduced two new tube purposes: LRC Bank Input 0.8ml and LRC Bank Input 1ml to distinguish between tube types. The previous tube purpose “LRC Bank Input” is now obsolete but still appears as a selectable option when creating manifests. This has led to incorrect selections, which blocked sample processing in Limber until manual intervention was completed. The legacy option should be removed or inactivated to prevent future errors and ensure correct reporting of library types.

User story
As a lab user creating manifests, I want the legacy LRC Bank Input tube purpose to be removed or inactivated, So that only the valid tube purposes (LRC Bank Input 0.8ml and LRC Bank Input 1ml) can be selected, preventing incorrect submissions and processing delays.

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:

• The LRC Bank Input tube purpose is removed or marked as inactive so it cannot be selected when creating new manifests.
• Only LRC Bank Input 0.8ml and LRC Bank Input 1ml are available for selection for this workflow.
• Existing historical records using LRC Bank Input remain unchanged and accessible.
• The updated tube purpose configuration supports downstream reporting (e.g., MLWH/Tableau) without impacting existing data.

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.