Y24-222 - Select tag set in Limber tagging screen instead of tag groups

[yoldas]

User story
As lab user, I would like to select tag groups of the same tag set with a single dropdown to select the i7 and i5 tag groups together to reduce the possibilities of errors when setting tag sets for libraries such as accidental selection of unrelated tag groups. Replace the two existing drop-downs with a single drop-down as shown in the following images.

---

Existing drop-downs

i7 and i5 are selected separately from the same tag set.

---

Single dropdown

Only the tag set is selected. No need to select i7 and i5 separately.

Who are the primary contacts for this story
Abdullah, Andrew, Katy, Neil (PSD), Rich C (SSR)

Who is the nominated tester for UAT
Matt J

Acceptance criteria
To be considered successful the solution must allow:

• Remove two tag group drop-downs for i7 and i5
• Add a drop-down for tag set selection only
• Set i7 and i5 tag groups of the selected tag set for the Tagged Plate

Dependencies
This story is blocked by the following dependencies:

• Y24-170 - Link dual index tag groups sequencescape#4160
• Y24-220 - Create API V2 end point for tag sets sequencescape#4238
• Y24-218 - Create a new tag set model to link tag groups sequencescape#4236
• Y24-219 - Link tag groups with tag sets sequencescape#4237

References
This story has a non-blocking relationship with:
See links in the parent research story.

Additional context

The implementation of this story involves modification of custom tagged plate javascript component to extract the list of tag groups from the result of the new TagSet API call with the adapter type filter. The dropdown needs to list the tag set names. On select, tag groups of the selected tag set need to be set on the tagged plate.

[KatyTaylor]

Matt J is more appropriate as a tester - Rich C won't normally interact with this page.

[KatyTaylor]

I think it's blocked by sanger/sequencescape#4236 (creating the data model) as well.

[yoldas]

I think it's blocked by sanger/sequencescape#4236 (creating the data model) as well.

I have written the top-level and direct parent as dependencies in the stories to keep the list short. [I have added the suggestion as well to make it visible now]

[yoldas]

Matt J is more appropriate as a tester - Rich C won't normally interact with this page.

I have changed the tester.