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
Flagged internally by @rneher that the acknowledgements download does not include the GISAID isolate IDs.
#138 added the HA/NA segment accessions, but we do not include the isolate ID used to link multiple segments to the same isolate. The isolate id was added to the metadata upload in #160, so it should be available in the metadata for the builds.
The fields included in the acknowledgements is hardcoded in Auspice so the field will have to be named gisaid_epi_isl.
I don't depend on isolate_id as a field name anywhere. Since Auspice hardcodes separate fields for GISAID and GenBank accessions (without an awareness of segmented viruses), it makes sense to rename isolate_id to gisaid_epi_isl in the uploaded metadata.
Unless the Nextclade somehow depends on an isolate_id field downstream, I would just change the Nextclade workflow to use the new field name, too.
Flagged internally by @rneher that the acknowledgements download does not include the GISAID isolate IDs.
#138 added the HA/NA segment accessions, but we do not include the isolate ID used to link multiple segments to the same isolate. The isolate id was added to the metadata upload in #160, so it should be available in the metadata for the builds.
The fields included in the acknowledgements is hardcoded in Auspice so the field will have to be named
gisaid_epi_isl
.TODOs
isolate_id
togisaid_epi_isl
#179gisaid_epi_isl
in workflows #180The text was updated successfully, but these errors were encountered: