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
We recently added functionality (via PR #506 and PR3 over in Mercury repo: theiagen/mercury#3) in Mercury to automatically generate the NCBI BioSample metadata field isolate in the following format:
A user requested that the string pdm09 is appended to the string auto-generated in the isolate column, so for example A/California/sample-0001/2024 (H1N1)pdm09. This is to designate that samples are descendants/related to the pandemic 2009 strain.
However, we currently do not have a way in TheiaCoV wfs to determine if samples are truly descendants or not.
Also, not all H1N1 strains are descendants (like those collected prior to 2009) or H1N1 samples collected in the future could potentially not be part of the pdm09 lineage.
It would be beneficial to our users if this designation could be determined (perhaps via Nextclade or another mechanism/algorithm like something involving collection dates) and appended to the string auto-generated in Mercury code.
The current workaround is to run Mercury and manually edit the BioSample metadata TSV output from the workflow to include this lineage designation prior to NCBI submission
The text was updated successfully, but these errors were encountered:
🆒
📌 Explain the Request
We recently added functionality (via PR #506 and PR3 over in Mercury repo: theiagen/mercury#3) in Mercury to automatically generate the NCBI BioSample metadata field
isolate
in the following format:A user requested that the string
pdm09
is appended to the string auto-generated in theisolate
column, so for exampleA/California/sample-0001/2024 (H1N1)pdm09
. This is to designate that samples are descendants/related to the pandemic 2009 strain.However, we currently do not have a way in TheiaCoV wfs to determine if samples are truly descendants or not.
Also, not all H1N1 strains are descendants (like those collected prior to 2009) or H1N1 samples collected in the future could potentially not be part of the pdm09 lineage.
It would be beneficial to our users if this designation could be determined (perhaps via Nextclade or another mechanism/algorithm like something involving collection dates) and appended to the string auto-generated in Mercury code.
The current workaround is to run Mercury and manually edit the BioSample metadata TSV output from the workflow to include this lineage designation prior to NCBI submission
The text was updated successfully, but these errors were encountered: