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

acceptedKey (checklist) vs acceptedTaxonKey (occurrence) don't follow same strategy #78

Open
damianooldoni opened this issue Mar 20, 2019 · 1 comment

Comments

@damianooldoni
Copy link

In checklists:
the field acceptedKey is not present if taxon isn't a synonym.

In occurrences:
the field acceptedTaxonKey is always present and equal to taxonKey if taxon is not a synonym.

Example: taxonKey = 2769766

http://api.gbif.org/v1/species/2769766
http://api.gbif.org/v1/occurrence/2006075512

Is there a reason for this asymmetry?

@mdoering
Copy link
Member

not really. NULL values lead to the property being dropped. And pointing to oneself as the accepted I never felt is right. But yes, I guess we need to take some effort in harmonizing the API. There are more discrepancies between the occurrence and species API

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