Data Vault Modeler: I would love an option that looks at a naming scheme (Look at Naming Scheme apache/hop#7735 for an idea) for tables and fields to see if we can have naming schemes for source systems (every source system will have their own peculiar system), but also for data vault vault models.
Suppose there is a third party system for updating data vault 2.0 models and an organization wants to migrate to this tool we'd need to be able to look at a target data model, along with information about the used naming scheme to reverse engineer Hub, Satellite, Link tables and their relationships based on the naming used for tables and fields, optionally defined PK and FK indexes/constraints. We should be able to select a number of tables in a DV target database and generate a DV model with DvTables for those physical database target tables.
Data Vault Modeler: I would love an option that looks at a naming scheme (Look at Naming Scheme apache/hop#7735 for an idea) for tables and fields to see if we can have naming schemes for source systems (every source system will have their own peculiar system), but also for data vault vault models.
Suppose there is a third party system for updating data vault 2.0 models and an organization wants to migrate to this tool we'd need to be able to look at a target data model, along with information about the used naming scheme to reverse engineer Hub, Satellite, Link tables and their relationships based on the naming used for tables and fields, optionally defined PK and FK indexes/constraints. We should be able to select a number of tables in a DV target database and generate a DV model with DvTables for those physical database target tables.