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
A common task in metadata wrangling is renaming the columns to match expectations. This will be especially important for the forthcoming augur join/merge command that would expect input metadata to share the same column names.
I originally thought we could avoid creating our own rename command and just use csvtk rename, but discussion in #1475 has pushed for doing it ourselves.
I think it'd be simple to implement some variation of the config option suggested by @jameshadfield in #1475, but it can also be left as a future TODO.
The text was updated successfully, but these errors were encountered:
Context
A common task in metadata wrangling is renaming the columns to match expectations. This will be especially important for the forthcoming augur join/merge command that would expect input metadata to share the same column names.
I originally thought we could avoid creating our own
rename
command and just usecsvtk rename
, but discussion in #1475 has pushed for doing it ourselves.Description
augur curate rename
can start from transform-field-names from ingest.I think it'd be simple to implement some variation of the config option suggested by @jameshadfield in #1475, but it can also be left as a future TODO.
The text was updated successfully, but these errors were encountered: