Y26-231 - Ultima Library Conversion - bulk submissions

[andrewsparkes]

User story

As Ultima conversion SSR users we will need to be able to make submissions for Illumina-->Ultima library conversion, plus multiplexing and sequencing.

Who are the primary contacts for this story

SSR user Liz C
Mike Q
Andrew S
Katy T
Abdullah Y

Who is the nominated tester for UAT

SSR user Liz C

Acceptance criteria

Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:

• As an SSR, I can make the following submissions on the final plate of any Illumina library prep (submission template and request type names are suggestions only):
  • Limber-Htp - Ultima Conv - Ultima UG100 sequencing (made up of request types: ultima htp conversion + ultima htp multiplexing + ug100 seq)
  • Limber-Htp - Ultima Conv - Ultima UG200 sequencing (made up of request types: ultima htp conversion + ultima htp multiplexing + ug200 seq)
  • Limber-Bespoke - Ultima Conv - Ultima UG100 sequencing (made up of request types: ultima ltp conversion + ultima ltp multiplexing + ug100 seq)
  • Limber-Bespoke - Ultima Conv - Ultima UG200 sequencing (made up of request types: ultima ltp conversion + ultima ltp multiplexing + ug200 seq)
• In a bulk submission for any of the above, I can set values for a column ‘ultima application’.
  • The above column It is a dropdown list, with the values coming from the list of applications created in Y26-230 - Ultima Library Conversion - Persist ultima applications and their applicable primer set #5983
  • The above column is mandatory for the Ultima conversion submission templates
  • On upload, it errors unless all rows have the same application
• On upload, it sets the values for the corresponding UGA and UGB primer names for the choice of application, from the data structure created in Y26-230 - Ultima Library Conversion - Persist ultima applications and their applicable primer set #5983
  • The application and the primer data is persisted in the Ultima conversion submission requests in new request metadata fields (for use later in validations of tag plate selection, batch creation and in writing to useq_wafer table (handled in other stories)).

Dependencies
None

References
This story has a non-blocking relationship with:
Y26-230 - Ultima Library Conversion - Persist applications and their applicable primer set
Can use placeholder values if that story is not yet completed.

Additional context
To make column validation dependant on submission template see the existing scRNA example in method apply_additional_validations_by_template_name in app/models/submission/validations_by_template_name.rb

This will be a manual submission on XP plates from any Illumina library pipeline. Acceptable purposes will include all those XP plate purposes (and the XP Norm plate purpose for HiC).

Example drafts of Submission template and request config can be found in Abdullah's draft PR
NB. do not use this PR as is, it has not been updated to the latest plan for 2 conversion pipelines (manual and high throughout). But it helps as a reference. And the HiC pipeline update will be handled in another story.

And where possible separate the config into WIP'd files so we can control release.

Deployment notes
Nothing special