Skip to content

Y25-712 - PacBio - Allow Traction receipt page to set cost codes by sample #2576

@andrewsparkes

Description

@andrewsparkes

User story

As the PacBio team we would like Traction receipt to include cost codes at sample level, rather than the current plate level. Once cost code can be retrieved from Sequencescape at sample level via the API, we would like reception in Traction to set these cost codes on the imported samples.

Who are the primary contacts for this story

Emily A (PacBio team)
Andrew
Ben

Who is the nominated tester for UAT
Emily A

Acceptance criteria

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

  • a mode in Traction reception that will check for cost code information at receipt
  • when in this mode, reception of labware in Traction should look for the sample level cost code information and set it on the samples created in Traction
  • when in this mode, inform the user if the scanned labware do not have cost codes (cost code must be present to receive)

Dependencies
This story is blocked by the following dependencies:

This dependency could be mitigated by having a feature flag prevent visibility and use of the new reception mode until ready.

References
This story has a non-blocking relationship with:

Additional context
The Sequencescape story plans to store project_id on the aliquots in the plate labware. So when in Traction receipt the user scans the labware, it should be possible to extract the cost codes from the projects stored on the aliquots for each of the samples in the labware, from the Sequencescape API.

I'm assuming Traction reception still needs to receive other labware where cost codes are not set on samples. So we need some option in the GUI that puts you into a mode where the cost codes are expected for the scanned labware. Whether a dropdown or a checkbox. TBC with users.

Deployment notes
Nothing specific

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions