Documentation Center

Creating the Contenta hierarchy

You organize the information in your Contenta database and Contenta Explorer in a hierarchy of Contenta objects.

With this hierarchy, you can do the following.
  • Create a hierarchy or hierarchies by product line.
  • Separate stable data from data undergoing revision.
  • Organize data for output to a publishing application.
  • Create separate data objects (MRUs—minimal revisable units) with text that appears in multiple publications.

The top level of a database or hierarchy in the Contenta Explorer is always the sysadmin desktop. All data in the Contenta Explorer hierarchy is created and exists on the sysadmin desktop. Within the database, the top level desktop is the Global desktop which is not seen in the Contenta Explorer—the sysadmin desktop exists on the Global desktop in the Contenta database.

The sysadmin desktop contains the following.

  • All data organized in a hierarchy or hierarchies comprised of containers, data, and

    compound and/or hybrid objects. You organize your data by building a hierarchy or hierarchies within the Contenta Explorer using Contenta objects. For example, you may have a Configuration object which contains a hierarchy for your data that is organized by product line. The configuration object may be the top level container and you may have other container objects under it, one for each product line.

  • User and ProjMan desktops

    User and ProjMan desktops are the means to grant users access to the Contenta database. Users can login to Contenta only if they have a desktop.

    A user may have access to one or more configurations, or may have access to specific branches of the configuration on their desktop. The sysadmin links copies of data in the configuration onto the desktops depending on the information the user needs to access. Note that the sysadmin has access to all user desktops.

  • Workpools

    If users work on data concurrently, (as opposed to working in a single stream of tasks) your sysadmin creates workpools. ContentRoutingProject or Project tasks can be assigned to a workpool whereby all users assigned to the workpool receive the Project or objects in the ContentRoutingProject at the same time.

    If users work on data concurrently, (as opposed to working in a single stream of tasks) your sysadmin creates workpools. ContentRoutingProject or Project tasks can be assigned to a workpool whereby all users assigned to the workpool receive the Project or objects in the ContentRoutingProject at the same time.