-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sometimes empty string as input moves entire names #16
Comments
Thank you again for your quick answers @ojalaquellueva! |
@Rekyt I am still scoping this out. Assuming I can isolate and replicate the issue within the perl controller, I will transfer the issue to https://github.com/ojalaquellueva/TNRSbatch. In the meantime, you can bypass issues #14, #15 and #16 by processing your names as follows:
|
Thanks for the very detailed process! Will follow right away :) |
Added a note to the readme. Thanks for catching this, @Rekyt |
I also had a strange bug when having the empty string as input (but not the same as #14).
Sometimes, if the dataset is "big enough", testing with a data.frame with an empty string actually removes from the input and moves the next name to that ID instead. This causes many issues if you want to match back the names through the ID.
See my reproducible example:
Created on 2023-02-14 with reprex v2.0.2
I dived into the issue by looking at the query done through
TNRS_core()
and it seems all fine.The data JSON looks like this:
So perfectly fine. But the API returns the same table as above with the names moved up.
So it seems to be rather an issue with the API.
The text was updated successfully, but these errors were encountered: