Y25-444 - Enable Library Tube Creation from NT Numbers in Traction for Kinnex Pipeline

[Stan1520]

Context
Currently, Long Read (LR) teams are unable to create a final library tube in Traction using an NT barcode. This is problematic for the Kinnex pipeline, where one NT tube often contains multiple Sanger Sample IDs. Traction is currently configured to use a single Sanger Sample ID for creating PacBio libraries. This limitation breaks the workflow when there are multiple Sanger IDs tied to one NT number, which is common in actual lab processes.

During user acceptance testing (UAT), the team didn't anticipate this scenario, and the system behavior defaulted to treating NT-derived samples as if they had a single Sanger ID (e.g., NT68967P-sample-1-1). In reality, each NT tube may represent a pool of several Sanger Sample IDs, which introduces ambiguity and prevents proper library creation and tracking.

User story
As a member of the Long Read team, I want to be able to create a Trac ID for a library tube using an NT number in Traction, So that I can correctly process pooled Kinnex PacBio libraries that contain multiple Sanger Sample IDs and avoid breaking the sequencing workflow.

Who are the primary contacts for this story
Danni W.

Who is the nominated tester for UAT
Danni W.

Acceptance criteria
To be considered successful the solution must allow:

• The system must allow the creation of a PacBio library in Traction using an NT number as the identifier instead of a single Sanger Sample ID.
• If a single NT number maps to multiple Sanger Sample IDs, the system should either:
  - Allow using a concatenated string of those Sanger IDs as a composite identifier, or
  - Use the NT number as the primary sample identifier and store the associated Sanger IDs as metadata.
• The NT-based library tube should generate a valid Trac ID that can be used throughout the pipeline.

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

Emailed Information from Mary below

The issue is that we create a pacbio library on Traction using the Sanger Sample ID. If there are multiple Sanger Sample IDs associated with one NT number, then we are not sure how we can create the Traction ID.

If the Sanger Sample IDs associated with an NT number are, for example, in the format SangerSampleID1,SangerSampleID2,SangerSampleID3, can we use that combined string as the Sanger Sample ID in Traction? If not, then we will require an option to create Kinnex pacbio libraries on Traction using the NT number instead of the Sanger Sample ID.

During UAT, the Sanger Sample ID appeared in a format like NT68967P-sample-1-1, and we didn’t realize at the time that there would multiple Sanger Sample IDs associated with one NT number. It was only later in a discussion with Liz that this was identified.