Ontology Manager doesn't raise issues about unmapped columns

I’ve had multiple cases where I’ve made adjustments to data pipelines and their output datasets, but forgot to map the new columns for the object type in the Ontology Manager. It’s especially error prone if a pipeline produces multiple datasets and the same property needs to be mapped for multiple object types at once.

There is an Issues column on the Object types page, which could be used to display a warning if an object type doesn’t map all properties from its backing dataset. This would match the behavior of e.g. pipeline builder, which warns about implicitly dropped columns if they are not mapped to the output dataset.

Note: I found the below post while checking if someone had already asked about the same topic. In our use case an unmapped column is always an error that needs fixing, but for some other use cases this kind of warning would probably be an annoyance. So this feature would benefit from the “tag as intentionally not used” feature as well.

https://community.palantir.com/t/tag-columns-as-intentionally-not-mapped-in-ontology-management/1973