Ranking errors in Ostracoda

[aoern]

There are obvious ranking errors in Ostracoda:

1. suborder Palaeocopa is listed directly under class Ostracoda
2. Palaeocopa contains infraclasses Leiocopa and Leperditicopa as direct children.

If you browse to "Palaeocopa (prov. suborder in Ostracoda)" on the Browse page, you get something like this: class: Ostracoda Latreille, 1802

subclass: Myodocopa Mueller, 1894 subclass: Platycopa Sars, 1866

subclass: Podocopa Mueller, 1894

subclass: Not assigned

suborder: Palaeocopa Henningsmoen, 1953

infraclass: †Leiocopa Schallreuter, 1973 infraclass: †Leperditicopa Pokorny

infraclass: Not assigned

suborder: [Not assigned] Load more... Load more...

Can't understand where these mystical "Load more..." rows come from and what they mean. If you open and close branches in the tree, you'll get more "Load more..." rows! Could these display problems be somehow caused by the ranking errors?

[yroskov]

Regarding hierarchy & ranks: I would say, CoL interpretation of original WoRMS data (i.e. sunbclass "Ostracoda incertae sedis" with suborder "Palaeocopida incertae sedis" and many genera and families as children) is correct in a paradigm of current interface.

@thomasstjerne, could you please have a look on "load more" issue in the interface pointed by Ari. Is it expected (taking in account multiple "Not Assigned" nodes in the tree due to original data)?

[aoern]

@yroskov, yes you are right. The error that I wanted to report is the suborder being the parent of infraclasses, which makes no sense.

[yroskov]

@bart-v, indeed infraclass Leiocopa is beneath suborder Palaeocopa: https://www.marinespecies.org/aphia.php?p=taxdetails&id=715605

[bart-v]

This basically duplicates https://github.com/CatalogueOfLife/data/issues/612 WoRMS editors are now reminded on this

[bart-v]

Should be fixed in WoRMS