Bookshelf v7.7: Content Center Job Roles and Terms

Descriptions of Content Center job roles are in Table 58, and terms are defined in Table 59.

Table 58. Content Center Job Roles
Position	Responsibilities
Content Administrator	One or more people in your business who are authorized to administer content. These people need to understand your business requirements in order to know what types of content and content items need to be managed and the appropriate contributor and approver workflows. Depending on your business requirements, one or more of these people may also be responsible for selecting and possibly configuring the appropriate business components, content objects, and content types. Alternatively, this may be done by an application developer.
Content Contributor	A person in your business who is authorized to contribute content items. Examples are technical writers, Web designers, and graphic artists.
Content Approver	A person in your business who is authorized to approve content posted to your company's Web site. Examples are managers and your company's attorneys.

Table 59. Content Center Terms
Term	Definition
Content	The components of the application that are authored, as opposed to application code. Siebel applications recognize the following classes of content: Business rules, such as personalization rules and assignment rules Application content, such as product catalog, price lists, and product promotions Web content, such as Web templates and static Web pages, typically stored as HTML, XML, and image files Documentation, such as product data sheets, forms, and white papers Content Center provides content production services for three of the classes listed above: application content, Web content, and documentation, while content asset management only applies to Web content and documentation.
Content Asset	An instance of content managed within Content Center and stored in the content asset repository. Content assets are typically comprised of unstructured markups and can be related to other content assets. For example, an HTML content asset can link to other pages or reference images. For more information, see Content Asset Management.
Content Item	Represents a transaction (add, update, delete) stored and associated with a piece of content.
Content Object	Specifies the information that will be transferred from the staging environment to the production environment when the content is published. Each content object is composed of a business object and an integration object.
Content Project	A group of related content items. Grouping content items into projects makes it easier to manage changes that should be published simultaneously. Delete because this is defined on the first page.
Content Type	A set of business rules you define for handling content, including rules that apply to the approval workflow, contributors, approvers, and the application views your company uses to edit or preview content. Each content type is based on a content object, and is associated with an approval workflow and a group of contributors and approvers. The following are examples of content types authored in Siebel applications that can be managed through Content Center: Siebel Sales Catalog: catalog, categories, product, product line, and product literature Siebel Pricer: price list, pricing factor, rate list, and volume discount Siebel Marketing: offers (Web, phone, email, direct mail, newsletter), campaign, and marketing development fund Siebel Service: service solution, decision issue, resolution document, and SmartScript The term Content Type is also used to describe the file type (or filename extension) of a content asset.