<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Blocking Strategies for Data Matching in Talend Data Integration/Data Quality and Talend MDM in Talend Data Catalog</title>
    <link>https://community.qlik.com/t5/Talend-Data-Catalog/Blocking-Strategies-for-Data-Matching-in-Talend-Data-Integration/m-p/2335245#M1393</link>
    <description>&lt;P&gt;Scenario : The Employee CSV file from HR system is source 1. Source 2 is another CSV from different system. In this case, HR system always has the recent address and other information about the employee. there are duplicate records for the same employee from both of the systems.&lt;/P&gt;
&lt;P&gt;Question 1 : is there a way&amp;nbsp; to instruct the MDM job to consider the HR system as latest record while merging? Is that can be automated or only handled manually?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Question 2: In talend MDM UI there is a link called STAGING AREA. What is that? Is that predefined staging area inside the MDM repository&amp;nbsp;or can we configure any of the database as staging? Because, I want to use landing and staging in a single oracle database with different schema.Also, there is a button named Validation which will take care of validation. Internally what validation does?&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 08:53:32 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T08:53:32Z</dc:date>
    <item>
      <title>Blocking Strategies for Data Matching in Talend Data Integration/Data Quality and Talend MDM</title>
      <link>https://community.qlik.com/t5/Talend-Data-Catalog/Blocking-Strategies-for-Data-Matching-in-Talend-Data-Integration/m-p/2335245#M1393</link>
      <description>&lt;P&gt;Scenario : The Employee CSV file from HR system is source 1. Source 2 is another CSV from different system. In this case, HR system always has the recent address and other information about the employee. there are duplicate records for the same employee from both of the systems.&lt;/P&gt;
&lt;P&gt;Question 1 : is there a way&amp;nbsp; to instruct the MDM job to consider the HR system as latest record while merging? Is that can be automated or only handled manually?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Question 2: In talend MDM UI there is a link called STAGING AREA. What is that? Is that predefined staging area inside the MDM repository&amp;nbsp;or can we configure any of the database as staging? Because, I want to use landing and staging in a single oracle database with different schema.Also, there is a button named Validation which will take care of validation. Internally what validation does?&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 08:53:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Data-Catalog/Blocking-Strategies-for-Data-Matching-in-Talend-Data-Integration/m-p/2335245#M1393</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T08:53:32Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking Strategies for Data Matching in Talend Data Integration/Data Quality and Talend MDM</title>
      <link>https://community.qlik.com/t5/Talend-Data-Catalog/Blocking-Strategies-for-Data-Matching-in-Talend-Data-Integration/m-p/2335246#M1394</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Sorry for delay.&lt;/P&gt;
&lt;P&gt;We have redirected your issue to our MDM experts and will keep you posted.&lt;/P&gt;
&lt;P&gt;Thanks for your time.&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;
&lt;P&gt;Sabrina&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 10:16:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Data-Catalog/Blocking-Strategies-for-Data-Matching-in-Talend-Data-Integration/m-p/2335246#M1394</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-01-25T10:16:27Z</dc:date>
    </item>
  </channel>
</rss>

