-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add typifiedName #1065
Comments
This will be really useful to clean up type specimens on GBIF and link them to their nomenclatural details and literature. |
It will probably come up in the Darwin Core public review, but it might be worth thinking about implementing a data quality warning when typifiedName is populated and typeStatus is empty. A warning might also be possible in the other direction. However, it is quite common that collections know a specimen is a type, but are not certain what name it is a type of. |
It would be great if typifiedName became a standard for GBIF publication. Our type specimens curated on the JACQ network already have the field (called "type of" here), so we could provide the data for typifiedName immediately. see https://www.jacq.org/detail.php?ID=1053795 |
This would be a nice additioin |
There will soon be an update to the typeStatus controlled vocabulary gbif/vocabulary#87 - I am mentioning it here if any synergy is expected for interpretation. |
Good to know! I don't foresee too much complication except where a specimen is a type for multiple names. In the long term it would be nice to see a guide written to the best practises for publishing typification data. While it is not that difficult, it would encourage standardization. |
It is probably too difficult to do anything with this in the pipelines, but when we worked on the typeStatus vocabulary (and inspired by this comment), I noticed most of the verbatim values (71%, n = 107140) included an |
I've had an approach from a GBIF publisher:
This is a likely candidate to pass the next round of DwC review, and so I suggest we add it to the next batch of edits we make to the ingestion (in a gbif or dwc namespace depending on the state).
The text was updated successfully, but these errors were encountered: