Ashish,
So my take-away is:
For an update of an attribute to the same value that had previously been pinned or ignored:
1) if overrideIgnorePin = false then will retain the pin / ignore
2) if overrideIgnorePin = true (or omitted since default is true) then will lose the pin / ignore
Thanks,
Mark
------------------------------
Mark Burlock
Dodge Data & Analytics
Hamilton NJ
------------------------------
Original Message:
Sent: 01-19-2023 10:11
From: Ashish Rawat
Subject: L3 Configuration: overrideIgnorePin Additional Context and Information
Hi Mark,
overrideIgnorePin parameter provides user an option to preserve ignored and pinned status of an attribute value. Consider a case where for a golden record contributed by multiple crosswalk, Data steward Ignored a value from highest priority source. Now next time when record is updated with same value ignored status will be removed for that value it will again become the golden value when overrideIgnorePin is set as true now if business agrees and user want to preserve pinned and ignored status of the attribute value overrideIgnorePin can be set as false.
------------------------------
Ashish Rawat
Manager
Fresh Gravity
Bangalore
Original Message:
Sent: 01-18-2023 17:36
From: Mark Burlock
Subject: L3 Configuration: overrideIgnorePin Additional Context and Information
Hi,
I am looking for any additional information, context, etc regarding L3 Configuration Parameter: overrideIgnorePin and functional behavior.
Per documentation, I am seeing very limited information:
Determines if the "pin"/"ignore" flags must be overridden after updating an attribute by the same value. By default, true. Example: "overrideIgnorePin": "false"
URL: Reltio
Thanks,
Mark
------------------------------
Mark Burlock
Dodge Data & Analytics
Hamilton NJ
------------------------------