Data Domain Glossary in Informatica Developer
You manage data domains and data domain groups in the data domain glossary. You can add, edit, and remove data domains and data domain groups. You can also search for specific data domains and data domain groups.
You can export data domains from the data domain glossary to an XML file. You can also import data domains from an XML file to the data domain glossary. You create a data domain group to organize data domains into specific groups such as Personal Health Information (PHI), Personally Identifiable Information (PII), or any other conceptual group that is relevant to the project. You can have a data domain in multiple data domain groups. For example, phone number can belong to both PII and PHI data domain groups.
Creating a Data Domain Group in Informatica Developer
You can add data domains to data domain groups for effective column data analysis.
1. Click Window > Preferences.
The Preferences dialog box appears.
2. In the Preferences dialog box, select Informatica > Data Domain Glossary.
The Developer tool displays a list of all data domains in the Data Domain Glossary panel.
3. In the Show field, select Data Domain Groups.
The Data Domain Glossary panel rearranges the data domain list based on data domain groups.
4. In the Data Domain Glossary panel, select Data Domain Groups.
5. Click Add.
The Data Domain Group dialog box appears.
6. Enter a name and description.
7. Click Next.
8. Click Choose to open the Select Data Domains dialog box.
9. Select the data domains you want to add to the data domain group and click OK.
The Developer tool lists the selected data domains in the Select Data Domains panel.
10. Click Finish.
The Developer tool adds the data domain group to the data domain glossary.
Creating a Data Domain in Informatica Developer
You can create data domains and add them to the data domain glossary. You can also add data domains to one or more data domain groups.
1. Click Window > Preferences.
The Preferences dialog box appears.
2. In the Preferences dialog box, select Informatica > Data Domain Glossary.
The Developer tool displays a list of all data domains in the Data Domain Glossary panel.
3. In the Data Domain Glossary panel, select Data Domains.
4. Click Add.
The Data Domain dialog box appears.
5. Enter a name and description.
6. Click Use data rule to discover data domains based on column data. You can also select Use column name rule to discover data domains based on column names in the data source.
The Browse button is enabled.
7. Click Browse to open the Select Location dialog box.
8. Select the appropriate rules and click OK.
When you create a data domain, the Developer tool copies rules and other dependent objects associated with the data domain to the data domain glossary. To edit a rule associated with a data domain, you must go to the original rule and make changes to it. You can then associate the modified rule to the data domain again.
The rules that you selected appear in the Data rule and Column name rule fields.
9. Click Next.
10. Click Choose to open the Select Data Domain Groups dialog box.
11. Select the data domain groups you want to include the data domain in and click OK.
The Developer tool displays the selected data domain groups in the Assign to Data Domain Groups pane.
12. Click Finish.
The Developer tool adds the data domain to the data domain glossary.
Creating a Data Domain from Profile Results in Informatica Developer
After you run a column profile, you can view the values and patterns of source data. You can then create a data domain from them.
1. Run a column profile to view its results.
2. Select the values or patterns based on which you want to create a data domain.
The values, patterns, and statistics appear in the Results view.
3. Right-click the values or patterns, and then select Send to > New Data Domain.
The Data Domain dialog box appears.
4. Enter the data domain name and an optional description.
The location is set to data domain glossary by default.
5. Click Finish.
The data domain gets added to the data domain glossary.
Find Data Domains in Informatica Developer
The data domain glossary displays all the data domains by default. You can search for specific data domains and data domain groups.
The Data Domain Glossary pane in the Preferences dialog box displays all the data domains and data domain groups. You can search for and view more information on data domains and data domain groups in the following ways:
- Search for data domains and data domain groups.
- Type in part of the data domain name or data domain group name in the field on top of the Data Domain Glossary panel. If you are in the Data Domain Groups View, the Developer tool lists the data domains that contain the search string in their names and the data domain groups associated with them. If you are in the Data Domain View, the Developer tool lists all the data domains that contain the search string in their names.
- View data domain groups and data domains within them.
- In the Show field, select Data Domain Groups.
- View all data domains.
- In the Show field, select Data Domains.
- View properties of a data domain.
- Click a data domain name to view its properties under the Data Domain Glossary panel. You can view the description and associated rules. To view the domain groups a data domain belongs to, click Show in data domain groups.
- View properties of a data domain group.
- Click a data domain group name to view its description under the Data Domain Glossary panel.
Importing Data Domains
You can import data domains from a source XML file into the data domain glossary in the Developer tool. You must verify that the file contains information on data domains that you need to import.
1. Open the data domain glossary.
2. Verify that Data Domains or Data Domain Groups is selected.
3. Click Import.
The Import dialog box appears.
4. In the File Name field, enter the XML file name from which you want to import data domains.
Click Browse to choose the file.
5. Click Next.
The Select Objects to Import pane appears where you can specify the source and target.
6. In the Source panel, select the data domains that you want to import.
Note: To select multiple data domains, hold the Shift key.
7. Click Auto Match to Target to move the data domains to the Target panel.
The Developer tool tries to match the descendents of the current source selection individually by name, type, and parent hierarchy in the target selection and adds the objects that match.
8. Click Resolution to specify how to handle duplicate objects.
You can rename the imported object, replace the existing object with the imported object, or reuse the existing object. The Developer tool renames all the duplicate objects by default.
9. Click Next.
The Developer tool summarizes the import settings for your review. You can specify additional import settings in the Additional Import Settings pane.
10. Click Finish.
Exporting Data Domains
You can export data domains and data domain rules from the data domain glossary in the Developer tool to an XML file.
1. Open the data domain glossary.
2. Verify that Data Domains or Data Domain Groups is selected.
3. Click Export.
The Export dialog box appears.
4. To export data domains, select Export Data Domains. Select Export Data Domain Rules to export data domain rules.
5. Click Next.
6. In the Export to file panel, select the data domains or data domain rules you want to export.
7. To export data domains, click Browse to choose the export file and its location. To export data domain rules to another project in the Model Repository Service, select Copy to projectand choose the project you want to copy the data domain rules to.
8. Click Next.
The Dependencies pane displays a list of the dependent objects.
9. Click Next.
The Content Export Settings pane appears. You can select associated reference tables for export.
10. Click Finish.
If you associate a rule that uses reference tables with a data domain, you may not be able to export the reference tables in the same Developer tool session that you use to create the data domain. After you click Export in the data domain glossary, disconnect from the Model Repository Service and connect again before you can import the rule that uses reference tables.