ODI Data Quality - Relationship Linker Process

Question

Hi All,
I have been trying to use the relationship linker process in the ODI data quality interface with limited success.
My Problem:
The process tab in the relationship linker asks for two inputs. 1) Attribute containing record type & 2) Attribute Containing window key
The attribute containing window key is pre-filled to be window_key_01 (window key) that you can set up in the prior step. I am not able to determine which exact field i should be specifying in the "ATTRIBUTE CONTAINING RECORD TYPE" column.
Things that i have tried out:
I have used the following column for attribute containing record type
1) PR_BUSNAME_RECODED01
2) US_POSTAL_MATCH_INPUT_AREA
3) WINDOW_KEY_01
4) PR_ STREET_NAME
The window key i am using is as follows
1) Business name - 5 chars( first character + subsequent non-repeating consonants of the business name)
2) State Name - 2 chars
3) City Name - 5 chars (first character + subsequent consonants)
4) postal code - 5 chars (numerics only)
Guidance Needed
1) Which attribute should be selected for "ATTRIBUTE CONTAINING RECORD TYPE" column. If possible, can you also include the reason to use that attribute?
2) In the advances features window of the relationship linker process, the linking rules are also not very clear. I am still trying to figure out what lev2_matched_in_lev1_matched and other similar options correspond to.
The help files do not explain this at length.
I am having some difficulty in understanding the relationship linker process and I have tried out many options.
If any ODI data quality guru's or pro's can help me out with this. I'll be really grateful.
Thanks,
Chapanna

Answer 1

Hi,
thanks for your reply.
Yes I got the second connection; the question was about the procedure described in the manual.
The solution I found is a trick also because the way described in docs is not limited to a second repository but could be used also for several entries.
Because I am trying develop knowledge on ODI I would solve any possible unexpected behavior. Do you see in your setup the entry described in docs?
Taking a look at the Store the ODQ is quoted 70,000 $ / processor which is one reason more I would expect customer wanting to be able to follow the procedure depicted in the documentation or being removed from there (I try to answer questions that someone could ask to me).
Thanks
Fabio D'Alfonso