@eliagbayani : @JRice alerted us to the fact that the pbdb hierarchy has a lot of "root nodes" (370), i.e., hierarchy entries that don't have any parents. Since this is a continually updated, community curated hierarchy, it's expected that there might be a few species, genera, families, etc. dangling around the root until somebody takes mercy on them and gives them a parent. But I don't remember there being quite so many. A spot check of some of the affected taxa reveals that they do have parents at the source, e.g.:
https://paleobiodb.org/data1.1/taxa/single.json?id=170202&show=attr
https://paleobiodb.org/data1.1/taxa/single.json?id=282936&show=attr
https://paleobiodb.org/data1.1/taxa/single.json?id=14054&show=attr
Is this just a matter of our data being old, and it will fix itself once we re-run the connector? Or is there something about these taxa that makes it difficult for our connector to catch their parents?
@eliagbayani : @JRice alerted us to the fact that the pbdb hierarchy has a lot of "root nodes" (370), i.e., hierarchy entries that don't have any parents. Since this is a continually updated, community curated hierarchy, it's expected that there might be a few species, genera, families, etc. dangling around the root until somebody takes mercy on them and gives them a parent. But I don't remember there being quite so many. A spot check of some of the affected taxa reveals that they do have parents at the source, e.g.:
https://paleobiodb.org/data1.1/taxa/single.json?id=170202&show=attr
https://paleobiodb.org/data1.1/taxa/single.json?id=282936&show=attr
https://paleobiodb.org/data1.1/taxa/single.json?id=14054&show=attr
Is this just a matter of our data being old, and it will fix itself once we re-run the connector? Or is there something about these taxa that makes it difficult for our connector to catch their parents?