-
Notifications
You must be signed in to change notification settings - Fork 10
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
dwc:higherClassification #30
Comments
@hollyel are you saying that higherTaxonomy should include both a concatenated list of names AND their rank for each individual name in the list? |
From Matt during 11/28/2018 mtg: dwc:taxonRank tells the iDigBio matching algorithm which dwc taxon level field to weight the heaviest. So if we give iDigBio a taxonRank value that is not also a dwc field (e.g. subclass) then the matching is affected negatively. |
From Nicholas Rejack during 11/28/2018 mtg: FYI taxonRank w/ controlled vocabulary for the field |
@garymotz No sorry. Just the actual names. I wasn't sure how to explain it in a clear way... I edited my original post |
As an issue "suborder" is an allowed value for taxonRank in the controlled vocab however there is no suborder DwC field so if that is provided, there is no DwC field for a matching algorithm to weight higher. |
just realized I used the wrong term name. Thread name is updated, but there are other instances of higherTaxonomy throughout the discussion |
Important to include for paleontological data. Darwin Core does not provide terms for all of the ranks that might be necessary for a given fossil specimen. A concatenated list of names in higherTaxonomy helps to fill that gap.
https://dwc.tdwg.org/terms/#dwc:higherClassification
Best practice and further comments below:
The text was updated successfully, but these errors were encountered: