@roy-lowry Yes you can store any scientific name within the taxonomic hierarchy 
in Darwin Core `scientificName` and then there are more terms to specify the 
taxonomy as well as the rank. So for instance you could have:
`scientificName` = "Calanus finmarchicus` and then have:
`scientificNameID` = "urn:lsid:marinespecies.org:taxname:104464"
`[taxonRank](https://dwc.tdwg.org/terms/#dwc:taxonRank)` = "species"
`[kingdom](https://dwc.tdwg.org/terms/#dwc:kingdom)` = "Animalia"
`[phylum](https://dwc.tdwg.org/terms/#dwc:phylum)` = "Arthropoda"
`[class](https://dwc.tdwg.org/terms/#dwc:class)` = "Crustacea" (and on down 
to...)
`[specificEpithet](https://dwc.tdwg.org/terms/#dwc:specificEpithet)` = 
"finmarchicus"

For something like dinoflagellates it would be:
`scientificName` = "Dinoflagellata"
`[vernacularName](https://dwc.tdwg.org/terms/#dwc:vernacularName)` = 
"dinoflagellates"
`scientificNameID` = "urn:lsid:marinespecies.org:taxname:146203"
`taxonRank` = "Infraphylum"
`kingdom` = "Chromista" etc

But really you have all you need with just `scientificName` and 
`scientificNameID` since all the rest can be extracted from WoRMS using the 
LSID. Just showing that you can include a scientific name at any level of the 
taxonomic hierarchy in Darwin Core and the associate terms. Also GBIF is 
accepting BOLD and UNITE stable Operational Taxonomic Units (OTUs, eDNA) in 
`scientificName` as well (more info on that 
[here](https://docs.gbif-uat.org/publishing-sequence-derived-data/1.0/en/)). 
Realize that's more than what you're asking about but just in case it's 
relevant.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/309#issuecomment-731271425

This list forwards relevant notifications from Github.  It is distinct from 
[email protected], although if you do nothing, a subscription to the 
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to 
[email protected].

Reply via email to