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
1.CO with type status added since the release of 46.1 does not have type status+taxon name on DwC export only type status.
2. For example see: https://sfg.taxonworks.org/tasks/accessions/comprehensive?collection_object_id=2069512
and compare to: https://sfg.taxonworks.org/tasks/accessions/comprehensive?collection_object_id=1688793
3.
...
Screenshot
Expected behavior
No response
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
No response
Browser Used
No response
The text was updated successfully, but these errors were encountered:
@mjy We are a tiny bit closer to understanding the issue with Taxon Names not outputting correctly in DwC. We now understand that there are 3 ways to create new taxon names in TW but only one way will create the desired outcome. The three ways are:
in Comprehensive Determination, if a name is not in the pull down option, you can create a new OTU or new Taxon name
The Data tab Taxon Name: if you create a new Taxon name using this option, the Taxon Name will not be complete. This option does not automatically add "original combination and rank," - which may be the issue.
New Taxon Name from the New Taxon Name Task. This appears to be the only way to correctly create a new taxon name.
We still don't understand why some Taxon Names also appear as OTUs (why you can filter OTUs and find some of the Taxon Names but not all)
It would be helpful to have guidance on how when to use each of the three options for new Taxon Name creation. Also, if we don't want Taxon Names as an OTU, how should we delete them? Or do we just leave them there as an OTU?
Steps to reproduce the bug
Screenshot
Expected behavior
No response
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
No response
Browser Used
No response
The text was updated successfully, but these errors were encountered: