GPL-735 Prevent Users selecting same panel when tagging

[JamesGlover]

96 well variant pulled out into: https://github.com/sanger/limber/issues/569

User story As Lesley I want to restrict tag-plate selection in the Heron Tailed workflow (Sanger_tailed_artic_v1_nnn) to ensure that the same primer panel is not picked for each fork.

• Primer panels now included in tag plates, so applied at same time
• Need to ensure that PCR1 and PCR2 plates each use a different panel.
• Tag plate become Lib PCR1 and Lib PCR 2 ad in place currently

Suggested approach:

• Two different tag layout templates, with same tag group. Suffix primer panel name.
• Adjust approved layout templates to be confined to corresponding template
• Remove flag ensuring identical templates are used (As we now will have contrasting ones)
• Remove old templates from approved list

Edit While this works for the 384 well pipeline, the approach is not suitable for the 96 well version. Lesley S has indicated that prioritisation of the 384 well version is good for the time being, so this has been completed using the approach above.

96 well version

• Current flag to ensure identical tag templates should be switched to ensure identical tag groups instead
• The existing templates should be switched out for the primer-panel variants.
• There's a rake task in Sequencescape to generate these variants (lib/tasks/generate_primer_panel_templates.rake)

Note: Complete switch over to new process is acceptable and desirable

• Remove old library types from purposes.yml and request_types_library_types in SS.
• Remove non-tailed pipelines from Limber (Keep purposes themselves in there for the moment to avoid Limber getting shouty when you look at old plates)

Who are the primary contacts for this story Lesley S Naomi P

Acceptance criteria To be considered successful the solution must allow:

• [x] 384 well pipeline 96 well pipeline (See: https://github.com/sanger/limber/issues/569)

Dependencies This story is blocked by the following dependencies:

• sanger/#

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

[JamesGlover]

Just double checking that this is for both 96 and 384 well processes.

[JamesGlover]

Lesley: It will be for both, but 384 is the focus.

[JamesGlover]

96 well fork is a little trickier, as we need to still make sure tag groups are the same.