[Bug]: Automatic combinations don't match TW's rules for genera with nominotypical subgenera

[dhobern]

Steps to reproduce the bug

1. Create name with genus having a nominotypical subgenus as parent or with subgenus as parent
2. Select "Set as current" for original combination
3. TW creates original combination with genus set to reference the genus name not the nominotypical subgenus
4. TW then warns: "Relationship should move from genus Aus to subgenus Aus (Aus)"

Screenshot

No response

Expected behavior

If the relationship should be with the subgenus, it should be set that way automatically

Additional Screenshots

No response

Environment

Production

Sandbox Used

No response

Version

No response

Browser Used

Firefox

[typophyllum]

I think if the author of the new species name doesn't care about subgenera, the original combination and rank would be Aus cus, independent of TW preferring to store the relationship at the lowest possible level.

[dhobern]

@typophyllum You can certainly create subgenus-free names and combinations in TW, even in genera with subgenera. I was raising this issue to address the inconsistency in the internal processes and rules that TW applies. By default, it creates the combination with the genus as the name, but then it complains that the combination should be using the subgenus.

[proceps]

When we create a combination, we just use parent child relationships, at this stage, we do not know that coordinate subgenus exists in the database. The only thing which could be done is to soft_validate and fix of each of the TN relationships. It does not affect the spelling of the new combination. The soft_validation and fix was designed for future use, when we are able to run fixes on the entire project in order to optimize it.