Transactional Link for capturing Customer Signature upon receive of the product

Data Vault 2.0
, , , ,
1

We have a LINK to capture the ORDER and PRODUCT for a Orders: LINK_ORDER_PRODUCT with HK_LINK_PRODUCT

Now we want to capture the Signature data from the Customer when they receive the PRODUCT. The product may be shipped on multiple Pallets (for e.g. sod, concrete etc.) at different times. The Customer signs for each Pallets individually upon receiving it. We are thinking of using a Non delta-driven LINK (Transactional Link) for this purpose.

We have two options:

  1. Include the Pallet Number as a Dependent Child in this Transactional Link and then generate a new HK_LINK_ORDER_PRODUCT with Dependent Child in it. Issue here is that this will not join to the HK_LINK_ORDER_PRODUCT in LINK_ORDER_PRODUCT
  2. Include the Pallet Number as a Dependent Child in this Transactional Link but do not include it as part of the HK_LINK_ORDER_PRODUCT. This will allow joins to LINK_ORDER_PRODUCT using HK_LINK_ORDER_PRODUCT. However this goes against the Standard which says that the Dependent Child should be part of the LINK Hashkey generation.

Please advise.

2

This is the Anti-Pattern

This is actually how you should do it. Although, T-Links being deprecated you could treat this as a NH-Link if every event is guaranteed to be exactly once and always a change.

If you need help with justifying which pattern is correct or you can relate to, Rules for an (almost) unbreakable Data Vault | by Patrick Cuba | The Modern Scientist | Medium

Under the section rule #4. Cruft, the Big Ball of Mud.

3

Hi @patrickcuba . Thanks. So the Dependent Child should not be included in calculating the LINK_HASHKEY in a LINK?