You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User story
As Biosero we would like to be able to warn the user at the start of a run when a destination plate has already been created in the LIMS (e.g. partial created as result of error recovery or created via lighthouse-ui).
Who are the primary contacts for this story
Rob H
Andrew
Eduardo
Harry
Acceptance criteria
To be considered successful the solution must allow:
add a new table 'destination_plates_in_lims' with a barcode (unique) column
add a new endpoint for lighthouse to call with a barcode
endpoint adds the barcode to the table
add a new stored procedure 'isDestinationPlateInLIMS' that takes a barcode as input, checks the new table, and returns a boolean (see existing stored procedure 'doesSourcePlateExist' for example
Dependencies
This story is blocked by the following dependencies:
None
References
This story has a non-blocking relationship with:
Lighthouse story sanger/lighthouse#397
Additional context
Discussed error recovery at technical mtg 16th July. Outcome of that was that this would be good to have in place.
The text was updated successfully, but these errors were encountered:
TWJW-SANGER
changed the title
DPL-nnn Biosero - Update cherrytrack when destination created in LIMS
DPL-078 Biosero - Update cherrytrack when destination created in LIMS
Jul 30, 2021
User story
As Biosero we would like to be able to warn the user at the start of a run when a destination plate has already been created in the LIMS (e.g. partial created as result of error recovery or created via lighthouse-ui).
Who are the primary contacts for this story
Rob H
Andrew
Eduardo
Harry
Acceptance criteria
To be considered successful the solution must allow:
Dependencies
This story is blocked by the following dependencies:
None
References
This story has a non-blocking relationship with:
Lighthouse story sanger/lighthouse#397
Additional context
Discussed error recovery at technical mtg 16th July. Outcome of that was that this would be good to have in place.
The text was updated successfully, but these errors were encountered: