CSV file format to import glossary assets

To modify glossary assets outside of the catalog, you can import from and export to a file that is in a comma-separated value (CSV) format.

You can import glossary assets from a CSV file that was generated from another software application such as a spreadsheet program. Or, you can import from a CSV file that you originally exported from IBM® InfoSphere® Information Governance Catalog. You can then edit the CSV export file to contain the glossary assets that you want to import.

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 attributes 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 formatted in the same way as shown in the CSV sample file. You can download the sample file from the Choose Import Format window of the Import wizard in the Administration tab.

Considerations when you import from a CSV file

Consider the following points before you import from a CSV file:
  • If you import terms and categories that exist, the imported terms and categories replace the existing ones.
  • If you import the values of custom attributes, those custom attributes must exist in the target catalog.
  • You cannot assign relationships other than to categories, subcategories, and terms. For example, you cannot specify synonyms or assign information 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 CSV file was created by exporting glossary assets, then the locale of the exporting IBM InfoSphere Information Server host and the importing host must be identical.
  • Assets imported by using a CSV file are case-sensitive. It means that for example Business Labels number and NUMBER are treated as two distinct labels, not one.

Considerations when you export to a CSV file

Consider 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 export from the Information Governance Catalog Export wizard, you can choose between UTF-8 and locale encoding.
    • UTF-8 encoding is the default option. Select this option if you plan to open the resulting CSV file with an application that supports UTF-8.
      Note: If you plan to open the file with Microsoft Excel, run the following command first:
      • Windows operating system: IS_install_path/ASBServer/bin/iisAdmin.bat -set -key com.ibm.iis.gov.vr.setting.addBomToCsv -value true
      • Linux® operating system: IS_install_path/ASBServer/bin/iisAdmin.sh -set -key com.ibm.iis.gov.vr.setting.addBomToCsv -value true
      The changes are applied within a minute. This command adds BOM (byte order mark) characters to the exported CSV files, so that applications like Microsoft Excel are able to display the content correctly.
    • If you plan to open the file with an application that does not support UTF-8, select Encoding same as 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 the computer that is hosting InfoSphere Information Server. If the locale settings do not match, the file might be corrupted when you open it.