Taxonomy Repository Manager

Use

The taxonomy repository manager is used at runtime to generate the content of virtual folder hierarchies created by taxonomies. You need a taxonomy repository manager if you want to classify documents and access them based on their classification.

See also:

Taxonomies and Classification

Integration

The taxonomy repository manager uses a CM repository to store taxonomies, pertaining categories, and taxonomy-specific metadata persistently. In the standard delivery, the CM repository /taxdata is defined for this. This repository is empty initially. However, in contrast to other repository managers, the taxonomy repository manager does not store content persistently.

Prerequisites

The application property service is activated and registered for all repositories that contain documents to be classified. The categories assigned to a document in the classification process are stored as application properties.

Features

If taxonomies are maintained using an iView, the taxonomies and their category hierarchies are stored in the repository as a hierarchy of folders.

The type of taxonomy, and other settings, is stored as application-defined properties of the relevant taxonomy directory. This is why the application property service is registered with the taxonomy repository manager.

Taxonomy Repository Manager Parameters

Parameter	Required	Description
Data Repository Prefix	Yes	The prefix of the CM repository in which the taxonomy repository manager is integrated, for example, /taxdata.
Description	No	Description of the repository manager.
Prefix	Yes	The URI prefix for which the manager is registered. This specification is entered in the list in the root directory. The URIs of all resources managed by this repository manager have this prefix in common. This prefix is used to identify the repository manager that is responsible for a resource with a given URI. Note that the prefix must be entered with a forward slash.
Active	No	You can (de)activate the repository manager using the Active parameter.
Hide in Root Folder	No	Specifies whether the repository is listed in the root directory. If you activate this parameter, the repository is not listed in the root directory.
Send Events	No	Specifies whether the repository sends events when operations such as delete, and update content are performed on resources. The repository sends events if this parameter is activated. This is necessary in order to use services such as the subscription service. By default, this parameter is activated.
Property Search Manager	No	Selection of manager for property search.
Repository Services	No	Identifiers of the repository services you want to use for the taxonomy repository. In the standard delivery, the application property service and the subscription service are selected.
ACL Manager Cache	No	Cache identification for resource ACLs. This parameter is required if an ACL security manager is specified in the Security Managerparameter. The cache ca_rsrc_acl is preset in the standard delivery (see Caches ).
Security Manager	No	Selection of the security manager that controls access to repository content. If you want CM to perform an authorization check when resources are accessed, you need to specify a security manager. The AclSecurityManager is preset in the standard delivery.

Activities

A taxonomy repository manager is preconfigured in the standard delivery. Normally, you do not need to change its configuration.

To check or modify the configuration, choose Content Management → Repository Managers → Taxonomy Repository.