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
#266 is the proof of principle here. It goes through the list of builds in the sars-cov-2 build catalogue, and fetches the auspice dataset from the url listed in each build entry. This dataset is used to attach metadata about the dataset (from the dataset's meta property) to the build entry and write it out to an "augmented" build catalogue file that is used by nextstrain.org/sars-cov-2 to display these metadata about each build on the map there (e.g. when the dataset was last updated).
Currently this is limited to build entries with urls of a certain format.
Three things need to happen to remove this limitation:
go through the build catalogue and manually enforce that all build urls are running an auspice server that will return 1 dataset, so that we can uniformly fetch one dataset per build url.
rewrite fetching function code that gets the dataset name from the url and fetches the dataset using charon.
The text was updated successfully, but these errors were encountered:
#266 is the proof of principle here. It goes through the list of builds in the sars-cov-2 build catalogue, and fetches the auspice dataset from the url listed in each build entry. This dataset is used to attach metadata about the dataset (from the dataset's
meta
property) to the build entry and write it out to an "augmented" build catalogue file that is used by nextstrain.org/sars-cov-2 to display these metadata about each build on the map there (e.g. when the dataset was last updated).Currently this is limited to build entries with urls of a certain format.
Three things need to happen to remove this limitation:
The text was updated successfully, but these errors were encountered: