by work breakdown structure (WBS),
TaskNavigator becomes a powerful tool for work
coordination and collaboration in distributed teams.
2.1 Lightweight PID
The main idea of PID in TaskNavigator is to
proactively deliver task-relevant information e.g.,
documents, e-mails, web-history, wiki pages related
to the task without explicit user request. The
principle of lightweight PID is based on the
assumption that a task can be described sufficiently
by task title, description and comments as well as
documents attached to the task. The PID module of
TaskNavigator generates a keyword-based query
from the current task context represented by task
description and its attachments and sends request to
external information retrieval (IR) systems
automatically to get task-relevant information.
Results from the IR systems are sorted by their
relevance to the query and presented to the user.
The core advantage of lightweight PID is the low
level of human effort needed to make it work: the
user just types a task name in TaskNavigator to get
first PID results. A formal model of task information
needs is not required.
The main problem (P1) of lightweight PID is
that statistics-based query generation used in
lightweight PID can cause unsatisfactory quality of
generated queries or search results:
(P1.1), TF/IDF algorithm used for a query
generation has limitations, e.g. for the task
“Introduce new employee” the keyword “new” is
regarded as a stop word and removed from the
query, although it is essential in the given situation.
(P1.2), Compound search terms: Even if the
algorithm could identify the importance of the
keyword “new” for the task, the keyword does not
have sense as a query term without considering it in
the combination with the keyword “employee”.
(P1.3), Verbose task descriptions can spoil
automatically generated query, e.g., for the task
“Create new DB for TouchMap weblog” with the
description “To install a new wordpress blog we
need a separate database on our mysql server” would
generate the query “create, db, touchmap, weblog,
wordpress, install, separate, database ...” that would
result in delivery of no or too many documents.
2.2 Task Tagging Improves PID
The objective of the TaskNavigator project was to
find an optimal solution that requires a minimally
possible modeling effort to achieve acceptable PID
results. Our claim here is that bottom up task
modeling realized by collaborative task tagging is
feasible and can improve PID results (C1).
Tagging is a wide-spread technology for
lightweight annotation of electronic resources by
manually or automatically assigning keywords to
them (Golder and Huberman, 2006). Considering
tasks in TaskNavigator as resources that are
annotated collaboratively by tags, we decompose C1
into the following sub-claims:
(C1.1) Task tags can be used as keywords to
refine a search query for task-related PID. Keywords
defined by users do not cause problems P1.1 and
P1.2 (if multi-word tags are allowed). The implicit
semantics behind task tags given by humans will
highlight the most important task aspects
suppressing the problem P1.3.
(C1.2) Provided the bag tagging model is used in
TaskNavigator, where different users can tag tasks
multiple times with the same tag, the popularity of
task-related tags can be used to specify weights of
single terms comprising a PID query. A weighted
query expresses the importance of each term thus
better specifying the task semantics (see P1.3).
(C1.3) Provided a list of tags of the parent task is
easy available in the current task details, the parent
task tags will ease the effort on current task tagging.
In order to implement this new vision on PID,
the process of the task-specific information delivery
will be extended as follows: i) Propose possible tags
to the user proactively; ii) User accepts/rejects tag
proposals or tags tasks manually (compound tags are
allowed); iii) In collaborative task management
environment, users can vote for or against task tags
assigned by themselves or by colleagues. iv) A new
PID query is generated by TaskNavigator
considering tags and tag votes as (compound) search
terms and their weights in the query.
Although task tagging can solve problems of
lightweight PID, there are severe problems going
along with tagging such as synonymy (P2.1),
homonymy (P2.2), polysemy (P2.3) - see (Goldman
06). In respect to the information retrieval, the
problem P2.1 (includes synonyms, misspelling,
different writing styles and different languages) is
the most critical. Provided the user tagged the task
with “digitalpaper”, documents containing “digital
paper” or “digitales Papier” (Ger.) will not be found
by the IR engine. The problem of homonymy can
emerge, for example, if the user tagged a task with
“SME” assuming “subject matter expert” but
received documents about “small and medium
enterprises”. The problem of polysemy is sometimes
difficult to recognize but it can spoil the IR results:
ICAART 2010 - 2nd International Conference on Agents and Artificial Intelligence
612