-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Y24-100 Tube Rack Banking Uploads #1697
Comments
Just a note to mention that we may need to help / instruct the lab on how to configure their rack scanners to produce the desired output. |
Is this one blocked by the other more technical stories? |
I think "Support for creation of a TubeRack with new Tubes" is probably the only one that doesn't exist already, is that correct? The other 3 acceptance criteria are just there to make sure we retain that functionality? |
@KatyTaylor I have removed the redundant criteria and made a reference to DPL-811. I have also added the other two stories as dependencies. |
Use of rack scanners to generate 3-column output can be discussed and agreed in UAT. |
Think this will actually be done as part of #1696 |
Closing this as part of Y24-099 |
User story
As PSD, we would like to support Limber tube rack scan file uploads for new tubes 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
Dependencies
This story is blocked by the following dependencies:
References
This story has a non-blocking relationship with:
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.
The text was updated successfully, but these errors were encountered: