-
Notifications
You must be signed in to change notification settings - Fork 8
Description
User story
I have suggested that when setting up the 'automated' submissions in Limber for #2665, that we hardcode a dummy Project, so as to avoid holding up the rest of the pipeline development.
This story is to work out how to get the correct project into those submissions. We can't hardcode a project (as we did for Heron, which used the same 'choose workflow' screen), because this pipeline will be used across multiple projects (cost codes).
A few options I've thought of:
- Include it on the sample manifest (there is an existing project_id field on sample manifest we could use) - but would it work for repeats, where they may want to use a different cost code?
- Get the lab users to specify it in the 'Choose Workflow' screen (this information would probably need to be passed onto them by the SSR - perhaps another piece of information in a comment on the Labware).
- A hybrid of the above - able to specify it in the UI, but provide a suggestion based on the manifest, or based on previous library prep runs from the same plate.
But there may be other, better options.
Who are the primary contacts for this story
Scott G, Katy
Who is the nominated tester for UAT
Scott G, ...
Acceptance criteria
Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:
- Decide on a design for getting the project id into the LCM Triomics submissions
- Implement it
- Update Automated Submission documentation if needed
Dependencies
This story has a blocking dependency on:
Update: believe this can be picked up now with use of the Limber epic branch and careful communication with devs on the related stories.
Additional context
Deployment notes