Y24-099 Tube Rack Banking Sequencescape API

[yoldas]

User story As PSD, we would like to update Sequencescape v2 API to provide Limber support for TubeRack model similar to Plates using the versioned tube rack model proposed in Reuse of TubeRacks document.

Who are the primary contacts for this story Abdullah, Katy, Andrew

Who is the nominated tester for UAT TBD

Acceptance criteria

• [ ] Check existing labware creator (in DPL-811) for Sequencescape API calls and replace them for tube racks.
• [ ] Check TubeRacks and associated objects are retrieved by using JSONAPI includes, i.e. Tubes and RackedTube.
• [ ] Add resource methods to TubeRacks and RackedTubes so that they are similar to Plate and Wells.
• [ ] Add TubeRack barcode into new TubeRack poly_metadata in order to enable history tracking of physical tube rack

Dependencies This story is blocked by the following dependencies:

• 1482

References This story has a non-blocking relationship with:

• 1314

• 1713

Additional context The versioned tube rack model is researched in DPL-1011 Re-use of tube racks and the model is summarised in the Google Document DPL-1011 Re-use of tube racks

This story is part of re-implementation of DPL-811 Transfer PBMC isolations into FluidX tube racks (Banking) using the versioned tube rack model.

Story relationships are shown in the Lucidchart diagram TubeRack Stories .

It is not possible to release the implementation of this story in isolation.

[TWJW-SANGER]

A couple of queries:

• Do the features that require these APIs already exist or need to created? I suspect "API Support to allow History tracking of physical tube rack.." is a feature that does not yet exist? Would it make sense to split that feature out into its own user story so that we understand what the business need before designing this API call?
• I can see "API Support to find a tube on a tube rack" would be useful / needed. Curious as to how it works at the moment and/or where this is being called from. In the sense of - could this be split out into another smaller story?

[KatyTaylor]

"API Support to allow History tracking of physical tube rack using poly_metadata" - a bit more detail would be good. I think what we mean here is that the tube rack barcode will be saved into poly_metadata when the tube rack is created - is that correct?

[yoldas]

I have updated the criteria to address the comments.

• History tracking is part of the versioned TubeRack model described in the Google Doc DPL-1011 Re-use of tube racks . A code example is shown on Sequencescape side for this. It is a simple operation to future-proof the links between tubes and tube racks.
• Saving barcode in poly_metadata is covered in criteria better now and described in the document in the previous item.
• There is already a resource to find out the tube rack of a tube (RackedTube) because a tube is linked to a specific version of a tube rack but there is no support for finding historical locations of a tube through multiple tube racks. It is not a requirement for re-implementing banking. There is no need for that now.