- links are stateless, as that id there breaks link.
- you need hub for that entity and add new hk from new hub into link
now:
- depending if system in production, data quantity, etc… when a model change (e g. one new hub key on the link) that changes the grain of the link, and as always in data vault we dont drop stuff, delete stuff or update stuff… with these 3 ideas in mind its not too far to think that you need a new link table with same columns + new hub column, then a business view that union all both link tables assigning some zero-key (avoid nulls) on all records from old video.
I wonder what more experts in here think on this ?