Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove the requirement for a database field in augur curate parse-genbank-location [#1511] #1513

Merged
merged 1 commit into from
Jul 2, 2024
Merged

Remove the requirement for a database field in augur curate parse-genbank-location [#1511] #1513

merged 1 commit into from
Jul 2, 2024

Commits on Jul 2, 2024

  1. Remove the requirement for a database field [#1511] 

    Per discussion on #1508 and #1511, the field standardization across
records (cf #1510) makes the need to verify a `database` field less
important — essentially, if there's a `geo_loc_name` field (or a field
with the name given in the `--location-field` argument), parse it.
Otherwise, warn that it's not found.
    @genehack
    genehack committed Jul 2, 2024
    Configuration menu
    Copy the full SHA
    f1f05da View commit details
    Browse the repository at this point in the history