This article describes the basic concept of Link implementation in ODE. For a step-by-step configuration guide please refer to Configure a New Link.

Every Link must have a Source for defining the relationship between hubs being linked. The Hub key is generated by ODE once the new business key is inserted. The Link source should contain hub business keys, so that the generated vault hub keys can be looked up. Link source fields must be configured as source columns for the related hub keys.

Every Link in ODE must have a Satellite. Link satellites store business keys and auto-generated current state fields. They are important as they manage the time context of the Links.

Link source tables should have no duplicate rows. It makes sense that, if this table contains business keys only, NULL values are excluded. So, even if a hub and a link are sourced from one original table in the transactional database, it is necessary to have two separate timevault sources for them.

Hub key columns must be hooked up to the link source columns. If hub key doesn’t exist at the time of link load, it will be created and linked. This guarantees relationship is recorded even in case of late hub data arrival.


The minimal set of objects for ODE Links.

Currently ODE does not allow implementing hierarchical links or same-as-links.