Migration of the Document Library Structure

In V6R2013, the Document Library structure is enhanced to use the same classification capabilities as general and part libraries. Bookshelves and books have been replaces with Document Families. You can create a structure of Document Families and Sub Document Families as simple or complex as required to support your business processes.

The following topics are discussed:

Schema Changes

The migration schema changes existing schema to work in the updated Document Library structure

The migration script changes Bookshelf and Book types to Document Family types. It also combines the existing Name and Revision as the migrated object's Name. The migrated object uses the parent object's physical id as its Revision.

This table shows the changes made by the migration process for each type of migrated object:

Before Migration After Migration
Type Name Type Name
Bookshelf Fiction Document Family FictionA
Book Fairy Tales Document Family Fairy TalesA

The Has Bookshelves and Has Books relationships are migrated to the Subclass relationship; and the Has Documents relationship is migrated to the Classified Items relationship.

Bookshelves could be connected to more than one Document Library. When migrating, the process clones the bookshelf to maintain a one-to-one relationship between Document Library and Document Family. The migration script performs the same process for Books that have been added to multiple Bookshelves. Any documents added to a book are then connected to each of the cloned versions of that book, which are now Document Family objects.

For example, the structure exists prior to migration:



The migration process clones container objects, Bookshelves and Books, but it does not clone the end item (in this case, Generic Documents). This structure shows the migrated version of the above structure:



This charts also shows the migrated type and relationship names.

Log Files

The migration process generates log files that provide details you can use to debug and verify the migration.

This script creates these log files in the <IDSFILEPATH> directory (specified when you run the migration script):

  • migration.log lists all status, successes, and failures. It also includes debug information if you used the debug option.
  • convertedIds.txt lists the IDs that were successfully converted in each run. The IDs for subsequent runs are appended to the list.
  • filesStatus.csv lists the completion status (COMPLETE or FAILED) for each flat file, and the time taken in milliseconds for completed files.
  • unConvertedObjectIds_xx.csv lists the objects that could not be converted, where xx is a sequential number starting at 1. This file contains:
    • Run No: the migration run number
    • Object Id: the object ID of the failed object
    • Flat File Name: the name of the flat file that contains this object
    • Row No: the row in the flat file where this object is listed
    • Reason: the reason the migration failed for this object

    Each file contains up to 50,000 entries.