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.

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

augur curate parse-genbank-location: Remove database check #1511

Closed
joverlee521 opened this issue Jul 2, 2024 · 0 comments
Closed

augur curate parse-genbank-location: Remove database check #1511

joverlee521 opened this issue Jul 2, 2024 · 0 comments
Assignees

Comments

@joverlee521
Copy link
Contributor

Originally discussed in #1508 (comment).

As @genehack commented:

Seems to me like duck-typing on the field you're operating on is a better check than keying off a second field

@genehack genehack self-assigned this Jul 2, 2024
genehack added a commit that referenced this issue Jul 2, 2024
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 added a commit that referenced this issue Jul 2, 2024
Remove the requirement for a `database` field in `augur curate parse-genbank-location` [#1511]
@genehack genehack closed this as completed Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants