Some DI tools specify data movement logic at the table (or even schema) level. A database replication tool can ask to load a table from a file without specifying columns involved. MetaKarta customers would like to trace lineage through these bulk metadata at the column level.
The MetaKarta metamodel and Database/DI bridges support classifier-level-only mappings. The data mapper supports authoring of these type of mappings and resolves these “not completely defined” MIMB and Mapper mappings during the configuration assembly (verification) process.