Closed dylanbeaudette closed 3 years ago
The current strategy breaks down with "fibristels" "folistels" "hemistels" "glacistels" "sapristels", due to the contraction of "hist" to "ist".
Some ideas:
SubGroupFormativeElements()
This issue is resolved since the use of the lookup table using letter codes to denote parent-child relationships with little-to-no pattern matching required. Came with reorganization of the package in #14
The current strategy breaks down with "fibristels" "folistels" "hemistels" "glacistels" "sapristels", due to the contraction of "hist" to "ist".
Some ideas:
SubGroupFormativeElements()
where matching is performed on the formative elements vs. exact matching of parent taxa