Bug: Parent mismatch issue shows names without that error

[DianRHR]

Description

In the private dataset Coleoptera type genera and family-group names I am generating, I got 282 names with the issue Parent Name Mismatch. I checked randomly 10 cases and any of them has any problem (check Verbatim). However, I can't understand why is this issue showing in those specific names.

What browsers are you seeing the problem on?

Chrome

ChecklistBank URL

https://www.checklistbank.org/dataset/290628/names?facet=rank&facet=issue&facet=status&facet=nomStatus&facet=nomCode&facet=nameType&facet=field&facet=authorship&facet=authorshipYear&facet=extinct&facet=environment&facet=origin&facet=sectorMode&facet=secondarySourceGroup&facet=sectorDatasetKey&facet=group&issue=parent%20name%20mismatch&limit=50&offset=0

[mdoering]

In the interpreted view the species are placed in the wrong genus, e.g. Acanthocerus aeneus in Ceratocanthus

The verbatim shows both parentID=17 and flat classification fields like genus=Acanthocerus. In such cases the importer always prefers the parentID as this is more reliable and ignores all flat fields (which should probably be removed from the dataset for simplicity).

Usage 17 is Acanthocerus, but it is considered a synonym which can never be a parent in a classification. Hence it has the issue synonym parent and in turn links to usage 838 as the accepted taxon - which is the accepted genus Ceratocanthus which is finally used.

I'd recommend to:

• remove flat classification fields
• only link to accepted taxa via parentID, never to any synonym

The dataset has an issue with accepting species in a genus which is considered a synonym though. Not sure if you wanted that.

[mdoering]

Please use the backend repo for all importing issues in the future, checklistbank is just the frontend.