-
Notifications
You must be signed in to change notification settings - Fork 7
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
name2taxid
includes some questionable material
#27
Comments
that seems reasonable, by default excluding |
@sckott Sounds good. Is this an issue in |
this is what we get with taxize::get_uid("s2")
#>
#> Retrieving data for taxon 's2'
#>
#> [1] "164330"
#> attr(,"class")
#> [1] "uid"
#> attr(,"match")
#> [1] "found"
#> attr(,"multiple_matches")
#> [1] FALSE
#> attr(,"pattern_match")
#> [1] FALSE
#> attr(,"uri")
#> [1] "https://www.ncbi.nlm.nih.gov/taxonomy/164330" |
unarchiving it thanks to @stitam 😸 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This happens:
S2 is a strain name for this bacteria. See here.
The problem is that I allow matches against any
name_class
. Here are all the name classes in the database:So the question is, which of these should we include?
Most of them seem pretty reasonable. The problematic ones are
type material
andacronym
. Perhaps we should allow the user to select which name classes to allow?The text was updated successfully, but these errors were encountered: