1 of 1 people found this helpful
Can you check if creating Composite Data Domains in your environment (in addition to running profiling for composite data domains) helps with your use case?
A composite data domain helps you define search patterns based on a combination of existing data domains or composite data domains.
Thanks for the reply! I fear that composite data domains are not going to help. But maybe I'm wrong!
My understanding is that a composite data domain is something like an entity (like a CEO) whose attributes are spread across multiple columns (one of which, presumably, would be "CEO Phone Number").
What we need is to determine that a single column includes CEO telephone numbers from cues in the data (and metadata). At least until we can get enough similarity profile information for CLAIRE to take over, I guess?
I think a reasonably good cue is that a) the data recommends an interpretation as a telephone number and b) the column indicates that it has something to do with a CEO (whence the needed conjunction). I'm not sure what data domains would make up the components from which a composite would be formed. E.g., I can see how "CEO Phone Number" makes up a part of a "CEO" entity, but I don't see which columns would make up parts of "CEO Phone Number". We're not trying to classify this column as a complex entity, but as a simple one.
Or is the suggestion that we have a data domain e.g. "CEO Relata" with the metadata rule and "Telephone Number" with the data rule and have "CEO Telephone Number" be the composite?
Sorry if I'm being dense; it's just that the examples of composite data domains from the documentation don't bear a lot of resemblance to this case.
In any case, again, thank you for the suggestion!
2 of 2 people found this helpful
there are some changes coming in v10.4.1 that will allow you to define rules at the domain level to control the data/metadata rules.
for each domain - you will be able to specify either of the following:-
- data overrides metadata (if there is a conflict)
- metadata overrides data (if there is a conflict)
- both metadata and data match
So you could create a new domain that matches on both metadata (CEO in the name) and data (looks like a phone number) and only when they both match, would the domain be associated.
This is exactly what we're after. Our plan is to move to 10.4.1 as soon as it's practical, so I guess this will be one further thing to look forward to.
As always, Amrita and Darren, I appreciate both of your insights and help!
What is the current tentative release date for 10.4.1?
i believe it will be later this week, - June 26th