WO2003032153A1

WO2003032153A1 - Data driven access to categories

Info

Publication number: WO2003032153A1
Application number: PCT/US2002/031322
Authority: WO
Inventors: Jonathan C. Weiss; Ronen A. Botzer
Original assignee: GREY ZONE Inc
Current assignee: GREY ZONE Inc
Priority date: 2001-10-09
Filing date: 2002-10-01
Publication date: 2003-04-17
Anticipated expiration: 2004-04-09

Abstract

A category (or a portion of a pre-determined hierarchy of categories) (142-158) in which an item of information is classified is identified (7), if the item is marked as being published to a user (or to a group of users to which the user belongs) (2). The identification of the category is stored (6), and thereafter used to display the category to the user, to allow the user to access the item, e.g. for viewing, editing or deleting the item.

Description

DATA DRIVEN ACCESS TO CATEGORIES

BACKGROUND

Microsoft NTFS ("NT File System") is a file system used in Windows NT which uses the Unicode character set and allows file names up to 255 characters in length. NTFS uses Access-Control Lists ("ACLs") to control access to objects (e.g., files and directories) by users. An ACL is a list of access-control entries ("ACEs"). Each ACE in an ACL identifies a user (i.e., a user account or user group) and specifies the access rights allowed, denied, or audited for that user. In particular, a securable object in NT contains a discretionary access-control list ("DACL") associated with the object for purposes of negotiating access to the object. A DACL identifies the users that are allowed or denied access to a securable object. When a process tries to access a securable object, the system checks the ACEs in the object's DACL to determine whether to grant access to it. If the object does not have a DACL, the system grants full access to everyone. If the object's DACL has no ACEs, the system denies all attempts to access the object because the DACL does not allow any access rights. The system checks the ACEs in sequence until it finds one or more ACEs that allow all the requested access rights, or until any of the requested access rights are denied.

Using a DACL, a number of permission levels may be specified for the user, i.e., a particular user account or user group (e.g., a "Windows Guest" user group). The permissions include:

• Full control. The user can modify, add, move and delete files, and their associated properties, and directories. The user may also change permission settings for all such files and directories.

• Modify. The user can view and modify files and file properties, including deleting and adding files to a directory or file properties to a file.

Read and Execute. The user can run executable files, including scripts. List Folder Contents. The user can view a list of a folder's contents. Read. The user can view files and file properties. Write. The user can write to a file. • No access. The user has no access to the object, even if the user has access to a higher-level parent directory.

Thus, in NTFS, secure objects — such as a MS Word document — include an associated DACL specifying a list of user accounts or user groups wherein each user account or user group includes an associated permission relating to how the respective user may access the secure object. The file system automatically negotiates access to the DACL protected object for each user, and additionally offers authentication processes. Additional information relating to NTFS may be accessed at http://www.windows.com.

SUMMARY

A method and system implemented by a computer identifies a category in which an item of information (also called "data") is classified, if the item is marked in the computer as being accessible (e.g. viewable) by a user (or to a group of users to which the user belongs). After identifying the category, the computer stores in a storage medium, an association of the category with the user (or alternatively with the group of users). In some embodiments, based on the stored association (described above) the user accesses the item via the category. Depending on the embodiment, a number of such categories (and optionally any number of additional categories in which the just-described categories are classified) are displayed to the user, so that different users see different portions of a predetermined hierarchy of categories. The additional categories may have items classified within them, which the user may additionally access (which access may or may not be based as one or more stored associations, depending on the embodiment).

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 is a flow chart illustrating a method of identifying a category within which an item is classified, according to some embodiments of the present invention.

Fig. 2 is a block diagram illustrating a data organization on a storage medium supporting the method of Fig. 1 compatible with some embodiments of the present invention.

Fig. 3 is a screenshot illustrating an item and a category compatible with some embodiments of the present invention.

Fig. 4 is a flow chart illustrating additional processes in the method described in Fig. 1, according to some embodiments of the present invention.

Fig. 5 is a block diagram illustrating a relationship between groups and users according to some embodiments of the present invention.

Fig. 6 is a block diagram illustrating an example category hierarchy compatible with some embodiments of the present invention. Fig. 7 is a flow chart illustrating the method of Fig. 1 applied to the processing of multiple categories and items, according to some embodiments of the present invention.

Fig. 8 is a diagram chart illustrating a data organization on a storage medium supporting the method of Fig. 7 compatible with some embodiments of the present invention.

Fig. 9 is a block diagram illustrating a system for creating, publishing and classifying items compatible with some embodiments of the present invention.

Fig. 10 is a flow chart illustrating a method of publishing items to groups and classifying the items in a category hierarchy, according to some embodiments of the present invention.

Fig. 11 is a flow chart illustrating a method for identifying a user hierarchy compatible with some embodiments of the present invention.

Fig. 12 is a flow chart illustrating in more detail the method of Fig. 11, according to some embodiments of the present invention.

Fig. 13 A-C are block diagrams illustrating different user hierarchy portions of a category hierarchy compatible with some embodiments of the present invention.

Fig. 14 is a block diagram illustrating the process of dynamically determining a user hierarchy according to some embodiments of the present invention.

Fig. 15 is a block diagram illustrating the hardware components compatible with some embodiments of the present invention.

Fig. 16 is a block diagram illustrating a networked environment in which some embodiments of the present invention may be implemented.

Fig. 17 is a block diagram illustrating the software components compatible with some embodiments of the present invention.

Fig. 18 A is a flow chart illustrating a method of providing user interaction with categories and items via the user hierarchy, according to some embodiments of the present invention. Fig. 18A-1 is a block diagram of category hierarchy used to describe the method of Fig. 18, according to some embodiments of the present invention.

Figs. 18A-2 and 18A-3 are screenshots illustrating the stages of Fig. 18 A, according to some embodiments of the present invention.

Fig. 18B-18C are flow chart illustrating additional processes to the method of Fig.

18A compatible with some embodiments of the present invention.

Figs. 18C-1 and 18C-2 are screenshots illustrating the method of Fig. 18C, according to some embodiments of the present invention.

Fig. 19A is a flow chart illustrating the method of Fig. 1 implemented using database queries, according to some embodiments of the present invention.

Fig. 19B is a flow chart illustrating additional processes to the method of Fig. 19A, according to some embodiments of the present invention.

Fig. 20 is a block diagram illustrating a data organization on a storage medium supporting the methods of Fig. 19A-19B, according to some embodiments of the present invention.

Fig. 21 A-21B are flow charts illustrating a method of associating permissions with items to control user access to the items, according to some embodiments of the present invention.

Fig. 21 C is a block diagram illustrating a data organization on a storage medium supporting the methods of Fig. 21 A-21B, according to some embodiments of the present invention.

Fig. 21D is a block diagram illustrating in more detail an intersection table described in Fig. 21C compatible with some embodiments of the present invention.

DETAILED DESCRIPTION In accordance with the invention, privileges in a programmed computer are provided to users based on the specific items of content to which they have access. In one embodiment, the privileges are related to the user's access to categories in which the items are classified, as discussed herein. In another embodiment, the privileges are related to tools for creating, and/or editing and/or viewing the items, as discussed in detail in related application entitled "DATA DRIVEN ACCESS TO TOOLS," Attorney Docket No. M-12171 US filed concurrently by the same inventor, which is incoφorated by reference above. The just-described two embodiments have a common theme: namely, the provisioning of system-level access privileges based on access to individual items of content (or data). In an implementation of the tools embodiment, access to tools is granted based on editorial privileges to specified items of content. An example of this form of access provisioning would be granting access to a user for Adobe Photoshop (which is a tool) simply by giving access to the user to an editable Photoshop file (e.g. by sending the file via e-mail as an attachment or by sending a link to the file or copying the file to the user's directory or copying the file to any directory to which the user has access). In an implementation of the categories embodiment, access to categories is granted based on view privileges to such items. An example of this form of provisioning would be giving the user access to a directory (which may be modeled by a category), based on the user having been given access to an item contained in the directory.

In some embodiments of the present invention, a computer (having at least a processor, volatile memory and non-volatile memory) is programmed to execute computer instructions for performing operations described by stages in a method 5 illustrated in a flow chart (also called "flow diagram") in Fig. 1. The computer when executing the computer instructions implementing an embodiment of the present invention is hereafter referred to as the "System." Turning to Fig. 1, in the first stage

(stage 2) the System determines whether an item of information stored in the computer or accessible by the computer from another device is marked as being accessible by (e.g. viewable by) a group to which a user of the System (hereafter "user") belongs. Depending on the embodiment, the marking may indicate that the user has view access (and may or may not have edit access) to the item. Moreover, the marking may be done at the time the item is created, e.g. by a user that creates the item, i.e. when the item is published.

If the System determines that the item is marked for access by the user, then in the next stage (stage 4) the System identifies a category in which the item is classified. In the last stage (stage 6) the System stores data in a storage medium 20 (Fig. 2) associating the user with the following elements: the item, the group to which the user belongs and to which the item is published, and the category under which the item is classified. The data associating the user with the aforementioned elements (group, item, and category) shall be hereafter referred to as "associated data". In certain embodiments, categories of the type described herein are devoid of access permissions at the category level, and only item-level permissions are used to determine the categories displayed to a user. In such embodiments, the user may see any category and parent category needed to navigate to an item to which the user has access. In an alternative embodiment, categories also have access permissions, which are in addition to item-level permissions, and both kinds of permissions are used to limit a user's ability to access an item.

In one example in which only item-level permissions are used, an organization has an office in San Francisco, and a new employee has joined the San Francisco office as a Sales Director. A news release about this employee, entitled "June 22, 2001 -New Sales Director" is one of a number of items that are present in (or otherwise available to) the System, and this item has been classified into a category labeled "San Francisco Office". In this specific example, the news release is published to a specific group of users namely "San Francisco Employees", and at the time of publication an identifier of the press release "June 22, 2001 -New Sales Director", the group "San Francisco Employees", and the category "San Francisco Offices", are stored in non-volatile memory (e.g. a database in a hard disk) as illustrated by the associated data 25 in Fig. 2 (described below).

In performing method 5 (FIG. 1) in this example, the System checks whether the item is marked as being published to a group to which a user belongs, e.g. determines that a specific user that the System is currently interacting with is a member of the group "San Francisco Employees". Thereafter, in stage 4 (FIG. 1) the System identifies the category "San Francisco Offices" and thereafter stores in stage 6 an association of the group "San Francisco Employees" and the category "San Francisco Offices" with the user in non- volatile memory (e.g. in a flat file in a hard disk).

In some embodiments, associated data 25 may be organized in storage medium 20 using data structures and data storage techniques of the type that will be apparent to the skilled artisan in view of the disclosure. In some embodiments, for example, the System uses a table 22 (based on associated data 25) in a relational database to form an association among the item, group and category elements during stage 6 (which happens in one embodiment at the time of user's login). In some of these embodiments, the table 22 includes three columns for storing identities (abbreviated "IDs"), namely an item ID 24, a group LD 26, and a category LO 28. Such identifiers are used by the System to access the item, group or category from other data structures (e.g. item, group and category tables 30-34).

Accordingly, the user may be associated with a single item, group and category relationship by associating the user with a row, e.g., row 38, in table 22. In some of these embodiments, the System stores data associating a user 36 with all of the groups 35 to which the user belongs; in typical embodiments, for example, data identifying the user is stored in non-volatile memory accessed by a data structure which includes the group IDs of the groups to which the user belongs. The groups 35 are then used to associate the user with a row, e.g., row 38, in table 22 which includes a group LD 26 to which the user belongs. The row, e.g., 38, then identifies the item ID 24 published to the group and the category LD 28 within which the item is classified.

The item, group and category association for the user are stored (stage 6), according to some embodiments of the present invention. In yet other embodiments, table 22 may include the actual category name, group or item, instead of, for example, an ID for the category, group or item. In still other embodiments, the associated data may be stored in a single flat file without a table, so long as the System is programmed to identify the associated elements in the flat file. Because the various embodiments of the present invention are operable with a wide range of data structures and data organizations, certain embodiments are not limited to any particular data structure, or data organization, or type of memory.

The associated data 25 in the storage medium 20 of stage 6 is used by the System in several embodiments of the present invention. In some embodiments, for example, the System sends a link (such as a URL) of item 24B to the user's computer, along with a description of the category 28C under which the item 24B is classified. The category 28B — in some embodiments where the category 28B includes a descriptive label 28C displayed to the user within which the item 24B is classified — informs the user at a glance the importance and meaning of the item 24B to the user.

Fig. 3 illustrates a screenshot of an exemplary category description 28C and item link 24C presented by the System to a particular user in an embodiment of the present invention. The category description "San Francisco Offices" 28C provides ready information and context to the user for purposes of deciding whether to access the item 24B described as "June 22, 2001 - New Sales Director" and identified by the link 24C. Thus, if the user is an employee physically located in the San Francisco Offices, then the

-1- item 24B classified within this category 34 may immediately acquire relevance to the user due to displaying of the category label 28B for the item 24B to the user on the user's display device.

The above-described method 5 (Fig. 1) can be performed in any context, e.g. prior to (or even at the time of) interacting with a user to provide information of interest to the user, depending on the embodiment. In some embodiments of the present invention, the System performs operations in addition to the above-described method 5 (Fig. 1) in additional stages that are illustrated in boxes 70 and 76 in Fig. 4. Box 70 includes two stages — stages 72 and 74 — performed by the System prior to stage 2. In stage 72, the System receives data identifying the user; in some embodiments, the data is received during conventional authentication processes requiring (typically) the user to enter a user ID (such as the user's initials) and a password.

In stage 74, the System identifies each of a number of groups to which the user belongs. In some embodiments, the groups to which a user belongs may be stored in memory accessed by a data structure associating the user ID of the user with the group IDs of the groups to which the user belongs. In typical embodiments, the user may belong to multiple groups. In some embodiments, the user is the sole member of a group, thereby enabling the System to perform processes targeted to an individual user which are otherwise designed for groups of users.

The relationship between groups and users is illustrated in Fig. 5, according to some embodiments of the present invention. In Fig. 5, three groups are illustrated: groupl 90, group2 92, and groupM 94. (The "M" in groupM is intended to signify that any number of groups within computer resource constraints may be implemented in the differing embodiments of the present invention.) Eight users are additionally illustrated: userl through user7 96-108, and userN 110. (The "N" in userN is intended to signify that any number of users may be implemented in different embodiments of the present invention to the extent permitted by the available computer resources.)

Groupl 90 includes the users circumscribed by dashed line 91, i.e., userl to user4 86-102. Group2 92 includes the users circumscribed by rectangle 93, i.e., userl 96, user3 100, user5 104, and user7 108. GroupM 94 includes the users circumscribed by the dashed line 95, i.e., userό to userN 106-110. Accordingly, for example, user5 104 belongs to a single group: group2 92. User3 100, on the other hand, belongs to two groups: groupl 90 and group2 92. In some embodiments of the present invention, the users are generally known by the system in reference to the groups to which they belong. A single user may be known to the System, as mentioned above, via a group that includes only the single user in some embodiments compatible with the present invention.

Therefore, in certain embodiments, at the time of log in of a user into the System, the System identifies a portion of a predetermined hierarchy of categories, using as the basis for identification, a list of all items to which that user has viewing privileges, a list of all items to which that user has viewing privileges (or a privilege to view and edit) but not items to which there is no view privilege. In such embodiments, box 76 of Fig. 4 includes a single stage (stage 78) performed by the System in replacement of stage 4 in Fig. 1, according to some embodiments of the present invention.

In these embodiments, after the computer determines whether an item is marked as being published to a group (e.g. for view access) to which the user belongs (stage 2), then in stage 78 (Fig. 4) the computer identifies a category in which the item is classified from among a predetermined hierarchy of categories (hereafter "category hierarchy"). An example category hierarchy 128 compatible with the present invention is illustrated in Fig. 6. In the example category hierarchy 128 (the categories 142-160 are shown as bold, unshaded rectangles), the category hierarchy 128 is distributed across seven levels 130-140; each parent-child relationship of categories (i.e., category to sub-category) and each relationship of categories to the items classified within the categories defines two levels. Thus, the category hierarchy 128 includes seven levels 130-140 as illustrated in Fig. 6 (note that the last level 140 is being defined by the items classified within the "leaf category 160). One or more of the categories thus identified may be empty of items, but are identified uniquely as empty passageways to subcategories that contain items viewable by the user.

In some embodiments of the present invention, the categories 142-158 in the category hierarchy 128 form a tree structure, e.g., the "general" category 148, includes a parent category, e.g., the "news" category 144, and one or more categories classified within it (the "news" category 144), e.g., the "employees" category 156. In such a tree structure, "leaf node" categories, e.g., 150, 160, 158, and 154, do not have any categories classified within them as a matter of definition. The "root" category, e.g., 142, likewise does not include a parent category as a matter of definition. Each (child) category classified within a (parent) category lies at a lower level in the category hierarchy relative to the root category "home" 142. Thus, the "general" category 148, being a child of the "news" category 144, lies at level 134 while the "news" category 144 lies at level 132.

It should be noted that the category hierarchy 128 defined by, in this example, the "root" category 142 (i.e., the "home" category) may itself be, in some embodiments, merely a branch in a larger tree structure within the computer, e.g., the "home" category 142 may itself be a child of a higher-level category (not shown). Such higher-level categories may be used by an operator of the System to manage items of multiple unrelated organizations that are clients of the operator. When used in this manner, a user of an organization has access only to one higher-level category assigned to the organization but not to higher-level categories that may be assigned to other organizations.

As used herein, an "intermediate" category refers to a category lying in a branch of the predetermined category tree 128 connecting a category within which an item is classified to the root category; thus, an intermediate category is defined relative to a particular item within the relevant category hierarchy. In Fig. 6, for example, an item 2 164 at level 136 is classified within the "general" category 148. The "general" category 148 is in turn classified within the "news" category 144. As a result, the "news" category 144 operates as an intermediate category connecting the root "home" category 142 to the "general" category 144, thereby enabling the category tree 128 to be generated from the root category ("home" category 142) to item 2 164. Some intermediate categories may or may not contain items, depending on the example. As noted above, even intermediate categories that are empty may be useful as passageways to subcategories.

As additionally illustrated in Fig. 6, each category 142-160 may include any of the following elements classified within it: an item, a category, or an intermediate category. As used herein, a "top-level" category refers to one or more categories at the highest level in the category hierarchy within which the System is programmed to classify an item, for a given organization. Thus, for example, if the item is classified within the "home" category 142 in category hierarchy 128, then the "home" category 142 operates as a single "top-level" category within the category hierarchy 128 (because there are no other categories). If, however, items may not be classified within the "home" category 142, but the System is programmed instead to classify items within categories further down the nodes of the category hierarchy 128 beginning at level 132, then the "news" category 144 and the "departments" category 146 operate as the top-level categories within the category hierarchy 128.

It should be noted that differing embodiments of the present invention are compatible with category hierarchies having a non-tree structure, e.g., a given category may have more than one parent category. It should also be noted that a category

"hierarchy" comprising a single category is compatible with some embodiments of the present invention, as well as a category "hierarchy" comprising multiple hierarchies. Even categories operating as top-level categories within the System may be positioned at different levels with the category hierarchy. In general, those skilled in the art will recognize that different embodiments of the present invention may be implemented using a diverse range of category organizations, and that certain embodiments are not limited to a particular category organization.

In some embodiments of the present invention, the System performs the method 5 of Fig. 1 for a number of categories and for a number of items; these additional stages (box 200) are illustrated in method 198 in Fig. 7. Thus, after the System stores the associated data (i.e., data associating an item, a group to which the user belongs, and a category in which the item is classified with a user) in a storage medium (stage 6), then in stage 202 the System determines whether the item is classified within additional categories in the category hierarchy. If the item is classified in additional categories, then in stage 204 the System identifies one of the additional categories. After identifying the additional category in stage 204, control returns to stage 6 in which the System stores the new data association (of item, group and category with the user) in a storage medium 20.

Stages 6 and 202-204 (Fig. 7) are repeated until all of the categories within which the item is classified are identified. After identifying all of the aforementioned categories for the item, then in stage 206 the System determines whether there are additional items marked as being published to a group (e.g. for view access) to which the user belongs. If the System determines that additional items exist, then in stage 208 the System identifies an additional item and process returns to stage 4. In stage 4, the System identifies the category in which the additional item is classified. Stages 6 and 202-204 are then repeated for the new item, resulting in identification of all of the categories within which the new item is classified. Repetition of stage 4-6 and 202-208 results in identification by the System of each item published to a group to which the user belongs, as well as identification of each category within which each of the identified items is classified. In addition, the System generates and stores the associated data for the user, including the categories within which each of the aforementioned items is classified, in the storage medium 20. As noted above, in some embodiments any number of additional categories within which the identified categories are present are also identified and stored, and this is done recursively until a portion of a predetermined category tree is identified, including a "top-level" category.

In some embodiments of the present invention, data stored during the performance of the stages in Fig. 7 are read from a storage medium 20 as illustrated in Fig. 8. The data structures in Fig. 8 differ from the example data structures in Fig. 2 in that additional rows 226 and 228 are included in table 22 representing multiple associations of items, groups, and categories with the user 36. It should also be noted that an example item content and category description is not illustrated in Fig. 8 for purposes of simplicity. Additional category 226, for example, illustrates an association between an item 1, a group B, and a category N. Row 228, as an additional example, shows an association between item 2, a group A, and a category N+l . The additional rows 226 and 228 include associations to multiple items, e.g., item 1 30 and item 2 220, multiple groups, e.g., group A 32 and group B 222, and multiple categories, e.g., category N 34 and category N+l 224.

Data 36 associating the user to the groups to which the user belongs, e.g., 37, is also shown in which the user is associated with multiple groups, e.g., group A 32 and group B 222. In these embodiments of data storage in storage medium 20, therefore, multiple item-group-category associations may be stored as additional rows in table 22 and multiple entries in, for example, item, group, and category tables (not shown), respectively. Those skilled in the art will recognize that the data associations in the example data structures in Fig. 8 may be equivalently stored in a variety of other differing data structures and that the particular data structure representation in Fig. 8 is not intended as limiting the present invention.

Some embodiments compatible with the present invention, as described in reference to Figs. 1-8, may be implemented within larger system-level embodiments as illustrated, for example, in Fig. 9. In some embodiments of the present invention, System 250 implements processes enabling users, e.g., 96, 98 and 110 to create items of information, publish the items of information to one or more groups of the users, and classify the items of information within one or more categories in a category hierarchy 251. System 250 further enables users, e.g., 100, 106 and 110, to access the items of information via the categories of the category hierarchy 251 (as illustrated by arrow 261).

Fig. 10 shows a method 301 illustrating process stages implemented by System 250 enabling users to create new items of information, publish the items to one or more groups, and classify the items within one or more categories, according to some embodiments of the present invention. In stage 300, the user accesses System 250, and retrieves an information creation tool by which to create a new item of information. In some embodiments, multiple tools — each tool used to create a particular type of content — may be available to the user for item creation. In stage 302, the user creates the item with the tool. In stage 304, the user publishes the newly created item to one or more groups of users. In stage 306, the user classifies the newly created item in one or more categories in the category hierarchy 128.

Process stages illustrated in method 301 are illustrated in reference to System 250 in Fig. 9, according to some embodiments of the present invention. Accordingly, a userl 96 accesses tool 1 254 to create items 1-1 and 1-2 (items in Fig. 9 are illustrated as shaded rectangles). Arrow 260 illustrates process stage 304 in which userl 96 publishes newly created items 1-1 and 1-2 to one or more groups of users. In the particular example of Fig. 9, the userl 96 publishes item 1-1 to groups 1 and 2 90-92, and publishes item 1-2 to groups 1 through N 90-94. Arrow 262 illustrates process stage 306. In the particular example of Fig. 9, userl 96 classifies newly created item 1-1 in a single category — category 1.1 264 — of the category hierarchy 251. Userl 96 also classifies newly created item 1-2 within category 1 266 of the category hierarchy 251. In like manner as userl 96, user2 98 accesses tool 2 256 to create items 2-1 and 2-2. User2 98 then publishes item 2-1 to group2 92, and publishes item 2-2 to group N 94. User2 98 then classifies item 2-1 within category 1.1.1.1 268, and classifies item 2-2 within category 1 266 and category 1.2 270.

Fig. 9 additionally illustrates a userN 110 publishing items to the groups and classifying those items within the categories. In summary, Fig. 9 illustrates a particular example of item creation, publication and classification compatible with some embodiments of the present invention. In particular, box 280 illustrates a particular set of items created by a particular set of tools; box 282 illustrates the groups to which those items are published; and box 128 illustrates the category hierarchy 251 within which those items are classified by users 1-N 96, 98 and 110. In addition, Fig. 9 illustrates how users with distinct group affiliations access items published to them via category hierarchy 251. For example, user3 100 (belonging to groupl 90 and group2 92) accesses (arrow 261) the items within category hierarchy 251 and userό 106 (belonging to group M 94) accesses 261 the items published to group M via the category hierarchy 251.

Process stages implemented by System 250 relating to user access to items via the category hierarchy 128 is illustrated in the flow diagram of Fig. 11, according to some embodiments of the present invention. In Fig. 11, System 250 first executes stages 2, 78 and 6 as described in Fig. 4 above. System 250, after executing processes described by stage 6, next executes processes corresponding to stage 304 for identifying a portion of the category hierarchy 128 available for access by the user (the portion is hereafter referred as "user hierarchy," and may include a single category). Consequently, System 250 denies access to a user to particular portions of the category hierarchy 128 that are omitted during generation of the user hierarchy for the particular user. In stage 306, System 250 stores data associating the user hierarchy with the user in a storage medium.

In some embodiments of the present invention, the process of identifying the user hierarchy for a particular user from the category hierarchy in stage 304 for a single item includes the additional stages described in flow diagram 349 of Fig. 12. In the first stage of flow diagram 349 — stage 350 — System 250 determines from the associated data stored in stage 6 for the item whether the category associated with the item (i.e., within which the item is classified) is a top-level category. If the category under which the item is classified is a top-level category, then process terminates and the user hierarchy consists of the top level category. If the category, however, under which the item is classified is not a top-level category, then System 250 determines the top-level category from which the category is accessed in stage 352.

In stage 354, System 250 determines whether the parent category of the category under which the item is classified is an intermediate category. If System 250 determines that the parent category is an intermediate category, then in stage 356 System 250 determines all of the intermediate categories connecting the top-level category to the category under which the item is classified. At this point, the user hierarchy generated by the System in reference to the single item thus includes the category under which the item is classified, the top-level category from which the item is accessed, and the intermediate categories, if any, connecting the top level category to the category within which the item is classified. If, however, in stage 354 System 250 determines that the parent category of the category under which the item is classified is not an intermediate category (i.e., it is a top-level category), then process terminates, and the user hierarchy identified by System 250 consists of the category under which the item is classified and its parent category (which is a top-level category).

Application of flow diagram 249 for purposes of identifying a user hierarchy is illustrated in reference to Figs. 13A-13C, according to some embodiments of the present invention. Fig. 13 A illustrates the portion of example category hierarchy 128 constituting the user hierarchy 380 for a user who has item 1 162 published to a group to which the user belongs. Item 1 in Fig. 13A is classified under two categories: the "news" category 144 and the "departments" categories 146. Each of these categories 144-146 are in turn classified under the "home" category 142. For purposes of the examples of Figs. 13A-13C, the "home" category 142 is assumed to be the top-level category. Applying the process stages of Fig. 12 to Fig. 13A, in stage 350 the "news" category 144 and the "departments" category 146 are not top-level categories, and therefore process resumes in stage 352.

In stage 352, the system determines that the "home" category is the top-level category from which the "news" category and the "departments" category 146 are both accessed. In stage 354, System 250 determines that the "new" category 144 and the "departments" category 146 are not classified within an intermediate category, but rather within a top-level category — the "home" category 142. The user hierarchy 380 portion of the category hierarchy 128 thus comprises the top-level "home" category 142, and the "news" category 144 and "departments" category 146 classified within the "home" category 142.

In Fig. 13B, the user hierarchy 382 portion of the category hierarchy 128 is illustrated for the case in which item 2 164 is published to a group to which the user belongs. If item 2 is the only item published to a group to which the user belongs, then all of the categories in the category hierarchy 128 are identified as belonging to the user hierarchy 382 accessible to the user except the "accounting" category 154. The "accounting" category is omitted from the user hierarchy 382 identified using the process stages 350-356 because the "accounting" category 154 is neither a top level category, an intermediate category, or a category under which the item (item 2 164) is classified within. It should be noted that a particular category in the category hierarchy 128 may operate as an intermediate or non-intermediate category depending upon the user or the particular user session. Accordingly, the "general" category 148 operates both as a category under which item 2 164 is classified, and also as an intermediate category providing access to the "San Francisco offices" category under which item 2 164 is classified.

Fig. 13C illustrates a user hierarchy 384 portion of the category hierarchy 128 for some embodiments of the present invention in which item 3 166 is published to a group to which the user belongs. In the user hierarchy 384 portion of the category hierarchy 128, the "home" category 142 operates as a top-level category, the "news" category 144 and the "accounting" category 154 operate as categories within which item 3 166 is classified, and "departments" category 146 operates as an intermediate category connecting the "home" category 142 to the "accounting" category 154. Accordingly, performance of the process stages 350-356 in Fig. 12 by System 250 may often result in the identification of different user hierarchies, e.g., 380-384, for each user as a function of the groups to which the user belongs and to which items are published, and the categories within which the items are classified.

In some embodiments of the present invention, the category hierarchy for a particular user is dynamically-determined each time the user accesses the System, typically via a user login and authentication process. In yet other embodiments, the category hierarchy may be dynamically re-determined at periodic intervals to account for items newly published to groups to which the user belongs during, for example, a user's session with System 250. The dynamic-determination of the category hierarchy (also called "user hierarchy" or "user category tree") in some embodiments compatible with the present invention is illustrated in Fig. 14. In particular, the processes implemented by System 250 for generating the dynamically-determined categories for user3 100 and userό 106 within the item publication and classification example of Fig. 9.

Turning to Fig. 14, user3 100 accesses server computer 508 hosting System 250 via one or more login screens (not shown) displayed on display device 504 of the user's computer, typically a remote client. System 250 receives data identifying user3 100 (arrow 522) — e.g., a userlD — and determines the groups (box 512) to which the user belongs; in the example provided in Fig. 9, the user3 100 belongs to groupl 90 and group2 92. System 250 then determines all of the items published to groupl 90 and group2 92 (illustrated as box 524). Box 524 includes a first box 514 and a second box 516; the first box 514 includes four items corresponding to the items published to groupl 90, and the second box 516 includes two items corresponding to the items published to group2 92 (as illustrated in reference to group 292 in box 282 of Fig. 9). System 250 therefore determines each category (there may be more than one) within which each item published to either groupl 90 or group2 92 is classified. System 250 accesses (arrow 526) database 510 which stores data comprising the category hierarchy 128. System 250 then determines (arrow 528) all of the categories (box 518) within which the items published to the groups to which the user belongs (box 524) are classified.

In box 520, System 250 then executes (arrow 519) the process stages in flow diagram 349 (Fig. 12) to generate the user hierarchy 500 using the category list of box 518, the item list in box 514, and the category hierarchy 510. Accordingly, item 1-1 in box 524 is classified, as illustrated in the category hierarchy 128, within category 1.1 530. In like manner, item 1-2 in box 524 is classified within category 1 532. The remaining categories within box 518 are similarly derived from the category hierarchy 128 for each of the remaining items in box 524.

The particular user hierarchy 500 generated by System 250 for user 3 100 is shown displayed in display device 504. As illustrated by the user hierarchy 500, all of the items in box 524 published to groups to which user3 100 belongs are classified within one or more of the categories of the user hierarchy 500. By the same token, categories within the category hierarchy 128 that do not include an item classified within them that is published to a group to which the user belongs (i.e., the item is not in box 524), or that do not provide access to such an item as an intermediate or top level category, is excluded from the user hierarchy 500. Consequently, categories that do not provide access to items accessible by the user (i.e., published to a group to which the user belongs) either directly or as intermediate categories are not only inaccessible to the user, but in some embodiments entirely hidden from the user.

In this example, category 1.2 534 within the category hierarchy 128 is excluded from the user hierarchy 500 for user3 100 because item 2-2 — which is classified within category 1.2 53 — is not published to a group (either group 1 90 or group 2 92) to which the user3 100 belongs (it is published only to group M 94). Conversely, in some embodiments of the present invention, the categories included within the user hierarchy 500 are guaranteed to provide access to items accessible by the user (i.e., published to a group to which the user belongs) either directly or as intermediate (or top-level) categories.

In like manner as user3 100, userό 106 accesses System 250 via one or more login screens displayed on display device 506 (as illustrated by arrow 540) of the user's computer. Userό 106, as illustrated in Fig. 9, belongs to a single group, group M 94. The three items in box 542 are published to group M 94 (refer to box 282 in Fig. 9). In box 544, System 250 determines all of the categories within which each item in box 542 is classified using the category hierarchy 128 stored in database 510. In box 546, as in box 520, System 250 dynamically determines the categories comprising the user hierarchy 502 for userό 106. As illustrated by the user hierarchy 502, categories 1.1 530, category 1.1.1 548, and category 1.1.1.1 550 are excluded from the user hierarchy 502 because no items in box 542 are classified within these categories 530, 548, and 550. Additionally, neither of these categories 530, 548 and 550 operate as an intermediate category (or top- level category). Thus, in some embodiments, System 250 dynamically determines a different user hierarchy 502 for each user depending upon the user's particular group affiliations.

The various embodiments of the present invention as described in Figs. 1-14 may be implemented at the hardware level within a host computer 508 as illustrated in Fig. 15. Host computer 508 is a general purpose computer comprising standard hardware components well-known to those skilled in the art. In particular, host computer 508 includes a CPU 600 connected to a system memory 602 and a plurality of peripheral devices 604, the latter including a monitor 606 and a hard drive 608 comprising a magnetic storage medium on which the database 610 is stored.

In some embodiments of the present invention, the host computer 508 is a Relion 100 Server computer, manufactured by Penguin Computing, Inc., of San Francisco, California, equipped with a Pentium III 800 MHz CPU 600 and 512 Megs of system memory 602, and running Red Hat 7.0 Linux operating system, manufactured by Red Hat of Durham, North Carolina. It should be noted that in some embodiments, the processes comprising System 250 executing within host computer 508 may be distributed across multiple physical computers in other embodiments compatible with the present invention. In addition, in some embodiments of the present invention, the database 610 may be implemented on multiple hard drives in multiple physical machines. In yet other embodiments, the database 610 may be distributed across multiple hard drives 608 implemented in one or more separate physical computers (not shown). The construction of such scalable systems and databases is well-known to those skilled in the art.

In some embodiments of the present invention, the various embodiments described in reference to Figs. 1-14 are implemented in a networked environment as illustrated in Fig. 16. In these embodiments, the processes comprising System 250 may be implemented in host computer 508 which in turn accesses a database hosted in a separate database server 510. System servers 508 and 510, located in physical location 550, are then interconnected to, e.g., corporate Internet 512, physically located in first remote location 552, and, e.g., portable computer 514, located in second remote location 554. Corporate intranet 512 may, in turn, include a plurality of interconnected computers, e.g., 516-520. System servers 508 and 510 are connected to corporate intranet 512 and portable computer 514 via computer network 556.

In some embodiments, the computer network 556 includes a global-area network, such as the Internet; the Internet comprises the millions of computers interconnected by the well-known TCP/IP communication protocol. The computer network 556 may also include local area network (LAN), wide area network (WAN), metropolitan area network (MAN), a public Internet, a private intranet, a private computer network, a secure Internet, a private network, a public network, a value-added network, an interactive television network, a wireless network, and generally any other connection capable of delivering electronic content between computer devices. Computer network 556 may operate with communication protocols other than TCP/IP, such as the Open Systems Interconnection developed by the International Standards Organization. It should be noted that some embodiments of the present invention may be made available to a limited portion of computer network 556, such as a corporate intranet 512, in which the System may be hosted on, for example, computer 520.

Fig. 17 is a block diagram illustrating the component processes of some embodiments of the present invention at the software level. In certain embodiments, the software components of the present invention are implemented in a three-tier architecture. The first tier 580 comprises a web browser 586 executing on, e.g., remote computers 512-520. Web browser 586 may be any conventional web browser such as Internet

Explorer, manufactured by Microsoft Corporation of Redmond, Washington, or Netscape Navigator, manufactured by Netscape Corporation of Mountain View, California. The second tier 582 comprises software executing on the host computer, e.g., 508. The second tier 582 software includes business and presentation logic 588 operating within application web server 590. Application/web server 590, in some embodiments, provides a container-managed solution for business and presentation logic 588 well-known to those skilled in the art. The third tier 584 includes software executing, according to some embodiments of the present invention, on database server 510.

In some embodiments, data server 510 is implemented using the same Relion 100 Server machine used to implement host computer 508. Third tier 584 software includes database management system software 594. Database management system processes 594 communicate with second tier 582 processes via the conventional JDBC APIs and their particular database driver 592 implementation (the JDBC database driver is typically manufactured and distributed by the database management system manufacturer).

In some embodiments of the present invention illustrated by files in the attached appendix, application/web server processes 590 are implemented using BEA Weblogic

6.0 application server, manufactured by BEA Corporation of San Jose, California. The BEA Weblogic application server implements the J2EE (Java 2d Enterprise Edition)

API's well-known to those skilled in the art; J2EE is developed and maintained by Sun Microsystems, Inc., of Palo Alto, California. In some embodiments of the present invention, business and presentation logic 588 are coded as Java classes within the J2EE specification (including the enterprise javabeans (e.g., EJB 1.1) specifications well- known to those skilled in the art) as implemented by the BEA Weblogic application server 590.

In some such embodiments, database management system processes 594 are implemented using PostgreSQL 7.1, maintained and developed by the Open-Source Community. In some embodiments of the present invention, JDBC database driver 592 is implemented using the Postgres JDBC driver 7.0-1.2, also distributed by the

Open-Source Community. Published documentation describing the BEA Weblogic 6.0 application server, the J2EE specification, the Java programming language, PostgreSQL

7.1 and the Postgres JDBC driver 7.0-1.2 are widely available on the Internet, for example, at www.bea.com, www.sun.com, and www.postgresql.org.

In other embodiments of the present invention, Apache Web server 1.3.20 (not shown) conventionally embedded with mod_php as an extension adds the PHP interpreter to Apache (child) processes, thus enabling the Apache Web server to execute PHP programs embedded within the webpages it serves. Accordingly, the PHP-enabled Apache Web server generally enables similar functionalities to be performed using PHP coded logic as is performed using business logic 588 operating within a Java application server 590 (e.g., Weblogic available from BEA Corporation, Websphere available from IBM and iPlanet application server available from Sun Microsystems, Inc.)

In some embodiments, PHP encoded processes access a MySQL 3.23.27 database management system directly from within the Apache Web server using conventional wrappers around the native MySQL APIs. In some embodiments, the Apache Web server is executing within a Red Hat Linux Operating System. More information relating to the to the Red Hat Linux operating system, the Apache Web server running the PHP server module, and MySQL database management system is accessible over the Internet at http://www.redhat.com, http://php.apache.org, http://www.mysql.com respectively.

In some embodiments of the present invention, users access the System executing on host computer 508 via (remote client) computers 512-514 over a computer network 556 using conventional World Wide Web (HTTP, HTTPS) and other Internet (e.g., SNMP, FTP) communication protocols. Accordingly, in some embodiments of the present invention, users send HTTP requests from their web browsers 586 to application/web server 590, which then processes the requests and returns responses over HTTP to the users via the users' web browser 586. Processing of the HTTP requests from the user is performed by business and presentation logic 588 operating within application web server container logic (also referred to as a "servlet engine") 590. Web- based and other Internet communication protocols used for communicating between a host computer and one or more remote client computers are well-known to those skilled in the art.

Turning to Fig. 11, after the user hierarchy, e.g., 500 and 502, is dynamically- determined by System 250 for each user 100 and 106 respectively, access by the user to the items published to the groups to which the user belongs is mediated by the user hierarchy, e.g., 500 and 502, according to some embodiments of the present invention. Those skilled in the art will recognize that the user category tree, e.g., 500, stored in host computer may be displayed on the user's device for purposes of negotiating access in numerous differing ways. In some embodiments, for example, the entire user hierarchy, e.g., 500, may be displayed as a graphical object on the user's display device, e.g., 500, as shown in Fig. 14. Each category in the user hierarchy, e.g., 500, may be sent and rendered on the user's display device, e.g., 504, as a set of selectable hyperlinks. In yet other embodiments, the user category tree 500 may be displayed as an expandable tree (not shown) wherein selection of a category in a portion of the user category tree displayed to the user expands the next level of the user category tree including the items within the expanded category, for display to the user. In still other embodiments, a fixed number of levels (e.g., 2 levels) of the user hierarchy at any one time may be displayed to the user as selectable hyperlinks, wherein the user upon selecting one of the hyperlinks may navigate to higher or lower levels within the category hierarchy. In yet other embodiments, the first two levels of the user hierarchy may be persistently displayed in an area of the user's screen. Those skilled in the art will recognize that numerous variations for displaying the user category tree to the user are compatible with some embodiments of the present invention, and that the present invention is not limited to any particular manner of displaying the user category tree to the user.

Figs. 18A-18C illustrate stages performed by System 250 for enabling the user to interact with the items and categories within the dynamically-determined user hierarchy, according to some embodiments of the present invention. In Fig. 18A, System 250 performs stage 600 after performing the stages described in Fig. 11 (box 610), according to some embodiments of the present invention. In stage 600, System 250 sends a description of at least one first category from among the user hierarchy to the user. In some embodiments, the description is automatically sent by the application/web server 590 in response to a login request by the user from a web browser 586. In stage 602, the application/web server 590 sends a link to the first category.

In some embodiments, the link is a hyperlink identifying a location within host computer 508 in which information relating to the first category — e.g., the items classified within the first category — is stored in System 250. The description and the link sent to the client computer in stages 600 and 602 are sent to the web browser 586 in a format displayable by web browser 586 on the user's display device (e.g., conventional HTML or XML). In some embodiments, the description end link in stages 602 and 604 are sent together as a conventional hyperlink. In stage 604, the System receives an instruction caused by selection of the link by the user in which the instruction indicates selection of the first category by the user. In stage 606, in response to receiving the instruction in stage 604, System 250 sends a description of at least one second category classified within the first category. In stage 608, the system sends a second link to the user's display device, wherein the second link provides a connection to the second category. In some embodiments, the second category and the second link are sent to the user as a conventional hyperlink.

Stages 600 through 608 in Fig. 18A are illustrated in reference to user hierarchy 128 in Fig. 18A-1, according to some embodiments of the present invention. For example purposes, the "news" category 144 will operate as the "first category" in stage 600. Thus, in stage 600, the description of the first category 144 is sent to the user over the computer network, typically via a web browser running on the user's client computer. The description sent in stage 600 is, according to some embodiments, the label "news" describing the first category 144. In stage 602 the first link to the first category ("news" category 144) may in some embodiments be a textual hyperlink displayed using the descriptive label "news" of stage 600. Fig. 18A-2 is a screen shot illustrating a descriptive label and link in stages 600 and 602 for the "news" category 144 compatible with some embodiments of the present invention.

Also displayed in the left margin in screen shot 610 (Fig. 18A-2) are all the categories in the second layer 132 and third layer 134 of the user hierarchy 128. As discussed above, different embodiments of the present invention may display differing arrangements of categories to the user. For example, in some embodiments, only a single layer of the user hierarchy 128 may be displayed in the margin of the webpage 612; in yet other embodiments, the entire user hierarchy 128 may be displayed in the margin of webpage 612 for the user.

Returning to Fig. 18A, stage 604 is performed, in some embodiments, in response to user selection of the first category 144 using a pointing device. In some embodiments, user selection of the first category 144 causes an instruction to be sent to System 250 in which the first category 144 is passed as a parameter. The instruction causes System 250 to execute another sequence of instructions (for example, a servlet) which causes the computer to dynamically generate a second webpage which is subsequently sent to the user. In some embodiments, the second web page will include a description of at least one second category classified within the first category as described in reference to stage 606. Thus, the second web page will contain a second description (stage 606) and a second link (stage 608) for a second category, for example, the "general" category 148 (note that the "training" category 150 may also operate as a second category in this example). Fig. 18 A-3 is a screen shot illustrating, according to some embodiments, a second dynamically generated web page 614 compatible with some embodiments of the present invention which incorporate the processes of stages 604 to 608. In response to user selection of the first category, e.g., the "news" category 144, System 250 dynamically generates web page 614, which displays the description of a second category classified within the first category, e.g., the "general" category of 148 or the "training" category 150. As described in 608, the second categories, e.g., the "general" category 148 and the "training" category 150, include links (e.g., conventional hyperlinks) to each of the second categories. Thus, in accordance with stages 600-608, System 250 enables the user — via dynamic web page generation in response to user hyperlink selection — to efficiently navigate through the categories of the user hierarchy, according to some embodiments of the present invention.

As shown by box 142 in Fig. 18A-2, different graphical devices to assist the user in navigating among the categories of the user hierarchy may be made available to the user. Box 142, for example, displays one embodiment in which the branch of categories connecting the category recently selected by the user to the root category, i.e., the "home" category 142; is persistently displayed to the user. In this manner, the user is provided a graphical device showing his current location relative to the root category within the user hierarchy.

Fig. 18B is a flow diagram illustrating two additional stages 632 and 634 performed by System 250 after the stages in Fig. 18A (box 630) in some embodiments of the present invention. In stage 632, System 250 sends a description of at least one item classified within the second category and marked as being published to a group to which the user belongs. In stage 634, the System sends a third link to the described item. Fig. 18 A-3 is a screen shot illustrating the description of the item and the link to the item described in stages 632 and 634 compatible with some embodiments of the present invention.

Accordingly, in some embodiments, when the system dynamically generates webpage 614 in response to selection of the "news" category 144, the system also, in stage 632, sends a descriptive label 636 of at least one item classified within the "news" category 144; in the exemplary webpage 614, the descriptive label 636 is "June 07, 2001- test 2." In stage 634, the descriptive label 636 operates, in some embodiments, as a textural hyperlink selectable by the user with, e.g., a pointing device. Accordingly, in some embodiments, stages 632 and 634 may be repeatedly performed by System 250 in response to user selections to dynamically generate webpages for displaying all of the items published to a group to which the user belongs for each category in the user hierarchy.

Fig. 18C is a flow diagram illustrating two additional stages performed by System

250 in additional embodiments of the present invention. After performing the stages illustrated in Fig. 18B (stage 670), the System in stage 672 receives an instruction from the user indicating the selection of the third link, e.g., 636. In some embodiments of the present invention, upon receiving the instruction in stage 672, System 250 executes a sequence of instructions (typically a servlet) to dynamically generate a third webpage, e.g., 676 (Fig. 18C-1). During the dynamic generation of the third webpage 676, the content of the item labeled " June 07, 2001-test 2" is generated within webpage 676. The webpage 676 is then, in stage 674, sent to the user for display in the user's web browser.

Fig. 18C-2 illustrates the display of an item described by label "New Sales Director" 680 in the "San Francisco Offices" category 158 compatible with the present invention. Accordingly, as described in reference to Fig. 18A-18C, System 250 performs a sequence of instructions that enables the user to navigate through a user hierarchy unique to the user — and dynamically-determined by System 250 — via a web browser executing on, typically, a remote client computer. In addition, differing embodiments of the present invention will display differing portions of the user hierarchy to the user using dynamic web presentation technologies (e.g., HTTP/HTML, JSP, PHP, Perl Scripts, ASP) well known to those skilled in the art. Moreover, a system administrator has access to a number of administration tools of the type illustrated in, for example, Fig. 18C-2 under the label "Admin Tools".

In some embodiments of the present invention, System 250 processes for identifying associations between items, categories, groups and users are performed using SQL queries on data structures stored in a single database as described herein. In some embodiments, for example, the process of identifying a category in which an item is classified (stage 4 of Fig. 1) — is implemented using a database query (stage 702 in flow diagram 700 (Fig. 19)). In addition, in some embodiments, the queries made by System 250 are performed on a single database.

Database querying operations for identifying categories and items are illustrated in stages 714 and 716 of Fig. 19B. In some embodiments of the present invention, the querying operations are performed as SQL queries apparent to those skilled in the art in view of the disclosure (e.g. see Appendix A below). In some embodiments of the present invention, stages 702 and 714 are performed using a single SQL query upon the database in which all of the categories in which an item is classified may be retrieved as a result of the single query. In like manner, a single query may be made upon the database to identify all of the items marked as being published to a group of users to which the user belongs (stage 716).

The database queries performed in stages 702, 714 and 716 in Fig. 19B may be made upon a data organization 800 as illustrated in database 20 of Fig. 20, according to some embodiments of the present invention. Data organization 800 includes two intersection tables 802 and 804, a user table 806, a group table 808, a category table 810, and item table 812. In some embodiments of the present invention, intersection table 802 provides an "intersection" for user table 806 and group table 808. Accordingly, intersection table 802 in some embodiments includes a user LD column and a group ED column wherein a user ID in the user LD column operates as a key for identifying a user in a user table 806, and a group LD in the group LD column operates as a key for identifying a group in a group table 808. In some embodiments of the present invention, intersection table 804 provides "intersection" for group table 808, category table 810, and item table 812.

Accordingly, intersection table 804 includes an item LD column, a category ID column, and a group ID column. The category LD, item EO, and group ID in intersection table 804 operate as keys for identifying a category tree, an item and a group in a category table 810, an item table 812, and a group table 808 respectively. It should be recognized that those skilled in the art will recognize that the computer processes described in the various embodiments of the present invention may be supported by data organization 800, as well as numerous variations to and modifications of data organization 800. For example, intersection table 804 may be divided into two intersection tables: a first intersection table which includes item LD and category EO columns (not shown), and a second table which includes columns for a category ID and a group LD (not shown).

Given the particular data organization 800 compatible with some embodiments of the present invention, a query to identify a category (or all categories) in which an item is classified — as performed, for example, in stages 702 and 714 — may be directed to intersection table 804; in these embodiments, all of the categories in which an item is classified in the category hierarchy is discoverable using intersection table 804. In like manner, intersection table 804 may be queried for purposes of identifying all of the items published to one or more groups to which the user belongs, as performed in stage 716. Use of a single intersection table 804 to retrieve associations of items, groups to which the items are published, and categories under which the items are classified, enables System 250 to efficiently identify all of the items and categories accessible by the user via a single (SQL) database query.

In some embodiments of the present invention, as described above, System 250 determines whether an item is marked as being published to a group to which the user belongs (stage 2 in Fig. 1). In some embodiments, System 250 determines whether an item is marked in this manner by directing an SQL query to intersection table 804; in some embodiments, the data identifying the item (e.g., the item ID) in the intersection table operates as the relevant marking of System 250. In yet other embodiments, a permission is additionally associated with the data identifying the item in, for example, intersection table 804; this permission, if set, operates as an additional mark recognized by System 250 for identifying the item as being accessible for viewing by the user (belonging to a group to which the item is published). (This operation is illustrated in Fig. 21 A in which new stage 860 replaces stage 2 in flow diagram 5.)

Additional types of access to an item may be provided by System 250 by associating additional permissions with each item in, e.g., intersection table 804; in some embodiments, for example, a second permission (in addition to the view permission) may be associated with each item which enables System 250 to provide editing access to the relevant user. System 250 then provides editing privileges to the user if the item is properly marked with an edit privilege in interface table 804. (This additional operation of checking an edit privilege associated with the item is illustrated as additional stage 862 in flow diagram 5 (Fig. 2 IB).) In yet other embodiments, the categories comprising the user hierarchy are only used by System 250 for providing view access; in these embodiments, editing access to items are excluded as a design principle (other means of providing editing access may be provided in such other embodiments).

Because the identification of items published to a group to which the user belongs, and the identification of the categories within which each of the items are classified, is performed using intersection table 804, the use of permissions associated with each item is, in some embodiments, efficiently implemented by adding additional columns to the intersection table 804. In some embodiments, for example, first additional column may be added to intersection table 804 for the view permission; in other embodiments, a second additional column may be added to the intersection table 804 for the edit permission. In some embodiments, the view permission and the edit permission are Boolean values. Intersection table 804 with the added columns for the edit and view permissions is illustrated, according to some embodiments, in Fig. 2 ID. Consequently, once the group associations for a particular user are identified by the system, the intersection table 804 may be efficiently queried by System 250 to rapidly determine the items accessible to the user, the user hierarchy for negotiating access to the items, and the type of access (e.g., view or edit) to the items.

In some embodiments of the present invention, in order to speed system responsiveness to user navigation of the user hierarchy and access to item via the user hierarchy, the user hierarchy is dynamically-determined during the user login process. In one specific embodiment illustrated in the attached appendix, the table

CAT_TREE_ITEMS is used to identify each of a number of items that may be accessed by a user, e.g. to which the user has either a view privilege or an edit privilege. Specifically, at the time of login, a table USER in the database is check to obtain a user ED, and this user LD is in turn used to determine a group ED from the table GROUP.

Thereafter, another table GID_TOOL_ID is used to identify any tools that the user may use to create new items. Note that in this example, the table GEO_TOOL_ID is not used to identify a user's edit or view privileges for an item. Instead, this table GID TOOL ID is used only to identify the user's creation privileges to provide access to certain tools as described in the related U.S. Patent Application, attorney Docket No. M- 12171 incoφorated by reference above. Instead, in this implementation, the table CAT TREE LTEMS is used to find all categories as illustrated by the query in the attached Appendix A.

After all of the categories have been identified, a tree is constructed using these categories, and thereafter displayed to the user for providing access to the items of information that have been marked as being accessible by the user, and classified within the just-described categories. A dynamically-determined user hierarchy of the type described above is stored in a session object of the host operating environment (e.g., the Unix file system), in one embodiment. The session object is typically implemented in PHP as a serialized flat file registered to the user in the file system, and in Java as a hash map object, which is stored in volatile memory and passed between user events. This is illustrated in Fig. 15 in which two users, userl 910 and user2 912, are connected via remote client computers 920 and 922 to System 250 host computer 508 via computer network 556. System memory 602 in host computer 508 is shown with user session objects 900 and 902 created upon login processes started by userl 910 and user2 912, respectively.

User session objects 900-902 of such embodiments in addition include the dynamically-determined user hierarchy for each respective user, according to some embodiments of the present invention. In addition, user (remote client) computer 3 924 is shown without a user (empty box 914), and therefore when a user logs into System 250 via this computer 924, a user session object containing the new user's dynamically- determined user hierarchy 904 will be created by the System, in some embodiments in volatile memory 602 (illustrated by box 904 in Fig. 15) and in other embodiments in a file system in hard disk 608. By maintaining each user's user hierarchy in the file system, System 250 can dynamically generate webpages in response to user navigation of his or her user hierarchy without making a time-consuming query to the database prior to dynamic generation of each webpage. In these embodiments, the categories encoded in the dynamically-generated webpage are determined using data in the session object (such as a Java last maps object) stored in the host file system.

Numerous modifications and adaptations of the various embodiments, implementations and examples described above will be apparent to the skilled artisan in view of the disclosure. For example, although stage 6 in Fig. 1 indicates that the "associated data" is stored, in other embodiments such data may not be stored in the non- volatile memory, and instead such data may be transmitted directly to the computer of the user. Moreover, depending on the embodiment, even if the "associated data" is stored in the System, such data may be stored either in volatile memory in which case the data is lost when the power is turned off, or alternatively in non-volatile memory so that the data is available even after the System has been rebooted. Furthermore, depending on the embodiment, other kinds of information may be included in the "associated data", and in other embodiments certain data may be omitted from the "associated data". For example, in some embodiments, the "group" may be omitted, if the System is programmed to handle publication of information on an individual basis to each user, instead of publication on a group basis. Also, instead of checking whether an item is marked as being published to a user's group in stage 2 (Fig. 1), any other method may be used to identify an item to which the user has access. For example, the item may itself contain a list of all users that have access to the item.

Moreover, in certain embodiments, the System performs method 5 (Fig. 1) at the time an item is published. Specifically, in such embodiments, stages 2, 4 and 6 are repeatedly performed for an item being published, for each user (or group of users) that may use the System, and the information stored in stage 6 is thereafter used at the time a user logs in to directly determine the portion of the predetermined hierarchy of categories which is to be displayed to the user for access to the item. In other embodiments, stages 2, 4 and 6 are performed at the time a user logs in, for each of a number of items that are published in the System, instead of being performed at the time of publication.

Furthermore, in certain embodiments described in the related application entitled "Data Driven Access to Tools", Attorney Docket No. M-12171 incoφorated herein by reference above, the System may also identify a tool for use by the user in viewing and/or editing an item of information that has been published to the user, and for which a predetermined hierarchy of categories has been identified as discussed above. In such an embodiment, the user's access to a tool may be limited by the items to which the user has access, unless the user has been granted privileges to use a tool independently. When tool privileges are present, the system allows user access to a tool to create new items, even if the user has no privilege to edit or view items of the same type and vice versa. Therefore, such embodiments implement two tiers of privileges — at the item level and also at the tool level. Such a System may be used to manage the publication and distribution of on-line materials, in effect as a network-based file system, providing for the organization and access privileging of files. The provision of access to tools and/or categories based on item-level privileges reverses the top-down methodology that is implemented traditionally.

Numerous such modifications and adaptations of the embodiments, implementations and examples described above are encompassed by the attached claims. APPENDIX A

The user object (in some embodiments) is a session-based file of serialized data on the server side that is referenced by the user's current session ID. It is this ID which is returned [post login] as the reference to the user object. Secure_zone::get_groups()

This method gathers a list (in the form of a one-dimensional array) of all of the groups of which the user is a member. The retreived list of groups is then registered in the user object.

The heart of this method is the following SQL query (in which $uid is a variable containing the user's unique ID):

SELECT DISTINCT GDO FROM GEDJ SERJD WHERE USER_ID='$uid'

Secure zone: :build_cat_tree()

This is the method that is used to build the user's category tree. Essentially, it gathers a list of distinct categories in which there are items published for the user to view. From this primary list of categories, a broader list is created by adding all of the intermediate categories necessary to create pathways between the categories of this primary list and the "Top-Level" categories of the system. Access from "Top-Level" categories down to those categories containing user content is provided as a means of granting the user the ability to navigate down to those populated categories. The result of this method is an associative array (or hash) in which the category ID is the key and the category Name is the value. This array is immediately (within this method itself) registered to the user object.

[Note: in all of the queries below the column VIRTU AL_ROOT and variable $vr refer to the users virtual root; that is, the topmost node for their portion of the group tree.] The following query is used to retrieve each category in which the user has a viewable item (here, the variable $group_str represents a comma-delimited list of the groups of which the user is a member — this is the list collected above):

SELECT DISTINCT CAT_LD FROM CAT_TREE_ITEMS WHERE GED IN (Sgroup str) AND VIRTUAL_ROOT='$vr' AND VIEW=1 The category naming scheme is based on simple iterated dot notation (each parent category is separated from its children by a "."; e.g., CATEGORY 1.1 is the parent of 1.1.1 and 1.1.2 . . .), we simply shear off the trailing digits and final dot of a CAT ED to find its parent categories all the way up to the top or root level (represented by ordinal numbers without trailing dots: 1, 2,3 . . .). Each of these parent categories are added to the user's CAT TREE (in the form of a PHP array registered to the user object) as necessary paths to the populated categories. No redundancies are retained.

Given the list of CAT_EOs, category names are retrieved from the CAT TREE table with the follow query (here, the CAT IDs have been assembled in a comma-delimited string represented by the variable $tree_str):

SELECT DISTINCT CAT_ED,NAME FROM CAT_TREE WHERE CAT_ED LN ($tree_str) AND VIRTUAL_ROOT='$vr' ORDER BY SEQ

The CAT_EDs and category names are then assembled into the associative array mentioned above that is registered to the user object. APPENDIX B

Volume in drive D is 011009_1436 Volume Serial Number is BCE2-6A1B Directory of D:\

10/09/01 02:36p <DIR>

10/09/01 08:36a 13,786 MIGRAT-3.REA

10/09/01 08:36a 275 README

10/09/01 02:36p <DIR> SECURE

10/09/01 08:36a 13,363 SZ-42M-9.SQL

10/09/01 08:36a 17,573 SZ-420-C.SQL

10/09/01 08:36a 17,577 SZ-42P-F.SQL

10/09/01 08:36a 1,869 SZ-42-12.REA

9 File(s) 64,443 bytes

Directory of D:\SECURE

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> ADMIN

10/09/01 08:36a 415 CAT~4.HTM

10/09/01 08:36a 398 COOKIE~6.HTM

10/09/01 02:36p <DIR> CRON

10/09/01 08:36a 316 ERRORS-B.PHP

10/09/01 08:36a 386 ERROR~E.HTM

10/09/01 08:36a 508 FORGO~10.HTM

10/09/01 02:36p <DIR> INCLUDES

10/09/01 08:36a 421 INDEX~14.HTM

10/09/01 08:36a 182 INDEX~16.HTM

10/09/01 02:36p <DIR> JAVAS-19

10/09/01 02:36p <DIR> LAYOUT

10/09/01 08:36a 453 LOGIN~lD.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 423 SITEM-21.HTM

10/09/01 02:36p <DIR> TOOLS

10/09/01 08:36a 1,257 USER_~25.HTM

^: 19 File(s) 4,759 bytes

Directory of D:\SECURE\ADMIN

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> ADMIN ~3

10/09/01 02:36p <DIR> CATTRE~5

10/09/01 08:36a 109 ERROR~7.HTM

10/09/01 02:36p <DIR> GROUPMAN

10/09/01 08:36a 671 INDEX~B.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 02:36p <DIR> MLCATT~F

10/09/01 02:36p <DIR> REORD-12

10/09/01 02:36p <DIR> SEARCH

10/09/01 02:36p <DIR> SECURITY

10/09/01 02:36p <DIR> USERMAN

10/09/01 02:36p <DIR> UTILS

^: 14 File(s) 780 bytes

Directory of D:\SECURE\ADMIN\ADMTN_~3

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 0/09/01 08:36a 235 ERRORS-3.PHP 0/09/01 08:36a 500 HEADERS.PHP 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 267 POSITI~A.HTM 0/09/01 08:36a 279 PREPUB~C.HTM 0/09/01 08:36a 265 PUBLIS~F.HTM 0/09/01 08:36a 6,927 TREESLIB.PHP 0/09/01 08:36a 277 UNPUB~14.HTM 0/09/01 08:36a 269 USER_~17.HTM H File(s) 9,019 bytes

Directory of D:\SECURE\ADMIN\ADMIN_~3\MJ 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D:\SECURE\ADMΓN\ADMΓN_~3\MASKING\INCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\ADMIN_~3\MA

10/09/01 02:36p <DIR>

10/09/01 02:36p <DΓR>

10/09/01 08:36a 1,062 ERRORS-3.PHP

10/09/01 08:36a 3,833 POSITI~6.HTM

10/09/01 08:36a 2,470 PREPUB~8.HTM

10/09/01 08:36a 10,169 PUBLIS~B.HTM

10/09/01 08:36a 2,952 UNPUB ~D.HTM

10/09/01 08:36a 1,024 USER_~10.HTM

8 File(s) 21,510 bytes Directory of D:\SECURE\ADMIN\ADMIN_~3\MASKING\MASKS

02:36p <DIR>

02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\ADMrN_~3\MASKING\MASKS\l

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>

10/09/01 08:36a 2,789 MASKS.XML

3 File(s) 2,789 bytes

Directory of D:\SECURE\ADMIN DMrN_~3\MAS vfG\TMPL

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\ADMIN_~3\MASKING\TMPL\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 828 ERRORS-3.PHP 0/09/01 08:36a 3,868 POSITI~6.HTM 0/09/01 08:36a 2,428 PREPUB~8.HTM 0/09/01 08:36a 10,158 PUBLIS~B.HTM 0/09/01 08:36a 2,912 UNPUB ~D.HTM 0/09/01 08:36a 1,029 USER ~10.HTM

8 File(s) 21,223 bytes Directory of D:\SECURE\ADMIN\CATTRE~5 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 319 ADDCON~3.HTM 0/09/01 08:36a 273 ADD~5.HTM 0/09/01 08:36a 20,741 CLASSC-7.PHP 0/09/01 08:36a 275 DROP~A.HTM 0/09/01 08:36a 312 ERRORS-C.PHP 0/09/01 08:36a 568 HEADER-F.PHP 0/09/01 08:36a 275 HOME~12.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 279 MODIF~17.HTM 0/09/01 08:36a 285 0RDER~19.HTM 12 File(s) 23,327 bytes

Directory of D:\SECURE\ADMiN\CATTRE~5\MASKTNG 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of D:\SECURE\ADMTN\CATTRE~5\MASKTNG\INCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\CATTRE~5\MA:

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 0/09/01 08:36a 4,340 ADDCON~3.HTM 0/09/01 08:36a 2,889 ADD~5.HTM

10/09/01 08:36a 1,937 DROP~7.HTM

10/09/01 08:36a 654 ERRORS-9.PHP

10/09/01 08:36a 539 HOME~D.HTM

10/09/01 08:36a 3,258 MODIFY~F.HTM

10/09/01 08:36a 5,026 ORDER~12.HTM

9 File(s) 18,643 bytes

Directory of D:\SECURE\ADMIN\CATTRE~5\MA!

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D :\SECURE\ADMIN\CATTRE~5\MASKING\MASKS\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,886 MASKS.XML 3 File(s) 3,886 bytes

Directory of D:\SECURE\ADMIN\C ATTRE~5\MASKTNG\TMPL

02:36p <DIR>

02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\ADMm\CATTRE~5\MASKTNG\TMPL\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 4,316 ADDCON~3.HTM 0/09/01 08:36a 2,898 ADD~5.HTM 0/09/01 08:36a 1.575 DROP~7.HTM 0/09/01 08:36a 473 ERRORS-9.PHP 0/09/01 08:36a 531 HOME~D.HTM 0/09/01 08:36a 3,300 MODIFY~F.HTM 0/09/01 08:36a 4,949 ORDER~12.HTM

9 File(s) 18,042 bytes

Directory of D:\SECURE\ADMIN\GROUPMAN 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 294 ADDCON~3.HTM

10/09/01 08:36a 261 ADD~5.HTM 0/09/01 08:36a 14,473 CLASSG-7.PHP

10/09/01 08:36a 263 DROP~A.HTM 0/09/01 08:36a 347 ERRORS-C.PHP

10/09/01 08:36a 275 GROUP ~F.HTM

10/09/01 08:36a 636 HEADE-11.PHP

10/09/01 08:36a 263 HOME~14.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 267 MODIF~18.HTM

: 12 File(s) 17,079 bytes

Directory of D:\SECURE\ADMIN\GROUPMAN\MASKING

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> INCLUDES 10/09/01 02:36p <DIR> MASKS 10/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\GROUPMAN\MASKING\INCLUDES

10/09/01 02:36p <DΓR>

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\ADMIN\GROUPMAN\MASKING\INCLUDES\l 10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 6,883 ADDCON~3.HTM 0/09/01 08:36a 5,334 ADD~5.HTM 0/09/01 08:36a 6,017 DROP~7.HTM 0/09/01 08:36a 902 ERRORS-9.PHP 0/09/01 08:36a 2,511 GROUP ~D.HTM 0/09/01 08:36a 562 HOME~F.HTM 0/09/01 08:36a 6,148 MODIF~l l.HTM

9 File(s) 28,357 bytes

Directory of D :\SECURE\ADMIN\GROUPM AN\M ASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\GROUPMAN\MASKING\MASKS\l

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 6,859 MASKS.XML 3 File(s) 6,859 bytes Directory of D:\SECURE\ADMIN\GROUPMAN\MASKJNG\TMPL

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\GROUPMAN\MASKING\TMPL\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 6,884 ADDCON~3.HTM

10/09/01 08:36a 5,165 ADD~5.HTM

10/09/01 08:36a 5,646 DROP~7.HTM

10/09/01 08:36a 613 ERRORS-9.PHP

10/09/01 08:36a 2,403 GROUP_~D.HTM

10/09/01 08:36a 579 HOME~F.HTM

10/09/01 08:36a 6,029 MODIF~l l.HTM

9 File(s) 27,319 bytes Directory of D:\SECURE\ADMiN\MASKING

10/09/01 02:36p <DIR>

10/09/01 08:36a 7,473 CLASSM-3.PHP

10/09/01 08:36a 383 CONFIG-5.PHP

10/09/01 08:36a 485 HEADER-8.PHP

10/09/01 08:36a 265 HOME~B.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 267 RESET~F.HTM

10/09/01 02:36p <DIR> SCRIPTS

10/09/01 08:36a 263 SET~13.HTM

10/09/01 08:36a 3,364 SZ_DE~15.TXT

10/09/01 08:36a 281 TOOL_~18.HTM

12 File(s) 12,781 bytes

Directory of D:\SECURE\ADMIN\MASKING\MASKING 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUE 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D:\SECURE\ADMlN\MASKrNG\MASKTNG\INCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\ADMINVMASKING\MA! 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 293 HOME~3.HTM 0/09/01 08:36a 1,718 RESET~5.HTM 0/09/01 08:36a 2,803 SET~7.HTM 0/09/01 08:36a 1,594 TOOL M~9.HTM

6 File(s) 6,408 bytes Directory of D:\SECURE\ADMlN\MASKING\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE' CURE\ADMIN\MASKING\]

10/09/01 02:36p <DIR>

10/09/01 08:36a 1,505 MASKS.XML

3 File(s) 1,505 bytes

Directory of D:\SECURE\ADMIN\MASKING\MASKING\TMPL

02:36p <DIR>

02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMrN\MASKING\MASKING\TMPL\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 294 HOME~3.HTM

10/09/01 08:36a 1,607 RESET~5.HTM

10/09/01 08:36a 2,818 SET~7.HTM

10/09/01 08:36a 1,512 TOOL_M~9.HTM

6 File(s) 6,231 bytes

Directory of D:\SE CURE\ADMΓN\MASKΓNG\SCR

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,341 GEN MA~3.PL

10/09/01 08:36a 1,472 RESET.PL

10/09/01 08:36a 830 SET MA~7.PL 5 File(s) 5,643 bytes

Directory of D:\SECURE\ADMIN\MLCATT~F 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 273 ADD~3.HTM 0/09/01 08:36a 1,275 CLASSM-5.PHP 0/09/01 08:36a 275 DROP~7.HTM 0/09/01 08:36a 318 ERRORS-9.PHP 0/09/01 08:36a 601 HEADER-D.PHP 0/09/01 08:36a 275 HOME~10.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 279 MODIF~14.HTM 0/09/01 08:36a 285 ORDER~17.HTM 0/09/01 08:36a 287 ORDER~19.HTM

12 File(s) 3,868 bytes

Directory of D:\SECURE\ADMIN\MLCATT~F\MASK1NG 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 10/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\MLCATT~F\MASKTNG\INCLUDES

10/09/01 02:36p <DIR>

3 File(s) 0 bytes Directory of D:\SECURE\ADMIN\MLCATT~F\MASKING\INCLUDES\1

10/09/01 02:36p <DIR>

10/09/01 08:36a 2.232 ADD~3.HTM 10/09/01 08:36a 2,103 DROP~5.HTM

10/09/01 08:36a 534 ERRORS-7.PHP

10/09/01 08:36a 494 HOME~B.HTM

10/09/01 08:36a 2,767 MODIFY~D.HTM

10/09/01 08:36a 4,780 ORDERC~F.HTM 10/09/01 08:36a 4,498 ORDER~12.HTM

9 File(s) 17,408 bytes

Directory of D:\SECURE\ADMIN\MLCATT~F\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\MLCATT~F

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,145 MASKS.XML

3 File(s) 3,145 bytes

Directory of D:\SECURE\ADMIN\MLCATT~F\MASKΓNG\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMΓN\MLCATT~F\M » 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 2,233 ADD~3.HTM 0/09/01 08:36a 1,744 DR0P~5.HTM 0/09/01 08:36a 419 ERRORS-7.PHP 0/09/01 08:36a 498 HOME~B.HTM 0/09/01 08:36a 2,796 MODIFY~D.HTM 0/09/01 08:36a 4,707 ORDERC~F.HTM 0/09/01 08:36a 4,473 ORDER~12.HTM

9 File(s) 16,870 bytes Directory of D:\SECURE\ADMIN\REORD~12 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 7,228 CLASSR-3.PHP 0/09/01 08:36a 299 ERRORS-6.PHP 0/09/01 08:36a 511 HEADER-9.PHP 0/09/01 08:36a 278 HOME~C.HTM 0/09/01 02:36p <DIR> MASKING

7 File(s) 8,316 bytes

Directory of D:\SECURE\ADMIN\REORD~12\M 0/09/01 02:36p <DIR> 0/09/01 02:36p <DΓR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS

10/09/01 02:36p <DTR> TMPL

5 File(s) 0 bytes Directory of D:\SECURE\ADMIN\REORD~ 12\MASKJNG\TNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1 3 File(s) 0 bytes

Directory of D :\SECURE\ADMIN\REORD~ 12\MASKING\INCLUDES\1

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>

10/09/01 08:36a 287 ERRORS-3.PHP

10/09/01 08:36a 4,615 HOME~6.HTM

4 File(s) 4,902 bytes Directory of D:\SECURE\ADMIN\REORD~12\MASKTNG\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1 3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\REORD~12\MASKTNG\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 1,103 MASKS.XML

3 File(s) 1,103 bytes

Directory of D:\SECURE\ADMIN\REORD~12\MASKlNG\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\REORD~12\MASKING\TMPL\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 283 ERRORS-3.PHP

10/09/01 08:36a 4,578 HOME~6.HTM

4 File(s) 4,861 bytes

Directory of D:\SECURE\ADMIN\SEARCH

10/09/01 02:36p <DIR>

10/09/01 08:36a 19,414 CLASSS-3.PHP

10/09/01 08:36a 280 ERRORS-5.PHP

10/09/01 08:36a 273 HEADER-8.PHP

10/09/01 08:36a 46 INDEX~B.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 288 SEARCH~F.HTM

10/09/01 08:36a 559 SET~11.HTM

9 File(s) 20,860 bytes Directory of D:\SECURE\ADMIN\SEARCH MASKΓNG

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> INCLUDES

10/09/01 02:36p <DTR> MASKS

10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\SEARCH\MASKrNG\INCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE' CURE\ADMIN\SEARCH\MAS1

10/09/01 02:36p <DIR>

10/09/01 08:36a 262 ERRORS-3.PHP

10/09/01 08:36a 5,934 SEARCH~5.HTM

10/09/01 08:36a 4,822 SET~8.HTM

5 File(s) 11,018 bytes Directory of D:\SECURE\ADMIN\SEARCH\MASKTNG\MASKS 10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\SEARCH\MASKΓNG\MASKS\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 1,463 MASKS.XML

3 File(s) 1,463 bytes

Directory of D:\SECURE\ADMIN\SEARCH\MASKING\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\SEARCH\MASKING\TMPL\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 233 ERRORS-3.PHP 0/09/01 08:36a 5,685 SEARCH~5.HTM 10/09/01 08:36a 4,754 SET~8.HTM 5 File(s) 10,672 bytes

Directory of D:\SECURE\ADMIN\SECURITY 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 7,911 CLASSS-3.PHP 0/09/01 08:36a 19,357 CRACKD-5 0/09/01 08:36a 434 ERRORS-8.PHP

10/09/01 08:36a 23,736 GOODDICT

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 370 PASSWD~E.HTM

10/09/01 08:36a 271 SECUR-11.PHP

10/09/01 08:36a 376 SUGGE~14.HTM

10 File(s) 52,455 bytes

Directory of D:\SECURE\ADMIN\SECURITY\MASKING

D ectory of D:\SECURE\ADMIN\SECURITY\MASKING\INCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\ADMTN\SECURITY\MASKING\rNCLUDES\l

10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 1 ,031 ERRORS-3.PHP 0/09/01 08:36a 3,286 PASSWD~5.HTM 0/09/01 08:36a 2,614 SUGGES~8.HTM

5 File(s) 6,931 bytes Directory of D:\SECURE\ADMrN\SECURITY\MASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1 3 File(s) 0 bytes

Directory of D:\SECURE\ADMlN\SECURITY\MASKING\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,158 MASKS.XML

3 File(s) 3,158 bytes

Directory of D:\SECURE\ADMIN\SECURITY\MASKING\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\SECURITY\MASKING\TMPL\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 923 ERRORS-3.PHP 0/09/01 08:36a 3,106 PASSWD~5.HTM 0/09/01 08:36a 2,301 SUGGES~8.HTM

5 File(s) 6,330 bytes

Directory of D:\SECURE\ADMIN\USERMAN

10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 328 ADD~3.HTM 0/09/01 08:36a 12,083 CLASSU-5.PHP

10/09/01 08:36a 332 DROP~7.HTM

10/09/01 08:36a 323 ERRORS-9.PHP

10/09/01 08:36a 578 HEADER-C.PHP

10/09/01 08:36a 330 HOME~F.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 336 MODIF~13.HTM

10/09/01 08:36a 330 VIEW~15.HTM

11 File(s) 14,640 bytes Directory of D:\SECURE\ADMIN\USERMAN\MASKING

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> INCLUDES

10/09/01 02:36p <DIR> MASKS

10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D :\SECURE\ADMTN\USERMAN\MASKTNG\INCLUDES

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 3 File(s) 0 bytes

Directory of D :\SECURE\ADMrN\USERMAN\MASKTNG\INCLUDES\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 4.231 ADD~3.HTM 0/09/01 08:36a 3,366 DROP~5.HTM 0/09/01 08:36a 283 ERRORS-7.PHP 0/09/01 08:36a 575 HOME~A.HTM 0/09/01 08:36a 7,443 MODIFY~C.HTM 0/09/01 08:36a 7,860 VIEW~E.HTM

8 File(s) 23,758 bytes

Directory of D:\SECURE\ADMIN\USERMAN\MASKING\MASKS 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMlN\USERMAN\MASKING\MASKS\l

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 3,630 MASKS.XML 3 File(s) 3,630 bytes Directory of D:\SECURE\ADMi JSERMAN\MASKING\TMPL

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\USERMAN\MASKTNG\TMPL\1

10/09/01 02:36p <DIR>

10/09/01 08:36a 4.340 ADD~3.HTM

10/09/01 08:36a 3.376 DROP~5.HTM

10/09/01 08:36a 277 ERRORS-7.PHP

10/09/01 08:36a 580 HOME~A.HTM

10/09/01 08:36a 7,680 MODIFY~C.HTM

10/09/01 08:36a 8,097 VIEW~E.HTM

8 File(s) 24,350 bytes

Directory of D:\SECURE\ADMIN\UTILS

10/09/01 02:36p <DIR>

10/09/01 08:36a 494 CONFPA~3.PL

10/09/01 02:36p <DIR> FORMAT-5

10/09/01 02:36p <DIR> MEDIA_~7

10/09/01 02:36p <DIR> METATA-A

10/09/01 08:36a 2,856 MYSQL_~C.PHP

10/09/01 08:36a 2,148 ORPHAN~F.PL

10/09/01 08:36a 4,626 THUMB- 11. PHP

10/09/01 08:36a 12,441 THUNK

10/09/01 08:36a 1,241 TMP_C~16.PL

11 File(s) 23,806 bytes Directory of D :\SECURE\ADMIN\UTILS\FORMAT~5 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> DIALOG 0/09/01 08:36a 2,069 EDITLI~4.HTM 0/09/01 08:36a 7,611 EDITME~7.HTM 0/09/01 08:36a 7,970 FORMAT~A.HTM 0/09/01 08:36a 8,469 FORMAT~C.HTM 0/09/01 02:36p <DIR> GRAPHICS 0/09/01 02:36p <DIR> JS 0/09/01 08:36a 2,287 LEFT~12.HTM 0/09/01 08:36a 271 LINK~14.HTM 0/09/01 08:36a 8,290 OPTIO~17.HTM 0/09/01 08:36a 3,136 README.TXT 0/09/01 08:36a 4,604 RIGHT~1B.HTM

14 File(s) 44,707 bytes

0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 08:36a 7,612 IMAGEG~3.HTM

10/09/01 08:36a 364 IMAGEP~5.HTM

10/09/01 08:36a 2,445 LEFT~8.HTM 0/09/01 08:36a 2,487 LINKGU~A.HTM 0/09/01 08:36a 259 LINK~C.HTM 0/09/01 08:36a 4,473 RIGHT-F.HTM

8 File(s) 17,640 bytes

Directory of D:\SECURE\ADMIN\UTILS\FORMAT~5\GRAPHICS

10/09/01 02:36p <DIR>

2 File(s) 0 bytes

Directory of D :\SECURE\ADMIN\UTILS\FORMAT~5\JS

10/09/01 02:36p <DIR>

10/09/01 08:36a 49 ACTIVE-3.JS

10/09/01 08:36a 15,494 CURSOR.JS

10/09/01 08:36a 10,559 EDITOR.JS

10/09/01 08:36a 6,469 FLATLIST.JS

10/09/01 08:36a 3,763 FLATLI-C.JS

10/09/01 08:36a 13,451 FORMAT-E.JS

10/09/01 08:36a 7,650 IMAGE.JS

10/09/01 08:36a 4,569 LINK.JS

10/09/01 08:36a 15,099 OLDTE-15JS

10/09/01 08:36a 9,733 OPTIO-18.JS

10/09/01 08:36a 17,371 TEXT_~1A.JS

13 File(s) 104,207 bytes Directory of D:\SECURE\ADMIN\UTILS\MEDIA_~7

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 436 ADDMED~3.HTM 10/09/01 08:36a 443 EDITME~5.HTM 10/09/01 08:36a 455 FILEUP~7.HTM 10/09/01 08:36a 221 HEADER.PHP 0/09/01 08:36a 455 LOCALD~C.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 7,794 MEDIA.JS 0/09/01 08:36a 526 MEDIA~16.INC 0/09/01 08:36a 455 MEDLI~11.HTM 0/09/01 08:36a 458 MEDLI~18.HTM 0/09/01 08:36a 458 MEDLI~1B.HTM 0/09/01 08:36a 458 MEDLI~1E.HTM 0/09/01 08:36a 458 MEDLI~21.HTM 0/09/01 08:36a 452 SETME~24.HTM

16 File(s) 13,069 bytes

Directory of D:\SECURE\ADMlN\UTILS\MEDIA_~7\MASKING 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D:\SE CUREVADMTΪ sf\UTILS\ME] 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMlN\UTILS\MEDIA_~7\MASKTNG\rNCLUDES\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

10/09/01 08:36a 1,397 ADDMED~3.HTM

10/09/01 08:36a 1,628 EDITME~5.HTM 10/09/01 08:36a 341 FILEUP~7.HTM

10/09/01 08:36a 873 LOCALD~A.HTM

10/09/01 08:36a 19,352 MEDIA~10.INC

10/09/01 08:36a 610 MEDLIB~D.HTM

10/09/01 08:36a 1,109 MEDLI~12.HTM 10/09/01 08:36a 126 MEDLI~15.HTM

10/09/01 08:36a 288 MEDLI~18.HTM

10/09/01 08:36a 434 MEDLI~1B.HTM

10/09/01 08:36a 3,280 SETME~1D.HTM

13 File(s) 29,438 bytes

Directory of D:\SECURE\ADMIN\UTILS\MEDIA_~7\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\UTILS\MEDIA_~7\MASKING\MASKS\1 10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,248 MASKS.XML

3 File(s) 3,248 bytes Directory of D:\SECURE\ADMIN\UTILS\MEDIA_~7\MASKING\TMPL 10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\UTILS\MEDIA_~7\MASKING\TMPL\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 1,385 ADDMED~3.HTM 0/09/01 08:36a 1,529 EDITME~5.HTM 0/09/01 08:36a 329 FILEUP~7.HTM 0/09/01 08:36a 812 LOCALD~A.HTM 0/09/01 08:36a 19,501 MEDIA-IO.INC 0/09/01 08:36a 508 MEDLIB~D.HTM 0/09/01 08:36a 1,130 MEDLI~12.HTM 0/09/01 08:36a 132 MEDLI~15.HTM 0/09/01 08:36a 288 MEDLI~18.HTM 0/09/01 08:36a 452 MEDLI~1B.HTM 0/09/01 08:36a 3,281 SETME~1D.HTM

^: 13 File(s) 29,347 bytes

Directory

0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 407 METATA-4.INC 0/09/01 08:36a 221 METATA-7.PHP

5 File(s) 628 bytes

Directory of D:\SECURE\ADMIN\UTILS\METATA~A\MASKlNG

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> INCLUDES

10/09/01 02:36p <DIR> MASKS

10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes Directory of D:\SECURE\ADMIN\UTILS\METATA~A\MASKING\lNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1 3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\UTILS\METATA~A\MASKING\INCLUDES\1

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>

10/09/01 08:36a 3,135 METATA-3. INC

3 File(s) 3,135 bytes

Directory of D:\SECURE\ADMTN\UTILS\METATA~A\MASKING\MASKS

10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\ADMIN\UTILS\METATA~A\MASKING\MASKS\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 487 MASKS.XML 3 File(s) 487 bytes

Directory of D:\SEClJRE\ADMlN\UTILS\METATA~A\MASKTNG\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\ADMIN\UTILS\META1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,143 METATA-3.INC

3 File(s) 3,143 bytes Directory of D:\SECURE\CRON 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 181 CRONTAB.TXT

3 File(s) 181 bytes

Directory of D:\SECURE INCLUDES

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,029 CLASSA-3.PHP

10/09/01 08:36a 50,201 CLASSC-5.PHP

10/09/01 08:36a 6,066 CLASSD-8.PHP

10/09/01 08:36a 4,523 CLASSD-B.PHP

10/09/01 08:36a 1,981 CLASSD-E.PHP

10/09/01 08:36a 41,026 CLASS-10.PHP

10/09/01 08:36a 10,843 CLASS-13.PHP

10/09/01 08:36a 31,273 CLASS-16.PHP

10/09/01 08:36a 23,627 CLASS-19.PHP

10/09/01 08:36a 7,806 CONFI-1B.PHP

10/09/01 08:36a 384 ERROR-1E.PHP

10/09/01 08:36a 4,512 GLOBA-21. PHP

10/09/01 08:36a 97 GROUP-24.PHP

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 5,706 SCHEM-28.SQL

10/09/01 08:36a 6,402 SCHEM-2B.SQL

10/09/01 08:36a 6,404 SCHEM-2E.SQL

10/09/01 08:36a 73,441 STDLIB.PHP

10/09/01 08:36a 10,976 SZERR-33.PHP

^: 21 File(s) 288,297 bytes

Directory of D:\SECURE\TNCLUDES\MASKTNG

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> INCLUDES

10/09/01 02:36p <DIR> MASKS

10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D :\SECURE\INCLUDES\M ASKINGMNCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D :\SECURE\INCLUDES\MASKING\ιNCLUDES\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 1,959 ERRORS-3. PHP

3 File(s) 1,959 bytes

Directory of D:\SECURE\ESfCLUDES\MASKTNG\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\TNCLUDES\MASKING\MASKS\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

10/09/01 08:36a 1,962 MASKS.XML

3 File(s) 1,962 bytes

Directory of D:\SE< CURE\ΓNCLUDES\MASKΓNG 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\ΓNCLUDES\MASKING

10/09/01 02:36p <DIR>

10/09/01 08:36a 2,157 ERRORS-3.PHP

3 File(s) 2,157 bytes

Directory of D:\SECURE\JAVAS~19

10/09/01 02:36p <DIR>

10/09/01 08:36a 9,665 DIALOG.JS

10/09/01 08:36a 10,061 MD5.JS

10/09/01 08:36a 7,981 NN_DIA~7.JS

5 File(s) 27,707 bytes

Directory of D:\SECURE\LAYOUT

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> BUTTONS

10/09/01 02:36p <DIR> CONFIG

10/09/01 02:36p <DIR> CSS

10/09/01 02:36p <DIR> GRAPHICS

10/09/01 02:36p <DIR> ICONS

10/09/01 02:36p <DIR> INCLUDES

8 File(s) 0 bytes

Directory of D:\SECURE\LAYOUT\BUTTONS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> DISCUS-3 0/09/01 02:36p <DIR> GLOSSARY

4 File(s) 0 bytes

0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

2 File(s) 0 bytes

Directory of D:\SE' CURE\LAYOUT\BUTTONS\C 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

2 File(s) 0 bytes

Directory of D:\SECURE\LAYOUT\CONFIG 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,562 CONFIG-3.PHP

3 File(s) 3,562 bytes

Directory of D:\SECURE\LAYOUT\CSS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 7,689 MACIE.CSS 0/09/01 08:36a 7,662 MACNAV.CSS 0/09/01 08:36a 7,642 UNIXNAV.CSS 0/09/01 08:36a 7,658 WINIE.CSS 0/09/01 08:36a 7,646 WINNAV.CSS

7 File(s) 38,297 bytes

Directory of D:\SECURE\LAYOUT\GRAPHICS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

2 File(s) 0 bytes

Directory of D:\SECURE\LAYOUT\ICONS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

2 File(s) 0 bytes

Directory of D:\SECURE\LAYOUT\lNCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 1,272 DUMMYH-3. INC 0/09/01 08:36a 346 FOOTER.INC 0/09/01 08:36a 346 HEADER.INC 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 340 NAV.INC

7 File(s) 2,304 bytes

Directory of D:\SECURE\LAYOUT\TNCLUDES\MASKING 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D :\SECURE\LAYOUT\iNCLUDES\MASKlNG\INCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\LAYOUT\ΓNCLUDE: 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 182 FOOTER.INC 0/09/01 08:36a 6,893 HEADER.INC 0/09/01 08:36a 6,121 NAV.INC

5 File(s) 13,196 bytes

Directory of D:\SECURE\LAYOUT\INCLUDES\MASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\LAYOUT\TNCLUDES\MASKTNG\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 293 MASKS.XML

3 File(s) 293 bytes

Directory of D:\SE CURE\LAYOUT\INCLUDE! 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\LAYOUT\TNCLUDEi 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

10/09/01 08:36a 182 FOOTER.INC

10/09/01 08:36a 6,914 HEADER.INC

10/09/01 08:36a 6,145 NAV.INC

5 File(s) 13,241 bytes

Directory of D:\SECURE\MASKING 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS

10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes Directory of D:\SECURE\MASKING\INCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\MASKING\INCLUDES\1 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 08:36a 6,806 CAT~3.HTM

10/09/01 08:36a 596 COOKIE~5.HTM

10/09/01 08:36a 384 ERRORS-7.PHP

10/09/01 08:36a 226 ERROR~A.HTM

10/09/01 08:36a 3,411 FORGOT~C.HTM

10/09/01 08:36a 4,071 INDEX2~F.HTM

10/09/01 08:36a 2,436 LOGIN~l l.HTM

10/09/01 08:36a 2,272 SITEM~13.HTM

10 File(s) 20,202 bytes

Directory of D:\SECURE\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\MASKTNG\MASKS\1

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,097 MASKS.XML

3 File(s) 3,097 bytes

Directory of D:\SECURE\MASKING\TMPL

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\MASKING\TMPL\1

10/09/01 02:36p <DIR>

10/09/01 08:36a 6,755 CAT~3.HTM

10/09/01 08:36a 362 COOKIE~5.HTM

10/09/01 08:36a 315 ERRORS-7.PHP

10/09/01 08:36a 231 ERROR~A.HTM

10/09/01 08:36a 3,391 FORGOT~C.HTM

10/09/01 08:36a 4,075 INDEX2~F.HTM

10/09/01 08:36a 2,435 LOGIN~l l.HTM

10/09/01 08:36a 2,278 SITEM~13.HTM

10 File(s) 19,842 bytes

Directory of D:\SECURE\TOOLS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> BIOS

10/09/01 02:36p <DTR> CAREERS 0/09/01 02:36p <DIR> CASE S~6 0/09/01 02:36p <DIR> DISCUS-8 0/09/01 08:36a 109 ERROR~B.HTM 0/09/01 02:36p <DIR> EVENTS 0/09/01 02:36p <DIR> FAQ 0/09/01 02:36p <DIR> FILES 0/09/01 02:36p <DIR> FORMS 0/09/01 02:36p <DIR> FREE -14 0/09/01 02:36p <DIR> GLOSSARY 0/09/01 02:36p <DIR> GZ DI-19 0/09/01 08:36a 671 INDEX~1B.HTM 0/09/01 02:36p <DIR> LINKS 0/09/01 02:36p <DIR> LOCAT-1F 0/09/01 02:36p <DIR> MAILI-21 0/09/01 02:36p <DIR> MEDIA-24 0/09/01 02:36p <DIR> NEWS 0/09/01 02:36p <DIR> PRODUCTS 0/09/01 02:36p <DIR> QUOTES

22 File(s) 780 bytes

Directory of D:\SECURE\TOOLS\BIOS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 262 ADD-3.HTM 0/09/01 08:36a 273 BIOSSC-5.SQL 0/09/01 08:36a 280 BIOSSC-8.SQL 0/09/01 08:36a 9,722 CLASSB-B.PHP 0/09/01 08:36a 332 ERRORS-D.PHP

10/09/01 08:36a 263 HEADE-10.PHP 0/09/01 08:36a 266 HOME~12.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 270 MODIF~16.HTM

10/09/01 08:36a 62 RESUL~19.HTM

10/09/01 08:36a 276 UNPUB~1B.HTM

10/09/01 08:36a 347 VIEW~1E.HTM

^: 14 File(s) 12,353 bytes

Directory

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> INCLUDES

10/09/01 02:36p <DIR> MASKS

10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\BIOS\MASKING\INCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\TOOLS\BIOS\MASKIN(

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,394 ADD~3.HTM

10/09/01 08:36a 862 ERRORS-5.PHP

10/09/01 08:36a 2,658 HOME~7.HTM

10/09/01 08:36a 6,200 MODIFY~9.HTM 0/09/01 08:36a 878 UNPUBL~C.HTM 0/09/01 08:36a 2,166 VIEW~E.HTM 8 File(s) 16,158 bytes

Directory of D:\SECURE\TOOLS\BIOS\MASKTNG\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\BIOS\MASKING\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 2,075 MASKS.XML

3 File(s) 2,075 bytes

Directory of D:\SECURE\TOOLS\BIOS\MASKTNG\TMPL 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\BIOS\MASKING\TMPL\l

10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,471 ADD~3.HTM 0/09/01 08:36a 663 ERRORS-5.PHP 0/09/01 08:36a 2,636 HOME-7.HTM 0/09/01 08:36a 6,281 MODIFY~9.HTM 0/09/01 08:36a 894 UNPUBL~C.HTM

10/09/01 08:36a 2,171 VIEW~E.HTM

8 File(s) 16,116 bytes

Directory of D:\SECURE\TOOLS\CAREERS

10/09/01 02:36p <DIR>

10/09/01 08:36a 293 ADD AP~3.HTM

10/09/01 08:36a 273 ADD~5.HTM

10/09/01 08:36a 1,023 CAREER-7.SQL 0/09/01 08:36a 1,223 CAREER-B.SQL

10/09/01 08:36a 27,483 CLASSC-E.PHP

10/09/01 08:36a 295 DROP ~10.HTM

10/09/01 08:36a 301 ERROR-13.PHP

10/09/01 08:36a 293 GREETING.PHP

10/09/01 08:36a 244 HEADE-18.PHP

10/09/01 08:36a 275 HOME~lB.HTM

10/09/01 08:36a 23 MAILTO.TXT

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 279 MODIF~21.HTM

10/09/01 08:36a 62 RESUL~24.HTM

10/09/01 08:36a 283 UNPUB~26.HTM

10/09/01 08:36a 295 VIEW -29.HTM

10/09/01 08:36a 275 VIEW-2B.HTM

: 19 File(s) 32,920 bytes

Directory of D:\SECURE\TOOLS\CAREERS\MASKTNG 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of D :\SECURE\TOOLS\C AREERSVMASKINGMNCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\TOOLS\CAREERS\MASKINGMNCLUDES\l 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 08:36a 4,446 ADD_AP~3.HTM

10/09/01 08:36a 5,878 ADD~5.HTM

10/09/01 08:36a 1,024 DROP_A~7.HTM

10/09/01 08:36a 2,130 ERRORS-A. PHP

10/09/01 08:36a 366 GREETING.PHP

10/09/01 08:36a 2,803 HOME~F.HTM

10/09/01 08:36a 7,364 MODIF~12.HTM

10/09/01 08:36a 62 RESUL~14.HTM

10/09/01 08:36a 919 UNPUB~16.HTM

10/09/01 08:36a 9,036 VIEW_~19.HTM

10/09/01 08:36a 3,912 VIEW~1C.HTM

13 File(s) 37,940 bytes

Directory of D:\SECURE\TOOLS\CAREERS\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\CAREERS\MASKING\MASKS\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 4,964 MASKS.XML

3 File(s) 4,964 bytes

Directory of D:\SECURE\TOOLS\CAREERS\MASKING\TMPL

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\CAREERS\MASKING\TMPL\l 10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 08:36a 4,537 ADD_AP~3.HTM

10/09/01 08:36a 6,017 ADD~5.HTM

10/09/01 08:36a 1,045 DROP_A~7.HTM 10/09/01 08:36a 1,754 ERRORS-A.PHP

10/09/01 08:36a 110 GREETING.PHP

10/09/01 08:36a 2,786 HOME~F.HTM 0/09/01 08:36a 7,539 MODIF~12.HTM 0/09/01 08:36a 62 RESUL~14.HTM 0/09/01 08:36a 935 UNPUB~16.HTM 0/09/01 08:36a 9,105 VIEW_~19.HTM 0/09/01 08:36a 4,005 VIEW~1C.HTM

13 File(s) 37,895 bytes

Directory of D:\SECURE\T00LS\CASE_S~6 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 272 ADD~3.HTM 0/09/01 08:36a 285 CASE_S~5.SQL 0/09/01 08:36a 283 CASE_S~8.SQL 0/09/01 08:36a 9,041 CLASSC-C.PHP 0/09/01 08:36a 276 ERRORS-F.PHP 0/09/01 08:36a 256 HEADE-12.PHP 0/09/01 08:36a 274 HOME~15.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 278 MODIF~19.HTM 0/09/01 08:36a 62 RESUL~1B.HTM 0/09/01 08:36a 284 UNPUB~1E.HTM 0/09/01 08:36a 274 VTEW~20.HTM

14 File(s) 11,585 bytes

Directory of D:\SECURE\TOOLS\CASE_S~6\MASKING 0/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> INCLUDES 10/09/01 02:36p <DIR> MASKS 10/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes Directory of D:\SECURE\TOOLS\CASE_S~6\MASKINGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\CASE_S~6\MASKINGMNCLUDES\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,268 ADD~3.HTM

10/09/01 08:36a 911 ERRORS-5.PHP

10/09/01 08:36a 2,584 HOME~8.HTM

10/09/01 08:36a 4,985 MODIFY~A.HTM

10/09/01 08:36a 886 UNPUBL~C.HTM

10/09/01 08:36a 2,082 VIEW~F.HTM

8 File(s) 14,716 bytes

Directory of D:\SECURE\TOOLS\CASE_S~6\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\CASE_S~6\MASKING\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 2,052 MASKS.XML 3 File(s) 2,052 bytes

Directory of D :\SECURE\TOOLS\CASE_S~6\MASKING\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\CASE_S~6\MASKING\TMPL\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,344 ADD~3.HTM 0/09/01 08:36a 691 ERRORS-5.PHP 0/09/01 08:36a 2,562 HOME~8.HTM 0/09/01 08:36a 5,065 MODIFY-A.HTM 0/09/01 08:36a 902 UNPUBL-C.HTM 0/09/01 08:36a 2,108 VIEW-F.HTM

8 File(s) 14,672 bytes Directory of D:\SECURE\TOOLSMDISCUS~8 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 287 ADDTOP~3.HTM 0/09/01 08:36a 277 ADD~5.HTM

10/09/01 08:36a 21,199 CLASSD-7.PHP

10/09/01 08:36a 303 DISCUS~A.HTM

10/09/01 08:36a 553 DISCUS-D.SQL

10/09/01 08:36a 586 DISCU-11.SQL

10/09/01 08:36a 289 DROPT-15.HTM

10/09/01 08:36a 291 ERROR-17.PHP

10/09/01 08:36a 328 HEADE-1B.PHP

10/09/01 08:36a 279 HOME~lE.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 283 MODIF-22.HTM

10/09/01 08:36a 293 MODIF~25.HTM

10/09/01 08:36a 187 RESUL~27.HTM

10/09/01 08:36a 289 UNPUB-2A.HTM

10/09/01 08:36a 279 VIEW-2C.HTM l8 File(s) 25,723 bytes

Directory of D:\SECU TOOLSMDISCUS~8\MASKTNG

10/09/01 02:36p <DΓR> 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> INCLUDES 10/09/01 02:36p <DIR> MASKS 10/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of D:\SECURE\TOOLSMDISCUS~8\MASKINGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DΓR>

3 File(s) 0 bytes Directory of D:\SECURE\TOOLSM3ISCUS~8\MASKlNGMNCLUDES\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,536 ADDTOP~3.HTM 0/09/01 08:36a 2,531 ADD~5.HTM 0/09/01 08:36a 10,986 DISCUS~7.HTM 0/09/01 08:36a 1,602 DROPTO~A.HTM 0/09/01 08:36a 1,486 ERRORS-D.PHP 0/09/01 08:36a 2,706 HOME~10.HTM 0/09/01 08:36a 3,823 MODIF~12.HTM 0/09/01 08:36a 3,623 MODIF~14.HTM 0/09/01 08:36a 955 UNPUB~17.HTM 0/09/01 08:36a 1,577 VIEW~1A.HTM

12 File(s) 32,825 bytes

Directory of D:\SECURE\TOOLSM3ISCUS~8\MASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM)ISCUS~8\MASKTNG\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,628 MASKS.XML 3 File(s) 3,628 bytes

Directory of D:\SECURE\TOOLSMDISCUS~8\MASKING\TMPL 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSMDISCUS~8\MASKING\TMPL\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,557 ADDTOP~3.HTM

10/09/01 08:36a 2,560 ADD~5.HTM

10/09/01 08:36a 10,954 DISCUS~7.HTM

10/09/01 08:36a 1.607 DROPTO~A.HTM

10/09/01 08:36a 1,093 ERRORS-D.PHP

10/09/01 08:36a 2,655 HOME~10.HTM

10/09/01 08:36a 3,856 MODIF~12.HTM

10/09/01 08:36a 3,673 MODIF~14.HTM

10/09/01 08:36a 954 UNPUB~17.HTM

10/09/01 08:36a 1,558 VIEW~1A.HTM

12 File(s) 32,467 bytes

Directory of D:\SECURE\TOOLSMiVENTS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 0/09/01 08:36a 267 ADD~3.HTM 0/09/01 08:36a 14,015 CLASSE-5.PHP

10/09/01 08:36a 258 ERRORS-7.PHP

10/09/01 08:36a 578 EVENTS-A.SQL

10/09/01 08:36a 576 EVENTS-D.SQL 0/09/01 08:36a 243 HEADE-10.PHP 0/09/01 08:36a 269 HOME~13.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 273 MODIF~17.HTM 0/09/01 08:36a 62 RESUL~19.HTM 0/09/01 08:36a 285 SEARC~1C.HTM 0/09/01 08:36a 279 UNPUB~1E.HTM 0/09/01 08:36a 269 VIEW~21.HTM

15 File(s) 17,374 bytes

Directory of D:\SE< URE\TOOLSMiVENTS\MASI 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes Directory of D:\SECURE\TOOLSMiVENTS\MASKlNGMNCLUDES 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE' CURE\TOOLSM VENTS\MASK 0/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 08:36a 7,246 ADD~3.HTM

10/09/01 08:36a 1,124 ERRORS-5. PHP

10/09/01 08:36a 3,704 HOME~7.HTM

10/09/01 08:36a 8,977 MODIFY-A.HTM

10/09/01 08:36a 4,285 SEARCH~C.HTM

10/09/01 08:36a 916 UNPUBL~F.HTM

10/09/01 08:36a 5,735 VIEW~11.HTM

9 File(s) 31,987 bytes Directory of D:\SECURE\TOOLSMiVENTS\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM5VENTS\MASKING\MASKS\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,771 MASKS. XML

3 File(s) 3,771 bytes

Directory of D:\SECURE\TOOLSMiVENTS\MASKlNG\TMPL

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM3VENTS\MASK1 J\TMPL\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 7.377 ADD~3.HTM 0/09/01 08:36a 853 ERRORS-5.PHP 0/09/01 08:36a 3,704 HOME~7.HTM 0/09/01 08:36a 9,112 MODIFY-A.HTM 0/09/01 08:36a 4,283 SEARCH~C.HTM 0/09/01 08:36a 932 UNPUBL~F.HTM 0/09/01 08:36a 5,878 VIEW-11. HTM

9 File(s) 32,139 bytes

Directory of D:\SECURE\TOOLS AQ 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 264 ADD~3.HTM 0/09/01 08:36a 9,225 CLASSF-5.PHP 0/09/01 08:36a 249 ERRORS-7.PHP 0/09/01 08:36a 273 FAQSCH-A.SQL 0/09/01 08:36a 262 FAQSCH-C.SQL 0/09/01 08:36a 238 HEADER-F.PHP 0/09/01 08:36a 266 HOME~12.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 270 MODIF~16.HTM 0/09/01 08:36a 62 RESUL~18.HTM 0/09/01 08:36a 277 UNPUB~1B.HTM 0/09/01 08:36a 266 VIEW~1D.HTM

14 File(s) 11,652 bytes Directory of D:\SECURE\TOOLS\FAQ\MASKTNG

Directory of D:\SECURE\TOOLSM AQVMASKTNGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM⁷ AQ\MASKTNGMNCLUDES\1

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 08:36a 2,677 ADD~3.HTM

10/09/01 08:36a 967 ERRORS-5.PHP

10/09/01 08:36a 2.647 HOME~7.HTM

10/09/01 08:36a 3,872 MODIFY~9.HTM

10/09/01 08:36a 62 RESULT~C.HTM 10/09/01 08:36a 911 UNPUBL~E.HTM

10/09/01 08:36a 1,590 VIEW- 11. HTM

9 File(s) 12,726 bytes

Directory of D:\SECURE\TOOLSM⁷ AQ\MASKING\MASKS

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1 3 File(s) 0 bytes

Directory of DΛSECUREVTOOLSΨAQ vIASKTNGNMASKSM 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 1,882 MASKS.XML 3 File(s) 1,882 bytes

Directory

0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS AQ\MASKTNG\TMPL\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 2,740 ADD~3.HTM 0/09/01 08:36a 753 ERRORS-5.PHP 0/09/01 08:36a 2,625 HOME~7.HTM 0/09/01 08:36a 3,939 MODIFY-9.HTM 0/09/01 08:36a 62 RESULT~C.HTM

10/09/01 08:36a 927 UNPUBL~E.HTM

10/09/01 08:36a 1,607 VIEW-11. HTM

9 File(s) 12,653 bytes

Directory of D:\SECURE\TOOLSMTLES

10/09/01 02:36p <DIR>

10/09/01 08:36a 266 ADD~3.HTM

10/09/01 08:36a 13,666 CLASSF-5.PHP

10/09/01 08:36a 255 ERRORS-7.PHP

10/09/01 08:36a 321 FILESS-A.SQL

10/09/01 08:36a 315 FILESS-D.SQL

10/09/01 08:36a 240 HEADE-10.PHP

10/09/01 08:36a 268 HOME~13.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 272 MODIF~17.HTM

10/09/01 08:36a 62 RESUL~19.HTM

10/09/01 08:36a 278 UNPUB~1B.HTM

10/09/01 08:36a 268 VIEW~1E.HTM

: 14 File(s) 16,211 bytes

Directory

Directory of D:\SECU TOOLS ILES\MASKINGMNCLUDES

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 1 as J> J> NJ to © © O o o LU

NO

NJ NJ

0/09/01 08:36a 293 UNPUB~1D.HTM 0/09/01 08:36a 283 VIEW~20.HTM 15 File(s) 17,554 bytes

Directory of D:\SECURE\TOOLS ORMS\M ASKING 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of DΛSECUREVTOOLSM^ORMSVMASKTNGMNCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM=ORMS\MASKΓNGMNCLUDES\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 5,456 ADD2~3.HTM

10/09/01 08:36a 2,094 ADD FO~5.HTM

10/09/01 08:36a 4,182 ADD~7.HTM

10/09/01 08:36a 3,251 ELEM D~9.HTM

10/09/01 08:36a 1,164 ERRORS-CPHP

10/09/01 08:36a 2,774 HOME~F.HTM

10/09/01 08:36a 2,588 MODIF~l l .HTM

10/09/01 08:36a 892 UNPUB~13.HTM

10/09/01 08:36a 7,358 VIEW~16.HTM

H File(s) 29,759 bytes

Directory of D:\SE( CUREYTOOLS FORMSXMASKJ

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE< CUREYTOOLSMORMSWIASK]

10/09/01 02:36p <DIR>

10/09/01 08:36a 5,925 MASKS.XML

3 File(s) 5,925 bytes Directory of D:\SECURJE\TOOLS θ S\MASKING\TMPL

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of DΛSECUREVTOOLSM'ORMSMVIASKINGXTMPLM

10/09/01 02 36p <DIR>

10/09/01 08 36a 5,553 ADD2~3.HTM

10/09/01 08 36a 2,030 ADD FO~5.HTM 0/09/01 08:36a 4,310 ADD~7.HTM 0/09/01 08:36a 2,555 ELEM D~9.HTM 0/09/01 08:36a 889 ERRORS-C.PHP 0/09/01 08:36a 2,747 HOME-F.HTM 0/09/01 08:36a 2,518 MODIF~l l .HTM 0/09/01 08:36a 908 UNPUB~13.HTM 0/09/01 08:36a 7,377 VIEW~16.HTM

11 File(s) 28,887 bytes Directory of DASECUREYTOOLSM^REE^M 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 278 ADD-3.HTM 0/09/01 08:36a 16,735 CLASSF-5.PHP 0/09/01 08:36a 358 ERRORS-8.PHP 0/09/01 08:36a 624 FREE F-B.SQL 0/09/01 08:36a 656 FREE F-F.SQL 0/09/01 08:36a 308 HEADE-13.PHP 0/09/01 08:36a 280 HOME~16.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 284 MODIF~lA.HTM 0/09/01 08:36a 62 RESUL~1D.HTM 0/09/01 08:36a 292 SET I~1F.HTM 0/09/01 08:36a 290 UNPUB~22.HTM

10/09/01 08:36a 455 VTEW.ΓNC

10/09/01 08:36a 229 VIEW~26.HTM l6 File(s) 20,851 bytes Directory of D:\SECUREYTOOLSMTlEE_~14\M ASKING

Directory of D:\SECU τOOLS REE_~14\MASKINGMNCLUDES

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of DΛSECUREVTOOLSM'REE^HVMASKlNGMNCLUDESM

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 08:36a 6.305 ADD~3.HTM

10/09/01 08:36a 948 ERRORS-5. PHP

10/09/01 08:36a 2,438 HOME~8.HTM

10/09/01 08:36a 8,204 MODIFY-A.HTM

10/09/01 08:36a 62 RESULT~D.HTM 10/09/01 08:36a 1,562 SET_IM~F.HTM

10/09/01 08:36a 905 UNPUB~11.HTM

10/09/01 08:36a 3,341 VIEW.INC

10 File(s) 23,765 bytes Directory of DΛSECUREYlOOLS REE -M vlASKING VlASKS

10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM^JREE_~14\MASKTNG\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 4,128 MASKS.XML 3 File(s) 4,128 bytes

Directory of DΛSECUREVTOOLSM'REE^H VIASKING^MPL

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM^;REE_~14\MASKrNG\TMPL\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 6.316 ADD~3.HTM

10/09/01 08:36a 693 ERRORS-5.PHP

10/09/01 08:36a 2,407 HOME-8.HTM

10/09/01 08:36a 8,221 MODIFY-A.HTM

10/09/01 08:36a 62 RESULT~D.HTM

10/09/01 08:36a 1,583 SET IM-F.HTM

10/09/01 08:36a 921 UNPUB~11.HTM

10/09/01 08:36a 3,346 VIEW.INC

1 [0 File(s) 23,549 bytes

Directory of D :\SECURE\TOOLS\GLOSS ARY

10/09/01 02:36p <DIR>

10/09/01 08:36a 281 ADD TE~3.HTM

10/09/01 08:36a 271 ADD~5.HTM

10/09/01 08:36a 25,333 CLASSG-7.PHP

10/09/01 08:36a 280 DROP T-A.HTM

10/09/01 08:36a 264 ERRORS-C.PHP

10/09/01 08:36a 761 GLOSSA-F.SQL

10/09/01 08:36a 788 GLOSS-12.SQL

10/09/01 08:36a 247 HEADE-16.PHP

10/09/01 08:36a 269 HOME~18.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 277 MODIF-ID.HTM

10/09/01 08:36a 284 MODIF-IF.HTM

10/09/01 08:36a 274 RELAT-21.HTM

10/09/01 08:36a 156 RESUL~24.HTM

10/09/01 08:36a 283 UNPUB~26.HTM

10/09/01 08:36a 283 VIEW ~29.HTM

10/09/01 08:36a 270 VTEW~2B.HTM

: 19 File(s) 30,321 bytes

Directory of D:\SECURE\TOOLS\GLOSSARY\MASKING

Directory of D:\SECURE\TOOLS\GLOSSARY\MASKlNGMNCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\TOOLS\GLOSSARY\MASKTNGMNCLUDES\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 2,109 ADD TE~3.HTM 0/09/01 08:36a 2,658 ADD~5.HTM 0/09/01 08:36a 859 DROP T~7.HTM 0/09/01 08:36a 2,107 ERRORS-A.PHP 0/09/01 08:36a 2,264 HOME~C.HTM 0/09/01 08:36a 3,614 MODIFY~F.HTM 0/09/01 08:36a 2,693 MODIF~l l.HTM 0/09/01 08:36a 3,609 RELAT~14.HTM 0/09/01 08:36a 779 UNPUB~16.HTM 0/09/01 08:36a 2,248 VIEW ~18.HTM 0/09/01 08:36a 4,205 VIEW~1B.HTM

13 File(s) 27,145 bytes

Directory of D:\SECURE\TOOLS\GLOSSARY\MASKING\MASKS

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\GLOSSARY\MASKLNG\MASKS\l

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 4,297 MASKS.XML 3 File(s) 4,297 bytes

Directory of D:\SECURE\TOOLS\GLOSSARY\MASKING\TMPL

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\GLOSSARY\MASKING\TMPL\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 2,113 ADD TE~3.HTM

10/09/01 08:36a 2,721 ADD~5.HTM

10/09/01 08:36a 871 DROP T~7.HTM

10/09/01 08:36a 1,586 ERRORS-A.PHP

10/09/01 08:36a 2,233 HOME~C.HTM

10/09/01 08:36a 3,681 MODIFY-F.HTM

10/09/01 08:36a 2,689 MODIF~l l.HTM

10/09/01 08:36a 3,558 RELAT~14.HTM

10/09/01 08:36a 791 UNPUB~16.HTM

10/09/01 08:36a 2,263 VIEW ~18.HTM

10/09/01 08:36a 4,181 VIEW~1B.HTM 13 File(s) 26,687 bytes Directory of D:\SECURE\TOOLS\GZ_DI~19 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 353 ADD EM~3.HTM 0/09/01 08:36a 337 ADD~5.HTM 0/09/01 08:36a 347 ADMIN -7.HTM 0/09/01 08:36a 33,633 CLASSG-A.PHP

10/09/01 08:36a 353 COPY E~D.HTM

10/09/01 08:36a 337 CSV~10.HTM

10/09/01 08:36a 369 DIREC~12.HTM

10/09/01 08:36a 350 DISPL~15.HTM

10/09/01 08:36a 353 DROP ~18.HTM 0/09/01 08:36a 355 EMPLO~lA.HTM 0/09/01 08:36a 285 ERROR-1D.PHP

10/09/01 08:36a 1,273 GZ DI-20.SQL

10/09/01 08:36a 1,290 GZ DI-24.SQL

10/09/01 08:36a 256 HEADE-27.PHP

10/09/01 08:36a 337 HOME~2A.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 339 MODIF~2E.HTM

10/09/01 08:36a 359 MODIF~30.HTM

10/09/01 08:36a 80 RESUL~33.HTM

10/09/01 08:36a 341 SEARC~36.HTM

10/09/01 08:36a 347 UNPUB~38.HTM

10/09/01 08:36a 337 VTEW~3A.HTM

>4 File(s) 42,031 bytes

Directory of D:\SECURE\TOOLS\GZ_DI~19\MASKING

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> INCLUDES 10/09/01 02:36p <DIR> MASKS 10/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes Directory of D:\SECURE\TOOLS\GZJDI~19\MASKlNGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\GZ_DI~19\MASKINGMNCLUDES\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 7,423 ADD_EM~3.HTM

10/09/01 08:36a 2.476 ADD~5.HTM

10/09/01 08:36a 5,659 ADMIN_~7.HTM

10/09/01 08:36a 4,244 COPY_E~A.HTM

10/09/01 08:36a 1.158 CSV~D.HTM

10/09/01 08:36a 7,223 DIRECT~F.HTM

10/09/01 08:36a 628 DISPL~12.HTM

10/09/01 08:36a 1,087 DROP_~15.HTM

10/09/01 08:36a 7,506 EMPLO~17.HTM

10/09/01 08:36a 1,853 ERROR-IA.PHP

10/09/01 08:36a 2,407 HOME-ID.HTM

10/09/01 08:36a 3,700 MODIF-IF.HTM 0/09/01 08:36a 8,222 MODIF~22.HTM 0/09/01 08:36a 5,368 SEARC~25.HTM 0/09/01 08:36a 884 UNPUB~27.HTM 0/09/01 08:36a 13,414 VIEW~29.HTM 18 File(s) 73,252 bytes

Directory of D:\SECURE\T00LS\GZ_DI~19\MASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\GZ_DI~19\MASKING\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 8,320 MASKS.XML

3 File(s) 8,320 bytes

Directory of D:\SECURE\TOOLS\GZ_DI~19\MASKING\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\GZ_DI~19\MASKING\TMPL\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 7,568 ADD EM~3.HTM

10/09/01 08:36a 2,539 ADD~5.HTM

10/09/01 08:36a 5,639 ADMIN -7.HTM

10/09/01 08:36a 4,258 COPY E~A.HTM

10/09/01 08:36a 1,113 CSV~D.HTM

10/09/01 08:36a 7,938 DIRECT~F.HTM

10/09/01 08:36a 633 DISPL~12.HTM

10/09/01 08:36a 1,108 DROP -15.HTM

10/09/01 08:36a 7,578 EMPLO~17.HTM

10/09/01 08:36a 1,392 ERROR-IA.PHP

10/09/01 08:36a 2,385 HOME-ID.HTM

10/09/01 08:36a 3,767 MODIF-IF.HTM

10/09/01 08:36a 8,363 MODIF~22.HTM

10/09/01 08:36a 5,368 SEARC~25.HTM

10/09/01 08:36a 900 UNPUB~27.HTM

10/09/01 08:36a 13,795 VIEW~29.HTM

] 18 File(s) 74,344 bytes Directory of D:\SECUREYTOOLSMJNKS

10/09/01 02:36p <DIR>

10/09/01 08:36a 266 ADD~3.HTM

10/09/01 08:36a 8,709 CLASSL-5.PHP

10/09/01 08:36a 255 ERRORS-7.PHP

10/09/01 08:36a 163 HEADER-A.PHP

10/09/01 08:36a 268 HOME~C.HTM

10/09/01 08:36a 346 LINKSS-F.SQL

10/09/01 08:36a 349 LINKS-12.SQL

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 272 MODIF~17.HTM 0/09/01 08:36a 62 RESUL~19.HTM 0/09/01 08:36a 278 UNPUB~1B.HTM 0/09/01 08:36a 721 VTEW~1E.HTM

14 File(s) 11,689 byl tes

Directory of D:\SEl ZUREXTOOU JMJNKSYMASKE 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes Directory of D :\SECURE\TOOLSM.ΓNKS\MASKINGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\TOOLSM.ΓNKSMVIASKI

10/09/01 02:36p <DIR>

10/09/01 08:36a 2,596 ADD~3.HTM

10/09/01 08:36a 911 ERRORS-5.PHP

10/09/01 08:36a 2,744 HOME~7.HTM

10/09/01 08:36a 3,769 MODIFY-9.HTM

10/09/01 08:36a 885 UNPUBL-C.HTM

7 File(s) 10,905 bytes

Directory of D:\SECURE\TOOLSM.INKS\MASKlNG\MASKS 10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\TOOLSM.INKS\MASKlNG\MASKS\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 1,988 MASKS.XML

3 File(s) 1,988 bytes

Directory of D:\SE ClJRE\TOOLSMJNKS\MASKl>

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE CURE\TOOLSM.INKS vIASKD

10/09/01 02:36p <DIR>

10/09/01 08:36a 2.639 ADD~3.HTM

10/09/01 08:36a 691 ERRORS-5.PHP

10/09/01 08:36a 2,722 HOME~7.HTM

10/09/01 08:36a 3,816 MODIFY~9.HTM

10/09/01 08:36a 901 UNPUBL-C.HTM 7 File(s) 10,769 bytes

Directory of D:\SECURE\TOOLSMX>CAT~lF 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 339 ADD~3.HTM 0/09/01 08:36a 13,030 CLASSL-5.PHP 0/09/01 08:36a 267 ERRORS-7.PHP 0/09/01 08:36a 248 HEADER-A.PHP 0/09/01 08:36a 341 HOME~D.HTM 0/09/01 08:36a 472 LOCATI-F.SQL

10/09/01 08:36a 491 LOCAT-13.SQL

10/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 343 MODIF~18.HTM 0/09/01 08:36a 62 RESUL~1A.HTM 0/09/01 08:36a 367 SEARC~1D.HTM

10/09/01 08:36a 349 UNPUB~20.HTM

10/09/01 08:36a 341 VTEW~22.HTM

15 File(s) 16,650 bytes

Directory of D:\SECURE\TOOLSM.OCAT~lF\MASKTNG

Directory of D:\SECURE\TOOLSM-OCAT~lF\MASKINGMNCLUDES

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM.OCAT~lF\MASKlNGMNCLUDES\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 5,876 ADD~3.HTM

10/09/01 08:36a 912 ERRORS-5.PHP

10/09/01 08:36a 3,838 HOME~8.HTM

10/09/01 08:36a 7,695 MODIFY-A.HTM

10/09/01 08:36a 4,314 SEARCH~C.HTM

10/09/01 08:36a 918 UNPUBL~F.HTM

10/09/01 08:36a 3,638 VIEW~11.HTM

9 File(s) 27,191 bytes

Directory of D:\SECURE\TOOLSM.OCAT~lF\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM.OCAT~lF\MASKING MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DΓR> 10/09/01 08:36a 2,709 MASKS.XML 3 File(s) 2,709 bytes

Directory of D:\SECURE\TOOLSM_OCAT~ 1F\MASKING\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM_OCAT~lF\MAf 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 5,977 ADD~3.HTM 0/09/01 08:36a 693 ERRORS-5.PHP 0/09/01 08:36a 3,844 HOME~8.HTM 0/09/01 08:36a 7,800 MODIFY-A.HTM 0/09/01 08:36a 4,293 SEARCH~C.HTM 0/09/01 08:36a 934 UNPUBL~F.HTM 0/09/01 08:36a 3,680 VIEW-11. HTM

9 File(s) 27,221 bytes Directory of D:\SECURE\TOOLS\MAILI~21

10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,155 CLASSM-3.PHP 0/09/01 08:36a 281 COMPOS~6.HTM 0/09/01 08:36a 277 ERRORS-8.PHP 0/09/01 08:36a 171 HEADER-B.PHP 0/09/01 08:36a 43 HOME~E.HTM

10/09/01 08:36a 137 MAILI-10.SQL

10/09/01 08:36a 140 MAILI-14.SQL

10/09/01 02:36p <DIR> MASKING

10 File(s) 4,204 bytes

Directory of D:\SECURE\TOOLS\MAILI~21\MASKlNG

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> INCLUDES 10/09/01 02:36p <DIR> MASKS 10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\MAILI~21\MASKTNGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\MAILI~21\MASKINGMNCLUDES\l 10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 08:36a 6,986 COMPOS~3.HTM

10/09/01 08:36a 221 ERRORS-5.PHP

4 File(s) 7,207 bytes

Directory of D:\SECURE\TOOLS\MAILI~21\MASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\T00LS\MAILI~21\MASKING\MASKS\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 1,185 MASKS.XML

3 File(s) 1,185 bytes

Directory of D:\SECURE\TOOLS\MAILI~21\MASKING\TMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\TOOLS\MAILI~21\MASKING\TMPL\1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 6,974 COMPOS~3.HTM 0/09/01 08:36a 209 ERRORS-5.PHP

4 File(s) 7,183 bytes

Directory of D:\SECURE\TOOLS\MEDIA~24 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

10/09/01 08:36a 273 ADD~3.HTM

10/09/01 08:36a 13,847 CLASSM-5.PHP

10/09/01 08:36a 280 ERRORS-8.PHP

10/09/01 08:36a 465 HEADER-B.PHP

10/09/01 08:36a 275 HOME-E.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 279 MODIF~12.HTM

10/09/01 08:36a 285 POSIT~14.HTM

10/09/01 08:36a 283 PUBLI~17.HTM

10/09/01 08:36a 62 RESUL~19.HTM

10/09/01 08:36a 285 UNPUB~1C.HTM

10/09/01 08:36a 295 UNPUB~1E.HTM

10/09/01 08:36a 275 VIEW~21.HTM

15 File(s) 16,904 bytes

Directory of D:\SECURE\TOOLS\MEDIA~24\MASKING

Directory of D:\SECU TOOLS\MEDIA~24VMASKINGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECURE\TOOLS\MEDIA~24\MASKINGMNCLUDES\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 2,014 ADD~3.HTM 0/09/01 08:36a 1,498 ERRORS-5.PHP 0/09/01 08:36a 2,697 HOME~8.HTM 0/09/01 08:36a 8,892 MODIFY-A.HTM 0/09/01 08:36a 4,443 POSITI~C.HTM 0/09/01 08:36a 9,291 PUBLIS~F.HTM 0/09/01 08:36a 893 UNPUB~11.HTM 0/09/01 08:36a 3,170 UNPUB~14.HTM 0/09/01 08:36a 3,532 VIEW~16.HTM

H File(s) 36,430 bytes

Directory of D:\SECURE\TOOLS\MEDIA~24\MASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\MEDIA~24\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 5,231 MASKS.XML 3 File(s) 5,231 bytes Directory of D:\SECURE\TOOLS\MEDIA~24\MASKING\TMPL

10/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\MEDIA~24\MASKING\TMPL\l

10/09/01 02:36p <DIR>

10/09/01 08:36a 2.036 ADD~3.HTM

10/09/01 08:36a 1,243 ERRORS-5.PHP

10/09/01 08:36a 2,675 HOME~8.HTM

10/09/01 08:36a 8,970 MODIFY-A.HTM

10/09/01 08:36a 4,492 POSITI~C.HTM

10/09/01 08:36a 9,267 PUBLIS~F.HTM

10/09/01 08:36a 909 UNPUB~11.HTM

10/09/01 08:36a 3,117 UNPUB~14.HTM

10/09/01 08:36a 3,587 VIEW~16.HTM

11 File(s) 36,296 bytes

Directory of D:\SECURE\TOOLS\NEWS

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>

10/09/01 08:36a 273 ADD~3.HTM

10/09/01 08:36a 11,920 CLASSN-5. PHP

10/09/01 08:36a 296 ERRORS-7.PHP

10/09/01 08:36a 238 HEADER-A.PHP 10/09/01 08:36a 282 HOME-C.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 286 MODIF-10.HTM 0/09/01 08:36a 418 NEWSS-13.SQL 0/09/01 08:36a 421 NEWSS-16.SQL 0/09/01 08:36a 62 RESUL~19.HTM 0/09/01 08:36a 283 UNPUB~1B.HTM 0/09/01 08:36a 280 VIEW~1E.HTM

14 File(s) 14,759 bytes

Directory of D:\SECURE\TOOLS\NEWSMvIASKTNG 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 0/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of D :\SECURE\TOOLSMSfEWS\MASKINGMNCLUDES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\NEWS\MASKINGMNCLUDES\l

10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR>

10/09/01 08:36a 4,678 ADD~3.HTM

10/09/01 08:36a 913 ERRORS-5.PHP

10/09/01 08:36a 2,702 HOME~7.HTM

10/09/01 08:36a 6,390 MODIFY~9.HTM

10/09/01 08:36a 911 UNPUBL-C.HTM

10/09/01 08:36a 1,952 VIEW~E.HTM

8 File(s) 17,546 bytes

Directory of D:\SECURE\TOOLS\NEWS\MASKING\MASKS

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\NEWS\MASKING\MASKS\l 10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR>

10/09/01 08:36a 2,500 MASKS.XML

3 File(s) 2,500 bytes Directory of D:\SECURE\TOOLS\NEWS\MASKTNG\TMPL

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1 3 File(s) 0 bytes

Directory of D:\SECURE\TOOLSWEWS\MASKING\TMPL\l

10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>

10/09/01 08:36a 4.785 ADD~3.HTM

10/09/01 08:36a 693 ERRORS-5.PHP 10/09/01 08:36a 2,677 HOME~7.HTM

10/09/01 08:36a 6,497 MODIFY~9.HTM

10/09/01 08:36a 927 UNPUBL-C.HTM

10/09/01 08:36a 1,957 VIEW~E.HTM

8 File(s) 17,536 bytes

Directory of D:\SECURE\TOOLSM>RODUCTS

10/09/01 02:36p <DIR>

1 10/09/01 02:36p <DIR>

10/09/01 08:36a 268 ADD~3.HTM

10/09/01 08:36a 16,358 CLASSP-5.PHP

10/09/01 08:36a 264 ERRORS-7.PHP

10/09/01 08:36a 247 HEADER-A.PHP

; ιo/09/oι 08:36a 270 HOME~D.HTM

10/09/01 02:36p <DIR> MASKING

10/09/01 08:36a 274 MODIF~l l.HTM

10/09/01 08:36a 521 PRODU-13.SQL

10/09/01 08:36a 637 PRODU-17.SQL

1 10/09/01 08:36a 274 RELAT~1A.HTM

10/09/01 08:36a 62 RESUL~1C.HTM

10/09/01 08:36a 280 UNPUB~1F.HTM

10/09/01 08:36a 278 UNREL~21.HTM

10/09/01 08:36a 270 VIEW~24.HTM l6 File(s) 20,003 bytes

Directory of D:\SEi CUREYTOOLSM'RODUCTS VD

10/09/01 02:36p <DIR>

) 10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> INCLUDES

10/09/01 02:36p <DIR> MASKS

10/09/01 02:36p <DIR> TMPL

5 File(s) 0 bytes

Directory of D:\SECURE\TOOLSM^>RODUCTS\MASKINGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SEi CURE\TOOLSM^>RODUCTS MA

10/09/01 02:36p <DIR>

10/09/01 08:36a 3,335 ADD~3.HTM

10/09/01 08:36a 1,472 ERRORS-5.PHP

10/09/01 08:36a 3,168 HOME~7.HTM

10/09/01 08:36a 5,066 MODIFY-A.HTM

10/09/01 08:36a 2,358 RELATE~C.HTM

10/09/01 08:36a 892 UNPUBL~E.HTM

10/09/01 08:36a 3,029 UNREL~11.HTM

10/09/01 08:36a 2,207 VIEW~13.HTM

10 File(s) 21,527 bytes

Directory of D:\SE< CURE\TOOLSM>RODUCTSMvIA

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D:\SECU TOOLSM^>RODUCTS\MASKING\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 4,083 MASKS.XML 3 File(s) 4,083 bytes

Directory of D :\SECURE\TOOLSM^>RODUCTSMvI ASKINGYTMPL 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS ODUCTS\MASKING\TMPL\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,413 ADD~3.HTM 0/09/01 08:36a 1,159 ERRORS-5.PHP 0/09/01 08:36a 3,138 HOME~7.HTM 0/09/01 08:36a 5.148 MODIFY~A.HTM 0/09/01 08:36a 2,267 RELATE~C.HTM 0/09/01 08:36a 908 UNPUBL~E.HTM 0/09/01 08:36a 2.946 UNREL-11.HTM 0/09/01 08:36a 2,216 VIEW-13.HTM

10 File(s) 21,195 bytes Directory of D:\SECURE\TOOLS\QUOTES 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 326 ADD~3.HTM 0/09/01 08:36a 9,560 CLASSQ-5.PHP 0/09/01 08:36a 258 ERRORS-7.PHP 0/09/01 08:36a 244 HEADER-A.PHP 0/09/01 08:36a 336 HOME~D.HTM 0/09/01 02:36p <DIR> MASKING 0/09/01 08:36a 334 MODIF~l l.HTM 0/09/01 08:36a 300 QUOTE-13.SQL

10/09/01 08:36a 295 QUOTE-16.SQL

10/09/01 08:36a 62 RESUL-19.HTM

10/09/01 08:36a 338 UNPUB-1C.HTM

10/09/01 08:36a 328 VIEW~1E.HTM

] 14 File(s) 12,381 bytes

Directory of D:\SECURE\TOOLS\QUOTES\MASKTNG 0/09/01 02:36p <DΓR> 10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> INCLUDES 0/09/01 02:36p <DIR> MASKS 10/09/01 02:36p <DIR> TMPL 5 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\QUOTES\MASKΓNGMNCLUDES

10/09/01 02:36p <DIR>

10/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes Directory of D :\SECURE\TOOLS\QUOTES\MASKINGMNCLUDES\ 1 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,509 ADD~3.HTM 0/09/01 08:36a 912 ERRORS-5.PHP 0/09/01 08:36a 2,697 HOME~7.HTM 0/09/01 08:36a 5,072 MODIFY-A.HTM 0/09/01 08:36a 911 UNPUBL-C.HTM 0/09/01 08:36a 1,765 VIEW~E.HTM

8 File(s) 14,866 bytes

Directory of D:\SECURE\TOOLS\QUOTES\MASKING\MASKS 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SECURE\TOOLS\QUOTES\MASKTNG\MASKS\l 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 2,416 MASKS.XML

3 File(s) 2,416 bytes

Directory of D:\SE< CURE\TOOLS\QUOTES\MASK 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 1

3 File(s) 0 bytes

Directory of D:\SE< CURE\TOOLS\QUOTES\MASK 0/09/01 02:36p <DIR> 0/09/01 02:36p <DIR> 0/09/01 08:36a 3,588 ADD~3.HTM 0/09/01 08:36a 693 ERRORS-5.PHP 0/09/01 08:36a 2,675 HOME~7.HTM 0/09/01 08:36a 5,153 MODIFY-A.HTM 0/09/01 08:36a 927 UNPUBL-C.HTM 0/09/01 08:36a 1,791 VIEW~E.HTM

8 File(s) 14,827 bytes

Total Files Listed:

1670 File(s) 2,550,485 bytes 0 bytes free

Claims

CLAIMSWe claim:

1. A method for a computer to interact with a user, the computer including a storage medium, the method comprising: identifying at least one category in which an item of information is classified, if the item is marked in the computer as being published to a group of users to which the user belongs; and storing data associating the item, the category and the user in the storage medium.

2. The method of claim 1, further comprising: performing the acts of identifying and storing in response to receiving data identifying the user.

3. The method of claim 2, further comprising: receiving the data identifying the user over a computer network from an input device used by the user.

4. The method of claim 2, further comprising: identifying the groups to which the user belongs from among a plurality of groups using the data identifying the user.

5. The method of claim 4, wherein: said category is part of a category hierarchy.

6. The method of claim 5, wherein the category hierarchy includes a plurality of levels, at least one top-level category in a designated level, and wherein the top-level category includes at least one least one category classified within it.

7. The method of claim 6, wherein the category is accessed from the top-level category via at least one intermediate category lying in a level between the top-level and the level of the identified category.

8. The method of claim 7, wherein each intermediate category lies at a different level.

9. The method of claim 5, further comprising: identifying a portion of the hierarchy of categories available for access by the user; and storing data associating the categories in the portion of the hierarchy of categories and the user in the storage medium.

10. The method of claim 9, the item in claim 1 being hereinafter "first item", wherein each category in the portion of the hierarchy of categories includes any of the following: at least one second item marked as being published to the group of users to which the user belongs; at least one category in which the second item is classified; and at least one intermediate category providing access to the category in which the second item is classified.

11. The method of claim 10, wherein the second item includes the first item.

12. The method of claim 9, the portion of the hierarchy of categories including at least one top-level category, wherein identifying the portion of the hierarchy of categories includes: if the category is not one of the top-level categories: determining the top-level category from which the category is accessed; and if the category is accessed from an intermediate category: determining the intermediate categories connecting the category to the top-level category.

13. The method of claim 5, wherein the category hierarchy is represented by at least one tree structure, wherein the tree structure includes at least one level, at least one node, including at least one top-level node, and wherein at least one category corresponds with one of the nodes.

14. The method of claim 13 , wherein identifying the portion of the hierarchy of categories includes: if the node corresponding to the category is not a top-level node: determining the top-level node lying on a branch connecting the node corresponding to the category; if the top-level node is connected to the node corresponding to the category via any intermediate nodes: determining the intermediate nodes.

15. The method of claim 5, further comprising: repeating the acts of identifying category and storing data for each category in which the item is classified.

16. The method of claim 15, the item being among a plurality of items marked as being published to at least one group from among the plurality of groups and to at least one category from among the category hierarchy, the method further comprising: repeating the acts of identifying and storing in claim 15 for a plurality of items marked in the computer as being published to the group of users to which the user belongs.

17. The method of claim 5, the item being among a plurality of items marked as being published to at least one group from among the plurality of groups and to at least one category from among the category hierarchy, further comprising: repeating the acts of identifying category and storing data for each item from among the plurality of items marked in the computer as being published to the group of users to which the user belongs; and repeating the acts of identifying category and storing data for each category in which each item is classified.

18. The method of claim 1 , further comprising: checking a permission associated with the item for the group to access the item; and using the permission during the identifying as a mark of the item being published.

19. The method of claim 18, wherein the permission includes a permission to view the item.

20. The method of claim 1, wherein the identifying includes querying a single database.

21. The method of claim 20, wherein the querying is performed using a database table associating the item, at least one category to which the item is published, and at least one group to which the user belongs.

22. The method of claim 16, wherein the identifying includes querying a single database.

23. The method of claim 9, the categories in the portion being hereinafter "dynamically-determined categories", the method further comprising: sending a description of at least one dynamically-determined category from among the portion of the hierarchy of categories to a display device used by the user.

24. The method of claim 23, further comprising: sending a link to the dynamically-determined category to the display device, wherein selection of the link by the user causes an instruction to be sent to the computer indicating a selection of the dynamically-determined category.

25. The method of claim 23, wherein the dynamically-determined category being sent is the category identified in the act of identifying.

26. The method of claim 23, wherein the dynamically-determined category includes a top-level category.

27. The method of claim 24, wherein the acts of sending are performed in response to receiving the data identifying the user.

28. The method of claim 24, wherein the link is a hyperlink and the description is a label for the hyperlink describing the dynamically-determined category.

29. The method of claim 24, further comprising: sending a description of at least one item classified within the dynamically-determined category and marked as being published to the group of users to which the user belongs to the user's display device.

30. The method of claim 29, further comprising: sending a link to the described item, wherein selection of the link by the user causes an instruction to be sent to the computer indicating a selection of the described item.

31. The method of claim 29, wherein the acts of sending are performed in response to receiving the data identifying the user.

32. The method of claim 24, further comprising: receiving the instruction from the user indicating the selection of the dynamically-determined category; and in response to receiving the instruction selecting the dynamically-determined category: sending a description to the user's display device of at least one item classified within the selected dynamically-determined category and marked as being published to the group of users to which the user belongs.

33. The method of claim 32, further comprising: in response to receiving the instruction selecting the dynamically-determined category: sending a link to the described item, wherein selection of the link by the user causes an instruction to be sent to the computer indicating a selection of the described item.

34. The method of claim 33, further comprising: receiving the instruction from the user indicating the selection of the described item; and in response to receiving the instruction selecting the described item: sending the described item to the user's display device.

35. The method of claim 32, the dynamically-determined category selected in claim 32 being hereinafter "first dynamically-determined category", the method further comprising: in response to receiving the instruction selecting the first dynamically-determined category: sending a description of at least one second dynamically-determined category classified within the first dynamically-determined category to the user's display device.

36. The method of claim 35, further comprising: in response to receiving the instruction selecting the first dynamically-determined category: sending a link to the second dynamically-determined category to the user's display device, wherein selection of the link by the user causes an instruction to be sent to the computer indicating a selection of the second dynamically-determined category.

37. A method for a computer to interact with a user, the method comprising: identifying one or more first items of information published to a user from among a plurality of items, wherein the first items are viewable by the user; determining a portion of a pre-determined hierarchy of categories in which the first items are classified; sending the portion of pre-determined hierarchy of categories to a display device used by the user; identifying one or more second items of information from among the plurality of items, wherein the second items are editable by the user; identifying a set of first tools from among a plurality of tools, wherein the first tools are to be used by the user to edit the second items; and sending links of the first tools to the display device used by the user.

38. The method of claim 37, wherein identifying the first items from among the plurality of items includes : determining at least one group assigned to the user; and determining each first item from among the plurality of items published to the group having a view privilege.

39. The method of claim 37, wherein identifying the set of first tools includes: determining at least one group assigned to the user; and determining each second item from among the plurality of items published to the group having an edit privilege.

40. The method of claim 37, further comprising: generating the portion of the pre-determined hierarchy, wherein the generating includes: for each item: identifying one or more first categories in the category hierarchy to which the item is published; and identifying one or more second categories in the category hierarchy required for accessing the first categories.

41. The method of claim 37, further comprising: identifying a second set of second tools from among the plurality of tools, wherein the second tools are to be used by the user to create new items and to edit one or more second items from among the plurality of items; and sending links of the second tools to the display device used by the user.

42. A method for a computer to interact with a user, the method comprising: entering information identifying the user into an input device; selecting a category from a portion of a pre-determined hierarchy of categories, wherein the portion of the category hierarchy is displayed subsequent to the act of entering the identifying information; and selecting one or more first items from among a plurality of items, wherein the first items are displayed subsequent to the act of selecting one or more categories.

43. The method of claim 42, further comprising: receiving the portion of the category hierarchy subsequent to the act of entering the identifying information.

44. The method of claim 42, further comprising: navigating through the categories of the portion of the category hierarchy using a pointing device.

45. The method of claim 42, wherein selecting provides access to at least one first item.

46. The method of claim 45, wherein access to the at least one first item includes access via one or more categories in the portion of the category hierarchy.

47. A computer-readable storage medium encoded with a table used in a database, the table comprising: a first column identifying one or more categories to which an item of information is published; and a second column identifying the item.

48. The computer-readable storage medium of claim 47, wherein the table further comprises: a third column identifying a right to use the item by a user.