Tab navigation
- Architecture
- Data Model- selected tab,
Data Model
Content Manager V8 provides a powerful XML-ready, physical data model. The advanced model can capture structural and relationship information across all types of content and its associated metadata or attributes. It facilitates the integration of structured data with unstructured content.
The V8 data model, combined with OO APIs, allows faster development of new and more sophisticated applications with greater flexibility. Applications which exploit fully linked relationships and management of virtual or compound documents can be created.
| V8 Capabilities | Benefits |
|---|---|
|
V8.3 XML schema mapping utility dynamically maps an XML schema to an IBM Content Manager schema either automatically (including creating the new Content Manager schema) or manually through the use of the graphical XML schema mapping utility. |
Simplifies the process of defining XML schema and capturing XML documents. Once the mapping is generated, XML documents adhering to the mapped XML schema may be captured, shredded, stored, and managed in Content Manager automatically, with no human interaction. |
Multi-level hierarchical structures
|
These relationships help customer service personnel and applications quickly assemble the "customer" relationship and provide improved service. Example: a Policy Folder could have a master corporate account number and then sub account numbers representing life, property, and health relationship accounts. Users could access the master (parent) by knowing just the life sub account number (child). |
Full-text search on text-type metadata attributes or text content
|
Full text indexing helps users find the information they need with more intuitive and flexible searches. Normally a few indexes, such as account number or social security number, are predefined for a document. They are set up based on the current usability and search needs. When business needs change, users may want to search for items in a different way. Full text search solves this problem. It allows users to search all words within the document -- so users are not restricted to the predetermined indexes. Example: an insurance company stores claim forms indexed by policy, claim and account numbers. If the system is set up to full text index claim forms as they are stored. a knowledge worker in the claims area who wants to do an analysis on back injuries can search for the words "back injury" within all claim forms. For even more power, the knowledge worker can combine the power of full text indexing with normal indexing and constrain the search to a location or age group or occupation or any other relevant parameter. |
Granular support for resources in Content Manager V8 allows:
|
Resources can be re-used across multiple documents and applications. Customers will have better and easier object oriented APIs for integration with line of business applications. |
| Reference Attribute connects an item to any item of any type in the system. The purpose is to maintain referential integrity between items - preventing deletion of an item so long as another item references it. | Custom applications can build more complex inter-item relationships with full referential integrity. |
| Foreign keys allow the administrator to configure validation of attributes against a pre-defined set of values. | Validation against a pre-defined set of values can be achieved by building external tables and defining Foreign Keys instead of writing client or server exits. |
| XPath-based query language allows applications to easily navigate the hierarchical model and explore inter-item relationships. | Application development with APIs utilizes a user friendly (XML like) way to perform queries. |
| Direct SQL statements can manipulate structured metadata |
Flexible application development Improved performance for Line of Business applications. |
