events-api: consider metadata for duplicate relationships
Opened this issue · 2 comments
When an Identity relationship comes is (A isIdenticalTo B) and this relationship has already been evaluated in the past, the event is skipped. We should first take a look if we can use something from metadata before discarding.
do you mean the metadata in the payload that contained the relationship or using this as an opportunity (or trigger) to re-evaluate the metadata of the two objects link in the relationship? I had always thought of the latter as a process with a separate timescale for updates rather than one triggered by the discovery of a relationship.
Hey, good question :) It's actually for both:
a) for the initial relationship payload (which is a bug and will be fixed)
b) all subsequent relationships which could potentially enrich (re-evaluate) metadata, which would be a nice feature, but then we get into the problem of determining which metadata is "better"