Tuesday, March 3, 2015


This blog will discuss the documentum content managment for an approach to deal with the documentum EMC 10-110 certification exam.


ECM

Enterprise Content Management (ECM) is a formalized means of organizing and storing an
organization's documents, and other content, that relate to the organization's processes.
The term encompasses strategies, methods, and tools used throughout the lifecycle
of the content.

Content

Content is a kind of information(valuable data) stored as computer data files. It can be in any formats.
The best solution to protect content is to move them to the centralized content managment system.

Content Server manages the content in a repository.

Repository has three main elements

1.Content Server

2. Filestore( a place where content is stored)

3. Database ( metadata of the content is stored)

Everything stored in a repository is a object.


If  a content is added to the repository, Content Server parses the object metadata,  and it generates additional information about the object, and stores a content file into the file store. Once stored as an object in the repository, there are many ways that users can access and interact with the content.

Document Object

In a repository, Document is defined by the type dm_document which is a sub-type of dm_sysobject.

Content Object

Content Object is a way of representing the content in a repository.

It is connection between document object and the file actually stores the content. It is an object of type dmr_content.

Versioning

Folder and cabinet SysObject subtypes cannot be versioned.

Versioning is a process that creates the historical record of the document. Each time we check-in the document, Content server creates a new version of the object without overwriting the existing version. All the version stored as some hierarchy.i.e Version Tree. Each version has some version label.

To identify the document in version tree, i_chronicle_id is used. It contains the object id of the original version of the document. i.e root of the version tree.

If a document is the original object, the values of r_object_id and i_chronicle_id are the same

Version Branching

Branching occurs automatically when we check out and then check back in an older version of a document because the subsequent linear versions of the document already exist and the server cannot overwrite a previously existing version.