To modify business glossary content outside of the business
glossary itself, business glossary administrators can import from
and export to a CSV (comma-separated values) file.
You can import business glossary content from a CSV file that has
been generated from another software application such as a spreadsheet
program. Or, you can import from a CSV file that you originally exported
from InfoSphere® Business Glossary and
then edited to contain the business glossary content that you want
to import.
CSV file content
With the CSV file format,
you can define categories, terms, information governance policies,
information governance rules, links to stewards, and the values of
custom attributes of categories and terms. You cannot define custom
attribute definitions or relationships. You can change the values
of most, but not all, term and category properties. See Import and export file formats for a list
of the properties that you can change by using a CSV file.
The
CSV file that you import must be in formatted in the same way as shown
in the CSV sample file. You can download the sample file from the
import wizard.
You should be aware of the following
points before you use the CSV import and export capability:
- If you import terms and categories that already exist in the business
glossary, the imported terms and categories replace the existing ones.
- If you import the values of custom attributes, the definitions
of those custom attributes must already exist in the target metadata
repository.
- You cannot assign relationships other than those among categories,
subcategories, and terms. For example, you cannot specify synonyms
or assign assets to terms.
- Names of categories and terms can contain any character, but cannot
begin or end with a leading blank space. Names can consist of several
words separated by spaces. Names can be up to 255 characters.
- The character encoding format (UTF-8 or a particular locale) of
the imported file is not changed by the import process.
- If the file was originally created by exporting business glossary
content to a CSV file, then the IBM InfoSphere Information Server that
hosts the business glossary into which the CSV file is imported must
be set to the same locale that was in effect for the instance of InfoSphere Information Server from
which the CSV file was originally created.
Considerations when exporting to a CSV file
You
should be aware of the following points before you export to a CSV
file.
- A parent category that contains subcategories
can be exported only if all of its subcategories are exported.
- If you are importing from the IBM InfoSphere Business Glossary import
wizard:
- You can choose between UTF-8 and locale encoding (UTF-8 is the
default). Use UTF-8 encoding unless you plan to open the resulting
CSV file with an application that does not support UTF-8, such as
Microsoft Excel. If you plan to open the file with an application
that does not support UTF-8, select Automatic coding -
according to server locale for the export format. If
you choose this option, make sure that the client computer that is
running the application that you use to open the exported CSV file
is set to the same locale setting as that of the computer that is
hosting InfoSphere Information Server.
If the locale settings do not match, the file could appear to be
corrupted when you open it.
- You can select the Glossary check
box to export the entire business glossary.