Skip to content
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

Mercury for Flu enhancement - label lineage pdm09 for H1N1 samples #589

Open
kapsakcj opened this issue Aug 20, 2024 · 2 comments
Open

Mercury for Flu enhancement - label lineage pdm09 for H1N1 samples #589

kapsakcj opened this issue Aug 20, 2024 · 2 comments

Comments

@kapsakcj
Copy link
Contributor

🆒

📌 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:

# format:
type/state/submission_id/year (subtype)

# example:
A/California/sample-0001/2024 (H1N1)

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

@kapsakcj
Copy link
Contributor Author

This wasn't completed, so I'm reopening it

@kapsakcj kapsakcj reopened this Aug 28, 2024
@sage-wright
Copy link
Member

sorry! this was a misclick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants