Reltio Connect

 View Only

  • 1.  Nested Address Management (clean-up & deduplication)

    Founding Member
    Posted 06-08-2021 11:31
    Hi all,

    As taken from the "What are the pros and cons of Address being implemented as Nested versus as an Entity?" discussion, I am curious what others have implemented regarding managing nested Addresses?

    More specifically, while we can obviously manage (e.g., dedup) entities through match/merge functionality, when leveraging nested Addresses within an entity, what techniques/processes were implemented to eliminate duplicate addresses within an entity? I'm guessing external process(es) were developed to analyze and cleanup address data within each entity?

    It would be nice if this was a built-in capability right? ;-)

    ------------------------------
    David Starnes
    Director, Enterprise Information Management & Architecture
    RedHill Biopharma, Inc.
    Raleigh NC
    ------------------------------


  • 2.  RE: Nested Address Management (clean-up & deduplication)

    Reltio Employee
    Posted 06-08-2021 13:03
    Any insights @Walt Feldman, @Angela Wawrzaszek from you end? ​​

    ------------------------------
    Chris Detzel
    Community Program Manager
    Reltio
    ------------------------------



  • 3.  RE: Nested Address Management (clean-up & deduplication)

    Founding Member
    Posted 06-09-2021 14:46
    We use Addresses as a separate Location Entity.  this does allow variations of addresses to come in, however if Locate deems them the same, it is cleansed and stored as 1 address.  If Locate is unable to cleanse the address the same, then you will see multiple addresses on the same profile.   

    Our data cleansing is done at the source only,  if addresses are different enough or in case where an account has an old address yet we merge it to the current address,  we send these back to our divisions to cleanup the data in the Source,  we do not clean in Reltio itself.  Since we do not integrate Reltio back to any source except SFDC (future desire to do so!),   and corrections were made only in Reltio,  our source is still incorrect and true issue is not resolved only hidden.   

    Does this help?

    ------------------------------
    Angela Wawrzaszek
    Manager, MDM governance and Application Enablement
    ------------------------------

    Original Message


  • 4.  RE: Nested Address Management (clean-up & deduplication)

    Founding Member
    Posted 06-09-2021 17:32
    Thanks Angela! We use the separate Location entity as well and it certainly provides certain advantages when it comes to dedup/cleanup efforts.  However, we may migrate to a nested Address attribute in the near future, which I have used before within a Reltio implementation at a prior company. If we do move to a nested Address solution, I'm curious what folks have done.

    I appreciate the feedback!

    ------------------------------
    David Starnes
    Director, Enterprise Information Management & Architecture
    RedHill Biopharma, Inc.
    Raleigh NC
    ------------------------------

    Original Message


  • 5.  RE: Nested Address Management (clean-up & deduplication)

    Reltio Employee
    Posted 06-09-2021 16:36
    Hi David,

    For nested attribute, Reltio provides a construct  to identify and merge duplicate.
    This is done by defining "matchFieldURIs", "matchFieldURIsExactOrAllNull", or "matchFieldURIsExactOrNull" or combination of these. You can check the help portal link.

    If duplicate addresses are cleansed, they will have the same cleansed values for all of the attributes, and by defining matchFieldURIs using the standard address fields, Reltio will merge them, effectively removing the duplicates. 
    The dedupe may not be very effective in case of uncleansed addresses having different source raw values, as the matching is always exact (compared to the Location, where we can define fuzzy rules), however with high rate of cleanse, it can effectively reduce the duplicates significantly.

    For the nested attributes, if matchFieldURIs section is not defined, it defaults to all of the sub-attributes. Following is an example how this is defined for nested address. 

    "matchFieldURIsExactOrNull": [
  "configuration/entityTypes/HCO/attributes/Addresses/attributes/AddressType",
  "configuration/entityTypes/HCO/attributes/Addresses/attributes/AddressLine1",
  "configuration/entityTypes/HCO/attributes/Addresses/attributes/AddressLine2",
  "configuration/entityTypes/HCO/attributes/Addresses/attributes/City",
  "configuration/entityTypes/HCO/attributes/Addresses/attributes/StateProvince",
  "configuration/entityTypes/HCO/attributes/Addresses/attributes/Zip5"
],​


    ------------------------------
    Sumit Singh
    ------------------------------



  • 6.  RE: Nested Address Management (clean-up & deduplication)

    Founding Member
    Posted 06-09-2021 17:34
    Thanks Sumit! I was thinking of a similar approach as we use this across other attributes as well.

    Thanks for the response!

    ------------------------------
    David Starnes
    Director, Enterprise Information Management & Architecture
    RedHill Biopharma, Inc.
    Raleigh NC
    ------------------------------

    Original Message


  • 7.  RE: Nested Address Management (clean-up & deduplication)

    Posted 06-09-2021 18:45
    Yes we also use "matchFieldURIs" in many of the attributes including Address to show one value where record is getting same values from multiple crosswalk.
    How you are loading Nested Address for a profile ? Contributor or Data provider.

    Any other issue noticed, I have seen some cases where for duplicate values exists for Loqate returned fields like AVC, or Verification status.

    ------------------------------
    Deepak Bhansali
    Sr Technical Product Manager
    Advance Auto P[arts
    Raleigh
    ------------------------------

    Original Message


Related Content