You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @dimus!
Thank you for your constant work and improvements made to your tools.
Some of my tests did not pass lately as for some DBs, all current... fields are empty.
See the difference between 1 and 4,179,180 (main ones I noted empty):
echo"Callichroma iris"| gnfinder -A -f compact -M -s 1,4,179,180
Is this expected and I did not follow the latest updates properly?
Best,
The text was updated successfully, but these errors were encountered:
@Adafede thank so much for spotting this. I suspect it is related to gnames/gnames#128, and I would say that for names where taxonomicStatus is accepted, there should be a consistency. Let me figure out what is going on.
There are two data sources, with classification (taxonomic) and without. For ones with classification gnverifier can see if a name is a current name or not. If there is no classification I used to give a name as a current, even I they don't give any opinion.
So if name got resolved to a data source with classification, posssible (simplified) taxonomicStatus can be 'Accepted' or 'Synonym' and current name appears.
If there is no classification, then taxonomicStatus would be 'N/A' and current name should not appear.
Hi @dimus!
Thank you for your constant work and improvements made to your tools.
Some of my tests did not pass lately as for some DBs, all
current...
fields are empty.See the difference between 1 and 4,179,180 (main ones I noted empty):
Is this expected and I did not follow the latest updates properly?
Best,
The text was updated successfully, but these errors were encountered: