Understanding Data dictionary

What the data dictionary is

The data dictionary is a collection of information about object types and their properties.
The information is stored in internal data types and made visible to users and applications through the process of publishing the data.

EMC Documentum Content Server Version 6.5 Fundamentals

The data dictionary is the mechanism you can use to localize Content Server. The data dictionary supports multiple locales. A data dictionary locale represents a specific geographic region or linguistic group.

Publishing the data dictionary

Data dictionary information is stored in repository objects that are not visible or available to users or applications. To make the data dictionary information available, it must be published. Publishing the data dictionary copies the information in the internal objects
into three kinds of visible objects:

  • dmi_dd_attr_info
    Contains the published data dictionary information for a property.
  • dmi_dd_common_info
    Contains the published data dictionary information that an object type and property have in common.
  • dmi_dd_type_info
    Contains the published data dictionary information for an object type.

For example, if a site has two locales, German and English installed, there will be two dd_type_info objects for each object type—one for the German locale and one for the English locale. Similarly, there will be two dd_attr_info objects for each property—one for the German locale and one for the English locale. However, there will be only one dd_common_info object for each object type and property because that object stores the information that is common across all locales.

Retrieving data dictionary information

You can retrieve data dictionary information using DQL queries or a DFC method. Using DQL lets you obtain multiple data dictionary values in one query. However, the queries are run against the current dmi_dd_type_info, dmi_dd_attr_info, and dmi_dd_common_info objects. Consequently, a DQL query may not return the most current data dictionary information if there are unpublished changes in the information.
Neither DQL or DFC queries return data dictionary information about new object types or added properties until that information is published, through an explicit publishDataDictionary method (in the IDfSession interface) or through the scheduled execution of the Data Dictionary Publisher job.

Compliance Services for Documentum

Comliance Services provide capabilities for retaining and managing content.

These services are:

  • Retention Policy Services
    Determines the length of time a object (document or folder) is retained. For the duration of its applied retention policy the managed object can’t be modified or deleted, although a new version of the object may be created.
  • Federated Records Services
    Managed the content and objects of external repositories with one master repository and created proxy objects for any external objects without importing all content and property information.
  • Records Manager
    The Records Manager inludes discrete modules. The customer can add additional modules that meets their unique requirements.
  • Trusted Content Services
    Enhanced security options on the Content Server like Digital Shredding and Encrypted file store storage areas.
  • Infromation Rights Management Services
    The IRM Policy Server extend the security and access controls on content beyond the repository.
  • Content Intelligence Services

CenterStage search features

 

Webtop Taskspace CenterStage
procentual no ranking up to three bullets

Searchranking Centerstage

Note: the most default columns are hidden to take the shot

Searchranking TaskSpace

Default view of TaskSpace 6.6. No columns hidden.

Searchranking Webtop

Screenshot was taken from the Documentum Webtop 6.6

 

 

 

 

 

 

eCTD Module 2

eCTD Module 2

Module 2 Summaries

The files in this module should be provided as PDF text with the exception of a few embedded images, when needed. The name of the folder for module 2 should be m2. The folders in module 2 should be named as follows.