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

match_taxa @ obistools Error: (204) No Content - AphiaRecordsByMatchNames #102

Open
haniehsaeedi opened this issue Feb 6, 2023 · 6 comments

Comments

@haniehsaeedi
Copy link

I have been using the match_taxa function in obistools and was working properly so far, but in the last few days I get this error with the same dataset that I used before and worked.
Error: (204) No Content - AphiaRecordsByMatchNames

This is my code
library("obistools")
names <- (data_merged$scientificName)
match_taxa(names)

Could this be related to WoRMS non-binomials issue ropensci/worrms#25? could you help me, please?

@pieterprovoost
Copy link
Member

@haniehsaeedi Can you please provide some names which are causing issues? Thanks.

@haniehsaeedi
Copy link
Author

@pieterprovoost I do not receive any error mentioning any names, only ''Error: (204) No Content - AphiaRecordsByMatchNames''

@pieterprovoost
Copy link
Member

I presume the issue is caused by one of the names in data_merged$scientificName, would you mind sharing what they are? Or the file you are reading the names from? Thanks.

@haniehsaeedi
Copy link
Author

data_merged.csv
Sure, the dataset is attached. But this issue was not appearing using the same dataset few months ago.

@pieterprovoost
Copy link
Member

I'm not able to reproduce the problem with your dataset, see below. There is a known issue with worrms, but this is only triggered in the not so likely event that none of the names submitted to the WoRMS API (in batches of 50 distinct names) have taxon matching results. This does not seem to be the case here.

> data_merged <- read.csv("data_merged.csv")
> names <- data_merged$scientificName
> res <- match_taxa(names)
5484 names, 0 without matches, 132 with multiple matches

We can add a workaround in this package, but it may take a while.

@haniehsaeedi
Copy link
Author

Thanks @pieterprovoost
I will try to update my RStudio to the newest version to see if the issue still insists.

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