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
There are synonyms with more than one acceptNameUsageID that may indicate taxon concepts rather than taxonomic treatment. eg http://data.canadensys.net/vascan/taxon/9946?lang=en. There is no appropriate way to represent this in DwC unless we create a new taxonID for a second, identically named synonym. The two identical synonyms can then have different acceptedNameUsageIDs. We could also make use of taxonConceptID to bundle the representations so as not to lose sight of what these relationships indicate. However, an auto-generated taxonID is dangerous unless we are certain it will never conflict with future taxonIDs. So, we'd have to prepend these taxonIDs with text or some other flag, which also means they must resolve on VASCAN.
dshorthouse
changed the title
Include potential taxon concept representations in the DwC-A export
Fix potential taxon concept representations to facilitate DwC-A creation
Nov 27, 2014
There are synonyms with more than one acceptNameUsageID that may indicate taxon concepts rather than taxonomic treatment. eg http://data.canadensys.net/vascan/taxon/9946?lang=en. There is no appropriate way to represent this in DwC unless we create a new taxonID for a second, identically named synonym. The two identical synonyms can then have different acceptedNameUsageIDs. We could also make use of taxonConceptID to bundle the representations so as not to lose sight of what these relationships indicate. However, an auto-generated taxonID is dangerous unless we are certain it will never conflict with future taxonIDs. So, we'd have to prepend these taxonIDs with text or some other flag, which also means they must resolve on VASCAN.
Linked to #8
The text was updated successfully, but these errors were encountered: