Our source system sends daily snapshots of Bookings and Booking Items. It does not send explicit information when a particular booking item was removed, it just sends the new snapshot of the booking and the currently active items.
It means that if an item was present in the previous load and is missing in the staged data, the item was deleted.
We represent the items as links (hub_booking ← link_item → hub_item). How could we best represent the end of the timeline of a given link item with the option that it may become active again at a later stage?