Closed victorlin closed 1 month ago
nextclade/sars-cov-2
is an odd one:
Maybe it can be represented by a tile like SARS-CoV-2 (Nextclade)
? This would only make sense as long as there is no other nextclade/*
.
My desire would be for every nextclade dataset to be represented at /nextclade
. Right now I find myself going to clades.nextstrain.org and picking a reference pathogen and example dataset if I want to see the nextclade reference tree for a particular nextclade dataset. I don't know how easy including an automated push to data.nextstrain.org as part of the release process for nextclade datasets would be. Having these pushed to data.nextstrain.org would have the added benefit of easily looking at past versions, eg https://nextstrain.org/nextclade/sars-cov-2@2024-01-01 cc @rneher and @corneliusroemer
@victorlin: My sense is that a tile that says SARS-CoV-2 (Nextclade)
is a fine solution for your PR. It may get revised to Nextclade
in the future.
My desire would be for every nextclade dataset to be represented at
/nextclade
…
Continuing in #1037
continuing from https://github.com/nextstrain/nextstrain.org/issues/940#issuecomment-2362591309:
Requirements