Y26-074 - Add “Amplicon” Library Type to Limber Bespoke Submission Template

[Stan1520]

Context
Currently, the Limber bespoke PCR submission templates do not include “amplicon” as a selectable library type. This limits the ability to accurately classify certain libraries during submission. Without this option, downstream reporting in Tableau (via MLWH) and charging categorisation cannot correctly capture this library type. Adding this option will support improved reporting and billing transparency.

User story
As a user, I want “amplicon” to be available as a library type in Limber bespoke PCR submission templates, So that libraries can be correctly categorised and reported for downstream analytics and charging purposes.

Who are the primary contacts for this story
Liz C

Who is the nominated tester for UAT
Liz C

Acceptance criteria
To be considered successful the solution must allow:

• [ ]“Amplicon” is added as a selectable value in the library type field across all Limber bespoke PCR submission templates.
• The selected “amplicon” library type is stored and passed through to MLWH as part of the submission metadata.
• The library type value is available for downstream reporting in Tableau via MLWH.

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.