-
Notifications
You must be signed in to change notification settings - Fork 5
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
Previously full "current{RecordId,NameId,Name,(Cardinality),CanonicalSimple,CanonicalFull}" fields are empty? #153
Comments
@Adafede thank so much for spotting this. I suspect it is related to gnames/gnames#128, and I would say that for names where 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. |
On a related topic, empty fields for currently accepted name should probably be hidden, when not used. |
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: