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

Allow to use a genus or higher taxon ranks #274

Open
damianooldoni opened this issue Dec 22, 2023 · 0 comments
Open

Allow to use a genus or higher taxon ranks #274

damianooldoni opened this issue Dec 22, 2023 · 0 comments

Comments

@damianooldoni
Copy link
Collaborator

Providing a genus among the "list of species" will stop the instance to work correctly if occurrences are found linked to a species (or subspecies, form, ...) belonging to that genus.

Example: the LIFE RIPARIAS instance stopped working on Dec 22 as one of the new species added on Dec 21 was a genus (Carpobrotus) and one downloaded occurrence (occurrenceID: 4170944384) was linked to the species Carpobrotus N.E.Br.. Thanks @niconoe for finding the core of the problem I have described here. Feel free to add more details if needed.

Probably we should allow not only genera, but also higher taxon ranks up to classes.

damianooldoni added a commit to riparias/taxon-keys-early-alert that referenced this issue Dec 22, 2023
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

1 participant