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

Some odd names to check #304

Open
6 of 14 tasks
ManonGros opened this issue Jun 20, 2024 · 10 comments
Open
6 of 14 tasks

Some odd names to check #304

ManonGros opened this issue Jun 20, 2024 · 10 comments
Assignees
Labels
fix request A fix requested for a specific paper or treatment

Comments

@ManonGros
Copy link

ManonGros commented Jun 20, 2024

Hi PLAZI,

Some of the names reported in this issue come from data published by PLAZI. They all seem to be oddly shaped. Would it be possible to check them out?

Let me know if you have any question, thanks!

@flsimoes flsimoes added the fix request A fix requested for a specific paper or treatment label Oct 29, 2024
@Carol-Sokolowicz
Copy link

I've fixed the names but don't know why it hasn't been updated on GBIF

@myrmoteras
Copy link
Contributor

@Carol-Sokolowicz you can get an idea why, if the ingestion here https://www.gbif.org/system-health is high

@flsimoes
Copy link

flsimoes commented Nov 23, 2024

@myrmoteras @ManonGros Some of the names reported here are invalid, are there guidelines on how to deal with them in GBIF?

Also, one of the reported names is a pro parte, meaning it includes more than one currently recognized entity, and that only one of those entities is being considered. Not sure how that should be presented on TB and GBIF

@flsimoes
Copy link

I've fixed the names but don't know why it hasn't been updated on GBIF

It's been updated, but they are not fully fixed yet

@flsimoes
Copy link

flsimoes commented Nov 23, 2024

Fixed the Smaragdina in C207BF1CD6BB50DB836ED0D0FED79BD9

They should be fixed in GBIF soon

@flsimoes
Copy link

As @Carol-Sokolowicz said, the Pericalus in AA26FF84157BFFAE490E7F133744FF98 should be fixed. I gave it another go to see if it finally triggers an update by GBIF

@flsimoes
Copy link

The Mus cypriacus in E2099A0D3426FF97E1372C0977498313 had a missing authority attribute.

@ManonGros
Copy link
Author

Thanks @flsimoes !

Some of the names reported here are invalid, are there guidelines on how to deal with them in GBIF?
Also, one of the reported names is a pro parte, meaning it includes more than one currently recognized entity, and that only one of those entities is being considered. Not sure how that should be presented on TB and GBIF

Perhaps this is a question for @DianRHR and @camiplata

@flsimoes
Copy link

Regarding the non-disappearance of the wrong taxonomicNames from GBIF (it does disappear from the Plazi record though) is likely a GBIF issue. Perhaps these wrong names are not cleaned up at all after we update them...

@ManonGros
Copy link
Author

Yes @flsimoes the link above are to the names that were already integrated in the GBIF backbone taxonomy so they won't disappear until the backbone gets updated. I checked the PLAZI datasets and the names were indeed removed from what is provided to GBIF. This means that the next backbone should be good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix request A fix requested for a specific paper or treatment
Projects
None yet
Development

No branches or pull requests

4 participants