Documentum content management foundations ebook




















Skip to content. Do you want to understand content management without having to dive into the underlying programming? This book provides a clear, unbiased overview of the entire CMS ecosystem—from platforms to implementations—in a language- and platform-agnostic manner for project managers, executives, and new developers alike.

Author Deane Barker, a CMS consultant with almost two decades of experience, helps you explore many different systems, technologies, and platforms. Learn what content is, how to compare different systems, and what the roles of a CMS team are Understand how a modern CMS models and aggregates content, coordinates workflow, and manages assets Explore the scope and structure of a CMS implementation project Learn the process and best practices for successfully running your CMS implementation Examine the practice of migrating web content, and learn how to work with an external CMS integrator.

Here you will find the most up-to-date information, analysis, background and everything you need to know. It reduces the risk of your technology, time and resources investment decisions by enabling you to compare your understanding of Web Content Management Systems WCMS with the objectivity of experienced professionals.

The 18 revised full papers presented were carefully reviewed and selected from 48 submissions. Create lists, bibliographies and reviews: or. Search WorldCat Find items in libraries near you. Advanced Search Find a Library. Your list has reached the maximum number of items. Please create a new list with a new name; move some items to a new or existing list; or delete some items.

Your request to send this item has been completed. APA 6th ed. Note: Citations are based on reference standards. However, formatting rules can vary widely between applications and fields of interest or study. The specific requirements or preferences of your reviewing publisher, classroom teacher, institution or organization should be applied. The E-mail Address es field is required. Please enter recipient e-mail address es. The E-mail Address es you entered is are not in a valid format.

Please re-enter recipient e-mail address es. You may send this item to up to five recipients. The name field is required. Please enter your name. The E-mail message field is required. Please enter the message. Please verify that you are not a robot. Would you also like to submit a review for this item?

You already recently rated this item. Your rating has been recorded. Write a review Rate this item: 1 2 3 4 5. Preview this item Preview this item. Content management systems utilize metadata extensively to provide sophisticated functionality. For example, metadata is essential for making documents searchable in terms of their author, title, subject, or keywords. It is hard to imagine any functionality of Documentum that does not utilize metadata in one form or another. The following figure shows two content items and their associated metadata:.

EMC Documentum uses the host file system by default to store the content and a database to manage metadata and its association with the content items. CAS provides a digital fingerprint for a stored content item. The fingerprint also known as an ID or logical address ensures that it is exactly the same item that was saved.

No duplicates are ever stored in CAS. A repository is a managed unit of content and metadata storage and includes areas on the file system and a database. However, the details of the organization of the files and metadata in a repository are hidden from the users and applications that need to interact with the repository.

The repository is managed and made available to the users and applications via standard interfaces by a Content Server process. These two terms are used interchangeably by the Documentum community. Content Server brings the stored content and metadata to life and manages its lifecycle. It exposes a known interface for using the content while hiding the details of how and where files and metadata are stored.

The term Content Server is used in two contexts — the Content Server software that is installed and resides on the file system and the Content Server instance , which is the running process that resides in memory and serves content at run time.

A Content Server instance is dedicated to and manages only one repository. However, we will see later in architecture discussion that multiple Content Server instances can be dedicated to the same repository. This is typically done for performance reasons where the multiple Content Server processes divide up the load for serving content from the same repository. The following figure shows two Content Servers serving one repository:. The Content Server uses an object-oriented model and stores everything as an object in the repository.

DQL can query objects and their relationships, in addition to any database tables registered to be queried using DQL. The default data dictionary can be altered by addition of user-defined object types and properties. Properties are also known as attributes and the two terms are used interchangeably to refer to metadata.

An individual document can be part of multiple virtual documents. The assembly of virtual documents can also be controlled by business rules and data stored in the repository. Collaborative features Documentum 5. Room: This is a secured area within a repository with defined membership and access restrictions.

Discussion: This is a comment thread associated with an object. Contextual folder: This is a folder with attached description and discussion. Note: This is simple document with built-in discussion and rich text content. A retention policy defines the phases through which such an object passes and how it is finally disposed of or exported. Workflows can be defined for documents, folders representing the contained documents , and virtual documents. A workflow definition acts like a template and multiple workflow instances can be created from one workflow definition.

For each stage, prerequisites can be defined and actions can be defined that are performed prior to an object's entry into that stage. The repository security can be turned off as well. The ACL provides object-level permissions to users and groups. When the repository security is enabled, the Content Server enforces seven levels of basic permissions and six levels of extended permissions.

There are additional privileges and security components, which are discussed in later chapters. Content Server provides robust accountability and capability via auditing and tracing facilities. A sign-off is a way of authorizing or approving a decision similar to signing off on paper. Documentum provides desktop and web-based client applications and supports creation of custom applications of either type.

The following figure shows several client applications:.



0コメント

  • 1000 / 1000