Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This topic describes the use of composite domains in Data Quality Services (DQS). Sometimes a single ___domain does not represent the data in a field satisfactorily, and you can represent the data only by grouping single domains. To do so, you create a composite ___domain. A composite ___domain consists of two or more single domains, and maps to a data field that consists of multiple related terms that are not parsed, but are included in a single composite value. Each term in the value will be represented by a different single ___domain. Once you have included single domains into composite domains, and then mapped the composite ___domain to the data field, you can build knowledge in the knowledge base about the data in that field by building knowledge in the single domains. A composite ___domain, like a single ___domain, is a semantic representation of the data in a single data field.
The single domains in a composite ___domain must have a common area of knowledge. An example is an address field that has street, city, state, country, and postal code data. The different terms in this field could have different data types. To handle that, you map those terms to different single domains. Another example is a full name field that has first name, middle name, and last name data. To use a composite ___domain, you have to be able to parse the data in the field into different single domains, creating a composite ___domain for the field and a single ___domain for part of the field.
Composite domains have different capabilities than single domains. You cannot change the values in the composite ___domain—you must do so in a single ___domain. With composite domains, you can use cross-___domain rules to test the values in the single domains of the composite ___domain. You can also view the value combinations that are found in the composite domains.
In This Section
Using a composite ___domain enables you to do the following:
Create a semantic representation for a data field that consists of multiple related terms that are not parsed |
|
When you are mapping complex data to a composite ___domain, you can parse the data based on knowledge, in addition to parsing on a delimiter. DQS will first attempt to use its knowledge about single domains to determine how parts of the complex string belong in single domains. |
|
Attach a reference data service, such as one handling address data, to a composite ___domain. |
|
Create a cross-___domain rule when the value of one ___domain in a composite ___domain affects the value of another. |
|
Identify value combinations so DQS can report their frequency. |
Related Tasks
Task Description |
Topic |
---|---|
Building a knowledge base by running knowledge discovery and interactively managing knowledge |
|
Importing knowledge into, or exporting it from, a knowledge base. |
|
Creating a single ___domain, and adding knowledge to the ___domain. |