Concepts
Links to the topics that contain information about Content Manager terminology, features, and tools.
- Object types
Content Manager stores content as modular objects, classified into types. You organize the objects to create your deliverables. - Metadata
Metadata is data about data; it is structured data which describes the characteristics of a resource. Metadata that is commonly associated with an object is the name of the author, date that the object was last revised, the object's status, version, and so on. Content Manager uses the metadata to identify objects, facilitate searching, and enable publication planners to specify the version of an object that is to be used in a publication. - Metadata hierarchy
To enable version and language management, Content Manager stores metadata at different levels for each object in the repository. This facilitates maximum reuse while allowing publication owners to specify which content is used in a specific publication. - Version management
When you check in a topic, library topic, map, or image to the repository, Content Manager automatically creates a new revision of the object but not a new version. When needed, you must explicitly create new versions of an object. - Translation management
Content Manager helps translation coordinators by minimizing the content that needs to be translated, determining the target languages following the reuse relationships, and by applying In-Context Perfect Matching. - Users and groups
Permissions to objects in the repository is based on user groups and roles, and the relationship between them and the objects in the repository. - Folders
All content in the Content Manager repository is stored in folders. When creating a folder, you define the type of content that it can contain. Content Manager does not use the location of an XML object for addressing or linking so the folders are for your convenience only for organizing, storing, and locating objects. - User and security
User access control policies provide secure access to the Content Manager repository and all the objects it contains. User roles and groups define access to objects in the repository. - Understanding Conditional Text
Conditional text refers to text or graphics to which a condition attribute setting has been applied. Condition settings can be used to specify whether specific content is to be hidden or shown when generating publication output. - Variables
Variables are placeholders inside your XML documents which are replaced by a text string or graphic at publishing time. - Search
Search the whole repository, metadata and content, based on criteria that you specify in the search window. - Publishing
In Content Manager, the publication is an object that is used to generate documentation in a particular output format such as PDF or Eclipse Help. A publication includes a map with references to the objects (maps and topics) to be included, and associated resources (variable library topics). The publication also manages the versions of the topics referenced by the map and used for output. Additionally, you can set conditions for the publication to produce customized output for a specific, target audience or situation. - Content Editor
Content Editor is a powerful web-based application that provides a rich and user-friendly XML editing tool. - Server roles
An overview of the different server roles which can be recognized within a Content Manager installation - Best practices for creating a Trisoft InfoShare BackgroundTask service with a specific role
The topic described how to create a Trisoft InfoShare BackgroundTask service with a specific role - Background task component
Background task is an application logic that is triggered on certain events, does not require user interaction and runs in a background by a background task service. Typical example is publishing process: it has to be triggered by user, but after it is triggered, it does not require user input neither does it require user to wait. Instead, the publishing process runs in a background, and user can know that it is finished by periodically checking the status of a publication. - Mandatory and optional fields
Typically a field is accessible in two user interfaces (website and client tools) and through the WebServices API. - Overview of the extension configuration
The extension configuration contains all information needed to configure extension plugins that can be used for metadata binding and search query enhancement.