The third submission will be an 'automated' one - created by Limber through the API. Consider using submission_class_name AutomatedOrder on the submission template. We don't seem to be using it for all our automated submissions, but perhaps should for this one.

Think ideally the submission would include the blending and sequencing (Novaseq) request types too. Could add that in here, or will it come in later in the blending stories?

Hi @BenTopping @KatyTaylor, I have partially implemented the changes in #4511. A couple of questions:

1. For the submission made with limber_bge_pcr_free and limber_bge_isc request types, do we need theillumina_htp_novaseqx_paired_end_sequencing in request_type_keys?
2. Are there any other additional request type keys for the submission related to the limber_bge_transition request?
3. I have named the submissions the following. Do we need to change them?
   • Limber-Htp - BGE PCR Free
   • Limber-Htp - BGE Transition
   • Limber-Htp - BGE ISC
4. The transition request type uses a IlluminaHtp::Requests::StdLibraryRequest. Is this correct or does this require a different type?

@dasunpubudumal

1. For the time being I think we can leave the sequencing requests off them until we get to the later stages of the pipeline and understand which requests are needed.
2. Just one request.
3. Look fine for the time being, im not sure if they classify as Htp (High throughput) - but these are just preliminary submissions to help with testing the pipeline so as long as they are wip'd we can change them down the line. Since BGE Transition is automated we could rename to Limber - BGE Transition - Automated
4. Good question, im not sure. Does the standard library request associate any unique data with the submission? We don't need any extra data, purely a request to help with the limber pipeline.

1. I'm hoping that we can include two extra request types in the upfront (pcr free) submission, one for the 'blending' step and one for the sequencing step. But, like Ben said, we probably need to leave them off until later on as we haven't quite figured out the blending step yet.
2. Agree with Ben
3. Agree with Ben
4. Library requests normally have a library type associated with them - not sure if it's mandatory. Could try a 'customer request' instead. Or, can set the library type as BGE.