Workbench: Implement a more deterministic solution for validating COType #6198
Labels
1 - Enhancement
Improvements or extensions to existing behavior
2 - WorkBench
Issues that are related to the WorkBench
Follow-up to #6194
As a quick fix, COType validation uses a naive approach of figuring out the COType value in a given row. It fetches the cotype column based on string matching but there could be scenarios where this is too simplistic. This can be improved upon by sending a parameter to
ScopedTreeRecord
which indicates which column to look at for COType, ideally obtained from parsing the rest of the dataset prior to this.specify7/specifyweb/workbench/upload/treerecord.py
Lines 342 to 348 in 764d34b
The text was updated successfully, but these errors were encountered: