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
In augur export v2, the accession node attribute gets exported as long as it's an available node attribute. The problem comes when "accession" is used as the metadata ID column - it is no longer available in the current implementation.
Originally noticed in nextstrain/rsv#29 (comment).
Current Behavior
In
augur export v2
, theaccession
node attribute gets exported as long as it's an available node attribute. The problem comes when "accession" is used as the metadata ID column - it is no longer available in the current implementation.I think this is an oversight of 3be4d18.
augur/tests/functional/export_v2/cram/metadata-with-accession.t
Lines 19 to 33 in bb4c4ca
Expected behavior
The "accession" column can both (1) be used as the metadata ID column and (2) exported as a node attribute.
augur/tests/functional/export_v2/cram/metadata-with-accession.t
Lines 30 to 32 in 72f645c
Possible solution
0ec4cc6
The text was updated successfully, but these errors were encountered: