-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Y24-218 - Create a new tag set model to link tag groups #4236
Comments
Thinking about details like
|
@KatyTaylor we have not in the past deleted tag groups preference has been to use the visibility flag |
I have assumed neither tag sets nor tag groups can be deleted. Tag groups can only be "soft-deleted" by setting visibility flag. I tied the visibility of tag set to visibility of its tag groups. I have added two criteria as associations and integrity now. |
User story
As PSD, we would like to create a new data model to link tag groups (indexes) of the same tag sets together in order to support selection of the pair of i7 and i5 tag groups for dual indexed tag sets together and unify access to single and dual indexed tag sets. This data model aims keeping the internal tag group model intact while providing support for a unified access to the tag groups at interfacing.
Who are the primary contacts for this story
Abdullah, Andrew, Katy, Neil
Who is the nominated tester for UAT
PSD
Acceptance criteria
To be considered successful the solution must allow:
PN-1000212 Single Index Kit N, Set A . It can link TagGroup with the same name.
Dependencies
This story is blocked by the following dependencies:
References
This story has a non-blocking relationship with:
See links in the parent research story.
Additional context
This simple model can co-exists and reuses the existing models, records, and operations in Sequencescape and Limber; hence allows changing for interfaces, queries, and UI elements without breaking existing models.
Linking existing TagGroup records in DB is covered in another story. See links in the parent research story.
Not adding a flag to explicitly specify if a tag set is single indexed or dual indexed; Rely on availability of tag_group and tag2_group associations on the tag set for now to keep it simple.
Adapter type can stay as tag group field. For dual indexed tag sets, both tag groups have the same adapter type, which is set when creating tag groups. [Tag set should return the first adapter type of its tag groups with the assumption that the adapters of its tag groups will be the same. Add a validation to enforce that]
Visible column: Tag set will find its visibility by checking the visibility of tag groups [Tag set will be visible if all of its tag groups are visible]
The text was updated successfully, but these errors were encountered: