Livelink ECM – Classifications

Troubleshooting and FAQs Guide

This guide provides assistance on using and understanding the

Livelink Classifications module.

LLESCLS040200-TGD-EN-1
Livelink ECM – Classifications
Troubleshooting and FAQs Guide
LLESCLS040200-TGD-EN-1
Rev.: 2009-Jan-22
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
E-mail: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com

Copyright © by Open Text Corporation

Open Text Corporation is the owner of the trademarks Open Text, The Content Experts, Great Minds Working Together,
Livelink, Livelink ECM, Livelink ECM-eDOCS, Livelink MeetingZone, MeetingZone, B2BScene, B2BScene.com, Client/Surfer,
Collaboration, Creative Desktop, Further Faster, Hyperinnovation, Internet Anywhere ,Livelink IRIMS, IRIMS, IXOS, Livelink
OnTime, OnTime, Livelink Remote Cache, Microstar, MyLivelink, O & Design, Odesta, Odesta Helix, Odesta Livelink, Open
Text Intranet, Open Text Web Index, Personality +, Putting Knowledge To Work, Techlib, The Hyperlinked Organization, The
Source For Business Knowledge, Worksmart, and World Of E among others. This list is not exhaustive.
ACKNOWLEDGEMENTS
SAP®, R/3® and SAP ArchiveLink® are registered trademarks of SAP AG.
Adobe® is a trademark of Adobe Systems Incorporated.
Lotus® and Lotus Notes® are registered trademarks of Lotus Development Corporation. Domino is a trademark of Lotus
Development Corporation.
Microsoft® and Microsoft SQL® are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Oracle® is a registered trademark of Oracle Corporation.
Netscape and the Netscape N and Ship's Wheel logos are registered trademarks of Netscape Communications Corporation in
the U.S. and other countries.
Firefox® is a registered trademark of the Mozilla Foundation.
Sentry Spelling-Checker Engine Copyright © 2000 Wintertree Software Inc.
WordNet 2.0 Copyright © 2003 by Princeton University. All rights reserved.
Outside In® Viewing Technology © 1992-2002 Stellent Chicago, Inc. All rights reserved. Outside In® HTML Export © 2002
Stellent Chicago, Inc. All rights reserved.
Portions of eDOCS DM are copyrighted by DataDirect Technologies, 1991-2002.
All other products or company names are used for identification purposes only, and are trademarks of their respective own-
ers. All rights reserved.
 Table of Contents

PRE Introduction .................................................................................5

i About Livelink ECM – Classifications....................................................... 5
ii About this document ................................................................................ 5
iii Contact information .................................................................................. 6

1 Overview ......................................................................................9
1.1 Understanding Taxonomies ..................................................................... 9
1.2 Understanding Livelink Classifications................................................... 11

2 Troubleshooting Livelink Classifications ...............................15

2.1 Troubleshooting the Installation ............................................................. 15
2.2 Troubleshooting Assisted or Automatic Classification ........................... 17

3 Frequently Asked Questions....................................................21

3.1 What is the difference between Livelink Classifications and Livelink
ECM – Classifications Professional? ..................................................... 22
3.2 How do I get a license key? ................................................................... 22
3.3 Does Livelink Classifications build taxonomies for me? ........................ 22
3.4 Where can I get a taxonomy? ................................................................ 22
3.5 How do I classify an existing index? ...................................................... 23
3.6 Are taxonomies created with Livelink Classifications 2.0 compatible
with later versions of Livelink Classifications? ....................................... 23
3.7 What are the rules for Classification inheritance? ................................. 23
3.8 What is the difference between automatic and assisted
classification?......................................................................................... 24
3.9 How long does it take to automatically classify a new item? ................. 24
3.10 How do I set up Enterprise Server so that I am notified when import
operations occur?................................................................................... 24
3.11 Why am I not receiving notifications of the success of an import? ........ 25
3.12 Is there a limit to the number of Classifications that I can add to a
Classifications Workspace? ................................................................... 25
3.13 Are there performance implications for exceeding the recommended
number of Classifications in the Classifications Workspace?................ 25
3.14 I have set up automatic Classifications. When new items are added
to Enterprise Server, how can I tell which items were classified and
which items were not? ........................................................................... 25

LLESCLS040200-TGD-EN-1 Livelink ECM – Classifications iii

Table of Contents

3.15 I have constructed a Profile Query based on categories and

attributes. Why is it not returning as many classified documents as I
expect?................................................................................................... 25
3.16 I have imported Classifications that include categories and attributes
to a new Enterprise Server system. Why do my Profile Queries yield
no results?.............................................................................................. 26
3.17 How can I have the Classifications assigned to a search result item
displayed on the Search Result page? .................................................. 27

iv Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

Preface
Introduction

i About Livelink ECM – Classifications

Livelink ECM – Classifications adds taxonomic classification capabilities to Livelink
ECM – Enterprise Server, providing an alternative way to organize, manage, and
browse Enterprise Server items. By classifying Enterprise Server items, such as
Documents, Compound Documents, Text Documents, and Folders, users can
browse Classification Trees in addition to the traditional Enterprise Server Folder
hierarchy.
The standard edition of Livelink Classifications provides manual classification or
categorization capabilities. Livelink ECM – Classifications Professional edition
provides Intelligent Classification functionality. Intelligent Classification provides
assisted and automatic classification capabilities, in addition to manual classification
capabilities, which help to automate the process of classifying items.

ii About this document

This document provides an in-depth analysis of the classification process, as well as
provides troubleshooting tips and frequently asked questions. This document
supplements the information in the Administering Classifications (LLESCLS-H-AGD).

ii.i Target readership

The information in this document is primarily intended for Enterprise Server
administrators. Some topics in this document may be useful to users designated as
Classification Librarians and other Enterprise Server users.

ii.ii Documentation conventions

Read the following conventions before you use this documentation.
Typography In general, this documentation uses the following typographical conventions:
• New terms
This format is used to introduce new terms, emphasize particular terms,
concepts, long product names, and to refer to other documentation.

LLESCLS040200-TGD-EN-1 Livelink ECM – Classifications v

Introduction

• User interface
This format is used for elements of the graphical user interface (GUI), such as
buttons, names of icons, menu items, names of dialog boxes, and fields.
• Filename, command, sample data
This format is used for file names, paths, URLs, and commands in the command
line. It is also used for example data, text to be entered in text boxes, and other
literals.
Note: If a guide provides command line examples, these examples may
contain special or hidden characters in the PDF version of the guide (for
technical reasons). To copy commands to your application or command
line, use the HTML version of the guide.
• Key names
Key names appear in ALL CAPS, for example:
Press CTRL+V.
• <Variable name>
The brackets < > are used to denote a variable or placeholder. Enter the correct
value for your situation, for example: Replace <server_name> with the name of
the relevant server, for example serv01.
Tip: Tips offer information that make your work more efficient or show
alternative ways of performing a task.
Note: Notes provide information that help you avoid problems.

Important
If this important information is ignored, major problems may be
encountered.

Caution
Cautions contain very important information that, if ignored, may cause
irreversible problems. Read this information carefully and follow all
instructions!

iii Contact information

Open Text Online is a single point of access for the product information provided by
Open Text. Depending on your role, you have access to different scopes of
information (see below for details).
You can access Open Text Online via the Internet at http://online.opentext.com/ or
the support sites at http://support.opentext.com/.
The following information and support sources can be accessed through Open Text
Online:

vi Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 Introduction

Knowledge Center
Open Text's corporate extranet and primary site for technical support. It is the
official source for:
• Open Text products and modules.
• Documentation for all Open Text products.
• Open Text Developer Network (OTDN): developer documentation and
programming samples for Open Text products.
• Patches for Open Text products.
The following role-specific information is available:
Partners
• Information on the Open Text Partner Program.
• Programs and support for registered partners.
Business Users
• Tips, help files, and further information from Open Text staff and other users
in one of the Open Text online communities
Administrators/developers
• Downloads and patches
• Documentation
• Product information
• Discussions
• Product previews
Feedback on If you have any comments, questions, or suggestions to improve our
documentation documentation, contact us by e-mail at documentation@opentext.com.

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide vii

Chapter 1
Overview
Classification is the systematic grouping of knowledge or items, or application of
taxonomy, based on a specific set of criteria. In Enterprise Server, this taxonomy is
based on search criteria that defines which Enterprise Server items are alike. The
goal of a taxonomic classification is to provide a single, logical location where
Enterprise Server users can find items of a single subject.
This chapter covers the following topics:
• “Understanding Taxonomies” on page 9
• “Understanding Livelink Classifications” on page 11

1.1 Understanding Taxonomies

Taxonomies provide an alternate view of the information in your Enterprise Server
repository and can therefore make it easier to navigate and search information.
When properly implemented, a well-defined corporate taxonomy increases
productivity by allowing Enterprise Server users to easily find the information they
need to complete tasks.
To simplify browsing, taxonomies are organized into tree structures. Broad
Classifications are located at the base of the tree with more specific Classifications
made available as you traverse the tree's branches. Figure 1-1 below provides a
sample taxonomy tree structure.

LLESCLS040200-TGD-EN-1 Livelink ECM – Classifications 9

Chapter 1 Overview

Figure 1-1: Sample Taxonomy

1.1.1 Creating Taxonomies

There are three accepted approaches to taxonomy creation: automatic, assisted, and
professional. The approach that you choose depends on the skill set of the taxonomy
creator and your organization's business needs.
• Automatic taxonomy creation groups items and arranges those groups into
taxonomies using statistical models. In this approach, the taxonomy is created
and the items are categorized in a single step.
• Assisted taxonomy creation requires a Knowledge Manager or Librarian to
monitor and review the taxonomy-creation process, suggesting alternatives, and
correcting categories in an interactive and iterative process. Assisted taxonomy
creation offers more precision and control over the categorization process but
requires a dedicated resource.
• Professional taxonomy creation is performed by many third-party vendors to
provide organizations with high quality categorization. For Records
Management applications, this is the most appropriate approach.

1.1.2 Classifying Items

Once you create a taxonomy, you must classify your knowledge appropriately.
When an item is classified, a Classification tag is associated with the item. This tag
specifies in which Classification or Classifications the item should be classified.
There are three accepted approaches to item classification: automatic, assisted, and
manual.
• Automatic classification involves creating rules or profiles that define the
classification(s) in which a particular item should be classified. This approach
does not require intervention by a Knowledge Manager or Librarian.

10 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 1.2 Understanding Livelink Classifications

• Assisted classification requires a Knowledge Manager or Librarian to monitor

and review the classification process, suggesting alternatives and correcting
classification in an interactive and iterative process. Assisted classification is the
most commonly used approach because it offers more precision and control over
the classification process.
• Manual categorization requires that a user explicitly classify each item added to
the repository. In highly regulated environments, such as the military, this is the
only acceptable approach.

1.2 Understanding Livelink Classifications

Livelink Classifications categorizes Enterprise Server items (for example,
Documents, Compound Documents, Text Documents, and Folders) into a taxonomy
of Classifications called Classification Trees. Once your Enterprise Server items are
classified into Classification Trees, Enterprise Server users can browse and search
for information more efficiently. By browsing Classification Trees, users can focus
on a subject area that interests them and search for content within that particular
area.
Note: Although Livelink Classifications does not suggest or build taxonomies
for you, it allows you to import and export the XML taxonomy definitions that
you provide.
The standard edition of Livelink Classifications provides only manual classification
capabilities. Livelink ECM – Classifications Professional provides assisted and
automatic classification capabilities, known as Intelligent Classification, in addition
to manual classification capabilities. Intelligent Classification makes use of a Profile
Query, which is a set of criteria that items must satisfy in order to be assigned to a
particular Classification. For information about the difference between manual,
assisted, and automatic classifications, see “Classifying Items” on page 10.

1.2.1 Understanding Automated and Assisted Classifications

Intelligent Classification capabilities rely on Enterprise Server's core search
technology. Figure 1-2 below illustrates some of the components in the Enterprise
Server Search architecture.

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide 11

Chapter 1 Overview

Figure 1-2: Enterprise Server Search Architecture

When you install Livelink Classifications, a Classification Importer process is added

to the Enterprise data flow. This process determines which assisted and automatic
Classifications best match the items represented by the data. The criteria is set by
constructing a Profile Query on a modified version of the Enterprise Server Search
page. Specifying key words or phrases provides the reference, and the Classification
Importer then matches against Enterprise Server items before they can be assigned a
Classification. For more information on constructing a Profile Query, see Livelink
ECM™ - Classifications - Resource Guide (LLESCLS-H-GGD).
Note: Classification Importer processes are also added to Livelink ECM –
Enterprise Library Services data flows.

12 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 1.2 Understanding Livelink Classifications

How it Works
After you enable Intelligent Classification, the Classification Importer process runs a
scheduled sequence of events beginning with a query of the Enterprise Server
indexes. The results are then read and parsed. The parsed content is placed into a
temporary location in the database, the DStagingImport table.
Once the content is in the DStagingImport table, an Import Agent transfers content
to a Task Handler, which requests the Classification drop-in (classresult). The
Classification drop-in performs Classification Query File updates and provides
ranking of the IPool content. Classifications are ranked based on the low threshold
score for the Classification and the get result X parameter in the Classification
Query File. Classifications are then returned for each item in the IPool. The
information in the LLClassify table is updated after each run of the Classification
Importer process.
Note: There are several processes that contribute to the overall success of Intel-
ligent Classification. If you are having difficulty applying assisted or automatic
Classifications using Intelligent Classification, see“Frequently Asked Ques-
tions” on page 21 for more information about each process.

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide 13

Chapter 2
Troubleshooting Livelink Classifications
A successful application of the Livelink Classifications module requires fairly
detailed knowledge and understanding of the contents of the Enterprise Server
repository, and an appropriately designed taxonomy.
Because the Livelink Classifications module relies on many different areas of
Enterprise Server, configuring some of the more advanced features, such as assisted
or automated Classifications, can be challenging. If you have installed and
configured Livelink Classifications but find that it is not functioning the way you
expected or fulfilling your business requirements, you can troubleshoot the system
using the suggestions in this chapter.
This chapter covers the following topics:
• “Troubleshooting the Installation” on page 15
• “Troubleshooting Assisted or Automatic Classification” on page 17

2.1 Troubleshooting the Installation

If you experience difficulty installing the Livelink Classifications module, or if you
encounter unexpected results after installation, you should verify that you have
installed the correct version of the module for your Enterprise Server site.
If you want to enable Intelligent Classification, you must purchase the Livelink ECM
– Classifications Professional module. This variation of Livelink Classifications
includes a license key that you must provide before you can configure assisted or
automatic classification functionality.

2.1.1 Verifying Module Compatibility

The following table lists the available versions of Livelink Classifications and
Livelink ECM – Classifications Professional and the compatible Enterprise Server
releases for each version. Because Livelink Classifications relies on functionality
provided by Enterprise Server's core search technology, installing non-compatible
combinations can cause irregular behavior or loss of functionality.

LLESCLS040200-TGD-EN-1 Livelink ECM – Classifications 15

Chapter 2 Troubleshooting Livelink Classifications

Table 2-1: Verifying Module Compatibility

Module Backplane (with latest monthly patch)

Livelink Classifications 2.0 Livelink 9.1 SP1 (with WebSystemObj 3.0 up-
grade)
Livelink 9.1 SP2
Livelink Classifications 2.5 Livelink 9.1 SP3
Livelink Classifications 2.5.1 Livelink 9.1 SP4
Livelink Classifications (Professional) 2.7 Enterprise Server 9.2
Livelink Classifications 2.7.1 Enterprise Server 9.2 SP1
Livelink Classifications 2.9 Enterprise Server 9.5
Livelink Classifications 2.9.1 Enterprise Server 9.5 SP1
Livelink Classifications 3.0.0 Enterprise Server 9.5 SP1
Livelink Classifications 3.0.1 Enterprise Server 9.5.5
Livelink Classifications 3.6 Enterprise Server 9.6
Livelink Classifications 3.8 Enterprise Server 9.7
Livelink Classifications 4.1 Enterprise Server 9.7.1
Livelink Classifications 4.2 Enterprise Server 9.7.1

2.1.2 Verifying the License Key

When you purchase the Livelink ECM – Classifications Professional module, Open
Text provides you with a license key that enables assisted and automatic
classification. This license key is based on your company name and the number of
users at your Enterprise Server site. Without a license key, you must classify
Enterprise Server items manually.
If you are responsible for installing Livelink Classifications and configuring assisted
or automatic Classifications, but do not have a license key, you should ensure that
you have purchased the Livelink ECM – Classifications Professional module. If you
have purchased the Livelink ECM – Classifications Professional, but do not have a
license key, contact Open Text Customer Support for assistance.
Tip: To enter the license key, click the Enable Intelligent Classification
Functionality link in the Livelink Classifications section of the Livelink
Administration page. For more information, see the Livelink ECM - Enterprise
Server - Administrator's Online Help (LLESCOR-H-AGD).
If you are upgrading to a new version of Livelink ECM – Classifications
Professional, you must enter new license key information; otherwise, you cannot
continue using assisted and automatic classification functionality.

16 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 2.2 Troubleshooting Assisted or Automatic Classification

2.2 Troubleshooting Assisted or Automatic

Classification
If you have installed Livelink ECM – Classifications Professional and entered the
appropriate license key information, but assisted or automatic classification is not
functioning correctly, you can troubleshoot the following components:
• Query File
• Import Agent
• Relevance Score Threshold
Note: When the Classifications Professional option is enabled in the Livelink
Classifications module and you are using Livelink ECM – Records
Management, RM Classifications will not support the Assisted management
type on the Extras tab of the RM Classifications. For more information on
configuring Classifications with Records Management, see Livelink Records
Management - Installation and Administration Guide (LLESRCM-IGD).

2.2.1 Examining the Classification Query File

The Classification Query File, queries.in, contains Profile Queries for all assisted
and automatic Classification nodes. The queries.in file is modified when a
Classification is updated within Enterprise Server using the Save as Profile button,
or when an assisted or automatic Classification node is deleted.
You can determine whether or not the Classification Profile Queries constructed
within Enterprise Server are being updated by examining the structure of the
queries.in file.

The queries.in file is located in the <Livelink_home>/config directory, and

contains the following parameters for each automatic or assisted Classification:
• SYNC "NNNN", which identifies the DataID of the Classification node

• SELECT "OTObject" and "OTScore"

• "get results score <X>", which instructs the search engine to return only items
with a relevance score greater than the Classification relevance score threshold X
If the queries.in file is not being updated, verify that the Update Distributor is
present and the Classification drop-in is loading correctly.
Note: If you are running Livelink Classifications in a clustered environment,
the Classification Query File is located relative to the Admin server of the
Update Distributor.

Ensuring the Update Distributor Is Present

To ensure that the Update Distributor is present, you need to verify the presence of
the Enterprise data source. If this is a first-time installation of Enterprise Server, the

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide 17

Chapter 2 Troubleshooting Livelink Classifications

Enterprise data source should have been generated during installation. If not, you
can create one. If the Enterprise data source has been deleted, you will need to create
a new one and configure the data flow Classification Importer process. The Update
Distributor is required to classify only new items being added to Enterprise Server;
therefore, any previously classified items will remain unaffected by the loss of the
data source. An Enterprise data source can be created in the System Object Volume.
For more information about adding a data source, see Livelink Admin Online Help -
Index and Search Administration (LLESWBS-H-AGD).

Ensuring That the Classification Drop-In Is Loaded

The Classification drop-in (classresult) is copied to Enterprise Server's bin directory
(<Livelink_home>/bin) during the first stage of the module installation and is loaded
when you restart the Livelink Server during the second stage of the module
installation. The drop-in is used to perform Classification Query File updates and to
rank assisted and automatic Classifications. Without the drop-in, assisted and
automatic classification does not function.
You can ensure that the drop-in is being loaded correctly by examining a thread log.
The loading of the drop-in occurs immediately before the loading of the
Classification OSpace and appears similar to the following (if successful):
KDropinClass::LoadPackage( classresult.DLL ) about to load.
#OSpace: classification Root: #61000001 File:
C:\OPENTEXT10_0\module\classification_3_8_0\ospace Size: 362240

Failure to load the drop-in will occur if the drop-in and OSpace versions do not
match, or if the file is not found. If the drop-in fails to load, the information appears
in the thread log similar to the following:
KDropinClass::LoadPackage( classresult.DLL ) about to load.
LoadLib::Open could not load: classresult.DLL (The specified
module could not be found.)
KDropin: Could not open Dropin library: classresult.DLL
KDropinClass::LoadPackage( classresult.DLL, DLLDropinInit ) Error
loading package.
C:\OPENTEXT10_0\module\classification_3_8_0\ospace Size: 362240

If the drop-in is not being loaded properly, re-run the Livelink Classifications
module installation program to copy the proper version of the drop-in to the
Enterprise Server bin directory (<Livelink_home>/bin).

2.2.2 Executing the Import Agent

Automatic and assisted classification relies on the Classifications Import Agent to
consume the imported IPool messages in the DStagingImport table and pass them
to the Classification task handler for processing. If you have set up assisted or
automatic Classifications and items are not being classified as you expect, you can
execute the Import Agent manually to kick off the Classification processing queue.
The Import Agent (SYSTEMOBJEX:Agents:ImportAgent) is registered in the
AgentSchedule table with AgentID 3001 and is scheduled to execute every five

18 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 2.2 Troubleshooting Assisted or Automatic Classification

minutes. The Agent Controller (LLAGENT:LLAgentObjects:AgentController)

scans the AgentSchedule table to determine which agents to run, according to their
schedule. The Agent Controller is executed by the notify.runagent request
handler (WEBNOTIFY:NotifyRequestHandler:RunAgent in versions earlier than
Livelink 9.5, and WEBAGENT:LLRequestHandler:RunAgent in Livelink 9.5 and later
versions).
If Enterprise Server is running in server mode, the notify.runagent request
handler executes the Agent Controller every five minutes. If Enterprise Server is
running in Builder mode, you must execute the notify.runagent request handler
manually and ensure that the RunWithoutLogin parameter is set to TRUE in the
[options] section of the opentext.ini file. Both the Agent Controller and the
notify.runagent request handler require that the EnableAgents parameter is set
to TRUE in the [options] section of the opentext.ini file.
Note: For more information about the RunWithoutLogin and EnableAgents
parameters, see Livelink ECM - Enterprise Server - Administrator's Online Help
(LLESCOR-H-AGD).

2.2.3 Editing the Relevance Score Threshold

If you have ensured that the Classification drop-in is loaded correctly, examined
your Classification Query Files, and executed the Import Agent, and you discover
that Enterprise Server items are not being classified as you expect, you can edit the
relevance score threshold.
When an item is extracted, the Intelligent Classification functionality compares the
item to each assisted and automatic Classification and then determines relevance
scores that represent how well the item satisfies each of the Classification's profiles.
The lowScoreThres setting identifies the minimum relevance score necessary for
the system to either suggest the item for an assisted Classification or assign an
automatic Classification to the item.
By default, the lowScoreThres parameter is set to 40, but does not appear in the
opentext.ini file. If you want to change the value of the parameter, you must add
the lowScoreThres parameter to the [Classifications] section of the
opentext.ini file, and specify an integer between 0 and 100 as the value. For more
information, see Administering Classifications (LLESCLS-H-AGD).
To test the relevance score threshold, lower the value to 1 and then regenerate the
Classification Query File to apply the new value to all Classification Profile Queries.
Lowering the relevance score threshold from 40 increases the number of
Classifications assigned to objects, but decreases the accuracy of the Classifications
(that is, less relevant objects will be assigned Classifications that they would not
usually receive). Open Text does not recommend that you deploy Livelink
Classifications with a relevance score threshold of 1. Increasing the relevance score
threshold will more greatly restrict the number of Classifications assigned to an
object but increases the accuracy. Experiment with the relevance score threshold
setting to find the correct value for your data.

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide 19

Chapter 2 Troubleshooting Livelink Classifications

Note: Only search results with a score greater than or equal to the relevance
score threshold are returned and processed as assisted or automatic Classifica-
tions. Results scoring below the relevance score threshold do not appear in im-
ported IPool messages or log files.

20 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

Chapter 3
Frequently Asked Questions
Although detailed information about Livelink Classifications is available in the
Livelink ECM™ - Classifications - Resource Guide (LLESCLS-H-GGD), you can use this
guide to find the answers to some frequently asked questions.
This chapter covers the following topics:
• “What is the difference between Livelink Classifications and Livelink ECM –
Classifications Professional?” on page 22
• “How do I get a license key?” on page 22
• “Does Livelink Classifications build taxonomies for me?” on page 22
• “Where can I get a taxonomy?” on page 22
• “How do I classify an existing index?” on page 23
• “Are taxonomies created with Livelink Classifications 2.0 compatible with later
versions of Livelink Classifications?” on page 23
• “What are the rules for Classification inheritance?” on page 23
• “What is the difference between automatic and assisted classification?” on
page 24
• “How long does it take to automatically classify a new item?” on page 24
• “How do I set up Enterprise Server so that I am notified when import operations
occur?” on page 24
• “Why am I not receiving notifications of the success of an import?” on page 25
• “Is there a limit to the number of Classifications that I can add to a
Classifications Workspace?” on page 25
• “Are there performance implications for exceeding the recommended number of
Classifications in the Classifications Workspace?” on page 25
• “I have set up automatic Classifications. When new items are added to
Enterprise Server, how can I tell which items were classified and which items
were not?” on page 25
• “I have constructed a Profile Query based on categories and attributes. Why is it
not returning as many classified documents as I expect?” on page 25

LLESCLS040200-TGD-EN-1 Livelink ECM – Classifications 21

Chapter 3 Frequently Asked Questions

• “I have imported Classifications that include categories and attributes to a new

Enterprise Server system. Why do my Profile Queries yield no results?” on
page 26
• “How can I have the Classifications assigned to a search result item displayed on
the Search Result page?” on page 27
• “How can I have the Classifications assigned to a search result item displayed on
the Search Result page?” on page 27

3.1 What is the difference between Livelink

Classifications and Livelink ECM –
Classifications Professional?
Livelink Classifications is an optional Enterprise Server module that provides you
with an alternative way to organize, manage, and browse Enterprise Server items.
Livelink ECM – Classifications Professional is an edition Livelink Classifications
that provides a way to automatically suggest or assign Classifications. If you
purchase the Livelink ECM – Classifications Professional edition, Open Text
provides you with a license key that you use to enable automatic or assisted
classification (Intelligent Classification).

3.2 How do I get a license key?

Open Text provides you with a license key when you purchase Livelink ECM –
Classifications Professional. If you did not receive a license key, or would like to
purchase one, contact your Open Text Sales representative.

3.3 Does Livelink Classifications build taxonomies

for me?
No, Livelink Classifications does not suggest or build custom taxonomies for your
Enterprise Server site. Instead, you must do one of the following:
• Provide a sample XML file that defines a hierarchy of Classifications (an XML
Classification taxonomy), and then import it.
• Create the Classification Tree and Classifications manually.
This allows you to construct a hierarchy of Classifications in Enterprise Server
without having to add each Classification individually to the Classification
Workspace.

3.4 Where can I get a taxonomy?

You can either create a custom taxonomy by defining a hierarchy of Classifications
in an XML file which you can then import, or you can purchase a taxonomy from a
third-party vendor.

22 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 3.5 How do I classify an existing index?

3.5 How do I classify an existing index?

For versions of Livelink Classifications that work with Livelink 9.5 and 9.6, you
must define a taxonomy and then reindex the content at your Enterprise Server site
in order to classify existing content.
Livelink Classifications 3.8 for Livelink 9.7.0 introduced a Classify Existing Content
administration operation that allows you to apply automatic and assisted
classifications (using Intelligent Classification) to existing content without re-
extracting your entire Enterprise content. The Classify Existing Content operation
issues Classification Profile Queries against all Enterprise Server and Enterprise
Library Services Update Distributors and then imports the resulting IPools and
processes the results. For more information on the Classify Existing Content
operation, see Livelink ECM™ - Classifications - Resource Guide (LLESCLS-H-GGD).

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.

3.6 Are taxonomies created with Livelink

Classifications 2.0 compatible with later versions
of Livelink Classifications?
No, the taxonomy import and export features for Livelink Classifications 2.5 and
later releases were reimplemented to provide extensibility for Livelink ECM –
Records Management items and to improve performance. This reimplementation
required a significant DTD change that is not backward compatible with version 2.0
XML files.

3.7 What are the rules for Classification inheritance?

• If you want items to inherit the Classifications of their parents, you can set up a
container inheritance. A container is an Enterprise Server item that can hold
classified items; for example a Folder or a Project.
• If an item was assigned a Classification manually, the Classification is applied to
that item. If the item's parent has Classifications applied to it, those
Classifications are inherited by the item.
• If an item was not assigned a Classification, but the item's parent has
Classifications applied to it, those Classifications are inherited by the item.

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide 23

Chapter 3 Frequently Asked Questions

3.8 What is the difference between automatic and

assisted classification?
Assisted and automatic classification are management types for the Classifications
that you add to your Enterprise Server site.
There are three management types:
• Manual, which means that the system will not automatically assign the
Classification to an item. Only Enterprise Server Administrators and users with
the appropriate permissions can assign this Classification.
• Assisted, which means that the system will suggest this Classification for items
that satisfy the Classification's Profile. Enterprise Server Administrators and
users with the appropriate permissions can assign this Classification manually.
• Automatic, which means that the system will automatically assign this
Classification to items that satisfy the Classification's profile. Enterprise Server
Administrators and users with the appropriate permissions can assign this
Classification manually.

3.9 How long does it take to automatically classify a

new item?
On a default Enterprise Server installation, automatic classification of a new item
takes approximately five minutes after the last IPool message passes through the
Classification Importer process. You can monitor the status of IPool messages in the
Interchange Pools section of the Data Flow Manager page for a data source.

3.10 How do I set up Enterprise Server so that I am

notified when import operations occur?
To set up notifications, you must do the following:
• On the Import Classifications page, select an Alert Level. This determines the
type of alert e-mail that Enterprise Server generates. By default, no e-mail is
generated.
• Enable system object volume checking and ensure that test e-mails can be sent
successfully from the Configure System Object Alert E-Mail Delivery page
(<Livelink_home/host:port>/livelink.exe?func=sysman.config). The mail
server settings from this page are used for sending Import Classifications email
messages.

24 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 3.11 Why am I not receiving notifications of the success of an import?

3.11 Why am I not receiving notifications of the

success of an import?
Notification of taxonomy import operations is based on the System Object Volume
alerts that are configured at your Enterprise Server site. Like SOV notification,
duplicate messages won't be sent unless the message table is purged and the five-
minute agent executes.

3.12 Is there a limit to the number of Classifications

that I can add to a Classifications Workspace?
There is no limit to the number of Classification nodes that can be added to the
Classifications Workspace.
Large installs with many thousands of automatic or assisted Classifications may
notice performance degradation with the Import Agent. The agent is on a five
minute schedule to process new automatic or assisted Classifications.

3.13 Are there performance implications for

exceeding the recommended number of
Classifications in the Classifications
Workspace?
Large installs with many thousands of automatic or assisted Classifications may
notice performance degradation with the Import Agent. The agent is on a five
minute schedule to process new automatic or assisted Classifications.

3.14 I have set up automatic Classifications. When

new items are added to Enterprise Server, how
can I tell which items were classified and which
items were not?
Instead of setting up automatic Classifications, consider setting up assisted
Classifications. Assisted Classifications allows you to review the Classifications that
Enterprise Server automatically suggests for items.

3.15 I have constructed a Profile Query based on

categories and attributes. Why is it not returning
as many classified documents as I expect?
The default value of the lowScoreThres parameter in the [Classifications]
section of the opentext.ini file is not optimal for automatic Classifications based

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide 25

Chapter 3 Frequently Asked Questions

on attributes. Category and attribute-only Queries often require you to specify a

lower relevance score threshold to return the expected number of results. You can
specify a lower relevance score threshold by clicking the Use Specific radio button
on the Profile tab and entering a number from 1 to 100. You can also change the
value of the lowScoreThres parameter. However, if you do, it will become the new
default relevance score threshold and you must regenerate the Classification Query
File after modifying the opentext.ini file in order for the changes to take place. For
information about regenerating the Classification Query File, see Administering
Classifications (LLESCLS-H-AGD).
Note: Lowering the value of the lowScoreThres parameter may adversely
affect Classification Profile Queries based on content, because a Classification
might be assigned to more items than expected.

3.16 I have imported Classifications that include

categories and attributes to a new Enterprise
Server system. Why do my Profile Queries yield
no results?
When you import Classifications to a new Enterprise Server system that uses
automatic Classifications, Profile Queries that reference categories and attributes
may yield no results because their Queries reference node IDs of items from the
source Enterprise Server system. For these Profile Queries to work on the
destination Enterprise Server system, the node IDs of the categories must be
remapped using the following method.

To manually remap the node IDs:

1. Export the Classification taxonomies to an XML file using the Classifications
Taxonomy Export. For more information about exporting taxonomies, see
Administering Classifications (LLESCLS-H-AGD).
2. Export the specific categories referenced by the Classification Profile Queries (or
the entire Category Volume) to a file. To export the Category Volume:
• Using the Livelink XML export feature, type the following in the address
bar of your browser to open the XML file:
func=ll&objAction=

xmlexport&scope=sub&nodeinfo&versioninfo=all&content&objID=

<[Category Volume DataID]>

• Save as<cats.xml>.
3. On the destination Enterprise Server system, import the category definition
XML file, <cats.xml>. To import the Category Volume:
• Using the Livelink XML import feature in the address bar of your browser
type:

26 Livelink ECM – Classifications LLESCLS040200-TGD-EN-1

 3.17 How can I have the Classifications assigned to a search result item displayed on the Search Result
page?

func=admin.XMLImport&

filename=<Root Directory>\cats.xml&objID=<[Category Volume

DataID]>

4. In the Classification taxonomy XML file, replace the node IDs of the categories
in all attribute reference tags imported from the source Enterprise Server system
with the new category node IDs that resulted from importing the category
definition XML file.
The following is an example of a Profile Query from the source Enterprise
Server system:
<query>SELECT &quot;OTObject&quot;, &quot;OTScore&quot; WHERE ((
[ region &quot;OTMeta&quot;:&quot;Attr_24496_2&quot; ]
&quot;one&quot; )) AND
(&quot;&lt;Attr_24496_3&gt;0&lt;/Attr_24496_3&gt;&quot;)
ORDEREDBY RANKINGEXPRESSION (( [ region &quot;OTmeta&quot;:&quot;
Attr_24496_2&quot; ] &quot; one&quot; )) AND (&quot;&lt;
Attr_24496_3&gt;0&lt;/Attr_24496_3&gt;&quot;)</query>

Note: In this example, 24496 represents the category node ID that must be
replaced when the Profile Query is exported to the destination Enterprise
Server system.
5. On the destination Enterprise Server system, import the Classification taxonomy
XML file using the Classifications Taxonomy Import. For more information
about importing taxonomies, see Administering Classifications (LLESCLS-H-
AGD).

3.17 How can I have the Classifications assigned to a

search result item displayed on the Search
Result page?
Open the Regions tab on the Enterprise Search Manager page and locate
OTClassificationTree. Selecting the Displayable check box will enable the
Classifications assigned to a search result item to be displayed on the Search Result
page. You can also change the display name to something more user-friendly by
typing a new name in the Display Name field.
For this option to be displayed properly when searched, you must click Change the
Way Results are Displayed on the Search Result page and move the option from the
Available box to the Displayed box.

LLESCLS040200-TGD-EN-1 Troubleshooting and FAQs Guide 27