-
Notifications
You must be signed in to change notification settings - Fork 0
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-010 Options to implement the ANOSPP non-destructive extraction pipeline. #373
Comments
Team Discussion 05 March 2024:
|
Updated process map to v3 on 18th March 2024. PCR1 creation has a single step bed verification rather than 2-step. |
Updating story to reduce the scope following discussions on 28/5/2024. |
@SujitDey2022 Would you like to make an ANOSPP issue label for these 2 stories above in SS and Limber? |
@andrewsparkes stories look good. I left a comment on the manifest one. I've just been reading through Scott's doc again and found a few things I thought worth mentioning:
|
Have updated Y24-136 to include requirement for double label. And asked Scott to clarify whether we need the empty H12 validation on the manifest upload. |
Added a new story for the H12 empty manifest type requirement: Y24-139 - ANOSPP - Add a manifest template for WGS with a restriction on use of H12 So, including the 2 above plus the one in the backlog about fake cherrypicking and this one, that is 4 stories in total. |
Description
We need to consider how the new ANOSPP non-destructive extraction (NDE) process will be implemented and create a backlog to implement the solution.
Output
A backlog of user stories to implement the NDE two step process for ANOSPP.
Who the primary contacts are for this work
Scott T
Emma D
PSD developers familiar with Bioscan
Knowledge or Stake holders
Scott T has a diagram for the ANOSPP options, here:
(updated to v3 on 18th March 2024)
Non-Destructive Extractions BIOSCAN ANOSPP v3.pdf
See ANOSSP Confluence page for up to date links
Additional context or information
Best to meet with Scott T and Emma D to go through the details for this.
The text was updated successfully, but these errors were encountered: