Classifications Administration Guide

OpenText™ Content Server

Select the object types that can be classified, import or export

classification taxonomies, and enable Intelligent Classification
to help automate the process of classifying objects.

LLESCLS230100-AGD-EN-01
Classifications Administration Guide
OpenText™ Content Server
LLESCLS230100-AGD-EN-01
Rev.: 2022-Nov-15
This documentation has been created for OpenText™ Content Server CE 23.1.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com

Copyright © 2022 Open Text. All Rights Reserved.

Trademarks owned by Open Text.

One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
 Table of Contents
1 Classifications ........................................................................... 5

LLESCLS230100-AGD-EN-01 OpenText™ Content Server iii

Chapter 1
Classifications

Classifications adds taxonomic Classification capabilities to Content Server,

providing an alternative way to organize, manage, and browse items. You can
classify items, such as Documents, Compound Documents, Text Documents, and
Folders. When items are classified, users can browse Classification Trees in addition
to the traditional Content Server folder hierarchy.

For example, if the items in your Enterprise Workspace are organized according to
departments such as Human Resources and Marketing, adding Classifications lets
you organize these items in the Classification Workspace according to other criteria
(such as date, subject, and item type), in addition to the departments.

Classifications are created by Administrators. Classifications are assigned to items

by Administrators and users who have sufficient permissions. If you have enabled
Intelligent Classification functionality, Classifications can also be suggested or
assigned automatically. For these assisted and automatic Classifications, you must
construct a Classification profile that defines the criteria that is used when Intelligent
Classification functionality suggests or assigns Classifications for items.

This section describes the following tasks:

• Enabling Intelligent Classification, which allows automatic or assisted

Classification of items, based on generated key phrases.
• Configuring Classifications, which allows you to set a Classification's
accessibility, and configure the storage provider rules.
• Configuring the classification profile, which includes adding Exemplar
Documents (documents used to generate key phrases) for assisted or automatic
Classifications, and constructing the Profile Query.
• Classifying items, which includes configuring managed objects (classifiable
Content Server items), setting the management type, and managing pending
objects.
• Exporting and importing Classification taxonomies, which includes exporting
Classifications to an XML file, importing Classifications from other Content
Server installations, and constructing an XML taxonomy.
• Performing maintenance, which allows you to adjust module features and keep
the system running smoothly.
• Using Content Server's XML Export API feature with Classifications, which
allows you to export Classification information in XML format.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 5

Chapter 1 Classifications

For more information about using Classifications (for example, classifying items and
searching Classifications), see OpenText Content Server - Classifications User Guide
(LLESCLS-UGD).

1.1 Creating Classifications and Classification Trees

Classification is the systematic grouping of knowledge or items, or application of
taxonomy, based on a specific set of criteria. Classifications categorizes Content
Server items (for example, Documents, Compound Documents, Text Documents,
and Folders) into a taxonomy of Classifications called Classification Trees.

Note: Although Classifications does not suggest or build taxonomies for you, it
allows you to import and export the XML taxonomy definitions that you
provide. For more information, see “Classification Taxonomies” on page 29.

There are three approaches you can use to create Classifications and Classification
Trees in Content Server:

• Manually add them in the Classifications Workspace. For more information, see
“Adding Classifications” on page 6.
• Construct and import an XML Taxonomy. For more information, see
“Constructing an XML Taxonomy” on page 29.
• Export an existing Classifications Taxonomy from another Content Server. For
more information, see “Classification Taxonomies” on page 29.

1.1.1 Adding Classifications

To add items to the Classification Workspace, you must have the Object Creation
privilege and See and Edit permissions. For more information about permissions,
see OpenText Extended ECM - Get Started User Guide (LLESRT-UGD).

The following types of items can be added to the Classification Workspace:

• Classification Trees, which contain hierarchies of Classifications or RM

Classifications and are stored at the base level of the Classification Workspace.
• Classifications, which are stored within Classification Trees or other
Classifications.
• RM Classifications, which are stored at the base level of the Classification
Workspace, within Classification Trees or other RM Classifications.
• Classification Shortcuts, which are Shortcuts to Classification Trees or
Classifications and are stored within Classification Trees and Classifications.

If Intelligent Classification is enabled, you must set the management type for a
Classification for managed objects such as Documents, Compound Documents, Text
Documents, and Folders. There are three management types:

6 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.2. Configuring Classifications Options

• Manual, which means that the system will not automatically assign the
Classification to an item. Only administrators and users with the appropriate
permissions will be able to assign this Classification.
• Assisted, which means that the system will suggest this Classification for items
that satisfy the Classification's Profile and place them on the Manage Pending
Objects page (Tools > Content Server Administration > Classifications Administration).
There they can be accepted or rejected by Content Server Administrators and
users with the appropriate permissions.
• Automatic, which means that the system will automatically assign this
Classification to items that satisfy the Classification's Profile.

Note: RM Classifications do not support the Assisted management type.

You must also decide if you want the Classification to be selectable by users.

For more information on manually creating Classifications in Content Server, see

OpenText Content Server - Classifications User Guide (LLESCLS-UGD).

1.2 Configuring Classifications Options

There are several Classifications settings that you can configure to control
permissions and the application of Classifications. You can specify the users and
groups that have permissions to create Classifications, Classification Trees, and
Shortcuts to Classifications. You can also specify which Item types can be classified,
and add additional item types as classifiable. You can also modify various other
opentext.ini file settings to specify how Content Server works with
Classifications. For more information about Classifications opentext.ini settings,
see “opentext.ini File Settings for Classifications” on page 17

1.2.1 Configuring Classifications Object and Usage Privileges

To manage which users can create Classifications and which users can apply or
remove Classifications for a Collection, you can configure both Object Privileges and
Usage Privileges.

To specify which users can create Classifications, Classifications Trees, or

Classification Shortcuts, configure Object Privileges on the Administer Object
Privileges administration page. For example, if there is a specific user who is the
Classifications Librarian, you can restrict the ability to create Classifications and
Classification Trees to only that user to better control the Classifications available in
your environment.

“Classifications Object Privileges” on page 8 lists the Classifications Object

Privileges that you can modify and the default restrictions, if any.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 7

Chapter 1 Classifications

Table 1-1: Classifications Object Privileges

Object Privilege Default Restrictions

Classification Restricted to Content Server Admin account
and the Business Administrators Group.
Classification Tree Restricted to Content Server Admin account
and the Business Administrators Group.
RM Classification Unrestricted
Classification Shortcut Unrestricted

For more information on how to configure object privileges, see OpenText Content
Server - Content Server Administration Guide (LLESWBA-AGD).

To specify which users can apply or remove Classifications for a Collection,

configure Usage Privileges on the Administer Usage Privileges administration
page. You can control the Usage Privileges Apply Classifications and Remove
Classifications for the Usage Type Collections Command on the page. This allows
you to restrict which users can see the Apply Classifications or Remove
Classifications menu options in the More Actions drop-down list in a Collection. By
default, these settings are Unrestricted.

For more information on how to configure usage privileges, see OpenText Content
Server - Content Server Administration Guide (LLESWBA-AGD)

1.2.2 Configuring Item Types as Classifiable

Item types that can be classified are called managed objects. You can configure four
default item types in Content Server as managed objects:

• Compound Documents

• Documents

• Text Documents

• Folders

For example, if you make the Documents item type a managed object, Content Server
users can manually classify Documents, or you can configure Content Server to
automatically classify or suggest Classifications for Documents using the Intelligent
Classifications functionality. For more information about automatic and assisted
Classifications, see “Adding Classifications” on page 6.

If you want to allow additional Content Server item types to be configurable as

managed objects (for example, URLs or Projects), you do so by adding the item type
to the Managed Objects administration page. For more information, see OpenText
Content Server - Records Management Administration Guide (LLESRCM-AGD).

8 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.3. Configuring the Classifications Widget for Smart View

1.2.3 To Configure RM Classified Objects

To configure RM classified objects:

1. In the Classifications Administration section of the Content Server

Administration page, click the Managed Objects link.

2. Clear or select the Managed check box for any of the following object types:

• Compound Document
• Document
• Folder
• Text Document

3. Click Save Changes.

1.3 Configuring the Classifications Widget for Smart

View
The Classifications widget provides a workspace in Smart View where you can add,
edit, and view Classifications.

• For information about configuring widgets using Edit Page mode in Smart View,
see the Help available in Smart View.
• For information about configuring widgets using the Perspective Manager tool,
see the Help available in the Perspective Manager.
• For information about the Classifications widget, see OpenText Content Server -
Widget Configuration Guide (CSAV-CWG).

1.4 Enabling Intelligent Classification Functionality

The Intelligent Classification functionality allows you to create assisted and automatic
Classifications that help to automate the process of classifying items. For each of
these Classification types, you construct a profile that defines the criteria that its
items must meet. Then, for each new item that meets the criteria, Content Server
either suggests the Classification to be assigned or automatically assigns the
Classification to the item. For more information about assisted and automatic
Classifications, see “Adding Classifications” on page 6.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 9

Chapter 1 Classifications

1.4.1 To Enable the Intelligent Classification Functionality

To enable the Intelligent Classification functionality:

1. In the Classification Administration section of the Content Server

Administration page, click the Configure Intelligent Classification
Functionality link.

2. On the Configure Intelligent Classification Functionality page, select the

Enable Intelligent Classification check box.

3. Click Save Changes.

1.5 Configuring the Classification Profile for

Intelligent Classifications
When using Intelligent Classification functionality for Classifications with a
management type of assisted or automatic, you must define and set a profile. In this
profile, you specify the criteria that items must meet to be assigned the
Classification. For each profile, the system examines every item that is added or
modified (provided that the item's type is a managed object). It then determines if
the item meets the profile's criteria for the corresponding Classification. If the item
fits the profile for a Classification, the system does one of the following:

• If the Classification's management type is assisted, the system suggests the

Classification for the item on the Manage Pending Objects page. The
Classification can then be accepted, rejected, or left as pending.
• If the Classification's management type is automatic, the system automatically
assigns the Classification to the item.

Note: You cannot set a profile for a Classification whose management type is
manual.

For more information about managed objects, see “Configuring Item Types as
Classifiable” on page 8. For more information about accepting or rejecting system-
suggested Classifications for items, see “Maintaining Classifications” on page 15.
For more information about setting a Classifications management type, see OpenText
Content Server - Classifications User Guide (LLESCLS-UGD).

Profile Tab
If the management type is assisted or automatic, the Profile tab will be visible when
you view a Classification's Properties page, and you will be able to:

• Set the relevance score threshold.

• Add and remove Exemplar Documents.
• See the key phrases that are generated.

10 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.5. Configuring the Classification Profile for Intelligent Classifications

Each of these criteria are used to determine if a managed object meets the
Classification's profile and to determine if it should be automatically classified or if
the Classification should be suggested.

Setting the Relevance Score Threshold

The relevance score threshold determines how closely a document must satisfy your
profile parameters. The higher the threshold, the more exact the match must be. The
value must be from 1 to 100. The default value is 40.

Note: You must click the Construct Profile Query button on the Profile tab,
and the Save as Profile button on the Search page, before a change to the
relevance score threshold takes effect.

Adding Exemplar Documents to the Profile

If you already have one or more documents or emails that exemplify a Classification,
you can quickly define a Classification profile by adding these documents or emails
to the profile as Exemplar Documents. Content Server then determines and displays
the Exemplar Document's key phrases (recurring words and word combinations,
especially those involving unusual words). These phrases are used to determine if
items satisfy the profile.

Once you add the Exemplar Documents, you must construct the Profile Query to
store the key phrases in the profile. A Profile Query is a set of search criteria that
defines the parameters for automatic and assisted Classifications.

When an Exemplar Document is added to a Classification profile, Content Server

automatically adds key phrases from the Document to the Profile Query Search
page. Additionally, the location of the Exemplar Document is shown in the Location
column on the Profile tab.

Note: Content Server can extract key phrases from only the latest major version
of an Exemplar Document that contains both major and minor versions.
Although you can add Documents without a major version as Exemplar
Documents, these documents cannot contribute key phrases to the
Classification profile.

Constructing the Profile Query

You can construct the Profile Query using the Content Server Search page. Any
information that is searchable in Content Server can be configured as criteria for
Intelligent Classifications. Managed objects that meet the criteria specified in the
Profile Query, and that satisfy the relevance score threshold specified in the
Classifications profile, are either assigned the Classification or the Classification is
suggested, depending on the management type for the Classification. By default, the
Classification Profile Query page opens with additional fields in the Full Text
section. These fields allow you to:

• Specify key phrases.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 11

Chapter 1 Classifications

• Edit key phrases from Exemplar Documents to change the automatically

extracted phrases.
• Edit key phrases from a complex query of an imported Classification taxonomy.

Each section is labeled with instructional text.

Note: You can edit the key phrases in the fields for Exemplar Documents and
complex queries from imported Classification taxonomies; however, Content
Server will not save your edits.

1.5.1 To Define the Relevance Score Threshold

To define a Relevance Score Threshold for a Classification profile:

1. In the Classifications Workspace, click a Classification or Classification Tree's

Functions menu, choose Properties, and then choose Profile.

2. Do one of the following:

• Click the Use Default radio button to use the default relevance score
threshold value.
• Click the Use Specific radio button to enter a custom value, and then type a
value from 1 to 100 in the input field.

1.5.2 To Add an Exemplar Document

To add an Exemplar Document:

1. In the Classifications Workspace, click the Functions menu of a Classification or

Classification Tree, choose Properties, and then choose Profile.

2. Click the Add Exemplar Document button.

3. On the Select Exemplar Document page, navigate to the document that you
want to add, and then click the associated Select link.

4. Repeat steps 2 and 3 for all Exemplar Documents that you want to add.

5. Click the Construct Profile Query button. For instructions on constructing the
Profile Query, see “To Construct the Profile Query” on page 13.

12 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.6. Classify Existing Content Using Intelligent Classification Functionality

1.5.3 To Construct the Profile Query

To construct the Profile Query:

1. In the Classification Workspace, click the Functions menu of a Classification or

Classification Tree, choose Properties, and then choose Profile.

2. Click the Construct Profile Query button.

3. On the Classification Profile Query page, do one of the following:

• In the first text field, type any user-defined phrases you want to use to
define the Classification.

• In the second text field, edit the Exemplar Document key phrases (if you
have used an Exemplar Document or Documents, and you want to edit the
automatically extracted key phrases).

• In the third text field, edit the key phrases from the imported Classification
complex query (if you have imported a Classification complex query, and
you want to edit the automatically extracted key phrases).

4. In the System Attributes section, specify the search criteria you want.

5. Click the Save as Profile button.

Note: You cannot add advanced options to the Classification Profile Query
page (for example, Natural Language Query and Scope). Content Server will
ignore these additional criteria. However, you may narrow the Profile Query
using the Categories, Browse Content Server, and XML Types links.

1.6 Classify Existing Content Using Intelligent

Classification Functionality
If you have configured assisted or automatic Classifications using the Intelligent
Classification functionality, you can use the Classify Existing Content functionality to
apply Classifications to existing content without re-extracting your entire Enterprise
content. For more information about assisted and automatic Classifications, see
“Adding Classifications” on page 6.

Note: The Indexing Processes (Update Distributors and Index Engines) of each
Enterprise Data Source must be running to receive and execute commands.

When you use the Classify Existing Content options, Content Server issues
Classification Profile Queries against all managed items, and then imports the
resulting IPools and processes the results, either assigning or recommending
Classifications.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 13

Chapter 1 Classifications

Important
Executing general Classification Profile Queries against large amounts of
content at one time may increase the load on the Import Agent, slowing the
server and the Classification process.

On the Set Auditing Interests page, you can specify which events are audited. You
can also view information about using the Classify Existing Content functionality on
all objects by selecting the appropriate criteria on the Query Audit Log page. For
information about the query audit log, see OpenText Content Server - Content Server
Administration Guide (LLESWBA-AGD).

1.6.1 To Classify Existing Content

To classify existing content:

1. In the Classifications Administration section of the Content Server

Administration page, click the Classify Existing Content link.

2. On the Classify Existing Content page, click Initiate.

3. Click Continue.
The processing of automatic and assisted Classifications will be completed with
the next scheduled Consumer Five Minute Agent execution.

1.7 Configuring Storage Rules for Classified Items

If you have flexible storage enabled, you can select an alternate storage location for
specified classified items by configuring storage provider rules.

When managed objects are added to Content Server, they are evaluated based on the
rule definition. You can create a complex expression for multiple Classifications
connected with And, Not, or Or modifiers. When using the storage provider rules,
Content Server evaluates the classified items in ascending order, and then stores the
items based on your specified criteria. For more information about flexible storage,
see OpenText Content Server - Content Server Administration Guide (LLESWBA-AGD).

1.7.1 To Configure Storage Rules

To configure storage rules:

1. In the Storage Provider Settings section of the Content Server Administration

page, click the Configure Storage Rules link.

2. On the Configure Storage Rules page, click the Add new rule before this one
icon.

3. On the Add New Rule page, click Node assigned classifications '?' in the Select
a Rule drop-down list.

4. Click one of the following in the Classify drop-down list:

14 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.8. Maintaining Classifications

• Browse Classifications
• My Favorites

5. In the Browse Classifications window, or the My Classification Favorites

window, click the Select link for the Classification you want to add to the
storage rule. Optionally, click the Modify link to add another Classification
using one of the modifiers.

6. Click the storage provider for the rule in the Logical Storage Provider drop-
down list.

7. Click Submit.

1.8 Maintaining Classifications

Maintaining Classifications includes tasks that you can perform and the settings that
you can change to perform maintenance on Classifications. These tasks and settings
allow you to adjust the way the module operates, so that your system runs as
smoothly as possible.

Maintenance tasks include regenerating the Classification Query File, removing or

reclassifying items associated with a Classification, managing objects pending
Classification, purging Classifications, purging the database of rejected
Classifications, and configuring the opentext.ini file settings for Classifications.

Regenerating the Classification Query File

The Classification Query File (queries.in) is a system file that stores all the Profile
Query information for assisted and automatic Classifications, and is located in the
<content_server_home>/config directory. If you have not enabled the Intelligent
Classification functionality, your system does not contain this file. For more
information, see “Enabling Intelligent Classification Functionality” on page 9. The
queries.in file is modified when either a Classification is updated within Content
Server using the Save as Profile button, or an assisted or automatic Classification
node is deleted.

In the following cases, you must regenerate the Classification Query File so that it
contains the latest Profile Query information:

• After you import a Classification Tree.

• After you change the management type of a Classification from manual to
assisted or automatic, provided that the Classification had previously been set to
assisted or automatic
• When instructed to do so by OpenText Customer Support.

Managing Pending Objects

When you add an item to Content Server, and the item's type is a managed object,
Content Server examines the item and determines whether it meets the criteria in the

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 15

Chapter 1 Classifications

profile of each assisted Classification. If the item fits the profile for an assisted
Classification, Content Server suggests the Classification for the item. You can either
accept or reject the Classification, or you can defer the decision by leaving the item's
status as pending.

Purging the Database of Rejected Classifications

Each time you reject a system-suggested Classification for an item, the system
records this information in the Content Server database so that it will not suggest the
Classification for the item later. However, if this data gets sufficiently large, it might
slow down your system.

By purging the database of rejected Classifications, you remove entries based on the
specified number of days that they have been in the database. The default value is 45
days. Entries that are 45 days and older are purged.

Note: If you purge entries from the Content Server database, Classifications
that have been rejected for objects might be automatically suggested again.

1.8.1 To Regenerate the Classification Query File

To regenerate the Classification Query File:

1. In the Classifications Administration section of the Content Server

Administration page, click the Regenerate Classification Query File link.

2. On the Regenerate Classification Query File page, click Regenerate Query File.

1.8.2 To Manage a Classification

To manage a Classification:

1. In the Classification Workspace, click the Functions menu for the Classification
Tree or Classification that you want to manage, and then choose Manage
Classification.

2. On the Classification Tree's or Classification's Manage page, do one of the

following:

• To remove items from the Classification, click Remove in the corresponding

Action drop-down lists. Then click Submit. Optionally, click the Set All
Action to Remove button, then click Submit.

• To reclassify items in this Classification, click Reclassify in the

corresponding Action drop-down lists, and then click Submit. Next, in the
Browse Classifications window, navigate to the Classification that you want
to assign to the items, and then click its Select link. Optionally, click the Set
All Action to Reclassify button, and then click Submit.

16 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.8. Maintaining Classifications

1.8.3 To Manage Pending Objects

To manage pending objects:

1. In the Classifications Administration section of the Content Server

Administration page, click the Manage Pending Objects link.

2. On the Manage Pending Objects page, do one of the following:

• To accept or reject the suggested Classifications for objects, click Accept or

Reject in the corresponding Status drop-down lists, and then click the
Submit Status Changes button.
• To accept the suggested Classifications for all objects, click the Set All Status
to Accept button, and then click the Submit Status Changes button.

Tip: You can leave an object's status as pending if you do not want to accept or
reject its suggested Classification. After you click the Submit Status Changes
button, the system displays either a list of pending objects that have not
already been displayed, or, if none remain, an empty list. To view pending
objects that have already been displayed, return to the Content Server
Administration page, and then click the Manage Pending Objects link.

1.8.4 To Purge the Database of Rejected Classifications

To purge the database of rejected Classifications:

1. In the Classifications Administration section of the Content Server

Administration page, click the Purge Rejected Classifications for Objects link.

2. On the Purge Rejected Classifications for Objects page, specify how many
days old the entries that you want to purge must be in the Days Old field.

3. Click the Purge button.

1.8.5 opentext.ini File Settings for Classifications

The opentext.ini file, which is located in the <content_server_home>/config
directory, is the main configuration file for Content Server. It also contains several
settings that affect the behavior of Classifications. Occasionally, it may be necessary
to change these settings by editing the opentext.ini file directly using the Content
Server SDK Builder or a text editing program.

For information about the opentext.ini file, see OpenText Content Server - Content
Server Administration Guide (LLESWBA-AGD).

The following settings can appear in the [Classification] section of the

opentext.ini file. Some of these settings do not appear by default. For the settings
that do not appear by default, Content Server assumes default values, as
documented in “Classifications opentext.ini Settings” on page 18.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 17

Chapter 1 Classifications

Table 1-2: Classifications opentext.ini Settings

Setting Values Description

AllowAppearances true or false. Controls whether
Appearances can be created
By default, this setting does in the Classifications
not appear in the Workspace. For more
opentext.ini file, which is information about
equivalent to Appearances, see OpenText
AllowAppearances=true. Content Server - Custom Views
and Appearances User Guide
(LLESAPP-UGD).
AllowCustomViews true or false. Controls whether Custom
Views can be created in the
By default, this setting does Classifications Workspace.
not appear in the For more information about
opentext.ini file, which is Custom Views, see OpenText
equivalent to Content Server - Custom Views
AllowCustomViews=true. and Appearances User Guide
(LLESAPP-UGD).
DisplayNum An integer between 100 and Specifies the maximum
2000. number of items that are
displayed when a user
By default, this setting does browses a Classification.
not appear in the
opentext.ini file, which is
equivalent to DisplayNum=
100.

Note: If you set an

integer that is less than
100 or greater than
2000, Content Server
assumes the default
value 100.

18 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.8. Maintaining Classifications

Setting Values Description

reextract true or false. When an item is added to
Content Server or modified
By default, this setting does in some way, Content Server
not appear in the extracts the item. This process
opentext.ini file, which is assigns metadata to the item,
equivalent to reextract= indexes the item so that it is
true. searchable, and if you are
using Intelligent
Note: Configuring the Classifications, the process
reextract setting to determines which assisted or
true can slow down automatic Classifications best
large Content Server match the item and then
installations. assigns or suggests those
Classifications. To make the
Classification data for each
item searchable, whenever a
Classification is assigned
without matching it to
assisted and automatic
Classifications again, Content
Server must automatically
reextract the item.

The reextract setting

determines whether Content
Server reextracts items after
they have been assigned a
Classification. If this value is
set to true, the Classification
data for each item is
searchable immediately after
it is assigned a Classification.
If this value is set to false,
the Classification data for
each item is not searchable
until the item is extracted
again.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 19

Chapter 1 Classifications

Setting Values Description

maxClassifications An integer between 1 and When an item is extracted,
20. the Intelligent Classification
functionality determines
By default, this setting does which assisted and automatic
not appear in the opentext.ini Classifications best match the
file, which is equivalent to item. The
maxClassifications=5. maxClassifications
setting identifies the
Important maximum number of
Do not change this Classifications that the
setting unless Intelligent Classification
instructed to do so by functionality assigns to or
OpenText Customer suggests for an item when it
Support. Higher values is extracted.
might slow down your
system, and lower
values might
negatively affect the
accuracy of the
Intelligent
Classification
functionality.
maxImportAgentObjects An integer value. When processing automatic
and assisted Classifications
The default value is 100. (Intelligent Classifications),
the
Note: A value of 0 maxImportAgentObjects
restricts all objects from setting defines the maximum
being classified. A number of Classification
value smaller than 0 IPool objects that can be
disables the parameter. processed during a single
Consumer Five Minute
Agent run.
maxLargeImportAgentObject An integer value. When processing automatic
s and assisted Classifications
The default value is 5. (Intelligent Classifications),
the
Note: A value of 0 maxLargeImportAgentOb
restricts all large jects defines the maximum
objects from being number of large Classification
classified. A value IPool objects that can be
smaller than 0 disables processed during a single
the parameter. Consumer Five Minute
Agent run.
The size of large
Classification IPool
objects is defined by
the
largeImportAgentO
bjectSizeKB
parameter.

20 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.8. Maintaining Classifications

Setting Values Description

largeImportAgentObjectSize An integer value. When processing automatic
KB and assisted Classifications
The default value is 4000. (Intelligent Classifications),
the
largeImportAgentObjec
tSizeKB setting defines the
size (in KB) to be used with
the
maxlargeImportAgentOb
jectSizeKB setting.
lowScoreThres An integer between 0 and When an item is extracted,
100. the Intelligent Classification
functionality compares the
By default, this setting does item to each assisted and
not appear in the opentext.ini automatic Classification and
file, which is equivalent to then determines relevance
lowScoreThres=40. scores that represent how
well the item satisfies each of
Note: After you change the Classification's profiles.
this setting, you must The lowScoreThres setting
restart Content Server identifies the minimum
and regenerate the relevance score necessary for
Classification Query the system to either suggest
File to apply the new the item for an assisted
setting to Classification or assign an
Classifications using automatic Classification to
the new default the item.
relevance score
threshold. For more
information about
regenerating the
Classification Query
File, see “Maintaining
Classifications”
on page 15.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 21

Chapter 1 Classifications

Setting Values Description

siblingCompressRatio An integer between 0 and When an item is extracted,
100. the Intelligent Classification
functionality may determine
By default, this setting does that several assisted and
not appear in the automatic Classifications
opentext.ini file, which is within the same parent
equivalent to Classification match the item.
siblingCompressRatio= The
75. siblingCompressRatio
setting determines the
Note: If you set an percentage of Classifications
integer that is less than within a parent Classification
0 or greater than 100, that must match the item
Content Server before the parent
assumes the default Classification is assigned to
value. the item instead.

For example, if
siblingCompressRatio is
set to 75, lowScoreThres is
set to 40, and three of the
four assisted Classifications
within the automatic
Classification named Reports
match a document with
relevance scores greater than
or equal to 40, Content Server
assigns the Reports
Classification to the
document instead of the
three assisted Classifications.

22 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.8. Maintaining Classifications

Setting Values Description

RetainIntelClass true or false. Specifies whether all
previous automatic and
By default, this setting does assisted Classifications
not appear in the assigned to Content Server
opentext.ini file, which is items are retained when any
equivalent to new automatic and assisted
RetainIntelClass=true. Classifications are assigned.

If the value is set to true,

items retain their previous
automatic and assisted
Classifications and are
assigned new Classifications
as well; the previous
Classifications must be
removed manually.

If the value is set to false,

previous automatic and
assisted Classifications are
deleted, and items are
assigned new Classifications.
highScoreBypassThres An integer between 0 and Identifies the minimum
100. relevance score necessary for
an item to bypass the
By default, this setting does siblingCompressRatio
not appear in the setting.
opentext.ini file, which is
equivalent to For example, if
highScoreBypassThres= highScoreBypassThres is
70. set to 70,
siblingCompressRatio is
set to 75,
maxClassifications is
set to 5, and three of the four
assisted Classifications
within the automatic
Classification named Reports
match a document with
relevance scores higher than
70, the parent Classification
is not assigned to the item.
Instead, Content Server ranks
the three assisted
Classifications along with
other highly relevant
Classifications, and then
assigns the five most relevant
Classifications to the item.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 23

Chapter 1 Classifications

Setting Values Description

bulkOperations true or false. Enables the multiselect
functionality for classified
By default, this setting does items. Setting this parameter
not appear in the to true allows users to select
opentext.ini file, which is more than one Content
equivalent to Server item to copy, move,
bulkOperations=false. delete, (or collect, if enabled).

The multiselect functionality

does not have any
Classifications-specific
features; therefore, the
commands are applied
directly to the Content Server
item and not the
Classification.

24 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.8. Maintaining Classifications

Setting Values Description

bulkClassDisplayNum An integer greater than or Identifies the maximum
equal to 1. number of Classifications
that can be displayed for an
By default, this setting does item on the following pages
not appear in the in Content Server:
opentext.ini file, which is
equivalent to • Classify Search Results
page when the page is
bulkClassDisplayNum=2.
displaying Classifications
that are assigned to one or
more items. You use this
page when you classify
items from the Search
Result page.
• Classify Collection Items
page when the page is
displaying Classifications
that are assigned to one or
more items. You use this
page when you classify
items in a Collection.

If the
bulkClassDisplayNum
setting is set to a number of
Classifications that is less
than the number that is
assigned to an item, a view
all link is displayed.
Clicking this link displays all
Classifications that are
assigned to the item. If
assigned Classifications are
displayed for multiple items,
you can click a link at the top
of the page to show all
Classifications assigned to all
items.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 25

Chapter 1 Classifications

Setting Values Description

inheritedClassDisplayNum An integer greater than or Identifies the maximum
equal to 0. number of Classifications
that can be displayed on an
By default, this setting does item's Add page when the
not appear in the item is inheriting
opentext.ini file, which is Classifications. An item
equivalent to inherits Classifications when
inheritedClassDisplay you add it to a container that
Num=4. is classified.

For example, when you add a

Document to a Folder with
the Classification Confidential,
the Document inherits that
Classification. If the
inheritedClassDisplay
Num setting is set to a number
of Classifications that is less
than the number that the
item is inheriting, a view
all link is displayed.
Clicking this link displays all
Classifications that the item
is inheriting.

26 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.8. Maintaining Classifications

Setting Values Description

maxPathDisplayLen An integer greater than 2. Identifies the maximum
number of characters that can
By default, this setting does be displayed in the path that
not appear in the represents a hierarchy of
opentext.ini file, which is Classifications on the
equivalent to following pages in Content
maxPathDisplayLen=70. Server:
• An item's Add page when
the item is inheriting
Classifications. An item
inherits Classifications
when you add it to a
container that is
classified.
• Classify Search Results
page when the page is
displaying Classifications
that are assigned to one or
more items. You use this
page when you classify
items from the Search
Result page.
• Classify Collection Items
page when the page is
displaying Classifications
that are assigned to one or
more items. You use this
page when you classify
items in a Collection.

The hierarchy of the

inherited Classifications is
displayed as a horizontal
path in the following format:
Confidential:Presenta
tions:FinancialResult
s, and so on.

If you configure the

maxPathDisplayLensettin
g to a number of characters
that is less than the number
of characters in a
Classification hierarchy path,
the path is truncated to the
number of characters that
you specify. Characters in the
middle of the path are the
characters that are not
displayed, and are
represented with an ellipsis
(...).

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 27

Chapter 1 Classifications

Setting Values Description

searchResultPathLinks true or false. Controls whether an
alternate, non-hyperlinked,
By default, this setting does colon-delimited path is
not appear in the displayed. This option is
opentext.ini file, which is enabled by setting the
equivalent to searchResultPathLinks
searchResultPathLinks parameter to false.
=true.
By default, the paths display
as a sequence of hyperlinked
locations from the root of the
Classification Tree to the
Classification itself.
AssignRemoveClassification • PSee – users have see Users must have permissions
Perm permissions. to assign or remove
• PSeeContents – users Classifications on the object.
have see content The permissions required to
permission. perform these operations are
set by this parameter.
• PModify – users have
modify permissions
(default is set to
PModify).
• PEditAttributes –
users have edit attribute
permissions.
• PDelete – users have
delete permissions.
• PEditPerms – users
have edit permissions.

By default, this setting does

not appear in the
opentext.ini file, which is
equivalent to
AssignRemoveClassific
ationPerm=PModify.
applyDownBlockSize An integer greater than 1. Sub-items are processed in
blocks of set sizes. This
By default, this setting does parameter allows you to
not appear in the adjust the number of items
opentext.ini file, which is processed in each request.
equivalent to
applyDownBlockSize=50.

28 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.9. Classification Taxonomies

1.9 Classification Taxonomies

You export and import Classification Taxonomies when you want to copy a hierarchy
of Classifications (Classification Trees or Classifications and all the Classifications
that they contain) from one Content Server installation to another, or within an
Content Server installation. For example, if you have a Classification Tree named
Marketing Documents, which contains many Classifications, and you want to set up
an identical hierarchy of Classifications on another Content Server installation, you
would export and import the Classification Tree.

You can export and import the entire Classification Workspace, a Classification Tree,
or a Classification. When you export the Classification Workspace, all Classification
Trees and Classifications in the Workspace are exported. When you export a
Classification, it becomes a Classification Tree when imported. For example, if you
have a Classification named Project Schedules that is currently stored in the Product
Development Classification Tree, you can export the Project Schedules Classification
and import it into another Content Server installation. In this case, the Product
Schedules Classification is imported as a Classification Tree.

If you want to construct a hierarchy of Classifications without having to add each

Classification to the Classification Workspace individually, you can write an XML
file that defines a hierarchy of Classifications (an XML Classification Taxonomy), and
then import it.

Note: If you have not enabled the Intelligent Classification functionality, when
you import any Classification Trees, the management type is set to manual and
any associated profiles are disabled. For more information about enabling
Intelligent Classifications, see “Enabling Intelligent Classification
Functionality” on page 9.

1.9.1 Constructing an XML Taxonomy

If you want to construct a hierarchy of Classifications without having to add each
Classification to the Classification Workspace individually, you can write an XML
file that defines a hierarchy of Classifications (an XML Classification Taxonomy),
and then import it.

XML Classification Taxonomies are composed of a series of XML tags that define a
hierarchy of Classifications, including the names of all the Classifications and their
profile information.

Note: When you construct an XML Classification taxonomy manually, its

structure, tags, and values must meet certain requirements to import properly
into Content Server. The order of the metadata elements must be respected or
the Taxonomy Import will generate an XML DTD error. The order of the
metadata elements is defined in the DTD, which is generated on first use of
import/export.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 29

Chapter 1 Classifications

Header Section
The first part of an XML Classification taxonomy is a header section that defines the
XML file and the Classification Tree in general. This section begins with the
following XML declaration, which defines the XML version and the character
encoding used in the file:

<?xml version="1.0" encoding="UTF-8"?>

Next, the Classification Tree must be defined with the importexport start tag:

<importexport applanguage='USA' appname='ContentServer'

appversion='16.2.0' dtdversion='10.0' exportdate='<date_and_time>'>

“Attributes of the importexport Start Tag” on page 30 describes the attributes of

the importexport start tag:

Table 1-3: Attributes of the importexport Start Tag

Attribute Value
applanguage The language of the application, for example,
USA.
appname The name of the application, for example,
Content Server. This is a required
attribute.
appversion The version number of the application, for
example, 16.2.0. This is a required
attribute.
dtdversion The version number of the DTD that defines
XML Classification taxonomies.
exportdate The date and time that the Classification Tree
was exported from Content Server. The
format of this attribute is <yyyy>-<mm>-
<dd>T<hh>:<nn>:<ss> (for example,
2018-04-12T21:31:48), where:
<yyyy> is the year,
<mm> is the month,
<dd> is the day,
<hh> is the hour,
<nn> is the number of minutes,
and <ss> is the number of seconds.
This attribute is optional. When you
construct an XML Classification taxonomy
manually, you do not need to include this
attribute.

Classification Hierarchy Section

The second part of an XML Classification taxonomy defines the hierarchy of
Classifications and their settings. This section occurs between the start and end tags

30 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.9. Classification Taxonomies

of the importexport element, and consists of one or more classificationtree

elements that contain one or more classification elements.

The classification elements define Classifications as follows:

<classification managementtype='<type>' name='<name>'

selectable='<boolean>' subtype='<n>'><query>SELECT "OTObject" ,
"OTScore" WHERE "test" ORDEREDBY RankingExpression "test"</query></
classification>

Note: <n> in subtype='<n>' represents a valid subtype number.

“The classificationtree, classification, and query Tags” on page 31 describes the

classificationtree, classification, and query tags:

Table 1-4: The classificationtree, classification, and query Tags

Tag Description
classificationtree Defines a list of Classifications. Its attributes
contain settings for the list of Classifications.
classification Defines a Classification. Its attributes contain
all of the Classification's settings.
query Defines the Profile Query for a Classification
when it has been exported from Content
Server. Do not enter a value in this field.

“Attributes of the classificationtree and classification Tags” on page 31 describes

the attributes of the classificationtree and classification start tags:

Note: When defining the Classification Tree or Classification name attribute,

you cannot use the colon (:) character.

Table 1-5: Attributes of the classificationtree and classification Tags

Attribute Value
managementtype The management type of the Classification
Tree or Classification. Valid values are
manual, automatic, and assisted.
name The name of the Classification Tree or
Classification. This value is a string (for
example, Annual Reports).
selectable Whether or not the Classification Tree or
Classification is selectable. Valid values are
true and false.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 31

Chapter 1 Classifications

Attribute Value
subtype The subtype number of the Content Server
object. Valid values are 196 for the
Classification Tree tags and 199 for the
Classification tags.

“Optional Attributes of the classificationtree and classification Tags” on page 32

describes the optional attributes of the classificationtree and classification
start tags:

Table 1-6: Optional Attributes of the classificationtree and classification Tags

Attribute Value
score The number entered by the user. Valid
values are 1-100 (inclusive).
description The node description entered by the user.

In this section, the hierarchy of Classifications is defined by embedding

classification elements within other classification elements. For example, if a
Classification named Classification1 contains another Classification named
Classification2, then Classification2 would be embedded within Classification1 as
follows:
<classification managementtype='manual' name='Classification1'
selectable='true' subtype='199'>

<classification managementtype='manual' name='Classification2'

selectable='true' subtype='199'>

</classification>

</classification>

The following are rules regarding how the hierarchy is defined:

1. At the root level of the hierarchy, there can be no more than one
classificationtree element.
2. Each classificationtree and classification element can contain other
classification elements.

Note: A query element is optional in each classification and

classificationtree.

At the end of this section, you must include the end tag </classificationtree>
for the classificationtree element .

RM Classification Metadata Elements

RM Classifications require additional elements that define their metadata. These
elements appear between the start and end tags of the RMClassification element.

32 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.9. Classification Taxonomies

Table 1-7: RM Classification Metadata Elements

Tag Description
query This tag defines the profile query for a
classification when it has been exported from
Content Server. Do not enter a value in this
field.
rsi This tag identifies the RSI that is assigned to
the RM Classification. If the RM
Classification does not require an RSI, this
tag need not appear. The RSI cannot exceed
20 characters. This tag is optional.
filenumber This tag identifies the unique file number
assigned to the RM Classification. If a tree of
RM classifications is being created, the full
file number is the concatenation of all the file
numbers up the XML tree. The full file
number cannot exceed 64 characters,
including file number separators.
Furthermore, the File Number must be
unique at any given level. This tag is
required.
filestatus This tag identifies the status of the RM
Classification. This value cannot exceed three
characters and must exist in the Status table
in the Table Maintenance area of the Records
Management Workspace. This tag is
required.
createdate This tag identifies the creation date of the
RM Classification. This value must be of the
form yyyymmdd, where yyyy is the four-digit
year, mm is the two-digit month, and dd is
the two-digit day. This tag is required.
filestatusdate This tag identifies the status date of the RM
Classification. This value must be of the form
yyyymmdd, where yyyy is the four-digit
year, mm is the two-digit month, and dd is
the two-digit day. This tag is required.
essential This tag identifies the Essential code
assigned to the RM Classification. This value
cannot exceed three characters and must
exist in the Essential Record table in the
Table Maintenance area of the Records
Management Workspace. This tag is
required.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 33

Chapter 1 Classifications

Tag Description
storage This tag identifies the Storage Medium code
assigned to the RM Classification. This value
cannot exceed three characters and must
exist in the Storage Medium table in the
Table Maintenance are of the Records
Management Workspace. This tag is
required.
keywords An optional set of keywords that can be
assigned to an RM Classification. This value
cannot exceed 65K characters in MSSQL
Server and 2000 characters in Oracle. This tag
is optional.
subject An optional subject that can be assigned to
an RM Classification. This value cannot
exceed 65K characters in MSSQL Server and
2000 characters in Oracle. This tag is
optional.
dispauthority An optional Disposition Authority that can
be assigned to an RM Classification. This
value cannot exceed 64 characters. This tag is
optional.
cycleperiod The optional update cycle period of the RM
Classification. Valid values are 1, 2, 3, and 12,
which identify the number of months
between review periods of RM Classified
objects. If the Essential code for the RM
Classification is identified as a Vital Record
Code (see the Records Management
administration pages), this tag must be
populated with one of the valid values. This
tag is optional.
closedflag The optional closed flag indicator. Valid
values are 0 and 1. 1 indicates that the RM
Classification is Closed, while a 0 indicates
that the RM Classification is not closed. A
closed RM Classification cannot be assigned
to Content Server objects. If the RM
Classification is closed, this tag must be
populated with a value of 1. This tag is
optional.

Example Files
The following example is an empty Classification Tree named Test Classification
Tree. It is selectable and its management type is set to automatic:
<?xml version="1.0" encoding="ISO-8859-1"?>

34 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.9. Classification Taxonomies

<importexport applanguage='USA' appname='ContentServer'

appversion='16.2.0' dtdversion='10.0'
exportdate='2018-07-22T17:34:07'>

<classificationtree managementtype="automatic" name="Test

Classification Tree" selectable="true" subtype='196'>

<query>SELECT "OTObject" ,"OTScore" WHERE "test" ORDEREDBY

RankingExpression "test"</query>

</classificationtree>

</importexport>

The following example is a more typical Classification Tree. The name of the tree is
Corporate Information, and it contains three Classifications: About Us, Annual
Reports, and News. Inside News, there are two further Classifications: Press Releases
and Newsletters. At the root level, Corporate Information is non-selectable and its
management type is set to manual, while all the Classifications it contains are
selectable with their management types set to assisted.
<?xml version="1.0" encoding="ISO-8859-1"?>

<importexport dtdversion='10.0' appname='ContentServer'

appversion='16.2.0' applanguage='USA'>

<classificationtree managementtype='manual' name='Corporate

Information' selectable='false' subtype='196'>

<query></query>

<classification managementtype='assisted' name='About Us'

selectable='true' subtype='199'>

<query></query>

</classification>

<classification managementtype='assisted' name='Annual Reports'

selectable='true' subtype='199'>

<query></query>

</classification>

<classification managementtype='assisted' name='News'

selectable='true' subtype='199'>

<query></query>

<classification managementtype='assisted' name='Press

Releases' selectable='true' subtype='199'>

<query></query>

</classification>

<classification managementtype='assisted' name='Newsletters'

selectable='true' subtype='199'>

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 35

Chapter 1 Classifications

<query></query>

</classification>

</classification>

</classificationtree>

</importexport>

1.9.2 Importing and Exporting XML Taxonomies

Once you have created an XML Taxonomy, you can import the XML file to Content
Server and the Classifications are created automatically. See “Classification
Taxonomies” on page 29.

Note: If you have not enabled the Intelligent Classification functionality, when
you import any Classification Trees, the management type is set to manual. For
more information on Intelligent Classification, see “Enabling Intelligent
Classification Functionality” on page 9.

Exporting Classification Taxonomies

When you export the Classification Workspace or any of its contents, Content Server
writes information to an XML file. The XML file contains all the information that
defines the Classification Trees and Classifications, and the hierarchy of
Classifications that they may contain (for example, the names and management
types of each Classification). The system then stores this XML file in the temp
directory of your Content Server installation (for example, <content_server_home>/
temp) and uploads it to the My Workspace of the user who performs the export.

Note: Depending on system activity, the XML file containing each exported
Classification Tree and the Classifications might not appear in the My
Workspace immediately.

Importing Classification Taxonomies

When you import a Classification taxonomy to the Classification Workspace,
Content Server reads from an XML file all the information that defines the
Classification Tree (or Trees) and the hierarchy of Classifications that it contains.
When you begin the import process, the system builds that hierarchy of
Classifications in the Classification Workspace.

When you import a Classification taxonomy, you can also apply Categories. The
Categories are applied to all new Classification Trees and the Classifications created
by the import process. By default, when specify the import settings, any Categories
that have been applied to the Classifications Volume will appear in the Categories
field.

You can remove these Categories, add additional Categories, or change the
Categories to be applied to the imported Classifications. For more information on

36 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.9. Classification Taxonomies

Categories, see OpenText Content Server - Categories and Attributes User Guide
(LLESWAT-UGD).

After a Classification Tree has been imported, you can enable its assisted and
automatic Classifications by regenerating the Classification Query File. For more
information, see “Maintaining Classifications” on page 15.

Note: Depending on system activity, each Classification Tree and the

Classifications that you import might not appear in the Classification
Workspace immediately. If you import a Classification Tree with a large
number of Classifications (greater than 1000), and the import fails before it is
complete, you can delete the Classification Tree.

To Export a Classification Taxonomy

To export a Classification taxonomy:

1. In the Classifications Administration section of the Content Server

Administration page, click the Taxonomy Export link.

2. On the Taxonomy Export page, click in the Browse Content Server button, and
then do one of the following:

• Click the Select link for the Classification Workspace to export all
Classification Trees in the Classification Workspace.
• Navigate to a Classification Tree or Classification, and then click its Select
link.

3. Type a name for the XML file in the Export File Name field (for example,
classtree.xml).

4. Click Export.

5. On the Taxonomy Export page, click OK when the export process is complete.

Note: If you click the OK button before the export process is complete, you
will return to the Content Server Administration page and the export process
continues to run in the background.

To Import a Classification Taxonomy

To import a Classification Taxonomy:

1. In the Classifications Administration section of the Content Server

Administration page, click the Taxonomy Import link.

2. On the Taxonomy Import page, do one of the following:

• To select an XML file that is stored in your computer's file system, click the
Browse button, navigate to the XML file that contains each Classification
Tree that you want to import, and then double-click its name.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 37

Chapter 1 Classifications

• To select an XML file that is stored in Content Server, click the Browse
Content Server button, navigate to the XML file that contains each
Classification Tree that you want to import, and then click its Select link.

3. Click the level of error messaging you want to apply from the Alert Level drop-
down list:

• Severe Error, which notifies the recipient of critical system errors.

• Error, which notifies the recipient of general system errors.
• Warning, which notifies the recipient of non-critical errors in the system.
• Information, which notifies the recipient of general status and other system
information.
• None, which is the default.

For more information about error messaging, see OpenText Content Server -
Search Administration Guide (LLESWBS-AGD).

4. Optional Click the Edit button in the Categories area to apply or change the
Categories to be applied to the Classification Tree and its Classifications.

5. Click Import.

6. On the Taxonomy Import page, click OK when the import process is complete.

Note: If Categories have been applied to the Classification volume, these

Categories will appear by default in the Categories filed.

1.10 Using the XML Export API with Classifications

The Content Server XML Export API feature enables the information associated with
an Content Server volume or object to be translated into XML code and exported as
a file that can be used by another application, such as a data archive. When
Classifications is installed, you can use the XML Export API to export, in XML
format, the information associated with Classifications; for example, the
Classification hierarchies in the Classification Workspace and Content Server items
that have Classifications assigned to them. The XML Export API gives you control
over the structure of the XML files that Content Server generates, and allows you to
create custom skins for the Classifications interface. For more information about
Content Server's XML Export API, see the OpenText Content Server - XML Import and
Export Guide (LLESCOR-PGD), which is available on OpenText My Support.

You perform an XML export by adding parameters to the end of the basic Content
Server URL in a Web browser. An example of an XML export URL is:
http://<content_server_URL>?func=ll&objId=<[DataID]>&objAction=xmlexport&<optionalparame
, where:

• <content_server_URL> represents the URL prefix of the Content Server server,

38 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.10. Using the XML Export API with Classifications

• <[DataID]> represents the Content Server ID of the object to be exported

(Classification Workspace, Classification Tree, Classification, Document, Folder,
and so on),
• and &<optional parameters> represents parameters that control the content of
the resulting XML file.

The XML export query always starts with &xmlexport. Multiple parameters can be
added and are connected with an ampersand (&).

You can use any of the standard XML Export API optional parameters when you use
the XML Export API with Classifications. You can also use other parameters that are
specific to Classifications. The tables below provide information about some
standard XML Export API optional parameters (scope and callbackhandlername)
and the parameters that are specific to Classifications (xmlclassifieditems and
xmlclassificationstatus). For more information about other standard XML
Export API optional parameters, see the OpenText Content Server - XML Import and
Export Guide (LLESCOR-PGD).

“Optional Parameters” on page 39 lists some optional parameters that you can use
in an XML export.

Note: When you use the XML Export API, you must have the See and See
Contents permissions for a Classification object (Classification Workspace,
Classification Tree, or Classification) to be exported and all subitems within the
object. In addition, you must have the System Administration Rights privilege to
set certain optional parameters. “Optional Parameters” on page 39 below also
outlines which optional parameters require this privilege.

Table 1-8: Optional Parameters

Parameter Description Values

scope= Exports the child • base: exports the object
Classifications of a given only.
Classification object • sub: exports the object
(Classification Workspace, and all its children.
Classification Tree, or
Classification) according to
• one: exports the object
and its immediate
the specified child level.
children.
• <n>, where <n>
represents an integer
greater than 0: exports the
object and its immediate
children up to <n> levels
below the object. 1 for one
level below, 2 for two
levels below, and so on.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 39

Chapter 1 Classifications

Parameter Description Values

xmlclassifieditems= Exports the classified items of • true: exports all
a specific status that belong classified items that are
to a Classification Tree or visible in the interface; in
Classification. other words, with
“accepted” status.
Note: You must have • accepted: exports the
the System classified items that are
Administration Rights visible in the interface.
privilege to specify the
• pending: exports the
following statuses: items that have been
pending, rejected, all. assigned Classifications,
but the items are not yet
visible in the interface.
• rejected: exports the
classified items that have
had their Classifications
removed.
• all: exports all classified
items regardless of their
status.
callbackhandlername= Name of the callback handler classifications
used. When you use the
classifications value
with the
callbackhandlername
parameter, any
Classifications that have been
assigned to classifiable
objects are appended to the
export of the objects
xmlclassificationstat Appends Classifications with • accepted: exports the
us= a specific status that have Classifications that are
been assigned to classifiable visible in the interface.
objects to the export of the • pending: exports the
objects. Classifications that have
been assigned to objects,
Note: You must have but the items are not yet
the System visible in the interface.
Administration Rights
• rejected: exports the
privilege to specify the Classifications that have
following statuses: been removed from
pending, rejected, all. objects.
• all: exports
Classifications regardless
of their status.

You can combine optional parameters to make an XML export more specific. “XML
Export Examples” on page 41 below provides examples of URLs containing
optional parameters that you can combine.

40 Classifications Administration Guide LLESCLS230100-AGD-EN-01

 1.10. Using the XML Export API with Classifications

Note: If you combine optional parameters and Content Server returns

unexpected results, contact OpenText Customer Support.

Table 1-9: XML Export Examples

URL Description
<content_server_URL>?func=ll& Exports the contents of the Classification
objId=4962&objAction=xmlexport& Workspace object with object ID 4962 and all
scope=sub&xmlclassifieditems=true associated classified items with “accepted”
status
<content_server_URL>?func=ll& Exports a Classification with object ID 2040
objId=2040&objAction=xmlexport& and all associated classified items, regardless
scope=base&xmlclassifieditems=all of their status
<content_server_URL>?func=ll& Exports a Classification Tree with object ID
objId=2001&objAction=xmlexport& 2001, three levels of child Classifications in
scope=3&xmlclassifieditems= the Classification Tree, and classified items
pending with “pending” status
<content_server_URL>?func=ll& Appends to the export of the object with
objId=2245&objAction=xmlexport& object ID 2245 and its immediate children all
scope=one&callbackhandlername= Classifications with “accepted” status that
classifications& are assigned to the object and its children
xmlclassificationstatus=accepted
<content_server_URL>?func=ll& Appends to the export of the object with
objId=2401&objAction=xmlexport& object ID 2401 all Classifications that are
callbackhandlername= assigned to the object. Also appended to the
classifications& export are the classified items with
xmlclassifieditems=true “accepted” status that have been assigned
the Classifications that are assigned to the
object.

Note: In this type of example (when

the &callbackhandlername=
classifications&
xmlclassifieditems= parameters
are used together), only one level of
classified items of a Classification is
exported to prevent successive export
repetitions.
<content_server_URL>?func=ll& Exports the Classification with object ID 1365
objId=1365&objAction=xmlexport& and all its child Classifications, and
xmlclassifieditems=pending& associated classified items with “pending”
callbackhandlername= status. For each classified item, its
classifications& Classifications with “rejected” status are
xmlclassificationstatus=rejected exported.

LLESCLS230100-AGD-EN-01 OpenText™ Content Server 41