Reltio Connect

1. Source systems currently store a county id
2. There is an RDM Lookup for counties and a separate RDM Lookup for Metropolitan Statistical Areas (MSA's)
3. Both lookups use the source system county id values as input to RDM
4. We would like Reltio to separately maintain the County and MSA data
5. Creation of the entity would only specify one attribute likely as the county 
6. Both county and MSA would retain the value from the same source
7. Any future change thru either Hub or direct API calls would not be able to update 1 without the other

1. Source systems currently store a county id
2. There is an RDM Lookup for counties and a separate RDM Lookup for Metropolitan Statistical Areas (MSA's)
3. Both lookups use the source system county id values as input to RDM
4. We would like Reltio to separately maintain the County and MSA data
5. Creation of the entity would only specify one attribute likely as the county 
6. Both county and MSA would retain the value from the same source
7. Any future change thru either Hub or direct API calls would not be able to update 1 without the other

Abhradeep,

Appreciate the probing questions, which is changing my ask a bit.

To help clarify, we should distinguish between API based  updates which we consume in our Ingress ETL process  as contrasted to the Reltio Hub. 

5) Creation of the entity would only specify one attribute likely as the county
           Ingress ETL :  Only provide county code info, with the expectation that a separate MSA "read only or virutual"  attribute could also be populated using a                                       separate RDM lookup
           Hub:  Only the ability to update the county attribute using the county RDM lookup values but changes would be reflected in the separate MSA "read only or                               virtual"  attribute reflecting the descriptive info from the RDM lookup

6)   Both county and MSA would retain the value from the same source:

                   This is not referring to surivorship, but more specifically for the individual crosswalk being updated. If the MSA could be read-only

                             to the Hub user but reflective of the data in the county code that would be what we want
7)    Any future change thru either Hub or direct API calls would not be able to update 1 without the other

                  Change the ask here so that update would only be to the county and MSA could not be directly updated

In a relational DB world, i would handle the requirement in 1 of 2 ways; not clear if / how that would be handled in Reltio.

            8) Only store the data in one column but at the time of display translate based on 2 "lookup tables"  and display as 2 separate display columns

            9) Store the MSA as a virutal or read-only column and derive the value based on the code stored in the county column
Hope this helps to clarify.

Thanks,
Mark

1. Source systems currently store a county id
2. There is an RDM Lookup for counties and a separate RDM Lookup for Metropolitan Statistical Areas (MSA's)
3. Both lookups use the source system county id values as input to RDM
4. We would like Reltio to separately maintain the County and MSA data
5. Creation of the entity would only specify one attribute likely as the county 
6. Both county and MSA would retain the value from the same source
7. Any future change thru either Hub or direct API calls would not be able to update 1 without the other

Abhradeep,

Appreciate the probing questions, which is changing my ask a bit.

To help clarify, we should distinguish between API based  updates which we consume in our Ingress ETL process  as contrasted to the Reltio Hub. 

5) Creation of the entity would only specify one attribute likely as the county
           Ingress ETL :  Only provide county code info, with the expectation that a separate MSA "read only or virutual"  attribute could also be populated using a                                       separate RDM lookup
           Hub:  Only the ability to update the county attribute using the county RDM lookup values but changes would be reflected in the separate MSA "read only or                               virtual"  attribute reflecting the descriptive info from the RDM lookup

6)   Both county and MSA would retain the value from the same source:

                   This is not referring to surivorship, but more specifically for the individual crosswalk being updated. If the MSA could be read-only

                             to the Hub user but reflective of the data in the county code that would be what we want
7)    Any future change thru either Hub or direct API calls would not be able to update 1 without the other

                  Change the ask here so that update would only be to the county and MSA could not be directly updated

In a relational DB world, i would handle the requirement in 1 of 2 ways; not clear if / how that would be handled in Reltio.

            8) Only store the data in one column but at the time of display translate based on 2 "lookup tables"  and display as 2 separate display columns

            9) Store the MSA as a virutal or read-only column and derive the value based on the code stored in the county column
Hope this helps to clarify.

Thanks,
Mark

1. Source systems currently store a county id
2. There is an RDM Lookup for counties and a separate RDM Lookup for Metropolitan Statistical Areas (MSA's)
3. Both lookups use the source system county id values as input to RDM
4. We would like Reltio to separately maintain the County and MSA data
5. Creation of the entity would only specify one attribute likely as the county 
6. Both county and MSA would retain the value from the same source
7. Any future change thru either Hub or direct API calls would not be able to update 1 without the other