Skip to content
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

DPL-078 Biosero - Update cherrytrack when destination created in LIMS #16

Closed
4 tasks
andrewsparkes opened this issue Jul 16, 2021 · 1 comment
Closed
4 tasks

Comments

@andrewsparkes
Copy link
Member

andrewsparkes commented Jul 16, 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:

  • 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.

@andrewsparkes
Copy link
Member Author

No longer required, alternate solution found see sanger/lighthouse#399

@TWJW-SANGER 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant