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

How do we handle lineages that have been reclassified? #540

Open
ArtPoon opened this issue Oct 1, 2024 · 0 comments
Open

How do we handle lineages that have been reclassified? #540

ArtPoon opened this issue Oct 1, 2024 · 0 comments

Comments

@ArtPoon
Copy link
Contributor

ArtPoon commented Oct 1, 2024

This was not an issue when we were re-processing all data de novo, but now that we are storing sequences and metadata in a local database, there is a risk that a sample of lineage X becomes re-labelled lineage Y. As a result, we would have duplicate records in the database. This would cause the pipeline to crash when it attempts to insert a new record with accession number as unique key, which collides with the existing record with the same key. This would be easy to fix by modifying the database insert statement.

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

1 participant