Skip Headers
Oracle® Enterprise Data Quality for Product Data Knowledge Studio Reference Guide
Release 5.6.2

Part Number E23610-03
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

9 Export and Import Features

This chapter explains how to import and export data lenses, phrase and terminology rules, and Item Definitions.

Exporting a Data Lens

A data lens can be exported, which may be useful for archival and back up purposes.

To export a data lens, on the File menu, click Export Data Lens. Enter a descriptive filename for the data lens, and then click OK.

All exported data lenses are stored in the export directory, …\Application%Data\export.

Importing a Data Lens

An exported data lens can be imported for use.

To import a data lens, on the File menu, click Import Data Lens. Locate and double-click on the data lens to start the import process.

The Knowledge Studio checks to see if this data lens exists locally and if it does exist, you are prompted to rename the data lens to avoid overwriting files.


You must still check in the data lens to the Oracle DataLens Server in order to use it in applications.

Exporting Rules

Lens rules can be exported to a text file; this output is useful for reviewing the rules and comparing the existing rule set to prior rule sets.

You can check out a version of the data lens, create a text file, and then check out a prior version of the same data lens. Next, using any tool that allows a comparison to be generated, you can compare the differences between the files. This functionality is used if maintenance has been performed to a data lens and the results were not as expected.

Rules can be exported for an entire data lens or by Domain.

The rules are exported to the default export directory, …\data lens name\Application Data\DataLens\export, or you can specify the path and file name.


Exporting data lens rules is not the opposite of import rules; exported rules are not in a format that can then be imported. For assistance on importing exported rules, contact Oracle Consulting Services.

Importing Phrases and Terms

Knowledge that may exist within your organization can be used as part of the knowledge building of terms, phrases and standardizations for creating and enriching data lenses. This information can be imported into a data lens from an Excel spreadsheet with the use of the Import Phrases and Terms feature.

The format of the Excel spreadsheet or tab-delimited file (CSV or text) can be of your choosing. For example, you could include columns that indicate a phrase, a term for the phrase, and the initial data.

The following examples illustrate how you might create the columns and populate your spreadsheet files:

Surrounding text describes imptidef2.jpg.
Surrounding text describes imptidef1.jpg.

There are two columns you can use to create term variants as follows:


Allows for the import of the full-form variant of the term rule.


Allows for the option of creating term variants.


The fullform and handling columns must be located in your spreadsheet after any text or regex columns and before any standardization columns.

The values that can be used in the fullform and handling columns are as follows:


Automatically creates term variants of the text node.


Automatically creates term variants and plural forms.

No or a blank cell

Does not create any term variants; term remains unchanged.

Surrounding text describes imptidef.jpg.

In addition, standardization rules can be imported within the same spreadsheet. the standardization types are Full Description and Short Description.


Prior to importing rules within certain standardization, the standardization type must present in the data lens.

To import your new knowledge into your data lens:

  1. From File menu, click Import Phrases and Terms.

  2. Browse to the import spreadsheet and click Open.

The rules are imported into the data lens. The percentage of recognition increases with the addition of these newly imported rules.

Creating Aliases When Importing Rules and Phrases Using Excel

You can create aliases when you import rules and phrases using Excel. There is no 'Alias' column in the Excel spreadsheet so aliases are created automatically based upon the name of the attribute or Item Definition. The Knowledge Studio assumes that the labels you provide in the spreadsheet are aliases, modifying them as needed to create attribute names that abide by the required conventions (for example, changing spaces to underscores in the attribute name).

These alias names can be edited or viewed. For more information, see "Aliases".

Exporting and Importing Item Definitions

Importing and exporting Item Definitions from one data lens to another allows you to reuse Item Definition information in new ways.

You can easily export Item Definitions from one data lens and import them into another data lens. You can use this feature to import single Item Definitions or entire branches of an Item Definition hierarchy into a new or existing data lens.

When you import an Item Definition, all rules that participate in the Item Definition are also imported.

  1. Open the source data lens.

    This is the data lens that contains the Item Definition (or hierarchy of Item Definitions) you want to export out of the source data lens and import in your target data lens.

  2. To maximize reuse of knowledge contained in the source data lens, verify that all Smart Glossaries relevant to the Item Definition and all unit conversion knowledge you want to import are contained in the target data lens.

    If you need to import a Smart Glossaries, see "Importing a Smart Glossary".

  3. Select the Phrases tab and the Define Items sub-tab.

  4. Right-click the Item Definition branch that you want to export, and click Export Item Definition.

  5. Enter a name for the export file or accept the default filename, and then click Save to save the exported Item Definition(s).

  6. Open the destination data lens.

  7. Select the Phrases tab and the Define Items sub-tab,

  8. Right-click the parent branch into which you would like to import the Item Definition and click Import Item Definition.

  9. Select the export file you saved, and then click Open to import the Item Definition.

    The Item Definitions and all rules associated with the Item Definitions are imported into your destination data lens.

Troubleshooting Item Definition Export and Import

This section describes some possible issues you may encounter and how to resolve them.

Pre-existing Item Definitions with Same Name as Import

You cannot import an Item Definition that already exists in the target data lens and attempts to do so result in an informational message advising you that it is not possible.

This is best resolved by renaming the Item Definition.

Source Item Definition Relies on Knowledge Contained in an Smart Glossary

If you have exported an Item Definition that relies upon a Smart Glossary (for example, for unit conversion of units of measure), be sure you import the Smart Glossary into the target data lens before you import the Item Definition. If not, you may need to re-create some knowledge in the target lens.

Source Item Definition Relies on Standardization Information

Be sure to create all standardization types needed for the target Item Definition when you import the Item Definition into the target data lens. Standardization information is not preserved when you import an Item Definition.

Source Item Definition Relies on Unit Conversion Information

Be sure to create all unit conversion knowledge in the target data lens when you import any Item Definitions that require unit conversion. Unit conversion information is not preserved when you import an Item Definition.

Source Item Definition Relies on Value Logic Information

Attribute value logic is preserved after the import, provided the target data lens has the requisite unit conversion information. In most cases, unit conversion information is contained in Smart Glossaries, such as DLS_Units_of_Measure or DLS_Units_of_Measure_Retail, so importing the appropriate Smart Glossaries into the target data lens avoids this issue.

Search logic used by attributes of the imported Item Definition is preserved in the import.