Method and apparatus for performing data collection, interpretation and analysis, in an information platform6078924Abstract An information platform automates the collection of data, provides a method for organizing the library of information and provides analysis using multiple content-types, thereby providing a user with a market understanding necessary to execute rapid and knowledgeable decision making. The information platform collects and integrates data, observations and intelligence; provides controls for multiple methods of information navigation and analysis; and allows details to be digested in the context of other data, regardless of its type. The information platform is a client/server implementation that is subdivided into four major sections, including: (1) Data Retrieval, which provides a sophisticated catalog for finding internal and external information and collection agents which retrieve specific information without user intervention; (2) Data Classification and Storage which handles the storage of the information once it has been gathered from a source; (3) Information Browsing, Query, Analysis, and Report Creation which provides information browsing, reporting, and analysis tools; and (4) Desktop Integration where the information platform takes information from a wide variety of formats (HTML, text, spreadsheet) and combines them all into a single format (HTML, text, spreadsheet). Claims What is claimed is: Description BACKGROUND OF THE INVENTION
TABLE 1
__________________________________________________________________________
Knowledge Gathering
User Processes
User Tasks
Tasks & Functions
Components Used
Functions Available
__________________________________________________________________________
Client needs &
Determine needs and
<none>
objectives
objectives
Create new Case
Start Case, set aside
New Case dialog
Create blank case
space Create case from template
Set title for new case
<none> Set pre-built Objectives,
New Case dialog;
Set of pre-built objectives
collection Case Items,
Case Set of pre-built case items
and Search Items for case
and search items
template, if used
Open existing Case
Show available Cases,
Open Case dialog
Filter and sort Case listing
allow opening of selected
based on properties
Case Select Case to open
Opening a Case closes
current Case
Set or edit Case
Record properties
Case Set Case properties: Title;
properties Description; Owner;
Categories; Security/Access
Rights; Sharing
Edit Case Objectives
Enter or edit objectives
Case View, edit any predefined
needs for case template, if
used
View, add, edit, organize
objectives
Edit Objectives properties:
Fulfillment Status; Descrip-
tion; Due Date; Status;
Priority; Percentage Com-
plete; Owner
Edit Case Items
Enter or edit case items
Case; Catalog;
View, edit any predefined
User Sets; Favorites
case items from template
View, add, edit, organize
case items
Create new case
Save settings as new
Save As dialog
Edit objectives
template template View, add, remove case
items
Save as Case template
Create new Catalog
Store settings as new
Case; Catalog
View, add, remove
collection item
collection item collection items
Save as collection item
package
Data collection
Review case items Case; Catalog
View Case Item informa-
tion and properties
Edit Case Items properties:
Name; Description;
Criteria; Categories;
Collection Timing; Author
Determine or refine
Update Case Items
Case; Catalog;
Add, remove, and edit
information needs for User Sets; Favorites
Case Items
case Provide sources, informa-
Select categories, sources,
tion categories, inputs
common inputs; select
Catalog Items to add to the
Case
Enter criteria for collection
of Case Item
Provide gathering Collect the specified infor-
structures mation
Filter the Catalog for
Filter and sort the
Catalog Set filters
collection items
Catalog display by Select sort property
property Update Catalog display to
match filtering and sorting
settings
Review Case Item
Display Case Item and
Case View properties
progress progress information Edit properties for
collection
Search for information
Display Search Catalog
Case; Catalog;
Add, remove Search Items
at sources
for information retrieval
User Sets
Edit Search Items for the
Case and their properties:
Name; Description;
Criteria; Search Timing;
Author
Browse for informa-
Navigate to source
Case; Catalog;
Add information to Case
tion at sources
information Favorites;
from source data item
Document Analyzer
Edit properties for collected
Case Item
Edit catalog structure
Add catagories
Catalog Add category
Add collection packages
Add package
Assign items to Add items
categories
Categorize items Choose existing items to
associate with category
Choose categories to
associate with item
Add sources to
Access source and
Catalog Select source
catalog, select
information
source and
Categorization of source
Categorize source infor-
categorize
and items available mation
Add source and relation-
ships
Think, review
Review retrieved data
Display data elements
Case Select Case to view
data, analyze Select items within the
the data Case to view
Cut, copy, paste infor-
mation
Edit data
Output information
Analyze collected item
Display thumbnail
Case; Document
View components
Analyzer Select components
Display components Select component types to
view
Zoom in (parse selected
components)
Show components by Zoom out (parse document)
type Edit data or component
Parse and display select-
Add-Remove from Case
ed components Output information
Analyze across data
<none>
items
Filter & sort retrieved
Allow filtering and sort-
Case Enter filter criteria
information elements
ing by property Sort by property
Update display to items
matching settings
Select item for manipula-
tion
Create report
Select or create outline
<none>
outline
in reporting tool of
choice
Write report
Move data information
Export data to correct
Case Select item or data elements
format for reporting tool
within item
Copy selection
Output/export selection
Edit gathered informa-
Edit information with
In-place editing
Edit item
tion compatible tools
tools Save, output, export item
Edit report information
<none>
Publish report
Output draft
<none>
draft for feed-
Select recipients
<none>
back Edit report based on
Edit and reexport data to
Browser Select item or data elements
feedback correct format for report-
within item
ing tool Copy selection
Output/export selection
Publish final
Output final report
<none>
report Select recipients
<none>
__________________________________________________________________________
The following discussion provides an outline of a full task analysis of the information platform. FIG. 2 is a block diagram of information platform task analysis according to the invention. FIG. 2 shows top level client application operation, in which a client application is launched 40. The client (user) may then view and manipulate case information 42, view and manipulate source information 44, view and manipulate user sets 46, view and manipulate favorites 48, view user account information 50, or edit the catalog 52. Each of these operations is discussed in greater detail below. FIG. 3 is a block diagram of information platform source information breakdown according to the invention. More specifically, FIG. 3 identifies the flow with regard to client viewing and manipulation of case information 60. At the highest level, a user may navigate a case 99, view case properties 65, view a case summary 63, or create a case template. Each of these operations is discussed in greater detail below. When navigating a case 99, the user may view objectives 100, view case items 101, or view search items. For each of these operations, the user may sort a list of such information on properties 103 or may filter the list on properties 104. Thereafter, the user may choose an objective 105, choose a case item 112, or choose a search item 118. If an objective is chosen 105, the user may view the item 106 and either copy, delete, or add the item to a favorites list 107, select a property 110 and edit properties 111, or add the item to a case 108 and specify the case 109. If a case item is chosen 112, the user may select a collection item 113 or an information item 114. If a collection item is chosen 112, the user may view the item 106 and either copy, delete, or add the item to a favorites list 107, select a property 110 and edit properties 111, or add the item to a case 108 and specify the case 109. If an information item is chosen 114, the user may view the item 117 or organize the information 121 and move the information to a folder or copy the information to a folder 122. If the user views the item 117, the user may copy, delete, or add the item to a list of favorites 123, select a property 126 and edit the property 127, edit the information 124, and specify a tool for such editing 125, add the item to a case 140, specify the case to which the information is to be added 141, and specify the associated properties 142, export or output the information 143, specifying the format 144, or analyze the information 128 using a document analyzer 129. Document analysis can proceed by viewing bin items 130, geometry elements 131, or multiple elements 132. An item is then selected 133 and the item may be edited 134 using a specified tool 135, added to a case 136, where the case is specified 137, or exported or output 138 using a specific format 139. If the user chooses a search item 118, the user may view either a search item 119, where the user may view the item 106 and either copy, delete, or add the item to a favorites list 107, select a property 110 and edit properties 111, or add the item to a case 108 and specify the case 109; or the user may search a results item, in which case the user may view the item 117 or organize the information 121 and move the information to a folder or copy the information to a folder 122. An explanation of the user view selection 117 is provided above. When viewing case properties 65, the user may select a property 66 and edit the property 67. When viewing a case summary 63, the user may edit associated properties, copy, or import/output the summary 64. When creating a case template 61, the user may save a current case as a template 62. When creating a search item 68, the user may create a folder 69 in a specific location 70, create a case item 71 from a specific category 72, where the user may navigate the catalog 73 and either sort a list of items on a specific property 74 or filter the list on properties 75, choose an item 76, set properties and criteria for the item 77, and add the item to the case 78; or the user may create the case from another case 79, where information may be pasted from the system clipboard 80. Further, the user may create a search item 81 from another case 79, where information may be pasted from the system clipboard 80; or the search item may be created from the search catalog 82 by first navigating the catalog 83 and then either sorting a list on a specific property 84 or filtering the list on a properties 85. Thereafter, the user chooses the item 86, sets properties and criteria 87, and add the item to the case 88. Finally, when selecting a different case 89, the user may either begin a new case 90, where the case is either blank 91 and a new case is created 92, or from a template 93, where the user first views the available templates 94 and either sorts the templates on a specific property 95 or filters the templates on properties 96, and then chooses the template 97, and creates the new case 98; or the user may open an existing case 145, first viewing the available cases 146, either by sorting the cases on a specific property 147 or by filtering the cases on properties 148, and thereafter choosing the case 149 and opening the case 150. FIG. 4 is a block diagram of information platform manipulate source information breakdown according to the invention. More specifically, FIG. 4 identifies the flow with regard to client viewing and manipulation of source information 200. This operation is discussed in greater detail below. The source information is obtained from any of case items, search items, history, an entered location, an open file dialog, a favorite, or a link from a source (201). The user navigates to the source 202 and may view the item 203. The use may then copy, delete, or add the item to a list of favorites 204, add the item to the catalog 205, specifying item properties 209, add the item to a case 206, specifying the case 212 and case properties 213, export or output the item 207, specifying the format 214, edit information 210, specifying a tool therefor 211, or link the item to other source information 208. Importantly, the user may analyze the information 215 using a document analyzer 216. Such analysis may involve viewing bin elements 217, viewing geometry elements 218 or viewing multiple elements 219. An item is then selected 220 and may be edited 221 using a specified tool 22, added to a case 223, where the case is specified 224, or exported/output 225 in a specified format 226. FIG. 5 is a block diagram of information platform source user set breakdown according to the invention. More specifically, FIG. 5 identifies the flow with regard to client viewing and manipulation of user sets 250. This operation is discussed in greater detail below. The user may either view user sets 260 or create/add an item 270. If the user views user sets 260, the user may sort the sets on a specific property 261 or filter the sets on properties 262, choose and item 263 and either view the sets, edit set properties, import or output a set, duplicate a set, or share a set 264; or organize the set 265 and either move the set to a folder or copy the set to a folder 266. If the user creates/adds an item 270, the item may be either a folder 267 or a set item 268, both of which allow the user to set properties and/or locations for the item 269. FIG. 6 is a block diagram of information platform favorites breakdown according to the invention. More specifically, FIG. 6 identifies the flow with regard to client viewing and manipulation of favorites 2880. This operation is discussed in greater detail below. The user may either vie favorites 281 or create/add and item 282. If the user views favorites 281, an item is chosen 283 and the user may either view the sets, edit set properties, import or output a set, duplicate a set, or share a set 284; or organize the set 285 and either move the set to a folder or copy the set to a folder 286. If the user creates/adds an item 282, the item may be either a folder 287 or a favorite item 288, both of which allow the user to set properties and/or locations for the item 291. With regard to the favorite item, the user also may select from a blank favorite 287 or a current favorite 290. FIG. 7 is a block diagram of information platform user account breakdown according to the invention. More specifically, FIG. 7 identifies the flow with regard to client viewing of user account information 300. This operation is discussed in greater detail below. The user account information includes account information 301 and subscriptions 302. For the account information, the user chooses a property 303, specifying such items as name, server, log-in, password, group(s), and rights 304, each of which may be edited 305. For subscriptions 302, the subscription may be a group subscription 306, where the group account properties may be viewed 308; or it may be an individual subscription 307. For an individual subscription, the user may create a subscription 309, for example using an account wizard 310, providing set-up information 311, including subscription type, connection type, location, user name, log-in, password, access limits, and areas or topics (312). The user may also view an existing account 313 by choosing the account 314, which allows the user to view the account properties 315, such as subscription name, connection type, location, user name, log-in, password, access limits, and areas or topics (316). the information may be edited 317 as appropriate. FIG. 8 is a block diagram of information platform editing a catalog breakdown according to the invention. More specifically, FIG. 8 identifies the flow with regard to catalog editing 320. This operation is discussed in greater detail below. When editing a catalog, a user may either add an item 321 or select an item 322. Items that may be added include folders 323, collection items 324 which have specified properties 325 and locations 326, and package items 327. When selecting an item 322, the user may either copy the item or duplicate the item 328, view item properties 330 and edit those properties 331, move the item 329, or view a script 332, and also edit the script 333. Table 2 below lists some of the tasks performed by the users.
TABLE 2
__________________________________________________________________________
User Tasks
Domain
Task Description Steps & Entries
__________________________________________________________________________
Basic <Example> Retrieve all the press
Open catalog
Information
Use the information platform
releases issued in June by
Choose documents (press
Retrieval
client to get a specific
Apple, Microsoft, Intel and
releases
nugget of information
Aeneid. Enter company names
Select get now
View collected information
Select a profile for rapid
For example, the user may
comprehensive data gathering
enter a company name and
then be presented with a rich
body of information that was
(semi)automatically gathered.
Use the information platform
Retrieve, for example, all the
client to get a specific nugget
press releases issued in June
of information
by four companies.
Add a piece of data to an
While working in Excel, the
Excel spreadsheet.
user may add some data from
a SEC 10K, for example. The
user chooses "Insert
Information" from the
information platform menu
and then select what informa-
tion to retrieve, and where to
place it. The metadata (iden-
tifying information source) is
added as a note to the work-
sheet.
Add a piece of data to a Word
document
View the information down-
load log, and use it to search
for a specific piece of infor-
mation.
View the Retrieval Queue.
This is similar to viewing a
network printer queue. The
queue identifies what jobs
are pending, who submitted
them, the priority, and the
data to be retrieved.
Advanced
Run an analysis
Information
Create a bibliography/sources
Retrieval
document as foundation of a
research project
Create an information
Controls what information is
retrieval job
retrieved, how frequently it
should be retrieved, and
where the information is
stored.
Catalog
Add an internal data source
Management
to the catalog
Modify the classification of a
data source
Browse the catalog looking
for the types of information
Add a new set of classifica-
tions to the catalog
From Explorer, add a site to
the catalog
From Explorer, add a page to
the catalog
Define the geometry of an
unknown page to allow for the
intelligent gathering of
elements of the page
Configure the team's custom
Setting the competitor list by
relationships and interests.
market segment, configure the
most influential companies in
each market segment, rating
of value, influence and
accuracy of all information
sources.
Create a custom analysis
Configure the preferred sites
The customer is able to define
to gather specific information.
where to go for information
when the system includes
multiple potential sources.
The user should also be able
to set a "get from the
cheapest" option when
multiple are available
User/System
Configure individual user
Management
rights
Configure rights for a group
Rights include the ability to
add/edit/delete sites, users,
groups, profiles; access to
sites; controls which elements
of the resource catalog are
accessible.
Add a user to a group
Using NT services
Add/View/Modify/Delete the
Site location, user, password,
site list which details the
configuration and logon
details for secure/subscription
sites.
View the activity log
Control which activities are
logged
Control how often catalog
updates are accepted.
__________________________________________________________________________
Client Design Introduction. The various components that make up the information platform offer the user of the platform a host of functionality in an integrated, seamless information environment. To discuss the concepts and functionality of these components, the following discussion maps out the various capabilities of each. Client Interface Design. The client application must be able to incorporate the various controls in an integrated manner. In addition, there must be document display support, navigation, searching, and printing capabilities. Installation. There is a Windows installation application that installs all the necessary components on the user's system as well as locate the database that is used for Catalog information storage. The user is able to specify where the components are located and various installation settings during the installation process. Upon launch of the installer, the application determines if current or previous versions of the application or components are installed on the user's system. If components are detected, the user is informed that some components are installed and the application installs or updates the required components. The user has the choice of completing a Typical or Custom installation. User Accounts. During installation, the user selected a server that stores the Catalog and Case information. The user also may have selected an existing user account that was created on the server for them to use. If the account is not available at installation, the user is prompted to select an account when the application is first launched. Once the user has installed the appropriate components, the application can be launched and the user is automatically logged into their user account using the stored user information. The user enters their user password each time the system is launched to access the system. Global Elements. Navigation. There is a navigation support built into the information platform client. History Tracking and Access. Viewing and selecting from history of interactions; History includes location, controls, entries; Integration with the Windows' system history; and Viewing history across sessions. ARL Encoding and Display. Navigation to specific elements; Show the path, ARL, URL, other information about path; Use a Open (Point interaction or allow free form typing, or both. Progress Information Feedback. Navigation to a location or data item; Anytime the system is busy in a foreground task, animation and status feedback is necessary; Background tasks, like queued retrieval or updating, should be viewable but not prominent Menus The menu consists of File, Edit, Tools, History, Favorites, and Help. In the following tables, menu separators are shown as double lines between table cells.
TABLE 3
______________________________________
File Menu
Menu Item
Function
______________________________________
New ( Cascades to the following items . . .
Case . . .
Displays the New Case dialog, allowing the user to create a
new blank Case or a new Case from a template.
Objective
Creates a new Objective in the current case. If the user has
an Objective folder selected, then the new Objective is
created in that folder, otherwise it is created at the top
level.
Case Item
Creates a new Case Item from the currently displayed item.
Search Item
Creates a new Search Item, opening the Search Catalog for
the user to choose a search.
User Set
Creates a new User Set item, allowing the user to enter the
Item item properties.
Favorite
Creates a new Favorite for the currently selected item, this
item can be a location (like a web site, database, document,
local folder), Case element, or Catalog element.
Folder Creates a new folder in the item that has focus. The items
that can have the focus are: in the Case control, Objectives,
Case Items, Search Items; in the User Sets control, the
control itself (top level) or a Set Folder; in the Favorites
control, the control itself or a Favorites folder; in the
Catalog, the various levels within the hierarchy.
Open ( Cascades to the following items . . .
Item Opens the currently selected item, usually a folder or file.
Case . . .
Displays the Open Case dialog box.
File . . .
Displays an Open File dialog box, which allows the user to
open a file.
Location . . .
Displays an ARL entry dialog box for the user to enter a
location to open.
Save ( Cascades to the following items . . .
Item As . . .
Displays a Save As dialog for the currently displayed
information. The user can save the item as a file in the
following formats: MS Word (*.doc); MS Excel (*.xls);
plain text (*.txt); Web page (*.html); or MS PowerPoint
(*.ppt).
Case As . . .
Displays the Save Case As dialog, allowing the user to save
the Case as a new Case of as a Case template.
Page Displays the system Page Setup . . . dialog to allow the user
Setup . . .
to set printing options.
Print . . .
Prints the currently displayed item using the system Print
dialog and print drivers.
Delete Deletes the currently selected file or item.
Rename Selects the name of the currently selected item for editing.
Properties
Displays the properties of the currently selected item.
Exit Exists the application.
______________________________________
Toolbars Controls. The various components that make up the information platform offer the user of the platform a host of functionality in an integrated, seamless information environment. To discuss the concepts and functionality of these components, the following maps out the various capabilities of each. Cases Control. The Case is center of the information platform environment, it is the home base for the user to compile and review the information space that satisfies their business intelligence needs. The Cases control allows the user to set objectives, collect and review information for an individual Case, and manage multiple Cases. The elements of a Case are: Title, uniquely identifying the Case; Properties, defining the Case; Objectives, items to be fulfilled for the Case; Case Items, the information items that fulfill the Objectives; and Search Items, the results from source searches. The Cases Control uses the Hierarchy and Filtering List controls to display some of its elements. The Objectives, Case Items, and Search Items are all displayed in a combination hierarchy and list. Case Elements Case Title. The Case Title is a user defined text field, up to 256 characters, titling the Case. The user can directly enter the title of the case in the field, and the user can retitle the Case at any time. When the user retitles a Case, if there is a Case that already has the specified title, the user is prompted to replace the old Case with the current one or title the current Case using a different title. In a multi-user environment, the titling of the Case is limited to those with Ownership or Authorship status only. Properties. Each Case has a set of properties that can be reviewed by the user. The user can edit some of these properties (*), others are produced and updated by the system. Table 9 below identifies these properties.
TABLE 9
______________________________________
Case Properties
Property
Description
______________________________________
Icon Iconic representation for the Case <may be different for
shared, user is owner, user is author>
Title* Title for Case, user defined
Description*
User defined text
Date & time
System set time stamp
created
Date & time
System updated time stamp
last modified
Owner* User name of current Case owner
Last User name of last person to modify the Case
modifier
Base Template used in creation, if any
Template
Case Set of Case types that the Owner can select from when
Categories
initiating or editing the case; is predefined for templates,
but still can be edited by Owner*
Security/
The security, access rights setting for this user
access
rights*
Sharing Sharing settings for other users; if this user is the Owner,
then can be edited
______________________________________
The user can edit the Title, Description, Owner, Categories, and Security settings. In a multi-user environment, editing these properties is limited to user with Ownership or Authorship status, except for Owner and Security properties, which can only be edited by the Owner or Aeneid Platform Administrator. If the current user is the Owner, then the Sharing settings for other users can be edited. If the user is not the Owner, it is disabled. Objectives. The objectives are akin to a list of tasks that the user completes to gather the appropriate information to satisfy a Case. These objectives are represented as a list of items, which are user defined or can be initially from a template. The status for each objective, and set of objectives, is user controlled, and not automated or updated by system. Each objective has detailed properties associated with it; these properties are set forth in Table 10 below.
TABLE 10
______________________________________
Objective Properties
Property Description
______________________________________
Fulfillment Status
A check box which indicates the task is fulfilled
Icon Iconic representation for the Objective
Description A description of the task up to 250 characters
Due Date The date the task should be completed
Status Selection from a combo box with the following
values: Not Started; In Progress; Completed;
Waiting on Someone Else; Deferred
Priority Selection of: High; Medium; Low
Percentage Complete
0-100
Owner One of more Troy users, or Not Assigned
______________________________________
These fields correspond with the Microsoft Outlook Tasks. The information platform supports the transfer of items to Outlook; this allows the user to see the case tasks in the context of other cases, and tasks which are not information platform tasks. This mitigate the need for a user to see a list of all their cross case objectives within the information platform itself. The user maintains each of these properties. In a multi-user environment, all users with Ownership or Authorship status can edit these items. The items can be viewed, edited, added, or removed from a Case. The user can also move objectives from one Case to another. Organizing Objectives. The user can create folders and sub-folders to organize the Case Objectives. These are viewed in a hierarchical tree of items, which the user can navigate. Selection of a folder displays the contained sub-folders and Objectives in the list. When a sub-folder is displayed in the list, its associated properties are displayed. The properties for an objective folder are shown below in Table 11.
TABLE 11
______________________________________
Objective Folder Properties
Property Description
______________________________________
Fulfillment Status
A check box which indicates that all the
objectives within the folder are fulfilled
Icon Iconic representation <folder>
Description A description of the folder up to 250 characters
Due Date <no entry>
Status <no entry>
Priority <no entry>
Percentage Complete
<no entry>
Owner <no entry>
______________________________________
The user can choose to view all the Objectives for a Case, or all the Objectives below a specified level, by right clicking on a level and choosing List All Contained Items (the specific implementation of this is to be determined). The selected folder remains selected, however, the hierarchy control is disabled and the list displays all the items in that folder and all contained sub-folders. The user can re-enable the hierarchy navigation by right clicking on the hierarchy and choosing List This Level Only. Filtering & Sorting the Objectives. The display of the Case Objectives uses the Filtering List control. This control allows the user to view a list of items and their associated properties, sort the list in an ascending or descending order based on a selected property, and filter the list on property criteria. The Case Objectives (see Table 12 below) are listed with their properties. Each property can be used for sorting the list of Objectives and can be used to filter the list.
TABLE 12
______________________________________
Case Objectives
Property
Logical operators
Filter options
______________________________________
Fulfillment
Is Selection of: Fulfilled; Not fulfilled
Status Is not
Contains*
Starts*
Ends*
(*text entry only)
Icon <no filtering allowed>
Description Text entry
Due Date Date entry; fielded entry box <or
Selection of: Past Due; Not Yet Due;
Due Today; Due Tomorrow; Due This
Week>
Status Selection of: Not Started; In Progress;
Completed; Waiting on Someone Else;
Deferred
Priority Selection of: High; Medium; Low
Percentage Numeric entry of 0-100 <or Selection
Complete of: 0%; 0-25%; 26-50%; 51-75%; 76-
100%>
Owner Text entry
______________________________________
Case Items. The Case Items are the information items that satisfy the Case Objectives. These items can represent one of two things: a collection item from the Catalog that needs to be fulfilled; or an information item that contains data. The collection items have an unchecked Collection Status property, while the information items have a checked Collection Status. Additionally, there is a different iconic representation for each type of item. The Case Items are displayed in a list with each item's associated properties. The properties that are associated with a particular Case Item are shown below in Table 13.
TABLE 13
______________________________________
Case Item Properties
Property Description
______________________________________
Collection Status
A check box, indicates if item is collection item or
information item (information item is checked); the
application manages the status of the item
Icon Iconic representation of the item
Name The name of the Case Item
Description
The item description, inherited from the Catalog
collection item it was created from
Criteria The criteria for fulfillment
Progress Selection from a combo box with the following values:
Collected; In Collection Queue; Waiting for Collection
Timing; Deferred; Paused; Partially fulfilled; Error -
unable to fulfill.
Categories
The selected item categories: for example, financial;
press release; corporate; product review.
Information Type
Retrieved type of data: document; financial data; table.
Input Type
The type of input needed to retrieve: company name;
SIC code; product name; product type.
Source The source the information is, or will be, collected
from
Source Type
The type of source: web site; subscription; local;
intranet.
Collection Timing
Setting showing when the information is fulfilled, for
example: immediate; cheap rate; after 5 PM; weekend.
Date & Time
When the item was collected, if fulfilled
Author User who set the collection item or added the informa-
tion item
______________________________________
Organizing Case Items. Case Items can be organized into folders and sub-folders, using the Hierarchy and Filtering List controls. The folders and sub-folders are viewed in a hierarchical tree, which the user can navigate. Selection of a folder displays the contained sub-folders and Items in the list. When a sub-folder is displayed in the list, its associated properties are displayed. The properties for a Case Item folder are listed below in Table 14.
TABLE 14
______________________________________
Case Item Folder Properties
Property Description
______________________________________
Collection Status
A check box, indicates if items in the folder are all
fulfilled; the application manages the status of the item
Icon Iconic representation <folder>
Name The name of the folder
Description
<no entry>
Criteria <no entry>
Progress <no entry>
Categories
<no entry>
Information Type
<no entry>
Input Type
<no entry>
Source <no entry>
Source Type
<no entry>
Collection Timing
<no entry>
Date & Time
When the folder's items were completely fulfilled
Author <no entry>
______________________________________
The user can choose to view all the Items for a Case, or all the Items contained in a specified level, by right clicking on the level and choosing List All Contained Items. The selected folder remains selected and the hierarchy control disables and the list displays all the items in that folder and all contained sub-folders. The user can re-enable the hierarchy navigation by right clicking on the hierarchy control and choosing List This Level Only. Filtering & Sorting Case Items. The display of the Case Items uses the Filtering List control. This control allows the user to view a list of items and their associated properties, sort the list in an ascending or descending order based on a selected property, and filter the list on property criteria. The Case Items are listed with their properties. Each property can be used for sorting the list of Items and can be used to filter the list (see Table 15 below).
TABLE 15
______________________________________
Case Item Properties
Property
Logical operators
Filter options
______________________________________
Collection
Is Selection of: Collected; Not Collected
Status Is not
Contains*
Starts*
Ends*
(*text only)
Icon <no filtering>
Name Text entry
Description Text entry
Criteria Text entry
Progress Selection of: Collected; In Collection
Queue; Waiting for Collection
Timing; Deferred; Paused; Partially
fulfilled; Error - unable to fulfill
Categories Selection of items' categories, for
example: financial; press release;
corporate; product review
Information Selection of items' types: document;
Type financial data; table
Input Type Selection of items' types: company
name; SIC code; product name; product
type
Source Text entry
Source Type Selection of items' types: web site;
subscription; local; intranet
Collection Selection of items' timings: immediate;
Timing cheap rate: after 5 pm; weekend
Date & Time Date entry; fielded entry box
Author Text entry
______________________________________
Viewing Case Items. Case Items are either collection items or information items. Collection items are added from the Catalog or are supplied from the Catalog as part of a Case template. These items have collection criteria associated with them that the user can view and edit. Selecting the Case Item in the list displays the collection criteria for the user to review and edit. These include some of the properties that are associated with the Case Item. Information items can be items that were added from the Catalog as collection items and are now fulfilled, items that were added directly from information sources while browsing, or items transferred from other Cases. These items have the same properties as the collection items, however, the Status is fulfilled, Progress is collected, and Collection Timing cannot be changed. Selecting the Case Item in the list displays the information that was collected. Editing Case Items. The user can edit the Case Item properties as well as the content. When the Case Item represents an unfulfilled collection item, the content is the collection settings. When the Case Item represents a fulfilled information item, the content is the collected data. Editing Properties. The user can edit the properties of a Case Item directly in the list control or by selecting the item and choosing Properties from the menu. In the list control, the user can choose a property setting for an item and change its setting. If the property is a free from text entry, the user can select and edit the text. If the property has a limited number of possible settings, those settings can be chosen from a drop down list. If the setting requires complex interaction, the user can choose the setting and click on an ellipse (. . . ) button to open a dialog to change the settings. If the user chooses Properties from the menu, the user is presented with a Property Sheet dialog for the item. Within this dialog, the user can change the property settings for the item. Editing Collection Settings. If the Case Item is a collection item that has not yet been fulfilled, clicking on it displays the collection settings associated with that item. The user can change the settings and the item is automatically updated. This interaction is the same as when the user first added the item to the Case. Editing Collected Data. Once the Case Item has been fulfilled, clicking on it displays the collected information. The user can edit this information directly using in-place activation. Adding Case Items. Case Items are added the user from interaction with the Catalog, by selecting New (Case Item from the menu, adding directly from a source, or by copying and pasting from another Case. Search Items The Search Items are source searches using the Search Catalog, and are intended to allow the user to perform limited scope searching. Similar to the Case Items, these items can represent one of two things: a search item from the Search Catalog that in the process of fulfillment; or a results item that contains returned search results. The former have an unchecked Completion Status property, while the latter have a checked Completion Status. Each has a different iconic representation. The Search Items are displayed in a list with each item's associated properties. The properties that are associated with a Search Item are shown in Table 16 below.
TABLE 16
______________________________________
Search Item Properties
Property Description
______________________________________
Completion
A check box, indicates if item is a search item or a
Status search results item (results are checked); the applica-
tion manages the status of the item
Icon Iconic representation of the item
Name The name of the search item
Description
The item description, inherited from the Search
Catalog item it was created from
Criteria The criteria for fulfillment
Progress Selection from a combo box with the following values:
Collected; In Collection Queue; Waiting for Collection
Timing; Deferred; Paused; Partially fulfilled; Error -
unable to fulfill.
Source The source(s) the information was, or will be,
collected from
Source Type
The type(s) of source(s): web site; subscription; local;
intranet
Search Timing
Setting showing when the information is fulfilled, for
example: immediate; cheap rate; after 5 pm; weekend
Date & Time
When the search was completed, if fulfilled
Author User who set the collection item or added the informa-
tion item
______________________________________
Organizing Search Items. Search Items can be organized into folders and sub-folders, using the Hierarchy and Filtering List controls. The folders and sub-folders are viewed in the hierarchical tree, which the user can navigate. Selection of a folder displays the contained sub-folders and search items in the list. When a sub-folder is displayed in the list, its associated properties are displayed. The properties for a search folder are shown in Table 17 below.
TABLE 17
______________________________________
Search Folder Properties
Property Description
______________________________________
Completion Status
A check box, indicates if item if all contained
items are completed; the application manages the
status of the item
Icon Iconic representation <folder>
Name The name of the folder or sub-folder
Description
<no entry>
Criteria <no entry>
Progress <no entry>
Source <no entry>
Source Type
<no entry>
Search Timing
<no entry>
Date & Time
When the folder search items were all completed
Author <no entry>
______________________________________
The user can choose to view all the Search Items contained in a specified level and its sub-folder, or all the Search Items in a Case, by right clicking on a folder and selecting View All Contained Items from the pop up menu. The hierarchy control disables and all the items at that level and all contained levels are displayed in the list. The user can right click on the hierarchy control and select List This Level Only to re-enable folder by folder navigation of the items. Filtering & Sorting Search Items. The display of the Search Items uses the Filtering List control. This control allows the user t | ||||||
