Overview of Managing Types

Types, or schemas, define the shape of the data that makes up a content object. Types are associated at the repository level. The administrator can create types in BEA Systems repositories and third-party repositories that support this feature.

Type properties can be string, integer, Boolean, double, calendar, or binary. They can also be single unrestricted, single restricted, multiple unrestricted, or multiple restricted. The administrator gives each property a name. Settings for each property include required, read-only, and default values.

The administrator can set the property as explicit, storing the property in a horizontal format to limit the number of joins in content queries. Types do not have to include a binary, although a common example of a type is a single binary with a set of non-binary properties that describe the document.

Administrators can define default values for properties. To be used with Interaction Management, Content Nodes need a primary property that will be rendered as a result of an ad action.