Importing document definitions

Before you import, you must decide whether to empty the target repository before importing. If you select not to empty the repository, you must decide whether to overwrite existing data in the target repository.

Cleaning the repository before importing

If you select to empty the repository before importing, all data is removed from the repository before data is imported from the zip file.

Overwriting data when importing

•	If you select to overwrite existing data, all rows are imported from the zip file. Existing rows in the repository are replaced by the corresponding rows imported from the zip file.

•	If you select not to overwrite existing data, only new rows are imported from the zip file.

Folder structure for imported document definitions and resources

When you import document definitions from a full export (see Exporting all document definitions) the folder structure for the document definitions and resources is maintained in the target repository. When you import separate document definitions (see Exporting individual document definitions) the document definitions and all related resources end up at root level in the target repository.

When importing data from an SP4 web content repository

If you have upgraded from SP4 to 5.6, and want to import data from the SP4 web content repository to the 5.6 web content repository, you are prompted to include a document types file. This document types file translates the SP4 representation of metadata used in texts (metadata name) to the correct 5.6 representation of the same metadata (metadata GUID).

The document types file must include all document types represented in the web content repository. To retrieve this file, you can do as follows:

1	Upgrade the Design Center Projects to 5.6.

2	Export and deploy the Projects.

Note:

If you are using the same global resource set for the document types in all your Projects, you only have to deploy one of the Projects to define the document types file.

3	In Control Center, right-click the application domain node and select Retrieve Document Types File. A file browser opens.

4	Specify the name and path of the document types xml and click Save.

To import document definitions

1	Click the Web content Repository category button. The Web content repository view is activated.

2	In the Import section, click Browse. A file browser opens.

3	Browse to the zip file to import and click Import. The import path is displayed in the Import from field.

4	Select whether to Empty the repository before importing, and whether to Overwrite existing matching data.

5	Click Import. Data is imported to the repository.

Log for import failures

Errors during the import are logged in import-failures.log. You will find this log in:

<user_home>\dbadmintool-files