You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As team lead for RNA (Liz E) it is very hard for the lab team, when making pools, to determine the correct label to put on the tube as the whole name doesn’t fit on the tube.
LCMB custom pool and LCMB custom Pool Norm. both of these samples have the same human readable name on the label ‘Custom Pool’ making it difficult for us to know which label is which when we print them.
Please can we remove the word custom Or Make one Custom Pool and one Custom Norm.
Slack discussion and thoughts from @As28
3 parts to story (small):
change limber config for LCMB to adjust name of purpose(s) (check the purpose(s) are not also defined in SS as well, don't think so unless defined for multiplexing)
change integration suite for LCMB pipeline to use changed purpose names
on deployment to UAT/Training/Prod, update name of existing purpose(s) in database BEFORE deploying config change (or it will create NEW instances of the purposes based on their new names on deployment which we don't want)
As team lead for RNA (Liz E) it is very hard for the lab team, when making pools, to determine the correct label to put on the tube as the whole name doesn’t fit on the tube.
LCMB custom pool and LCMB custom Pool Norm. both of these samples have the same human readable name on the label ‘Custom Pool’ making it difficult for us to know which label is which when we print them.
Please can we remove the word custom Or Make one Custom Pool and one Custom Norm.
Raised via RT799627
The text was updated successfully, but these errors were encountered: