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

Unmatched species #10

Open
mathieuLU opened this issue Oct 14, 2020 · 1 comment
Open

Unmatched species #10

mathieuLU opened this issue Oct 14, 2020 · 1 comment
Assignees

Comments

@mathieuLU
Copy link
Collaborator

Ecodata/BioCollect and the Lists components are based on the scientific names of species to match the elements.
Which means that if a scientific name is not provided in the species list, or misspelled, it won't be matched with other GBIF occurences.
And then the element will be labelled as " Unrecognised taxa " in the lists module, and it won't be possible to use it in BioCollect/Ecodata

In SEBMS for instance, Lars is using a lot of aggregates taxon names. No scientific names for them.

In Ecodata, if a user creates a row with a new name (non-existing in the species list), the row is "successfully saved" with this new name. But the record won't be create. Data exists in the output collection though.

Several questions :

  • how to deal with the aggregate species for the LISTS module
  • is it allowed to add a row with unknon species in SFT/SEBMS forms ? (no ideas what are Lars/Åke' views on this subject)
  • shall I address Sathish/Peter on that subject?
@mathieuLU
Copy link
Collaborator Author

All the taxa are recognized. The remaining problem is about the species-aggregate in SEBMS

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