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

GPL-606 Sentinal remove need to upload box manifest to LabWhere before box arrives #96

Open
1 task
rl15 opened this issue Aug 6, 2020 · 1 comment
Open
1 task
Labels

Comments

@rl15
Copy link

rl15 commented Aug 6, 2020

User story
GPL-606 | As leads for PAM tracking (Sonia G & Rob K) we would like the Sentinel cherry picking process modified so box manifests are only uploaded to LabWhere when the box arrives

Rich C - Please could someone in PSD clarify how this would work to me as I have a few questions:
If the box manifest aspect is removed, would Sentinel still be able to show which plates have missing plate map data from a box? This is proving to be incredibly useful of the moment. Would this be reported somewhere else?
Would SSRs still be pasting in the box barcodes to pull plate and thus sample information to create samples in SS? Im keen not to be pasting in 80 plate barcodes, where currently we paste a single box barcode?

Who are the primary contacts for this story
Emma G
Rich C
Danni W

Preamble

Live Sentinel process as of 3rd August is documented in sequence flows diagrams here: https://ssg-confluence.internal.sanger.ac.uk/x/jqsKBg figures 2.1 & 2.2

Item of concern: Via PAM the SSR are uploading the LH box manifest before the box is here.
Why?: This allows SSR to create samples in SS via the new Sentinel process ahead of the box arriving.
Issue: PAM are planing on using the data of box upload to from LabWhere as a data point that the samples are on site at
Sanger: https://ssg-confluence.internal.sanger.ac.uk/x/u5kKBg table 3.1 row G.0
*Proposed improvement options (please generate atleast one more if you can and then discuss with SSR): SSR are very ken to not to break the sentinel process!

  1. Allow the box manifest to be uploaded in the lighthouse UI: http://lighthouse-ui.psd.sanger.ac.uk/

Acceptance criteria
To be considered successful the solution must allow:

  • TBD

Dependencies
This story may have associations with any feature request to improve the robustness of box manifest data see: https://ssg-confluence.internal.sanger.ac.uk/x/jqsKBg section 3.1.

Additional context
Add any other context or screenshots about the feature request here.

@rl15 rl15 added Enhancement New feature or request research and removed Enhancement New feature or request labels Aug 6, 2020
@rl15
Copy link
Author

rl15 commented Aug 7, 2020

See attached from PAM. Business value: Many of the items in pink 'Problems with obtaining this status' are removed if we separate
a) Creating samples expediently in SS using a box barcode to grab many samples from
b) This box of samples is on site.

Sample Status 0-3 Draft.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant