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
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?
The text was updated successfully, but these errors were encountered:
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 :
The text was updated successfully, but these errors were encountered: