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.

Sign up for GitHub

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

Jump to bottom

Add reasonable default for clade_legacy so that new clade doesn't require changes in ingest's clade-legacy-mapping.yml #406

Open
corneliusroemer opened this issue Jun 21, 2023 · 0 comments
Open

Add reasonable default for clade_legacy so that new clade doesn't require changes in ingest's clade-legacy-mapping.yml #406

corneliusroemer opened this issue Jun 21, 2023 · 0 comments
Assignees
@corneliusroemer
Labels
enhancement New feature or request

Comments

@corneliusroemer
Copy link
Member

Context

See "Future work" item in #405

Description

Add a reasonable default for clade_legacy so that new clade doesn't require changes in ingest. E.g., we could use the WHO column, or simply add (Omicron), or add nothing at all, i.e. map to itself.
@corneliusroemer corneliusroemer added the enhancement New feature or request label Jun 21, 2023
@corneliusroemer corneliusroemer self-assigned this Jun 21, 2023
@corneliusroemer corneliusroemer mentioned this issue Jun 21, 2023
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@corneliusroemer corneliusroemer

Labels
enhancement New feature or request
Projects
No open projects
Nextstrain planning (archived)
Status: New
Milestone
No milestone
Development

No branches or pull requests
1 participant
@corneliusroemer