Before we can generate the complete data vault, we first have to manage some extra settings for the different options.
Choose your data vault release and go to the HUB Management tab.

In the HUB grouping subtab, in the HUB Grouping section, you can see all the hubs of the different sources included in your data vault, tables of different sources are automatically linked based on their name. If a similar hub could not be found in a source, it will show a drop-down menu where you can manually select a hub to group, or leave it as is. In the Single HUB Listing section, you can see all the hubs that are not grouped. In the Unlinking section, you can unlink hubs if they were linked by mistake.

For example, we know the “persons” table of Source 2 is the same as the “employees” table of the two other sources, we connect their hubs in the HUB Grouping section.

In the Master/slave subtab, under the Source master/slave section, you can define whether a source is a slave of another, or under the HUB master/slave section, you can define whether a specific hub is a master or a slave.

In the third subtab of the HUB Management tab, i.e. the Name management subtab, names can be adapted by changing the short and abbreviated names, this is needed when two hubs have the same name but are not linked.

For example, if “hub_persons” and “hub_employees” are not linked, we get a naming conflict.

The LND Management tab only allows you to manage the names of the lnd tables.

The LNK Management tab, like the LND Management tab, only allows you to change the names of the lnk tables. The difference with the HUB Management and LND Management tabs is that only the table short names can be changed. The other names change with the hubs.

For example, if we return to the third section Name management under HUB Management and change the “hub_locations” short name to “loct”, the hubs and lnks dependent on this table will be automatically updated.

You can confirm this in the LNK Management tab.