This article provides steps for setting up the data model for a DB2® Content Manager system. The new data model adds the flexibility to have hierarchal child components.
One of the big benefits of DB2 Content Manager Standard Edition is the newly defined data model. Previous releases had a flat data model centered on Index Classes defined by their attributes. The Index Class was used to define and store all items in the system. Documents, images, and other objects were stored as parts of the item defined by the Index Class. An item without parts was also used to represent folders. A subset of Index Class attributes could also be defined to limit user access to certain attributes. The new model continues many of these benefits, but adds the flexibility to have hierarchal child components. The Index Class is now an Item Type that can have child components. This article provides steps for setting up the data model for your DB2 Content Manager system.
Jack Boswell is a Advisory Software Engineer for the DB2 Content Manager Partner Enablement Group and has worked for IBM over 28 years. He has over 17 years of experience in Document Imaging Systems. His areas of expertise are Content Manger System Design, Implementations, Content Manager Multiplatform, Content Manager Standard Edition, and Image Products for iSeries. Jack has previously developed Education and Training courses on imaging and DB2 Content Manager.