WO2003032111A2 - Data driven access to tools - Google Patents

Data driven access to tools Download PDF

Info

Publication number
WO2003032111A2
WO2003032111A2 PCT/US2002/031282 US0231282W WO03032111A2 WO 2003032111 A2 WO2003032111 A2 WO 2003032111A2 US 0231282 W US0231282 W US 0231282W WO 03032111 A2 WO03032111 A2 WO 03032111A2
Authority
WO
WIPO (PCT)
Prior art keywords
dir
item
user
htm
tool
Prior art date
Application number
PCT/US2002/031282
Other languages
French (fr)
Other versions
WO2003032111A3 (en
Inventor
Jonathan C. Weiss
Ronen A. Botzer
Cameron J. Brown
Original Assignee
Grey Zone, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Grey Zone, Inc. filed Critical Grey Zone, Inc.
Priority to AU2002334770A priority Critical patent/AU2002334770A1/en
Publication of WO2003032111A2 publication Critical patent/WO2003032111A2/en
Publication of WO2003032111A3 publication Critical patent/WO2003032111A3/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2149—Restricted operating environment

Definitions

  • a programmed computer (hereafter "System") 10 which mediates access to a plurality of tools 30-34 for creating and publishing items of information, e.g., 36-40, by a plurality of users 24-28 to groups (not shown) of users is known.
  • a System 10 implemented in a networked environment in which the System 10 executes as a process on a server computer is also known. In these applications, the System 10 is accessed by multiple users 24-28 via a computer network from multiple client computers. For example, a user 24 logs into the System 10 over the computer network in order to access Tool X 30; user 24 then uses Tool X 30 for creating a new item of information, which the user then publishes to groups of users.
  • One example of conventional System 10 is Secure Zone 4.1, developed by Grey Zone, Inc., of Capitola, California.
  • Fig. IB users 1-3 24-28 access to Tools X-Z 30-34 via the conventional System 10 is mediated via one or more groups 42-46.
  • GroupA 42 includes a number of users (not shown), including user 1 24.
  • GroupB 44 is illustrated to include to users, userl 24, userl 24 and user2 26.
  • GroupC 46 likewise, includes one user includes one user, user 328.
  • the tools 30-34 available to the System 10 are previously assigned to the users or groups of users 42-46.
  • the assignment of tools 30-34 to groups 42-46 may be performed manually by a systems administrator.
  • the assignment of tools 30-34 to groups 42-46 dictates which of tools 30-34 will be available for access by users 24-28.
  • access is further regulated by the level of access granted to each group per tool.
  • these access levels consist of basic read/write privileges: read, allowing users to view content created with the given tool; write, allowing users to both create and edit content with the tool.
  • the higher-level write privileges subsume and therefore include read privileges as well.
  • the tools 30-34 accessible to each user 24-28 are illustrated in Fig. IC.
  • userl 24 may access ToolX 30, ToolY 32, and ToolZ 34; user2 26 may access ToolY 32, and ToolZ 34; and user3 28 may only access ToolZ 34.
  • iteml 36 having been created by ToolX 30 — must have been created by userl 24, because only userl 24 has access to ToolX 30.
  • Item2 38 having been created by ToolY 32 — may, likewise, have been created by either userl 24 or user2 26, because both userl 24 and user2 26 has access to ToolY 32.
  • all of the users24-28 may have created item3 40, because all of the users24-28 have access to ToolZ 34 for creating item3 40.
  • any item that a content producer wishes to maintain editorial control over must necessarily be made "viewable" to a group of which she is a member; this may result in cluttering up her important viewable content with items to which she had only wanted to maintain editorial access.
  • a method and system implemented by a programmed computer provisions a user's privileges to one or more tools, based on access to individual items of content (or data). For example, the System identifies an editing tool for use by a user if an item of information is marked in the System as being editable by a group of users to which the user belongs.
  • a user accesses the System over a computer network from a client computer, and provides data identifying the user (such as a "login ID") to the System.
  • the System automatically identifies a tool, using the data identifying the user.
  • the System sends a link to the tool to the user, e.g. embedded in a webpage.
  • privileges for accessing tools are provided to users (via the groups to which they belong) by item creators, on an item by item basis (i.e. the users may use the tools only on the specific items identified by the creators).
  • the System identifies a first subset of tools for use by the user, for editing items published as editable by a group to which a user belongs. In some embodiments, the System additionally identifies a second subset of tools for use by the user, for creating new items of information for publishing. In some embodiments, the editing and creation tools accessible by a user for creating, publishing and editing items of information are made available to the user when the user accesses the System.
  • Figs. 1 A-1C are block diagrams illustrating a conventional system for mediating a user's access to tools for publishing items of information to groups of users.
  • Fig. 2 is a flow chart illustrating a method for identifying a tool for use by a user, for editing an item of information published to a group of users to which the user belongs, according to some embodiments of the present invention.
  • Figs. 3A-3B are block diagrams illustrating an application of the method of Fig. 2 in the context of an example user, group, and tool association according to some embodiments of the present invention.
  • Fig. 4 is a flow chart illustrating additional process stages to the method of Fig. 2, according to some embodiments of the present invention.
  • Figs. 5A-5D illustrate, in screen shots, a user's login followed by a display of tools and items available to the user, followed modification of an item.
  • Fig. 6 is a flow chart illustrating yet additional process stages to the method of Fig. 2, according to some embodiments of the present invention.
  • Fig. 7 is a block diagram illustrating a hardware environment for a system, compatible with some embodiments of the present invention.
  • Fig. 8 is a block diagram illustrating a networked environment for a system compatible with some embodiments of the present invention.
  • Fig. 9 is a block diagram illustrating a software environment for a system compatible with some embodiments of the present invention.
  • Fig. 10 is a flow chart illustrating a method of making the tools identified using the methods of Figs. 2 and 6 available to a user, according to some embodiments of present invention.
  • Figs. 11 A and 1 IB are screenshots illustrating a link to an tool identified using the method of Fig. 10, according to some embodiments of the present invention.
  • Fig. 12 is a screenshot illustrating a webpage for use by the user for editing an item using a tool, according to some embodiments of the present invention.
  • Fig. 13 is a flow chart illustrating a method of making the tools identified using the method of Fig. 6 available to a user, according to some embodiments of the present invention.
  • Figs. 14-16 are screenshots illustrating webpages for use by the user for creating an item using a tool, according to some embodiments of the present invention.
  • Fig. 17 and 18 are entity-relationship diagrams illustrating data organization compatible with some embodiments of the present invention.
  • Fig. 19 is a flow chart illustrating a method of publishing an item, according to some embodiments of the present invention.
  • privileges in a programmed computer are provided to users based on the specific items of content to which they have access.
  • the privileges are related to the user's access to tools as discussed herein.
  • the privileges are related to categories in which the items are classified, as discussed in detail in related application entitled "DATA DRIVEN ACCESS TO CATEGORIES,” Attorney Docket No. M-11475 US filed concurrently by the same inventor, which is incorporated 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).
  • 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).
  • 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.
  • a computer is programmed to execute computer instructions for performing operations described by the stages in flow diagram 50 (Fig. 2).
  • a computer executing computer instructions implementing one of the various embodiments of the present invention is hereafter referred as the "System.”
  • the System determines whether an item of information is marked in the computer as being editable by group of users to which the user belongs.
  • stage 54 if the System determines that the item is marked in this manner, then the computer identifies a tool (hereafter “editing tool”) for use by the user for editing the item (stage 54).
  • the "type" of an item as used herein refers to the tool used to create a new item, and thereafter to access or edit the newly created item.
  • the System stores data in a storage medium associating the user with the tool. If the item is not marked in the manner described in stage 52, then the process ends, and a tool is not identified for use by the user to edit an item.
  • FIGs. 3 A and 3B An application of the process stages in flow diagram 50 in the context of an example user, group, and tool associations described in reference to Fig. IB is provided in Figs. 3 A and 3B, according to some embodiments of the present invention.
  • an example is provided in box 60 (Fig. 3A) in which a userl 24 accesses ToolX 30 to publish Iteml 36 to a GroupC 46 of users.
  • Fig. 3B illustrates the tools provided to the user3 28 accessing a System compatible with some embodiments of the present invention contrasted with conventional Systems.
  • conventional Systems as described in reference to Fig.
  • the System determines in stage 52 whether Iteml 36 is editable to group of users to which the user belongs.
  • Iteml 36 is illustrated in FIG. 3B as properly marked in accordance with stage 52 by additional boxes 70-72 illustrating Iteml 36 marked by "GroupC” and "Editable” respectively.
  • the System identifies Iteml 36 as properly marked as being editable (box 72) to a GroupC of users (box 70) to which the User3 34 belongs.
  • the System identifies Iteml 36 as having been created by ToolX 30 from data associated with Iteml 36, illustrated by naming Iteml 36 as "X: Iteml,” and as being thereby editable by ToolX 30.
  • the System identifies ToolX 30 for use by User3 28 for purposes of editing Iteml 36.
  • the act of identifying is, moreover, performed by the System via processing of item-level data, i.e., data associated with each item — e.g., Iteml 36 — published to a group of users to which the user belongs; this may be contrasted with conventional techniques where tools are previously assigned to users via the groups to which they belong.
  • data associating the tool identified by the System enabling a particular user to edit a particular item of information is stored in a storage medium.
  • the System may make the editing tool accessible to the user in a wide range of ways compatible with the present invention.
  • the System may send a webpage as illustrated in Fig. 5B to the User3 28 that includes a link 141 to a ToolX 30 selectable by the User3 28 for accessing the ToolX 30.
  • An example link is link 141 labeled "Bios" and describing the ToolX 30 for use in creating and publishing biographies to groups of users.
  • Other links to conventional tools for creating, publishing and editing items using a System compatible with the present invention are listed at 98 (FIG. 11 A) under the heading "Content Control.”
  • the System performs operations described in additional stages to flow diagram 50; these additional stages are illustrated by boxes 121 and 129 in Fig. 4B.
  • Box 121 includes three stages 122-126 performed by the System prior to stage 52.
  • the System receives data identifying the user; in some embodiments, the data is received during conventional authentication processes (such as login), requiring the user to enter a user ID and a password as illustrated in Fig. 5A.
  • the System identifies the groups to which the user belongs, using the data identifying the user, e.g., the user ID.
  • the groups to which a user belongs may be stored in a data structure associating the user ID of the user with the group IDs of the groups to which the user belongs.
  • the user may belong to multiple groups.
  • 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 System identifies all of the groups to which the user belongs (hereafter, "user groups") in stage 124, then in stage 126, the System identifies all of the items of information published to the groups.
  • Box 127 includes two stages that are performed after stages 52-54 (Fig. 2) which are compatible with some embodiments of the present invention. These additional stages are performed by the System for identifying multiple items editable by a user from among the items published to the groups to which the user belongs. In stage 128, therefore, the System determines whether more items are marked as being published to a group to which the user belongs, e.g., as identified in some embodiments in stages 124-126. If an additional item still awaits processing in stage 128, then the System resumes process at stage 52 to determine whether the additional item is marked as being editable by the group to which the user belongs.
  • the System identifies the particular tool required for editing the item (hereafter, "editing tool") from among a predetermined set of tools supported by the System, e.g., tool list 98.
  • the System determines whether an additional item (from among the items published to the groups to which the user belongs) is marked as editable by a group to which the user belongs.
  • process returns to stage 54 and the System identifies the editing tool for the additional item from among the predetermined set of tools. It should be noted that multiple items may be of the same type and may therefore be identified by the System multiple times in some embodiments compatible with the present invention. After all items editable by the particular user — and all editing tools corresponding to the editable items — have been identified by the System, then in stage 130, the System stores data associating the user with the editing tools.
  • a user is guaranteed to be provided access to editing tools for editing individual items published to the user, if the user has been granted editing privilege.
  • a user is limited to editing the particular item using the editing tool, and is prohibited from creating a new item using the editing tool (if the editing tool can also be used for item creation), thereby enabling a System administrator to more carefully control item creation, for purposes of, e.g., increased security.
  • a user has edit- only privileges to the Bios tool. Specifically, on login (See Fig. 5A) the user is provided with a screen (5B) that only provides access to the Bios tool via link 141 (Fig.
  • Fig. 5C displays a list 145 of each of a number of items that the user may edit using the Bios tool.
  • list 145 lists all items to which the user has access.
  • List 145 of one embodiment includes three columns, wherein, as illustrated in Fig. 5C, two columns contain icons of functionality that is available to the user, and the third column identifies (e.g. by name and/or title) the items that can be manipulated with the functionality. For example, an item having the name "Friday Wins" and the title
  • buttons on list 145 do not provide the user with the functionality to create a new item as described below in reference to Fig. 14.
  • the System in processing data identifying a user, performs additional operations described in additional stages to flow diagram 50; these additional stages are illustrated in box 169 in Fig. 6.
  • Tools for items editable by a user may be identified in stage 168 in the manner described above in reference to Fig. 6 in some embodiments, although other methods may be used in other embodiments. Thereafter, the stages of box 169 are performed.
  • Box 169 includes, in a first embodiment, stages 170-172, and, in a second embodiments, stage 172-174; the stages in Box 169 may be performed before the stages (not shown in Fig. 6) in Fig. 2, or after the stages described in Fig. 2.
  • the System identifies a tool (such as Bios) for use by the user in creating an item of information (hereafter, "creation tool").
  • the creation tool may be the same as or of same type as an editing tool to which the user may have obtained access.
  • the functionality for editing is provided independent of the functionality for creating.
  • the functionality for editing may be incapable of allowing a user to create an item, and vice versa. Therefore a user's creation rights do not grant the user editing privileges over any of the items created with the creation tool.
  • this stage 170 is performed by first identifying a group to which the user belongs, and then determining which creation tools have been previously assigned to the group (tools may be previously assigned to groups by a System administrator), thereby to determine whether or not the user has the privilege to create items using such tools.
  • the System stores data associating the user with the creation tool identified in stage 170.
  • the System performs a looping operation in which it identifies all creation tools for use by the user. This stage is performed by identifying every tool previously assigned to each group to which the user belongs.
  • a System compatible with the present invention performing the stages illustrated in Figs. 4 and 6 results in the identification of a first subset of editing tools from among the predetermined tools supported by the System, and a second subset of creation tools from among the predetermined tools, for access by the user.
  • Each subset may include a single tool, or the same tool.
  • the identification of the editing tools is determined at the item-level in which each item published to a group to which the user belongs is processed for purposes of determining whether the item is editable by the group; the identification of the creation tools, on the other hand, is conventionally determined at the group level in which creation tools are previously assigned to the groups of which the user is a member (by, for example, a System administrator).
  • the determination of editing and creation tools for each user compatible with the present invention enables a System to provide effective security — creation access to tools must be expressly granted by a system administrator, and edit access to tools must be expressly authorized by the item creator and is limited to the particular item — and intuitive user- friendliness — tools that the user cannot use for creating or editing an item are hidden from the user.
  • the System described in Figs. 2-6 is implemented in a hardware environment as illustrated in Fig. 7.
  • the Fig. 7 the
  • System is implemented in host computer 200 executing a system program 202 (illustrated within system memory 204) consisting of a sequence of computer instructions causing the host computer 200 to perform the various operations of present invention.
  • Host computer 200 is a general purpose computer that includes conventional hardware components.
  • host computer 200 includes at least one CPU 206 connected to a system memory 204 and a plurality of peripheral devices 208, the latter including a monitor 210 and a hard drive 212 comprising a magnetic storage medium for storing database 220.
  • the host computer 200 includes 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 204, and running Red Hat 7.0 Linux operating system, manufactured by Red Hat, Inc., of Durham, North Carolina. It should be noted that in some embodiments, the processes comprising System executing within host computer 200 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 220, including a database management system application layer, may be implemented in a second host computer (not shown) connected to the first host computer.
  • the database 610 may be distributed across multiple hard drives 608 implemented in the host computer 200, or in one or more other computers (not shown).
  • the construction of distributed, scalable systems and databases is well-known to those skilled in the art.
  • the System is implemented in a networked environment as illustrated in Figs. 7-8.
  • the server-side processes comprising the System are implemented in host server computer 200 and database server 201 hosting database management system processes.
  • System servers 200 and 201 located in physical location 304 (e.g., a secure server farm), are interconnected to, e.g., corporate Internet 310, physically located in first remote location 306, and, e.g., portable computer 308, located in second remote location 312, via computer network 325.
  • corporate intranet 310 may, in turn, include a plurality of interconnected computers, e.g., 320-324.
  • System servers 300 and 302 are connected to corporate intranet 310 and portable computer 308 via computer network 325.
  • computer network 325 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 325 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 communications link capable of delivering electronic content between computing devices.
  • Computer network 325 may operate with communication protocols other than TCP/IP, such as the Open Systems Interconnection developed by the International Standards Organization.
  • the System may be made available to a limited number of computing devices in a computer network, such as computers 320-324 in corporate intranet 512, in which the System may be hosted on, for example, computer 324.
  • Fig. 9 is a block diagram illustrating the software components used to implement some embodiments of the present invention.
  • the present invention is implemented using a three-tier programming architecture.
  • the first tier 380 includes a web browser 390 executing on, e.g., client computers 320-324.
  • Web browser 390 includes 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 382 includes software executing on the host computer, e.g., 200.
  • the software of second tier 382 includes business and presentation logic 398 operating within application/web server 392.
  • Application web server 392 in some embodiments, provides a container-managed solution (e.g.
  • the third tier 384 includes database management system software executing, according to some embodiments of the present invention, on database server 201.
  • Database management system 396 processes communicate with second tier 382 application processes via conventional JDBC, ODBC or other database APIs supported by conventional database drivers (not shown) typically manufactured and distributed by the particular manufacturer of the database management system software.
  • a JDBC/Database driver 394 may be included in software of the second tier 382 in certain embodiments
  • application/web server processes 392 are implemented using the 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.
  • business and presentation logic 398 are coded as Java classes within the J2EE specification (including the ente ⁇ rise javabeans (e.g., EJB 1.1) specifications well-known to those skilled in the art) as implemented by the BEA Weblogic application server 392.
  • database management system processes 396 are implemented using PostgreSQL 7.1, maintained and developed by the Open-Source Community.
  • a JDBC database driver (not shown) 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.
  • Apache Web server 1.3.20 (not shown) conventionally embedded with mod_php as an extension adds a PHP inte ⁇ reter to Apache (child) processes, thus enabling the Apache Web server to execute PHP programs embedded within the webpages it serves.
  • the PHP-enabled Apache Web server generally enables similar functionalities to be performed using PHP coded logic as is performed using business logic 398 operating within an application server (e.g., Weblogic).
  • PHP encoded processes access a MySQL 3.23.27 database management system directly from within the Apache Web server using wrappers around the native MySQL APIs.
  • the Apache Web server is executing within a Red Hat Linux Operating System.
  • users access the System executing on host server computer 200 (Fig. 7) via client computers 320-324 (Fig. 8) over computer network 325 using World Wide Web (HTTP, HTTPS) and other Internet (e.g., SNMP, FTP) communication protocols.
  • HTTP World Wide Web
  • HTTPS World Wide Web
  • other Internet e.g., SNMP, FTP
  • users send HTTP requests from their web browsers 390 to application/web server 392, which then processes the requests and returns responses (HTML or XML webpages) over HTTP to the users via the users' web browser 390.
  • Processing of the HTTP requests from the user is performed by business and presentation logic 398 operating within application web server container logic (also referred to as a "servlet engine") 392, and may typically include generating SQL queries for processing by database management system 396.
  • Web-based and other Internet communication protocols used for communicating between a host computer and one or more remote client computers will be apparent to those skilled in the art in view of the disclosure.
  • a user accesses the System hosted on server computer 200 via one or more login screens (webpages) sent by the System to be displayed on a display device attached to a client computer used by the user.
  • the System 200 receives data identifying the user via an HTTP request returned by the user (via the login screens), creates a session object (instantiated, e.g., using the Java HashMap class) for the user in the host computer file system, and proceeds to perform one or more of the processes described in Figs. 2-6.
  • a session object instantiated, e.g., using the Java HashMap class
  • the System identifies the groups to which the user belongs, the subset of creation tools assigned to those groups, the items published to those groups that are marked as editable by the groups, and the subset of editing tools corresponding the types of identified groups. Each editing tool is identified only once even if multiple items of the same type are marked as being editable by the user.
  • the subsets of creation and editing tools are then stored in, for example, respective data arrays in the user session object (not shown). Storing the creation and editing tools in the user session object increases, for example, the efficiency of the
  • the webpages dynamically generated by the System in response to user requests typically include links to the user's specific creation and editing tools; thus, the webpages may be dynamically generated using the tool data stored in the session object, instead of requiring the System to re-identify the tool subsets prior to generation ofa responsive webpage (typically, e.g., requiring the processing of one of more SQL queries by the database management system 396).
  • the System may make the tools available to the user in a vast number of ways falling within the scope of the present invention.
  • a method of making the tools available to a user in some embodiments of present invention is illustrated in Fig. 10.
  • the System After performing the stages in Fig. 2 (stage 200), the System, in stage 402, sends to the user a first link to the editing tool identified during performance of the stages in Fig. 2; an example first link 520 is illustrated in the webpage 91 provided in Fig. 11 A.
  • the first link 520 includes a hyperlink.
  • the client computer in response to user selection of the first link 520 (e.g., with a pointing device on the client computer), the client computer sends an instruction to the System over HTTP.
  • the System processes the instruction and sends a second link 450 included in a second webpage 452 (Fig. 1 IB).
  • the second link 450 links an item editable by the user using the editing tool selected in stage 402.
  • the second link is an HTML button marked with an "M” signifying the act of "modification;" in some embodiments, the button is positioned next to a description 451 of the editable item.
  • the System receives a selection of the second link 450 to the editable item, which causes the System to generate, in stage 410, a webpage 470 (Fig. 12) providing editing access to the described item 451 by the user, according to some embodiments.
  • the System provides editable access to an item by populating an HTML form with item information accessible by the user.
  • the user may then in some embodiments modify the information in item 451 or modify characteristics of the item 451, such as the groups to which the item is to be published.
  • the modifiable characteristics or content of an item will depend upon the type of the item.
  • Fig. 13 illustrates additional stages performed by a System according to some embodiments of the present invention.
  • the System After performing the stages in Fig. 6 (stage 400), the System, in stage 502, sends to the user a first link to the creation tool identified during performance of the stages in Fig. 6; a example first link 520 is illustrated in the webpage 91 provided in Fig. 11 A.
  • the first link 520 includes a conventional hyperlink, such as a URL.
  • stage 504 in response to receiving a user selection of the first link 520 (e.g., with a pointing device on the client computer), the client computer sends an instruction to the System over HTTP.
  • stage 506 the System processes the instruction and sends a second link 501
  • the second link 501 provides access to the functionalities of the creation tool, for creating a new item.
  • the second link 501 is an HTML button marked with "Add” signifying the act of adding an item to the System using the creation tool.
  • the System receives a selection of the second link 501, which causes the System to generate, in stage 510, a webpage 530 (Fig. 14) enabling a user to create a new item of information using the creation tool, according to some embodiments.
  • the creation of a new item using the creation tool is performed via one or more webpages programmed to receive information from a user and to send instructions (e.g., via user selection of a hyperlink) to the System causing the System to create the new item of information using the tool.
  • the user may select button 149 (Fig. 14) to add the new item of information to the System.
  • the System may generate additional webpages of the type illustrated in Figs. 15 and/or 16 to permit the user to respectively specify the users or groups of users that may receive access to the newly-created item, and/or the category or a portion of a predetermined hierarchy of categories in which the newly-created item is to be classified.
  • the System stores access privileges for specific pieces of content themselves.
  • the creator When a new piece of content is produced, the creator is directed to a hierarchically organized checklist of groups as potential targets for the content, with two checkboxes corresponding the View and Edit privileges respectively; an alternative embodiment provides one checkbox of a single privilege scheme which merely provides access privilege, to allow a user to both view and edit the item.
  • the user must specify the groups of users to whom the newly-created item is being published, so that the system marks the item for future use in identifying the newly-created item when providing access to a user in a group specified in webpage 531 (Fig. 15).
  • the user may also be permitted to specify certain constraints on use of the newly-created item by users, for example, specify an expiration date and time in fields 532, after which the item is no longer available to the users.
  • the user may specification an option in fields 533 to indicate that the item is permanently published.
  • the user may additionally specify in fields 534, the specific date and time of publication.
  • the newly-created item may be classified by the user that creates the item into a category, or a portion of a predetermined hierarchy of categories as illustrated in Fig. 16.
  • classification may be performed in an automated manner, by a method well known in the art.
  • Use of categories that are identified based on items to which users have access is described in the related U.S. Patent, Attorney Docket No. M-11472 US entitled “Data Driven Access To Categories" which has been inco ⁇ orated by reference above.
  • Categories function as containers for items of content.
  • Categories are more topical than systemic: they are created by users based on the needs of organizing the substance of their content. Insofar as categories are devoid of access permissions, using categories does not require any technical knowledge of the hierarchy tree in which they are organized.
  • the bottom-up approach is implemented by a System (of the type described in U.S. Patent Application M-11475) which grants access to categories based on a user's access to files, or the pieces of content, contained within the categories.
  • a privileging scheme a user is granted access by such a System to any categories necessary to allow him to navigate down (from the root level) to each item of content to which he has access.
  • his category tree 151 (Fig. 14) is constructed (in reverse) from the bottom up: all categories necessary and only the categories necessary are added to his category tree 151.
  • Such a category tree 151 may include multiple roots 151 A and 15 IB, depending on the embodiment.
  • the System processes, in stage 54
  • FIG. 17 illustrates an entity-relationship diagram describing data structures in a database compatible with some embodiments of the invention.
  • Data organization 525 includes three intersection tables 524, 522, and 526, a user table 528, a group table 530, a tool table 532, and an item repository 534.
  • the user table 528, group table 530, tool table 532, and item repository 534 provide columns for conventional storage of relevant information relating to the users, groups, tools and items respectively.
  • the item repository in some embodiments includes a number of item tables (not shown), wherein each item is identified by a combination of the tool ID and item ID.
  • intersection table 522 provides an "intersection" for the user table 528 and the group table 530. Accordingly, intersection table 522 in some embodiments includes a user ID column and a group ID column wherein a user ID (an entry in the user ID column) operates as a key for identifying a user in the user table 528, and a group ID (an entry in the group ID column) operates as a key for identifying a group in the group table 530. In some embodiments of the present invention, intersection table 524 provides an "intersection" for the group table 530, the tool table 532, and the item repository 534.
  • intersection table 524 (illustrated in tabular form as 524-1) includes an item ID column 524A, a tool ID column 524B, a group ID column 524C, and an edit privilege column 524D.
  • a tool ID, item ID, and group ID in a row entry in intersection table 524 provides respective keys for identifying a tool, an item typed by the tool (i.e., the tool is of the proper type used to edit the item), and a group to which the item is published (in tool table 532, item repository 534, and group table 530 respectively); an additional edit privilege marks the item as being editable by the group in addition to being published to the group; also a view privilege marks the item as being viewable by the group (by virtue of being published to the group).
  • intersection table 524 may be divided into two intersection tables: a first intersection table which includes item ID and category ID columns (not shown), and a second table which includes columns for a category DD and a group ID (not shown).
  • a query to identify an editing tool (or all editing tools) to be made available to a user — as performed in stage 540 (Figs. 2 and 5 respectively) — is first directed to intersection table 522 for identifying the groups to which a user belongs.
  • the identified groups are used to identify, using intersection table 524, the row entries in intersection table 524 the identified groups and an edit privilege.
  • the edit privilege in each row entry may be implemented in intersection 524 using a simple Boolean value.
  • the tools stored in the identified row entries accordingly comprise the subset of editing tools available for use by a particular user (via the groups to which the user belongs).
  • each item of information is not only identified by a user that creates the item, as being published to a group of users as illustrated in Fig. 16, but also identified as being classified into a specific category as illustrated in Fig. 16.
  • a database of the type discussed above in reference to Fig. 17 is modified to also include an intersection Table 804 (Fig. 18) of the type described in U.S. Patent Application Attorney Docket No. M-11475 US that has been inco ⁇ orated by reference above.
  • a System of the type described above may be programmed to implement a dual privilege scheme wherein each item may be made accessible to a user either for viewing only, editing only, both, or neither. Specifically, when creating (or editing a piece of content, the user is simply prompted to assign "View,” “Edit” or both privileges to each of several groups of users, as illustrated in Fig. 15.
  • a dual privilege scheme of the type described above overcomes a problem when users produce content to be viewed by other groups, and need to maintain editorial privileges over the content but do not want such items to be published to them.
  • each user either has access to a piece of content or not.
  • the type of access to the published items (that is, whether they are simply viewable or also editable) in a single privilege scheme is dictated by one's level of access to a tool through which the item was produced.
  • the creator has back-end access to the item she created via the tool through which the item was created; if the "edit-only" item were a "bio,” for instance, the creator would automatically be given a link 98 (Fig. 14) to the Bios tool; clicking on this link 98 would give her access to all the bios she has editorial access to (other bios to which she has only "View” access would appear on her category tree 151 according to the ways in which they have been categorized).
  • the System allows editorial privileges to be delegated on the content level, it helps minimize the global decisions required in giving groups access to tools. Group administrators no longer need to decide from the outset which groups will need to have editorial access to content produced in various tools; moreover, they won't have to wo ⁇ y about every group that needs editorial privileges having the capacity to create extraneous publications. Creators of items, on the other hand, don't have to worry about groups that have editorial access to a tool getting editorial access to an item published to them through that tool.
  • each tool used to create content is defined by a class which extends a parent class "Tools", and its child class push tools, both of which are contained in the file tools.classes.php.
  • Each tool inherits an instance of the class cat_tree_items (See file class.cat_tree.php), from it's extension of another class push_tool.
  • These inherited objects give the tools access to the item publishing methods contained in the class cat_tree_items.
  • These methods provide the access privileging and positioning (also known as "categorizing") mechanisms for the System.
  • the methods populate the table CAT_TREE_ITEMS in the database.
  • a user initially goes to a page 452 (Fig. 1 IB) that provides access to a number of tools under the heading 99 of "content control".
  • An example of such a tool is "Bios", which is used to create files limited to biographic information as described herein. Such files may contain text, images, sound, video clips, flash animations, and links to other documents that contain such information.
  • an off-the-shelf tool such as Microsoft Word, or Adobe Photoshop can be used in other embodiments of the type described herein.
  • access to the tools listed under the heading 99 is governed by the profile of the user. Specifically, the user has access only to those tools to which the user has a "creation” privilege, or alternatively to those tools required for items to which the user has “Edit” privilege. Thereafter, the user may select an "Add" button 501 (Fig. 1 IB) in stage 602, and as discussed above the user has access to such a button only for tools to which the user has the "Creation” privilege.
  • Each tool has a database table, which contains an identification of items that were created with that tool.
  • Each tool also has an "add” method in it's class which populates the tools table in the database with data submitted by the creator of the content.
  • Such data is provided by the creator in stage 603, by filling in the various fields of the type illustrated in Fig. 12.
  • the specific fields that are filled in vary according to the specific function of the tool. See the functions bios::add_bio C (and cat_tree_items::add_item C) in the Appendix.
  • a place holder row is entered into the table cat_tree_items with the group ID set to zero.
  • stage 604 the user selects a number of groups that will be provided access to the newly created item, and also determines the level of access (either by providing "Edit” or "View” privilege, or neither privilege as illustrated in Fig. 15.
  • Each tool uses a central access privileging mechanism implemented in the software in the Appendix, which software replaces the items place holder in the table CAT_TREE_ITEMS, with one row for each group that is granted access to the new item.
  • Each such row contains a unique ID for the new item, another ID for the tool (also called “TOOL ID”) that is used to create the item, a group ID for the selected group (with each group having its own row in the table), Boolean values for the "Edit” and “View” privileges of this group for this item and various other publishing information pertaining to the item (e.g. expiration date, and publishing date).
  • TOOL ID another ID for the tool
  • group ID for the selected group
  • Boolean values for the "Edit” and “View” privileges of this group for this item and various other publishing information pertaining to the item (e.g. expiration date, and publishing date).
  • each row in the table CAT_TREE_ITEMS for the new item has a category value (also called "CATJD”) which is set to zero.
  • CatJD category value
  • stage 605 the user selects the categories in which the item is to be published (the user can select one or more categories), as illustrated in Fig. 16.
  • the category tree illustrated in Fig. 16 is a portion of the predetermined category tree to which the user has access, and such a category tree may be same as (or in another embodiment different from) another category tree that allows the user to navigate to items that have been published to the user, as described in the related U.S. Patent Application, Attorney Docket No. M-11475 US.
  • each group row for the new item in the table CAT_TREE_ITEMS is multiplied by the number of categories into which the item is placed, and with the category value for these rows set to the appropriate values based on the category selections made by the creator. For more information, see the function cat_tree::position() in the appendix. Thereafter, the user is returned to the front page (Fig. 11 A).
  • the user object is basically 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 [after login] as the reference to the user object.
  • the $group_str represents a comma-delimited list of the groups of which the user is a member.
  • This method is used to produce an array of the administrative tools for a user. Access to these tools can only be provisioned by an administrator who specifically doles them out on a per-group basis.
  • the following SQL statement is used to return a list of these tools which is then rendered in an array and registered to the user object.
  • This method is used to produce an array of the "Creation" tools for a user — i.e., tools with which the user can add original content. Access to these tools can only be provisioned by an administrator who specifically doles them out on a per-group basis.
  • the following SQL statement is used to return a list of these tools which is then rendered in an array and registered to the user object.
  • This method is used to produce an array of the "Edit” tools for a user. Access to these tools is established through the process of determining all the items of content to which the user has “Edit” access and then automatically granting access to the tools necessary to exercise these edit privileges — i.e., the tools with which the pieces of content were produced. The operation of this method is central to the item-based tool-granting procedures elaborated above.
  • the following SQL statement is used to return a list of these tools which is then rendered in a an array and registered to the user object.
  • Secure_zone: :build_cat_tree() This is the method that is used to build a 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.
  • VERTUAL_ROOT and variable $vr refer to the user's virtual root.
  • a virtual root is the topmost node of system's group tree to which a user has access. These topmost nodes function as the root level for the particular user. Insofar as these nodes may exist at any level within the group tree hierarchy, they do not necessarily coincide with the real root level for the system's tree and are thus referred to as virtual roots. Virtual roots provide great flexibility in the design of a system, allowing completely discrete subtrees to exist within a larger system-level tree. These subtrees may be used to host independent entities, e.g., partner companies, in self-contained partitions of the larger system. Members of these subtrees can be administered by higher level users, but themselves are completely cut-off from data (and functionality) available to groups above their virtual root level.
  • variable Sgroup 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_ID FROM CAT_TREE_ITEMS WHERE GID 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 ID 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.
  • 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):
  • Volume in drive D is 01 1009_1436 Volume Serial Number is BCE2-6A1B

Abstract

A programmed computer ('System') identifies a tool for use by a user for editing an item of information (54), if the item is marked as being editable by the user (52) or alternatively by a group of users to which the user belongs. After identifying the tool, the System stores data associating the tool with the user or the group of users (156), depending on the embodiment. In some embodiments, a user acccesses the System over a computer network from a client computer, providing data identifying the user; in response, the System identifies the tool for user by the user for editing an item for information. In some embodiments, the System sends a link of the editing tool to the user. In some embodiments, the System additionally identifies a tool for use by the user for creating a new item, and send a link to the creation tool to the user. The creation tool may be identical to the editing tool, depending on the embodiment.

Description

DATA DRIVEN ACCESS TO TOOLS
BACKGROUND
A programmed computer (hereafter "System") 10 — as illustrated in Fig. 1 A — which mediates access to a plurality of tools 30-34 for creating and publishing items of information, e.g., 36-40, by a plurality of users 24-28 to groups (not shown) of users is known. A System 10 implemented in a networked environment in which the System 10 executes as a process on a server computer is also known. In these applications, the System 10 is accessed by multiple users 24-28 via a computer network from multiple client computers. For example, a user 24 logs into the System 10 over the computer network in order to access Tool X 30; user 24 then uses Tool X 30 for creating a new item of information, which the user then publishes to groups of users. One example of conventional System 10 is Secure Zone 4.1, developed by Grey Zone, Inc., of Capitola, California.
As illustrated in Fig. IB, users 1-3 24-28 access to Tools X-Z 30-34 via the conventional System 10 is mediated via one or more groups 42-46. For example, in Fig. IB, GroupA 42 includes a number of users (not shown), including user 1 24. GroupB 44 is illustrated to include to users, userl 24, userl 24 and user2 26. GroupC 46, likewise, includes one user includes one user, user 328. In the prior art, the tools 30-34 available to the System 10 are previously assigned to the users or groups of users 42-46. The assignment of tools 30-34 to groups 42-46 may be performed manually by a systems administrator. In the prior art, the assignment of tools 30-34 to groups 42-46 dictates which of tools 30-34 will be available for access by users 24-28. Moreover, such access is further regulated by the level of access granted to each group per tool. Generally, these access levels consist of basic read/write privileges: read, allowing users to view content created with the given tool; write, allowing users to both create and edit content with the tool. Here, the higher-level write privileges subsume and therefore include read privileges as well. Thus, given the user-group-tool association as provided in Fig. IB (and assuming that these associations represent write privileges), the tools 30-34 accessible to each user 24-28 are illustrated in Fig. IC.
Accordingly, userl 24 (by previous assignment) may access ToolX 30, ToolY 32, and ToolZ 34; user2 26 may access ToolY 32, and ToolZ 34; and user3 28 may only access ToolZ 34. Returning to Fig. 1 A, therefore, iteml 36 — having been created by ToolX 30 — must have been created by userl 24, because only userl 24 has access to ToolX 30. Item2 38 — having been created by ToolY 32 — may, likewise, have been created by either userl 24 or user2 26, because both userl 24 and user2 26 has access to ToolY 32. For similar reasons relating to the creation of iteml 36 and item2 38 all of the users24-28 may have created item3 40, because all of the users24-28 have access to ToolZ 34 for creating item3 40.
Applicant notes that the conventional System 10 described in reference to Figs. 1 A-1C includes a number of limitations. Since access to content is predicated on access to tools and tool access is controlled on a system administration level, content producers are both limited to and must bear in mind system level configurations when creating new items of content. Accordingly, a content producer must bear in mind if the group to which she wishes to publish a viewable item of content has read (i.e., view) access to the tool through which she produces the content; if not, the members of that group will be unable to view that item. Additionally, if she wishes to publish an item of content to a group that has write privileges for the tool through which she is producing the content, then, that group will have the ability to edit the item even though they were only meant to be able to view it. Furthermore, she is limited in delegating editorial privileges to the item of content only to a group that already has write access to the tool used to create the item. Finally, insofar as write privileges subsume read privileges, any item that a content producer wishes to maintain editorial control over must necessarily be made "viewable" to a group of which she is a member; this may result in cluttering up her important viewable content with items to which she had only wanted to maintain editorial access.
SUMMARY
A method and system implemented by a programmed computer ("System") provisions a user's privileges to one or more tools, based on access to individual items of content (or data). For example, the System identifies an editing tool for use by a user if an item of information is marked in the System as being editable by a group of users to which the user belongs.
In some embodiments, a user accesses the System over a computer network from a client computer, and provides data identifying the user (such as a "login ID") to the System. At that time, the System automatically identifies a tool, using the data identifying the user. In some embodiments, the System sends a link to the tool to the user, e.g. embedded in a webpage. In one embodiment, privileges for accessing tools are provided to users (via the groups to which they belong) by item creators, on an item by item basis (i.e. the users may use the tools only on the specific items identified by the creators).
In some embodiments, the System identifies a first subset of tools for use by the user, for editing items published as editable by a group to which a user belongs. In some embodiments, the System additionally identifies a second subset of tools for use by the user, for creating new items of information for publishing. In some embodiments, the editing and creation tools accessible by a user for creating, publishing and editing items of information are made available to the user when the user accesses the System.
BRIEF DESCRIPTION OF THE DRAWINGS
Figs. 1 A-1C are block diagrams illustrating a conventional system for mediating a user's access to tools for publishing items of information to groups of users.
Fig. 2 is a flow chart illustrating a method for identifying a tool for use by a user, for editing an item of information published to a group of users to which the user belongs, according to some embodiments of the present invention.
Figs. 3A-3B are block diagrams illustrating an application of the method of Fig. 2 in the context of an example user, group, and tool association according to some embodiments of the present invention.
Fig. 4 is a flow chart illustrating additional process stages to the method of Fig. 2, according to some embodiments of the present invention.
Figs. 5A-5D illustrate, in screen shots, a user's login followed by a display of tools and items available to the user, followed modification of an item.
Fig. 6 is a flow chart illustrating yet additional process stages to the method of Fig. 2, according to some embodiments of the present invention.
Fig. 7 is a block diagram illustrating a hardware environment for a system, compatible with some embodiments of the present invention.
Fig. 8 is a block diagram illustrating a networked environment for a system compatible with some embodiments of the present invention. Fig. 9 is a block diagram illustrating a software environment for a system compatible with some embodiments of the present invention.
Fig. 10 is a flow chart illustrating a method of making the tools identified using the methods of Figs. 2 and 6 available to a user, according to some embodiments of present invention.
Figs. 11 A and 1 IB are screenshots illustrating a link to an tool identified using the method of Fig. 10, according to some embodiments of the present invention.
Fig. 12 is a screenshot illustrating a webpage for use by the user for editing an item using a tool, according to some embodiments of the present invention.
Fig. 13 is a flow chart illustrating a method of making the tools identified using the method of Fig. 6 available to a user, according to some embodiments of the present invention.
Figs. 14-16 are screenshots illustrating webpages for use by the user for creating an item using a tool, according to some embodiments of the present invention.
Fig. 17 and 18 are entity-relationship diagrams illustrating data organization compatible with some embodiments of the present invention.
Fig. 19 is a flow chart illustrating a method of publishing an item, according to 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 tools as discussed herein. In another embodiment, the privileges are related to categories in which the items are classified, as discussed in detail in related application entitled "DATA DRIVEN ACCESS TO CATEGORIES," Attorney Docket No. M-11475 US filed concurrently by the same inventor, which is incorporated 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 is programmed to execute computer instructions for performing operations described by the stages in flow diagram 50 (Fig. 2). A computer executing computer instructions implementing one of the various embodiments of the present invention is hereafter referred as the "System." Turning to flow diagram 50, in stage 52, the System determines whether an item of information is marked in the computer as being editable by group of users to which the user belongs. In stage 54 if the System determines that the item is marked in this manner, then the computer identifies a tool (hereafter "editing tool") for use by the user for editing the item (stage 54).
The "type" of an item as used herein refers to the tool used to create a new item, and thereafter to access or edit the newly created item. In stage 56, the System stores data in a storage medium associating the user with the tool. If the item is not marked in the manner described in stage 52, then the process ends, and a tool is not identified for use by the user to edit an item.
An application of the process stages in flow diagram 50 in the context of an example user, group, and tool associations described in reference to Fig. IB is provided in Figs. 3 A and 3B, according to some embodiments of the present invention. In particular, an example is provided in box 60 (Fig. 3A) in which a userl 24 accesses ToolX 30 to publish Iteml 36 to a GroupC 46 of users. Given this example, Fig. 3B illustrates the tools provided to the user3 28 accessing a System compatible with some embodiments of the present invention contrasted with conventional Systems. In conventional Systems, as described in reference to Fig. 1, user3 28 is the only user belonging to GroupC 46, and therefore the System makes ToolZ 34 accessible to user3 34 because of previous assignment to GroupC 46 (by, for example, a System administrator). By contrast, in accordance with the process stages in flow diagram 50 of this invention, the System determines in stage 52 whether Iteml 36 is editable to group of users to which the user belongs. In this example, Iteml 36 is illustrated in FIG. 3B as properly marked in accordance with stage 52 by additional boxes 70-72 illustrating Iteml 36 marked by "GroupC" and "Editable" respectively. Thus, pursuant to stage 52, the System identifies Iteml 36 as properly marked as being editable (box 72) to a GroupC of users (box 70) to which the User3 34 belongs.
Next, in stage 54, the System identifies Iteml 36 as having been created by ToolX 30 from data associated with Iteml 36, illustrated by naming Iteml 36 as "X: Iteml," and as being thereby editable by ToolX 30. Thus, the System identifies ToolX 30 for use by User3 28 for purposes of editing Iteml 36. The act of identifying is, moreover, performed by the System via processing of item-level data, i.e., data associated with each item — e.g., Iteml 36 — published to a group of users to which the user belongs; this may be contrasted with conventional techniques where tools are previously assigned to users via the groups to which they belong. In stage 56, data associating the tool identified by the System enabling a particular user to edit a particular item of information is stored in a storage medium.
After the System identifies an editing tool for a particular user, the System may make the editing tool accessible to the user in a wide range of ways compatible with the present invention. In some embodiments, for example, the System may send a webpage as illustrated in Fig. 5B to the User3 28 that includes a link 141 to a ToolX 30 selectable by the User3 28 for accessing the ToolX 30. An example link is link 141 labeled "Bios" and describing the ToolX 30 for use in creating and publishing biographies to groups of users. Other links to conventional tools for creating, publishing and editing items using a System compatible with the present invention are listed at 98 (FIG. 11 A) under the heading "Content Control." Those skilled in the art will recognize that multiple ways of providing access to tools by users are known, and that the present invention is not intended to be limited to any particular way of providing such access.
In some embodiments of the present invention, the System performs operations described in additional stages to flow diagram 50; these additional stages are illustrated by boxes 121 and 129 in Fig. 4B. Box 121 includes three stages 122-126 performed by the System prior to stage 52. In stage 122, the System receives data identifying the user; in some embodiments, the data is received during conventional authentication processes (such as login), requiring the user to enter a user ID and a password as illustrated in Fig. 5A.
In stage 124, the System identifies the groups to which the user belongs, using the data identifying the user, e.g., the user ID. In some embodiments, the groups to which a user belongs may be stored in 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. After the System identifies all of the groups to which the user belongs (hereafter, "user groups") in stage 124, then in stage 126, the System identifies all of the items of information published to the groups.
Box 127 includes two stages that are performed after stages 52-54 (Fig. 2) which are compatible with some embodiments of the present invention. These additional stages are performed by the System for identifying multiple items editable by a user from among the items published to the groups to which the user belongs. In stage 128, therefore, the System determines whether more items are marked as being published to a group to which the user belongs, e.g., as identified in some embodiments in stages 124-126. If an additional item still awaits processing in stage 128, then the System resumes process at stage 52 to determine whether the additional item is marked as being editable by the group to which the user belongs. In stage 54, if the item is marked as editable, the System identifies the particular tool required for editing the item (hereafter, "editing tool") from among a predetermined set of tools supported by the System, e.g., tool list 98. In stage 128, the System determines whether an additional item (from among the items published to the groups to which the user belongs) is marked as editable by a group to which the user belongs.
If the System determines that an additional editable item exists, then process returns to stage 54 and the System identifies the editing tool for the additional item from among the predetermined set of tools. It should be noted that multiple items may be of the same type and may therefore be identified by the System multiple times in some embodiments compatible with the present invention. After all items editable by the particular user — and all editing tools corresponding to the editable items — have been identified by the System, then in stage 130, the System stores data associating the user with the editing tools.
In accordance with some embodiments of the present invention, therefore, a user is guaranteed to be provided access to editing tools for editing individual items published to the user, if the user has been granted editing privilege. In addition, a user is limited to editing the particular item using the editing tool, and is prohibited from creating a new item using the editing tool (if the editing tool can also be used for item creation), thereby enabling a System administrator to more carefully control item creation, for purposes of, e.g., increased security. In the example illustrated in Figs. 5B and 5C, a user has edit- only privileges to the Bios tool. Specifically, on login (See Fig. 5A) the user is provided with a screen (5B) that only provides access to the Bios tool via link 141 (Fig. 5B) in panel 140. In this example, when the user clicks on link 141 the user is presented with a screen (Fig. 5C) that displays a list 145 of each of a number of items that the user may edit using the Bios tool. In this example, list 145 lists all items to which the user has access.
List 145 of one embodiment includes three columns, wherein, as illustrated in Fig. 5C, two columns contain icons of functionality that is available to the user, and the third column identifies (e.g. by name and/or title) the items that can be manipulated with the functionality. For example, an item having the name "Friday Wins" and the title
"BALL", illustrated by label 144 A in Fig. 5C, can be de-published as illustrated by icon 143 A, or alternatively modified as illustrated by icon 142 A. On selection of icon 142 A, the user is presented with a screen (Fig. 5D) that allows the user to change, for example, the name "Friday Wins", the title "BALL", as well as the contents, e.g. contents of a biography text field, and the image as illustrated in Fig. 5D. The links in list 145 only provide functionality that has been approved by a creator of the item in the list. For example, the buttons on list 145 do not provide the user with the functionality to create a new item as described below in reference to Fig. 14.
In certain embodiments of the present invention, in processing data identifying a user, the System performs additional operations described in additional stages to flow diagram 50; these additional stages are illustrated in box 169 in Fig. 6. Tools for items editable by a user may be identified in stage 168 in the manner described above in reference to Fig. 6 in some embodiments, although other methods may be used in other embodiments. Thereafter, the stages of box 169 are performed.
Box 169 includes, in a first embodiment, stages 170-172, and, in a second embodiments, stage 172-174; the stages in Box 169 may be performed before the stages (not shown in Fig. 6) in Fig. 2, or after the stages described in Fig. 2. Turning to Fig. 6, in stage 170, the System identifies a tool (such as Bios) for use by the user in creating an item of information (hereafter, "creation tool"). Depending on the example, the creation tool may be the same as or of same type as an editing tool to which the user may have obtained access.
However, the functionality for editing is provided independent of the functionality for creating. For example, depending on the embodiment, the functionality for editing may be incapable of allowing a user to create an item, and vice versa. Therefore a user's creation rights do not grant the user editing privileges over any of the items created with the creation tool.
In some embodiments, this stage 170 is performed by first identifying a group to which the user belongs, and then determining which creation tools have been previously assigned to the group (tools may be previously assigned to groups by a System administrator), thereby to determine whether or not the user has the privilege to create items using such tools. In stage 172, the System stores data associating the user with the creation tool identified in stage 170. In optional stage 174, the System performs a looping operation in which it identifies all creation tools for use by the user. This stage is performed by identifying every tool previously assigned to each group to which the user belongs.
Accordingly, a System compatible with the present invention performing the stages illustrated in Figs. 4 and 6 results in the identification ofa first subset of editing tools from among the predetermined tools supported by the System, and a second subset of creation tools from among the predetermined tools, for access by the user. Each subset may include a single tool, or the same tool. In particular, the identification of the editing tools is determined at the item-level in which each item published to a group to which the user belongs is processed for purposes of determining whether the item is editable by the group; the identification of the creation tools, on the other hand, is conventionally determined at the group level in which creation tools are previously assigned to the groups of which the user is a member (by, for example, a System administrator). The determination of editing and creation tools for each user compatible with the present invention enables a System to provide effective security — creation access to tools must be expressly granted by a system administrator, and edit access to tools must be expressly authorized by the item creator and is limited to the particular item — and intuitive user- friendliness — tools that the user cannot use for creating or editing an item are hidden from the user.
In some embodiments of the present invention, the System described in Figs. 2-6 is implemented in a hardware environment as illustrated in Fig. 7. In particular, the
System is implemented in host computer 200 executing a system program 202 (illustrated within system memory 204) consisting ofa sequence of computer instructions causing the host computer 200 to perform the various operations of present invention. Host computer 200 is a general purpose computer that includes conventional hardware components. In particular, host computer 200 includes at least one CPU 206 connected to a system memory 204 and a plurality of peripheral devices 208, the latter including a monitor 210 and a hard drive 212 comprising a magnetic storage medium for storing database 220.
In some embodiments of the present invention, the host computer 200 includes 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 204, and running Red Hat 7.0 Linux operating system, manufactured by Red Hat, Inc., of Durham, North Carolina. It should be noted that in some embodiments, the processes comprising System executing within host computer 200 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 220, including a database management system application layer, may be implemented in a second host computer (not shown) connected to the first host computer. In yet other embodiments, the database 610 may be distributed across multiple hard drives 608 implemented in the host computer 200, or in one or more other computers (not shown). The construction of distributed, scalable systems and databases is well-known to those skilled in the art. In some embodiments of the present invention, the System is implemented in a networked environment as illustrated in Figs. 7-8. In some embodiments, the server-side processes comprising the System are implemented in host server computer 200 and database server 201 hosting database management system processes. System servers 200 and 201, located in physical location 304 (e.g., a secure server farm), are interconnected to, e.g., corporate Internet 310, physically located in first remote location 306, and, e.g., portable computer 308, located in second remote location 312, via computer network 325. Corporate intranet 310 may, in turn, include a plurality of interconnected computers, e.g., 320-324. System servers 300 and 302 are connected to corporate intranet 310 and portable computer 308 via computer network 325.
In some embodiments, computer network 325 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 325 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 communications link capable of delivering electronic content between computing devices. Computer network 325 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 in some embodiments of the present invention, the System may be made available to a limited number of computing devices in a computer network, such as computers 320-324 in corporate intranet 512, in which the System may be hosted on, for example, computer 324.
Fig. 9 is a block diagram illustrating the software components used to implement some embodiments of the present invention. In some embodiments, the present invention is implemented using a three-tier programming architecture. The first tier 380 includes a web browser 390 executing on, e.g., client computers 320-324. Web browser 390 includes 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 382 includes software executing on the host computer, e.g., 200. The software of second tier 382 includes business and presentation logic 398 operating within application/web server 392. Application web server 392, in some embodiments, provides a container-managed solution (e.g. EJB containers) for, e.g., Java implementations of business and presentation logic 398; the use of a servlet engine or an application server within which application processes are coded in the methods described herein will be apparent to those skilled in the art in view of the disclosure. The third tier 384 includes database management system software executing, according to some embodiments of the present invention, on database server 201. Database management system 396 processes communicate with second tier 382 application processes via conventional JDBC, ODBC or other database APIs supported by conventional database drivers (not shown) typically manufactured and distributed by the particular manufacturer of the database management system software. A JDBC/Database driver 394 may be included in software of the second tier 382 in certain embodiments
In some embodiments of the present invention, application/web server processes 392 are implemented using the 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 398 are coded as Java classes within the J2EE specification (including the enteφrise javabeans (e.g., EJB 1.1) specifications well-known to those skilled in the art) as implemented by the BEA Weblogic application server 392. In some embodiments, database management system processes 396 are implemented using PostgreSQL 7.1, maintained and developed by the Open-Source Community. In some embodiments of the present invention, a JDBC database driver (not shown) 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 a PHP inteφreter 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 398 operating within an application server (e.g., Weblogic). In some embodiments, PHP encoded processes access a MySQL 3.23.27 database management system directly from within the Apache Web server using 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 server computer 200 (Fig. 7) via client computers 320-324 (Fig. 8) over computer network 325 using World Wide Web (HTTP, HTTPS) and other Internet (e.g., SNMP, FTP) communication protocols. In these embodiments, users send HTTP requests from their web browsers 390 to application/web server 392, which then processes the requests and returns responses (HTML or XML webpages) over HTTP to the users via the users' web browser 390. Processing of the HTTP requests from the user is performed by business and presentation logic 398 operating within application web server container logic (also referred to as a "servlet engine") 392, and may typically include generating SQL queries for processing by database management system 396. Web-based and other Internet communication protocols used for communicating between a host computer and one or more remote client computers will be apparent to those skilled in the art in view of the disclosure.
Accordingly, in some embodiments of the present invention, a user accesses the System hosted on server computer 200 via one or more login screens (webpages) sent by the System to be displayed on a display device attached to a client computer used by the user. The System 200 receives data identifying the user via an HTTP request returned by the user (via the login screens), creates a session object (instantiated, e.g., using the Java HashMap class) for the user in the host computer file system, and proceeds to perform one or more of the processes described in Figs. 2-6. In particular, in those embodiments where the stages in Fig. 6 are performed, the System identifies the groups to which the user belongs, the subset of creation tools assigned to those groups, the items published to those groups that are marked as editable by the groups, and the subset of editing tools corresponding the types of identified groups. Each editing tool is identified only once even if multiple items of the same type are marked as being editable by the user.
The subsets of creation and editing tools are then stored in, for example, respective data arrays in the user session object (not shown). Storing the creation and editing tools in the user session object increases, for example, the efficiency of the
System for puφoses of processing repeated HTTP requests from the user. Efficiency is increased because the webpages dynamically generated by the System in response to user requests typically include links to the user's specific creation and editing tools; thus, the webpages may be dynamically generated using the tool data stored in the session object, instead of requiring the System to re-identify the tool subsets prior to generation ofa responsive webpage (typically, e.g., requiring the processing of one of more SQL queries by the database management system 396).
After the System identifies the subsets of editing and creation tools accessible to a particular user (as described in reference to Figs. 2-6), the System may make the tools available to the user in a vast number of ways falling within the scope of the present invention. A method of making the tools available to a user in some embodiments of present invention is illustrated in Fig. 10. After performing the stages in Fig. 2 (stage 200), the System, in stage 402, sends to the user a first link to the editing tool identified during performance of the stages in Fig. 2; an example first link 520 is illustrated in the webpage 91 provided in Fig. 11 A. In typical embodiments, the first link 520 includes a hyperlink. In stage 402, in response to user selection of the first link 520 (e.g., with a pointing device on the client computer), the client computer sends an instruction to the System over HTTP.
In stage 406, the System processes the instruction and sends a second link 450 included in a second webpage 452 (Fig. 1 IB). The second link 450 links an item editable by the user using the editing tool selected in stage 402. In some embodiments, the second link is an HTML button marked with an "M" signifying the act of "modification;" in some embodiments, the button is positioned next to a description 451 of the editable item. In stage 408, the System receives a selection of the second link 450 to the editable item, which causes the System to generate, in stage 410, a webpage 470 (Fig. 12) providing editing access to the described item 451 by the user, according to some embodiments. In some embodiments, the System provides editable access to an item by populating an HTML form with item information accessible by the user. The user may then in some embodiments modify the information in item 451 or modify characteristics of the item 451, such as the groups to which the item is to be published. The modifiable characteristics or content of an item will depend upon the type of the item.
The example illustrated in Figs. 11 A and 1 IB are similar to the example illustrated in Fig. 5C except for button 501, described next. Specifically, Fig. 13 illustrates additional stages performed by a System according to some embodiments of the present invention. After performing the stages in Fig. 6 (stage 400), the System, in stage 502, sends to the user a first link to the creation tool identified during performance of the stages in Fig. 6; a example first link 520 is illustrated in the webpage 91 provided in Fig. 11 A. In typical embodiments, the first link 520 includes a conventional hyperlink, such as a URL. In stage 504 (Fig. 13), in response to receiving a user selection of the first link 520 (e.g., with a pointing device on the client computer), the client computer sends an instruction to the System over HTTP.
In stage 506, the System processes the instruction and sends a second link 501
(Fig. 1 IB) included in a second webpage 452. The second link 501 provides access to the functionalities of the creation tool, for creating a new item. In some embodiments, the second link 501 is an HTML button marked with "Add" signifying the act of adding an item to the System using the creation tool. In stage 508, the System receives a selection of the second link 501, which causes the System to generate, in stage 510, a webpage 530 (Fig. 14) enabling a user to create a new item of information using the creation tool, according to some embodiments. In some embodiments, the creation of a new item using the creation tool is performed via one or more webpages programmed to receive information from a user and to send instructions (e.g., via user selection of a hyperlink) to the System causing the System to create the new item of information using the tool.
After filling in the information in various field of webpage 530, the user may select button 149 (Fig. 14) to add the new item of information to the System. At this time, depending on the embodiment, the System may generate additional webpages of the type illustrated in Figs. 15 and/or 16 to permit the user to respectively specify the users or groups of users that may receive access to the newly-created item, and/or the category or a portion of a predetermined hierarchy of categories in which the newly-created item is to be classified. The System stores access privileges for specific pieces of content themselves. When a new piece of content is produced, the creator is directed to a hierarchically organized checklist of groups as potential targets for the content, with two checkboxes corresponding the View and Edit privileges respectively; an alternative embodiment provides one checkbox of a single privilege scheme which merely provides access privilege, to allow a user to both view and edit the item.
In one embodiment, as illustrated in Fig. 15, the user must specify the groups of users to whom the newly-created item is being published, so that the system marks the item for future use in identifying the newly-created item when providing access to a user in a group specified in webpage 531 (Fig. 15).
Depending on the implementation, the user may also be permitted to specify certain constraints on use of the newly-created item by users, for example, specify an expiration date and time in fields 532, after which the item is no longer available to the users. Alternatively, the user may specification an option in fields 533 to indicate that the item is permanently published. The user may additionally specify in fields 534, the specific date and time of publication.
Also, depending on the embodiment, the newly-created item may be classified by the user that creates the item into a category, or a portion of a predetermined hierarchy of categories as illustrated in Fig. 16. Alternatively, such classification may be performed in an automated manner, by a method well known in the art. Use of categories that are identified based on items to which users have access is described in the related U.S. Patent, Attorney Docket No. M-11472 US entitled "Data Driven Access To Categories" which has been incoφorated by reference above.
The user may be prompted (Fig. 16) to decide in which category or categories he wishes to place the item. Categories function as containers for items of content.
Categories, however, are more topical than systemic: they are created by users based on the needs of organizing the substance of their content. Insofar as categories are devoid of access permissions, using categories does not require any technical knowledge of the hierarchy tree in which they are organized. On the contrary, the bottom-up approach is implemented by a System (of the type described in U.S. Patent Application M-11475) which grants access to categories based on a user's access to files, or the pieces of content, contained within the categories. Through a privileging scheme, a user is granted access by such a System to any categories necessary to allow him to navigate down (from the root level) to each item of content to which he has access. When a user logs in, his category tree 151 (Fig. 14) is constructed (in reverse) from the bottom up: all categories necessary and only the categories necessary are added to his category tree 151. Such a category tree 151 may include multiple roots 151 A and 15 IB, depending on the embodiment.
Moreover, in each category granted to the user, such a System only displays pieces of content to which the user has been granted access. In other words, some of the user's categories may appear empty — granted uniquely as empty passageways to content in subcategories below. Ultimately, the upshot is the production of an extremely natural user experience. A user simply creates (or edits) content, decides who gets to access it (either as an editor, a viewer, or both) and then decides — topically, based on the substance of the content — where to place it. By granting access to the item, the creator guarantees that the user will have access to all the categories necessary for him to access that item. Such access provisions are automatic and take place behind the scenes. Thus when a creator grants a user access to a particular item, he can rest-assured (and, notably, without having to take any technical matters into account) that that user will be granted the appropriate access to that item.
In some embodiments of the present invention, the System processes, in stage 54
(Figs. 2 and 6) for identifying the editing tools (stage 54) to be made available to a user, are performed using one or more SQL queries on data structures stored in a database. Fig. 17 illustrates an entity-relationship diagram describing data structures in a database compatible with some embodiments of the invention. Data organization 525 includes three intersection tables 524, 522, and 526, a user table 528, a group table 530, a tool table 532, and an item repository 534. In some embodiments, the user table 528, group table 530, tool table 532, and item repository 534 provide columns for conventional storage of relevant information relating to the users, groups, tools and items respectively. The item repository in some embodiments includes a number of item tables (not shown), wherein each item is identified by a combination of the tool ID and item ID.
In some embodiments of the present invention, intersection table 522 provides an "intersection" for the user table 528 and the group table 530. Accordingly, intersection table 522 in some embodiments includes a user ID column and a group ID column wherein a user ID (an entry in the user ID column) operates as a key for identifying a user in the user table 528, and a group ID (an entry in the group ID column) operates as a key for identifying a group in the group table 530. In some embodiments of the present invention, intersection table 524 provides an "intersection" for the group table 530, the tool table 532, and the item repository 534.
Accordingly, intersection table 524 (illustrated in tabular form as 524-1) includes an item ID column 524A, a tool ID column 524B, a group ID column 524C, and an edit privilege column 524D. A tool ID, item ID, and group ID in a row entry in intersection table 524 provides respective keys for identifying a tool, an item typed by the tool (i.e., the tool is of the proper type used to edit the item), and a group to which the item is published (in tool table 532, item repository 534, and group table 530 respectively); an additional edit privilege marks the item as being editable by the group in addition to being published to the group; also a view privilege marks the item as being viewable by the group (by virtue of being published to the group).
In some embodiments, every unique item-group-tool relationship (i.e., of an item published to a group using a particular tool) is represented in a separate row entry in intersection table 524; accordingly, complex relationships between groups, tools and items are efficiently determined by executing queries or look-up routines using the intersection table 524. Those skilled in the art will recognize that the System processes described in the various embodiments of the present invention may be supported by numerous variations to and modifications of data organization 520. For example, intersection table 524 may be divided into two intersection tables: a first intersection table which includes item ID and category ID columns (not shown), and a second table which includes columns for a category DD and a group ID (not shown).
In some embodiments of the present invention, a query to identify an editing tool (or all editing tools) to be made available to a user — as performed in stage 540 (Figs. 2 and 5 respectively) — is first directed to intersection table 522 for identifying the groups to which a user belongs. Next, the identified groups are used to identify, using intersection table 524, the row entries in intersection table 524 the identified groups and an edit privilege. The edit privilege in each row entry may be implemented in intersection 524 using a simple Boolean value. The tools stored in the identified row entries accordingly comprise the subset of editing tools available for use by a particular user (via the groups to which the user belongs).
As noted above, in one specific embodiment, each item of information is not only identified by a user that creates the item, as being published to a group of users as illustrated in Fig. 16, but also identified as being classified into a specific category as illustrated in Fig. 16. In such an embodiment, a database of the type discussed above in reference to Fig. 17 is modified to also include an intersection Table 804 (Fig. 18) of the type described in U.S. Patent Application Attorney Docket No. M-11475 US that has been incoφorated by reference above.
A System of the type described above may be programmed to implement a dual privilege scheme wherein each item may be made accessible to a user either for viewing only, editing only, both, or neither. Specifically, when creating (or editing a piece of content, the user is simply prompted to assign "View," "Edit" or both privileges to each of several groups of users, as illustrated in Fig. 15. A dual privilege scheme of the type described above overcomes a problem when users produce content to be viewed by other groups, and need to maintain editorial privileges over the content but do not want such items to be published to them. In a single privilege scheme each user either has access to a piece of content or not. The type of access to the published items (that is, whether they are simply viewable or also editable) in a single privilege scheme is dictated by one's level of access to a tool through which the item was produced.
However, if a user has editorial access to the tool, then, they will have editorial authority over any content published with that tool; thus, in a single privilege scheme the users have access to change the content even though it was only meant for them to view.
When a piece of content is produced via the dual privilege scheme, access to that particular content is granted on a group-by-group basis assigned at the content-level, with access permissions attached to the items of content themselves, and not to the tools used to produce them. The separation of access privileges from tools means that such privileges can be assigned according to the necessities of individual items of content. Discrete segregation of the two access privileges, provides for both flexibility and intuitive ease of use: insofar as "View" and "Edit" are mutually exclusive levels of access (i.e., "Edit" does not subsume "View"), groups can be granted one or the other or both forms of access to a single piece of content.
This separation of access privileges into two levels neatly handles the issue whereby users want to target content to other groups (i.e., groups of which they are not members) while still maintaining editorial privileges over that content: to do this, the creator need simply grant "Edit" access to one of their own groups, without granting "View" access to this group. Such a configuration grants the creator (and other members of their own group) the editorial privileges she wants, without having to clutter the content targeted to her with extraneous posted material because the System uses the "View" privilege to build her category tree 151 (Fig. 14). From the front end, this configuration prevents the editable but un-viewable item from showing up in the creator's category tree; thus, again, it would not get glommed in with the "view" content targeted to the creator. Instead, the creator has back-end access to the item she created via the tool through which the item was created; if the "edit-only" item were a "bio," for instance, the creator would automatically be given a link 98 (Fig. 14) to the Bios tool; clicking on this link 98 would give her access to all the bios she has editorial access to (other bios to which she has only "View" access would appear on her category tree 151 according to the ways in which they have been categorized).
Insofar as the System allows editorial privileges to be delegated on the content level, it helps minimize the global decisions required in giving groups access to tools. Group administrators no longer need to decide from the outset which groups will need to have editorial access to content produced in various tools; moreover, they won't have to woπy about every group that needs editorial privileges having the capacity to create extraneous publications. Creators of items, on the other hand, don't have to worry about groups that have editorial access to a tool getting editorial access to an item published to them through that tool.
In an implementation of the type illustrated in the attached Appendix, each tool used to create content is defined by a class which extends a parent class "Tools", and its child class push tools, both of which are contained in the file tools.classes.php. Each tool inherits an instance of the class cat_tree_items (See file class.cat_tree.php), from it's extension of another class push_tool. These inherited objects give the tools access to the item publishing methods contained in the class cat_tree_items. These methods provide the access privileging and positioning (also known as "categorizing") mechanisms for the System. The methods populate the table CAT_TREE_ITEMS in the database.
As illustrated in Fig. 19, a user initially goes to a page 452 (Fig. 1 IB) that provides access to a number of tools under the heading 99 of "content control". An example of such a tool is "Bios", which is used to create files limited to biographic information as described herein. Such files may contain text, images, sound, video clips, flash animations, and links to other documents that contain such information. Instead of the tool "Bios", an off-the-shelf tool, such as Microsoft Word, or Adobe Photoshop can be used in other embodiments of the type described herein.
At this stage, access to the tools listed under the heading 99 is governed by the profile of the user. Specifically, the user has access only to those tools to which the user has a "creation" privilege, or alternatively to those tools required for items to which the user has "Edit" privilege. Thereafter, the user may select an "Add" button 501 (Fig. 1 IB) in stage 602, and as discussed above the user has access to such a button only for tools to which the user has the "Creation" privilege. Each tool has a database table, which contains an identification of items that were created with that tool. Each tool also has an "add" method in it's class which populates the tools table in the database with data submitted by the creator of the content. Such data is provided by the creator in stage 603, by filling in the various fields of the type illustrated in Fig. 12. The specific fields that are filled in vary according to the specific function of the tool. See the functions bios::add_bio C (and cat_tree_items::add_item C) in the Appendix. In one particular implementation, at the beginning of stage 603, a place holder row is entered into the table cat_tree_items with the group ID set to zero.
Thereafter, in stage 604, the user selects a number of groups that will be provided access to the newly created item, and also determines the level of access (either by providing "Edit" or "View" privilege, or neither privilege as illustrated in Fig. 15. Each tool uses a central access privileging mechanism implemented in the software in the Appendix, which software replaces the items place holder in the table CAT_TREE_ITEMS, with one row for each group that is granted access to the new item. Each such row contains a unique ID for the new item, another ID for the tool (also called "TOOL ID") that is used to create the item, a group ID for the selected group (with each group having its own row in the table), Boolean values for the "Edit" and "View" privileges of this group for this item and various other publishing information pertaining to the item (e.g. expiration date, and publishing date). At this point, each row in the table CAT_TREE_ITEMS for the new item has a category value (also called "CATJD") which is set to zero. For more information, see the function cat_tree_items::modify_groups() in the appendix.
Next, in stage 605, the user selects the categories in which the item is to be published (the user can select one or more categories), as illustrated in Fig. 16. The category tree illustrated in Fig. 16 is a portion of the predetermined category tree to which the user has access, and such a category tree may be same as (or in another embodiment different from) another category tree that allows the user to navigate to items that have been published to the user, as described in the related U.S. Patent Application, Attorney Docket No. M-11475 US. In this stage, each group row for the new item in the table CAT_TREE_ITEMS is multiplied by the number of categories into which the item is placed, and with the category value for these rows set to the appropriate values based on the category selections made by the creator. For more information, see the function cat_tree::position() in the appendix. Thereafter, the user is returned to the front page (Fig. 11 A).
Numerous modifications and adaptations of the embodiments, implementations and examples described herein will be apparent to the skilled artisan in view of the disclosure. Accordingly, numerous such modifications and adaptations are encompassed by the attached claims.
APPENDIX A
Below are the SQL statements for the get tool functions listed in the flowchart. Each of these ultimately returns a list of TOOL ID's which are stored in a PHP array and cached in the user object. (In the PHP implementation, the user object is basically 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 [after login] as the reference to the user object.)
In each of these following queries, the $group_str represents a comma-delimited list of the groups of which the user is a member.
Secure_zone: :getAdminTools()
This method is used to produce an array of the administrative tools for a user. Access to these tools can only be provisioned by an administrator who specifically doles them out on a per-group basis.
The following SQL statement is used to return a list of these tools which is then rendered in an array and registered to the user object.
SELECT DISTINCT GID_TOOL_ID.TOOL_ID,TOOLS.TYPE FROM GID_TOOL_ID,TOOLS WHERE GID TOOL ID.GID IN ($group_str) AND GID_TOOL_ID.TOOL ID=TOOLS.TOOL_ID AND TOOLS.TYPE='A' ORDER BY GID_TOOL ID.TOOLJD Secure_zone::getAddTools()
++++++++++++++++++++++
This method is used to produce an array of the "Creation" tools for a user — i.e., tools with which the user can add original content. Access to these tools can only be provisioned by an administrator who specifically doles them out on a per-group basis. The following SQL statement is used to return a list of these tools which is then rendered in an array and registered to the user object.
SELECT DISTINCT GID_TOOL_ID.TOOL_ID,TOOLS.TYPE FROM GID_TOOL_ID,TOOLS WHERE GID TOOL ID.GID IN (Sgroup str) AND GID_TOOL_ID.TOOL_ID=TOOLS.TOOL ID AND TOOLS.TYPE='A' ORDER BY GID_TOOL_ID.TOOL_ID
Secure zone: :getEditTools()
This method is used to produce an array of the "Edit" tools for a user. Access to these tools is established through the process of determining all the items of content to which the user has "Edit" access and then automatically granting access to the tools necessary to exercise these edit privileges — i.e., the tools with which the pieces of content were produced. The operation of this method is central to the item-based tool-granting procedures elaborated above.
The following SQL statement is used to return a list of these tools which is then rendered in a an array and registered to the user object.
SELECT DISTINCT TOOL_ID FROM CAT_TREE_ITEMS WHERE GID IN (Sgroup str) AND EDIT= I ORDER BY TOOL D
Secure_zone: :build_cat_tree() This is the method that is used to build a 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 VERTUAL_ROOT and variable $vr refer to the user's virtual root. A virtual root is the topmost node of system's group tree to which a user has access. These topmost nodes function as the root level for the particular user. Insofar as these nodes may exist at any level within the group tree hierarchy, they do not necessarily coincide with the real root level for the system's tree and are thus referred to as virtual roots. Virtual roots provide great flexibility in the design of a system, allowing completely discrete subtrees to exist within a larger system-level tree. These subtrees may be used to host independent entities, e.g., partner companies, in self-contained partitions of the larger system. Members of these subtrees can be administered by higher level users, but themselves are completely cut-off from data (and functionality) available to groups above their virtual root level.
The following query is used to retrieve each category in which the user has a viewable item (here, the variable Sgroup 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_ID FROM CAT_TREE_ITEMS WHERE GID 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 ID 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 IDs, 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_ID,NAME FROM CAT_TREE WHERE CAT D IN ($tree_str) AND VIRTUAL_ROOT-'$vr' ORDER BY SEQ The CAT IDs 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 01 1009_1436 Volume Serial Number is BCE2-6A1B
Directory ofD:\
10/09/01 02:36p <DIR>
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>
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 L257 USER_~25.HTM
] l9 File(s) 4,759 bytes
Directory of D:\SECURE\ADMIN
10/09/01 02:36p <DIR>
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\ADMIN_~3
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 235 ERRORS-3.PHP 10/09/01 08:36a 500 HEADERS.PHP
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 267 POSITI~A.HTM
10/09/01 08:36a 279 PREPUB~C.HTM i 10/09/01 08:36a 265 PUBLIS~F.HTM
10/09/01 08:36a 6,927 TREESLIB.PHP
10/09/01 08:36a 277 UNPUB~14.HTM
10/09/01 08:36a 269 USER ~17.HTM
11 File(s) 9,019 bytes
Directory of D:\SECURE\ADMIN\ADMIN ~3\MASKING
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR> INCLUDES i 10/09/01 02:36p <DIR> MASKS
10/09/01 02:36p <DIR> TMPL
5 File(s) 0 bytes
Directory of D:\SECURE\ADMIN\ADMIN_~3\MASKING\INCLUDES 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\ADMIN_~3\MASKING\INCLUDES\1
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
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
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\ADMIN_~3\MASKING\MASKS\1 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\ADMIN_~3\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\ADMIN\ADMIN_~3\MASKING\TMPL\1
1 02:36p <DIR>
1 02:36p <DIR>
1 08:36a 828 ERRORS-3.PHP
1 08:36a 3,868 POSITI~6.HTM
1 08:36a 2,428 PREPUB~8.HTM
1 08:36a 10,158 PUBLIS~B.HTM
1 08:36a 2,912 UNPUB ~D.HTM 10/09/01 08 36a 1,029 USER -10 HTM
8 Fιle(s) 21,223 bytes
Directory of D \SECURE\ADMIN\CATTRE~5
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 319 ADDCON-3 HTM
10/09/01 08 36a 273 ADD-5 HTM
10/09/01 08 36a 20,741 CLASSC-7 PHP
10/09/01 08 36a 275 DROP-A HTM
10/09/01 08 36a 312 ERRORS-C PHP
10/09/01 08 36a 568 HEADER-F PHP
10/09/01 08 36a 275 HOME-12 HTM
10/09/01 02 36p <DIR> MASKING
10/09/01 08 36a 279 MODIF-17 HTM
10/09/01 08 36a 285 ORDER-19 HTM l2 Fιle(s) 23,327 bytes
Directory ' of D \SECURE\ADMIN\CATTRE~5\MA:
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 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\CATTRE~5\MASKING\INCLUDES 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\CATTRE~5\MASKING\INCLUDES\1
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 4,340 ADDCON-3 HTM
10/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 Fιle(s) 18,643 bytes
Directory of D \SECURE\ADMIN\CATTRE~5\MASKING\MASKS 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\CATTRE~5\MASKING\MASKS\1 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 3,886 MASKS XML
3 Fιle(s) 3,886 bytes
Directory of D \SECURE\ADMIN\CATTRE~5\MASKING\TMPL 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes Directory of D:\SECURE\ADMIN\CATTRE~5VMASKING\TMPL\1
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 4,316 ADDCON~3.HTM
10/09/01 08:36a 2,898 ADD~5.HTM
10/09/01 08:36a 1,575 DROP-7.HTM
10/09/01 08:36a 473 ERRORS-9.PHP
10/09/01 08:36a 531 HOME~D.HTM
10/09/01 08:36a 3,300 MODIFY-F.HTM
10/09/01 08:36a 4,949 ORDER~12.HTM 9 File(s) 18,042 bytes
Directory of D:\SECURE\ADMIN\GROUPMAN 10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 294 ADDCON~3.HTM
10/09/01 08:36a 261 ADD~5.HTM
10/09/01 08:36a 14,473 CLASSG-7.PHP 10/09/01 08:36a 263 DROP~A.HTM
10/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 <DIR> 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>
10/09/01 02:36p <DIR>
10/09/01 08:36a 6,883 ADDCON~3.HTM
10/09/01 08:36a 5,334 ADD~5.HTM
10/09/01 08:36a 6,017 DROP~7.HTM
10/09/01 08:36a 902 ERRORS-9.PHP
10/09/01 08:36a 2,511 GROUP ~D.HTM
10/09/01 08:36a 562 HOME~F.HTM
10/09/01 08:36a 6,148 MODIF~l l .HTM
9 File(s) 28,357 bytes
Directory of D :\SECURE\ADMIN\GROUPMAN\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\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 Fιle(s) 6,859 bytes
Directory of D \SECURE\ADMIN\GROUPMAN\MASKING\TMPL 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\GROUPMAN\MASKING\TMPL\l
10/09/01 02 36p <DIR>
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-11 HTM
9 Fιle(s) 27,319 bytes
Directory of D \SECURE\ADMIN\MASKING
10/09/01 02 36p <DΓR>
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 Fιle(s) 12,781 bytes
Directory of D \SEC :URE\ADMIN\MASKING\MAS
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 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\MASKING\MASKING\INCLUDES 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\MASKING\MASKING\INCLUDES\1
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 293 HOME-3 HTM
10/09/01 08 36a 1,718 RESET-5 HTM
10/09/01 08 36a 2,803 SET-7 HTM
10/09/01 08 36a 1,594 TOOL M-9 HTM
6 Fιle(s) 6,408 bytes Directory of D \SECUREVADMIN\MASKING\MASKING\MASKS 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1 3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\MASKING\MASKING\MASKS\1 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 1 ,505 MASKS XML
3 Fιle(s) 1,505 bytes
Directory of D \SECURE\ADMIN\MASKING\MASKING\TMPL 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\MASKING\MASKING\TMPL\1 10/09/01 02 36p <DIR>
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 Fιle(s) 6,231 bytes
Directory of D \SECURE\ADMIN\MASKING\SCRIPTS
10/09/01 02 36p <DIR> 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 Fιle(s) 5,643 bytes
Directory of D \SECURE\ADMIN\MLCATT~F
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 1,275 CLASSM-5 PHP
10/09/01 08 36a 275 DROP-7 HTM
10/09/01 08 36a 318 ERRORS-9 PHP
10/09/01 08 36a 601 HEADER-D PHP
10/09/01 08 36a 275 HOME-10 HTM 10/09/01 02 36p <DIR> MASKING
10/09/01 08 36a 279 MODIF-14 HTM
10/09/01 08 36a 285 ORDER- 17 HTM
10/09/01 08 36a 287 ORDER- 19 HTM
12 Fιle(s) 3,868 bytes
Directory of D \SECUREVADMIN\MLCATT~F\M ASKING
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 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\MLCATT-F\MASKING\INCLUDES 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1 3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\MLCATT~F\MASKING\rNCLUDES\l
10/09/01 02 36p <DIR>
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 0RDER~12 HTM
9 Fιle(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> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMINλMLCATT~F\MASKING\MASKS\l 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 3,145 MASKS XML
3 Fιle(s) 3,145 bytes
Directory of D \SECURE\ADMIN\MLCATT~F\MASKING\TMPL 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\MLCATT~F\MASKING\TMPL\1
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 2,233 ADD-3 HTM
10/09/01 08 36a 1,744 DROP-5 HTM
10/09/01 08 36a 419 ERRORS-7 PHP
10/09/01 08 36a 498 HOME-B HTM
10/09/01 08 36a 2,796 MODIFY-D HTM
10/09/01 08 36a 4,707 ORDERC-F HTM
10/09/01 08 36a 4,473 0RDER~12 HTM
9 Fιle(s) 16,870 bytes
Directory of D \SECURE\ADMIN\REORD~12
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 7,228 CLASSR-3 PHP
10/09/01 08 36a 299 ERRORS-6 PHP
10/09/01 08 36a 511 HEADER-9 PHP
10/09/01 08 36a 278 HOME-C HTM
10/09/01 02 36p <DIR> MASKING
7 Fιle(s) 8,316 bytes
Directory of D \SECURE\ADMIN\REORD~12\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\RE0RD~12\MASKING\INCLUDES
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\REORD~12\MASKING\INCLUDES\l 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~12VMASKING\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\REORD~12\MASKING\MASKS\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR> 10/09/01 08:36a 1,103 MASKS. XML
3 File(s) 1,103 bytes
Directory of D:\SECURE\ADMIN\REORD~12\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\ADMIN\REORD~12\MASKING\TMPL\l 10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/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 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~1 1.HTM
9 File(s) 20,860 bytes
Directory of D:\SECURE\ADMIN\SEARCH\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\SEARCH\MASKING\INCLUDES 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:\SEC :URE\ADMIN\SEARCH\MASK
10/09/01 02:36p <DIR>
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\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\SEARCH\MASKING\MASKS\1
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 1,463 MASKS.XML
3 File(s) 1,463 bytes
Directory of D:\SECURE\ADMIN\SEARCH\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\ADMIN\SEARCH\MASKING\TMPL\1
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 233 ERRORS-3. PHP
1 100//0099//0011 08:36a 5,685 SEARCH~5.HTM
1100//0099//0011 08:36a 4,754 SET~8.HTM
5 File(s) 10,672 bytes Directory of D:\SECURE\ADMIN\SECURITY
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 7,911 CLASSS-3. PHP
10/09/01 08:36a 19,357 CRACKD-5
10/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-l l .PHP
10/09/01 08:36a 376 SUGGE~14.HTM
10 File(s) 52,455 bytes
Directory of D:\SECURE\ADMIN\SECURITY\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\SECURITY\MASKING\INCLUDES 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\SECURITY\MASKING\INCLUDES\1
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 1,031 ERRORS-3 PHP
10/09/01 08 36a 3,286 PASSWD-5 HTM
10/09/01 08 36a 2,614 SUGGES-8 HTM
5 Fιle(s) 6,931 bytes
Directory of D \SECURE\ADMIN\SECURITY\MASKING\MASKS 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\SECURITY\MASKING\MASKS\1 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 10/09/01 08 36a 3,158 MASKS XML 3 Fιle(s) 3,158 bytes
Directory of D \SECURE\ADMIN\SECURITY\MASKING\TMPL 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\SECURITY\MASKING\TMPL\1
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 923 ERRORS-3 PHP
10/09/01 08 36a 3,106 PASSWD-5 HTM
10/09/01 08 36a 2,301 SUGGES-8 HTM
5 Fιle(s) 6,330 bytes
Directory ' of D \SECURE\ADMIN\USERMAN
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 328 ADD-3 HTM
10/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
1 1 Fιle(s) 14,640 bytes
Directory of D \SECURE\ADMIN\USERMAN\M ASKING
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 Fιle(s) 0 bytes Directory of D \SECURE\ADMIN\USERMAN\MASKING\INCLUDES 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\USERMAN\MASKING\INCLUDES\1
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 4,231 ADD-3 HTM
10/09/01 08 36a 3,366 DROP-5 HTM
10/09/01 08 36a 283 ERRORS-7 PHP
10/09/01 08 36a 575 HOME-A HTM
10/09/01 08 36a 7,443 MODIFY-C HTM
10/09/01 08 36a 7,860 VIEW-E HTM
8 Fιle(s) 23,758 bytes
Directory of D \SECURE\ADMIN\USERMAN\MASKING\MASKS 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\ADMIN\USERMAN\MASKING\MASKS\1 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 3,630 MASKS XML
3 Fιle(s) 3,630 bytes Directory of D \SECURE\ADMIN\USERM AN\M ASKINGYTMPL
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory ofD \SEC :URE\ADMIN\USERMAN\MA5
10/09/01 02 36p <DIR>
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 Fιle(s) 24,350 bytes
Directory - of D \SECURE\ADMIN\UTILS
10/09/01 02 36p <DIR>
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- 1 1 PHP
10/09/01 08 36a 12,441 THUNK
10/09/01 08 36a 1,241 TMP C-16 PL
11 Fιle(s) 23,806 bytes
Directory of D \SECURE\ADMIN\UTILS\FORMAT~5 10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR> DIALOG
10/09/01 08:36a 2,069 EDITLI~4.HTM
10/09/01 08:36a 7,611 EDITME~7.HTM
10/09/01 08:36a 7,970 FORMAT-A.HTM
10/09/01 08:36a 8,469 FORMAT~C.HTM
10/09/01 02:36p <DIR> GRAPHICS
10/09/01 02:36p <DIR> JS
10/09/01 08:36a 2,287 LEFT~12.HTM
10/09/01 08:36a 271 LINK~14.HTM
10/09/01 08:36a 8,290 OPTIO~17.HTM
10/09/01 08:36a 3,136 README.TXT
10/09/01 08:36a 4,604 RIGHT~1B.HTM
14 File(s) 44,707 bytes
Directory of D :\SECURE\ADMIN\UTILS\FORMAT~5\DIALOG
10/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
10/09/01 08:36a 2,487 LINKGU~A.HTM
10/09/01 08:36a 259 LINK~C.HTM
10/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> 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 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 S
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-15.JS
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
10/09/01 08:36a 455 LOCALD~C.HTM
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 7,794 MEDIA.JS
10/09/01 08:36a 526 MEDIA- 16. INC
10/09/01 08:36a 455 MEDLI~11.HTM
10/09/01 08:36a 458 MEDLI~18.HTM 10/09/01 08:36a 458 MEDLI~1B.HTM
10/09/01 08:36a 458 MEDLI~1E.HTM
10/09/01 08:36a 458 MEDLI~21.HTM
10/09/01 08:36a 452 SETME~24.HTM
16 File(s) 13,069 bytes
Directory of D:\SECURE\ADMIN\UTILS\MEDIA ~7\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\UTILS\MEDIA_~7\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\ADMIN\UTILS\MEDIA_~7\MASKING\INCLUDES\1
10/09/01 02:36p <DIR>
10/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 i 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\ADMIN\UTILS\MEDIA -
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 1,385 ADDMED~3.HTM
10/09/01 08:36a 1,529 EDITME~5.HTM
10/09/01 08:36a 329 FILEUP~7.HTM
10/09/01 08:36a 812 LOCALD~A.HTM 10/09/01 08:36a 19,501 MEDIA-10.INC
10/09/01 08:36a 508 MEDLIB~D.HTM
10/09/01 08:36a 1,130 MEDLI~12.HTM
10/09/01 08:36a 132 MEDLI~15.HTM
10/09/01 08:36a 288 MEDLI~18.HTM
10/09/01 08:36a 452 MEDLI~1B.HTM
10/09/01 08:36a 3,281 SETME~1D.HTM
13 File(s) 29,347 bytes
Directory of D:\SECURE\ADMIN\UTILS\METATA~A
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 407 METATA-4.INC
10/09/01 08:36a 221 METATA-7.PHP
5 File(s) 628 bytes
Directory of D:\SECURE\ADMIN\UTILS\METATA~A\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\UTILS\METATA~A\MASKING\INCLUDES
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\ADM_nsr\UTILS\METATA-A\MASKING\INCLUDES\l 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\ADMIN\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 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 487 MASKS.XML
3 File(s) 487 bytes Directory of D:\SECURE\ADMIN\UTILS\METATA~A\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\ADMIN\UTILS\METATA~A\MASKING\TMPL\1
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 3,143 METATA-3.INC 3 File(s) 3,143 bytes Directory of D:\SECURE\CRON 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 181 CRONTAB.TXT
3 File(s) 181 bytes
Directory of D:\SECURE\TNCLUDES
10/09/01 02: 36p <DIR>
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 GLOB A-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
U File(s) 288,297 bytes
Directory of D:\SECURE\INCLUDES\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 F ιle(s) 0 bytes
Directory of D:\SECURE\INCLUDES\MASKING\INCLUDES 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\INCLUDES\MASKING\INCLUDES\1 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 1,959 ERRORS-3.PHP
3 File(s) 1,959 bytes
Directory of D:\SECURE\INCLUDES\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\INCLUDES\MASKING\MASKS\1 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 1,962 MASKS.XML
3 File(s) 1,962 bytes Directory of D:\SECURE\INCLUDES\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\INCLUDES\MASKING\TMPL\1 10/09/01 02:36p <DIR> 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 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
Figure imgf000042_0001
Directory of D:\SECURE\LAYOUT
10/09/01 02:36p <DIR>
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:\SE( :URE\LAYOl JTVBUTTONS
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR> DISCUS-3
10/09/01 02:36p <DIR> GLOSSARY
4 File(s) 0 bytes Directory of D:\SECURE\LAYOUT\BUTTONS\DISCUS~3 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
2 File(s) 0 bytes Directory of D:\SECURE\LAYOUT\BUTTONS\GLOSSARY 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
2 File(s) 0 bytes
Directory of D:\SECURE\LAYOUT\CONFIG 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 3,562 CONFIG-3.PHP
3 File(s) 3,562 bytes
Directory of D:\SECURE\LAYOUT\CSS
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 7,689 MACIE.CSS
10/09/01 08:36a 7,662 MACNAV.CSS
10/09/01 08:36a 7,642 UNIXNAV.CSS 10/09/01 08:36a 7,658 WINIE.CSS 10/09/01 08:36a 7,646 WINNAV.CSS 7 File(s) 38,297 bytes Directory of D:\SECURE\LAYOUT\GRAPHICS 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
2 File(s) 0 bytes Directory of D:\SECURE\LAYOUT\ICONS 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
2 File(s) 0 bytes Directory of D:\SECURE\LAYOUT\INCLUDES
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 1,272 DUMMYH-3.INC
10/09/01 08:36a 346 FOOTER.INC
10/09/01 08:36a 346 HEADER.INC
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 340 NAV.INC
7 File(s) 2,304 bytes Directory of D:\SECURE\LAYOUT\INCLUDES\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\LAYOUT\INCLUDES\MASKING\INCLUDES 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\LAYOUT\INCLUDES\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 182 FOOTER.INC
10/09/01 08:36a 6,893 HEADER.INC
10/09/01 08:36a 6,121 NAV.INC
5 File(s) 13,196 bytes
Directory of D:\SECURE\LAYOUT\INCLUDES\M ASKINGVMASKS 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\LAYOUT\INCLUDES\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
10/09/01 08:36a 293 MASKS.XML
3 File(s) 293 bytes
Directory of D:\SECURE\LAYOUT\INCLUDES\M ASKINGYTMPL 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SEC URE\LAYOUT\INCLUDES\M
10/09/01 02 36p <DIR>
10/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 Fιle(s) 13,241 bytes
Directory of D \SECURE\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 Fιle(s) 0 bytes
Directory of D \SECURE\MASKINGMNCLUDES
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\MASKING\INCLUDES\1
10/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-11 HTM
10/09/01 08 36a 2,272 SITEM-13 HTM
10 Fιle(s) 20,202 bytes
Directory of D \SECURE\MASKING\MASKS 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\MASKING\MASKS\1 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 3,097 MASKS XML
3 Fιle(s) 3,097 bytes
Directory of D \SECURE\MASKING\TMPL 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\MASKING\TMPL\1
10/09/01 02 36p <DIR>
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
1 O File(s) 19,842 bytes
Directory of D:\SECURE\TOOLS
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR> BIOS
10/09/01 02:36p <DIR> CAREERS
10/09/01 02:36p <DIR> CASE S-6
10/09/01 02:36p <DIR> DISCUS-8
10/09/01 08:36a 109 ERROR-B.HTM
10/09/01 02:36p <DIR> EVENTS
10/09/01 02:36p <DIR> FAQ
10/09/01 02:36p <DIR> FILES
10/09/01 02:36p <DIR> FORMS
10/09/01 02:36p <DIR> FREE -14
10/09/01 02:36p <DIR> GLOSSARY
10/09/01 02:36p <DIR> GZ DI-19
10/09/01 08:36a 671 INDEX~1B.HTM
10/09/01 02:36p <DIR> LINKS
10/09/01 02:36p <DIR> LOCAT-1F
10/09/01 02:36p <DIR> MAILI-21
10/09/01 02:36p <DIR> MEDIA-24
10/09/01 02:36p <DIR> NEWS
10/09/01 02:36p <DIR> PRODUCTS
10/09/01 02:36p <DIR> QUOTES
22 File(s) 780 bytes
Directory of D:\SECURE\TOOLS\BIOS
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 262 ADD~3.HTM
10/09/01 08:36a 273 BIOSSC-5.SQL
10/09/01 08:36a 280 BIOSSC-8.SQL
10/09/01 08:36a 9,722 CLASSB-B.PHP
10/09/01 08:36a 332 ERRORS-D.PHP
10/09/01 08:36a 263 HEADE-10.PHP
10/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 of D:\SEC :URE\TOOLS\BIOS\MASKINC
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\BIOS\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\TOOLS\BIOS\MASKJNG\INCLUDES\l
10/09/01 02:36p <DIR>
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
10/09/01 08:36a 878 UNPUBL~C.HTM
10/09/01 08:36a 2,166 VIEW~E.HTM
8 File(s) 16,158 bytes
Directory of D:\SECURE\TOOLS\BIOS\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\BIOS\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 2,075 MASKS.XML
3 File(s) 2,075 bytes
Directory of D:\SECURE\TOOLS\BIOS\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\BIOS\MASKING\TMPL\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 3,471 ADD~3.HTM
10/09/01 08:36a 663 ERRORS-5.PHP
10/09/01 08:36a 2,636 HOME~7.HTM
10/09/01 08:36a 6,281 MODIFY~9.HTM
10/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 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
10/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 VTEW~2B.HTM
19 File(s) 32,920 bytes
Directory of D:\SEC :URE\TOOLS\CAREERS\MA
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\CAREERS\MASKING\INCLUDES 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\INCLUDES\l
10/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> 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 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 10/09/01 08 36a 7,539 MODIF-12 HTM
10/09/01 08 36a 62 RESUL-14 HTM
10/09/01 08 36a 935 UNPUB-16 HTM
10/09/01 08 36a 9,105 VIEW -19 HTM i 10/09/01 08 36a 4,005 VIEW-IC HTM
] 13 Fιle(s) 37,895 bytes
Directory of D \SECURE\TOOLS\CASE S~6
10/09/01 02 36p <DIR>
) 10/09/01 02 36p <DIR>
10/09/01 08 36a 272 ADD-3 HTM
10/09/01 08 36a 285 CASE S-5 SQL
10/09/01 08 36a 283 CASE S-8 SQL
10/09/01 08 36a 9,041 CLASSC-C PHP i 10/09/01 08 36a 276 ERRORS-F PHP
10/09/01 08 36a 256 HEADE-12 PHP
10/09/01 08 36a 274 HOME- 15 HTM
10/09/01 02 36p <DIR> MASKING
10/09/01 08 36a 278 MODIF-19 HTM
) 10/09/01 08 36a 62 RESUL-1B HTM
10/09/01 08 36a 284 UNPUB-1E HTM
10/09/01 08 36a 274 VIEW-20 HTM
14 Fιle(s) 11,585 bytes Directory of D \SECURE\TOOLS\CASE_S~6\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 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\CASE_S~6\MASKING\INCLUDES 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\CASE_S~6\MASKING\INCLUDES\l
10/09/01 02 36p <DIR>
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 Fιle(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>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\CASE_S~6\MASKING\MASKS\l
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 2,052 MASKS XML 3 Fιle(s) 2,052 bytes Directory of D:\SECURE\TOOLS\CASE_S~6\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\CASE_S~6\MASKING\TMPL\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 3,344 ADD~3.HTM
10/09/01 08:36a 691 ERRORS-5.PHP
10/09/01 08:36a 2,562 HOME~8.HTM
10/09/01 08:36a 5,065 MODIFY~A.HTM
10/09/01 08:36a 902 UNPUBL~C.HTM
10/09/01 08:36a 2,108 VIEW~F.HTM
8 File(s) 14,672 bytes
Directory of D:\SECURE\TOOLS\DISCUS~8
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 287 ADDTOP~3.HTM
10/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
: 18 File(s) 25,723 bytes
Directory of D:\SECURE\TOOLS\DISCUS~8\MAS_
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\DISCUS~8\MASKING\INCLUDES 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\DISCUS~8\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 3,536 ADDTOP~3.HTM
10/09/01 08:36a 2,531 ADD~5.HTM
10/09/01 08:36a 10,986 DISCUS~7.HTM
10/09/01 08:36a 1,602 DROPTO~A.HTM
10/09/01 08:36a 1,486 ERRORS-D.PHP
10/09/01 08:36a 2,706 HOME~10.HTM 10/09/01 08:36a 3,823 MODIF~12.HTM
10/09/01 08:36a 3,623 MODIF~14.HTM
10/09/01 08:36a 955 UNPUB~17.HTM
10/09/01 08:36a 1,577 VIEW- 1A.HTM
12 File(s) 32,825 bytes
Directory of D:\SECURE\TOOLS\DISCUS~8\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\DISCUS~8\MASKING\MASKS\1 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
10/09/01 08:36a 3,628 MASKS.XML
3 File(s) 3,628 bytes
Directory of D:\SECURE\TOOLS\DISCUS~8\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\DISCUS~8\MASKING\TMPL\l
10/09/01 02:36p <DIR>
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
] l2 File(s) 32,467 bytes
Directory ' of D:\SECURE\TOOLS\EVENTS
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 267 ADD~3.HTM
10/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
10/09/01 08:36a 243 HEADE-10.PHP
10/09/01 08:36a 269 HOME~13.HTM
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 273 MODIF~17.HTM
10/09/01 08:36a 62 RESUL~19.HTM
10/09/01 08:36a 285 SEARC~1C.HTM
10/09/01 08:36a 279 UNPUB~1E.HTM
10/09/01 08:36a 269 VIEW~21.HTM
15 File(s) 17,374 bytes
Directory of D:\SECURE\TOOLS\EVENTS\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 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\EVENTS\MASKING\INCLUDES
10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR>
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\EVENTS\MASKING\lNCLUDES\l
10/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 Fιle(s) 31,987 bytes
Directory of D \SECURE\TOOLS\EVENTS\MASKING\MASKS 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\EVENTS\MASKING\MASKS\l 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 3,771 MASKS XML
3 Fιle(s) 3,771 bytes
Directory of D \SECURE\TOOLS\EVENTS\MASKING\TMPL 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\EVENTS\MASKING\TMPL\l
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 7,377 ADD-3 HTM
10/09/01 08 36a 853 ERRORS-5 PHP
10/09/01 08 36a 3,704 HOME-7 HTM
10/09/01 08 36a 9,112 MODIFY-A HTM
10/09/01 08 36a 4,283 SEARCH-C HTM
10/09/01 08 36a 932 UNPUBL-F HTM
10/09/01 08 36a 5,878 VIEW-11 HTM
9 Fιle(s) 32,139 bytes
Directory of D \SECURE\TOOLS\FAQ
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 264 ADD-3 HTM
10/09/01 08 36a 9,225 CLASSF-5 PHP
10/09/01 08 36a 249 ERRORS-7 PHP
10/09/01 08 36a 273 FAQSCH-A SQL
10/09/01 08 36a 262 FAQSCH-C SQL
10/09/01 08 36a 238 HEADER-F PHP 10/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~18.HTM
10/09/01 08:36a 277 UNPUB~1B.HTM
10/09/01 08:36a 266 VIEW~1D.HTM
14 File(s) 11,652 bytes
Directory of D:\SEC URE\TOOLS\FAQ\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\FAQ\MASKING\INCLUDES 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\FAQ\MASKING\INCLUDES\l
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\TOOLS\FAQ\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\FAQ\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 1,882 MASKS.XML
3 File(s) 1,882 bytes
Directory of D:\SECURE\TOOLS\FAQ\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\FAQ\MASKING\TMPL\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 2,740 ADD~3.HTM
10/09/01 08:36a 753 ERRORS-5.PHP
10/09/01 08:36a 2,625 HOME~7.HTM
10/09/01 08:36a 3,939 MODIFY~9.HTM
10/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\TOOLS\FILES
10/09/01 02:36p <DIR>
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 of D:\SECURE\TOOLS\FILES\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\FILES\MASKING\INCLUDES 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\FILES\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 3,160 ADD~3.HTM
10/09/01 08:36a 1,053 ERRORS-5.PHP
10/09/01 08:36a 2,618 HOME~7.HTM
10/09/01 08:36a 5,435 MODIFY~9.HTM
10/09/01 08:36a 912 UNPUBL~C.HTM
10/09/01 08:36a 2,367 VIEW~E.HTM
8 File(s) 15,545 bytes
Directory of D:\SECURE\TOOLS\FILES\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\FILES\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 2,463 MASKS.XML
3 File(s) 2,463 bytes
Directory of D:\SECURE\TOOLSVFILES\MASKING\TMPL
02:36p <DIR>
02:36p <DIR>
02:36p <DIR> 3 File(s) 0 bytes
Directory of D:\SECURE\TOOLS\FILES\MASKING\TMPL\l
10/09/01 02 36p <DIR> 10/09/01 0236p <DIR> 10/09/01 0836a 3,239 ADD~3.HTM 10/09/01 08:36a 825 ERRORS-5.PHP 10/09/01 08:36a 2,596 HOME~7.HTM 10/09/01 08:36a 5,544 MODIFY~9.HTM 10/09/01 08:36a 928 UNPUBL~C.HTM 10/09/01 08:36a 2,372 VIEW~E.HTM 8 File(s) 15,504 bytes
Directory ■ of D:\SECURE\TOOLS\FORMS
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 281 ADD2~3.HTM
10/09/01 08:36a 291 ADD FO~5.HTM
10/09/01 08:36a 279 ADD-7.HTM
10/09/01 08:36a 13,571 CLASSF-9.PHP
10/09/01 08:36a 307 ELEM D~C.HTM
10/09/01 08:36a 309 ERRORS-F.PHP
10/09/01 08:36a 1,128 FORMS- 11. SQL
10/09/01 08:36a 242 HEADE-14.PHP
10/09/01 08:36a 283 HOME~17.HTM
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 287 MODIF~lB.HTM
10/09/01 08:36a 293 UNPUB~1D.HTM
10/09/01 08:36a 283 VTEW~20.HTM
15 File(s) 17,554 bytes
Directory of D:\SECURE\TOOLS\FORMS\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\FORMS\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\TOOLS\FORMS\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/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-C.PHP
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
11 File(s) 29,759 bytes
Directory of D :\SECURE\TOOLS\FORMS\MASKING\MASKS
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\TOOLS\FORMS\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 5,925 MASKS.XML
3 File(s) 5,925 bytes
Directory of D:\SECURE\TOOLS\FORMS\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\FORMS\MASKING\TMPL\l
10/09/01 02:36p <DIR>
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
10/09/01 08:36a 4,310 ADD~7.HTM
10/09/01 08:36a 2,555 ELEM D~9.HTM
10/09/01 08:36a 889 ERRORS-C.PHP
10/09/01 08:36a 2,747 HOME~F.HTM
10/09/01 08:36a 2,518 MODIF-11. HTM
10/09/01 08:36a 908 UNPUB~13.HTM
10/09/01 08:36a 7,377 VIEW~16.HTM
1 [ 1 File(s) 28,887 bytes
Directory of D:\SECURE\TOOLS\FREE -14
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 278 ADD~3.HTM
10/09/01 08:36a 16,735 CLASSF-5.PHP
10/09/01 08:36a 358 ERRORS-8.PHP
10/09/01 08:36a 624 FREE F-B.SQL
10/09/01 08:36a 656 FREE F-F.SQL
10/09/01 08:36a 308 HEADE-13.PHP
10/09/01 08:36a 280 HOME~16.HTM
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 284 MODIF~lA.HTM
10/09/01 08:36a 62 RESUL~1D.HTM
10/09/01 08:36a 292 SET I~1F.HTM
10/09/01 08:36a 290 UNPUB~22.HTM
10/09/01 08:36a 455 VIEW.INC
10/09/01 08:36a 229 VIEW~26.HTM
] l6 File(s) 20,851 bytes
Directory of D:\SECURE\TOOLS\FREE ~14\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\FREE -14\MASKING\INCLUDES 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\FREE ~14\MAS*
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:\SECURE\TOOLS\FREE_ -14\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\FREE_~14\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 4,128 MASKS.XML
3 File(s) 4,128 bytes
Directory of D:\SECURE\TOOLS\FREE_ -14\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\FREE_~14\MASKING\TMPL\l
10/09/01 02:36p <DIR>
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
10 File(s) 23,549 bytes
Directory of D:\SECURE\TOOLS\GLOSSARY
10/09/01 02:36p <DIR>
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~lD.HTM
10/09/01 08:36a 284 MODIF~lF.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 VIEW-2B HTM
19 Fιle(s) 30,321 bytes Directory of D \SECURE\TOOLS\GLOSSARYVMASKING
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 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\GLOSSARY\MASKING\INCLUDES 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\GLOSSARY\MASKING\INCLUDES\l
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 2,109 ADD TE-3 HTM
10/09/01 08 36a 2,658 ADD-5 HTM
10/09/01 08 36a 859 DROP T-7 HTM
10/09/01 08 36a 2,107 ERRORS-A PHP
10/09/01 08 36a 2,264 HOME-C HTM
10/09/01 08 36a 3,614 MODIFY-F HTM
10/09/01 08 36a 2,693 MODIF-11 HTM
10/09/01 08 36a 3,609 RELAT-14 HTM
10/09/01 08 36a 779 UNPUB-16 HTM
10/09/01 08 36a 2,248 VIEW -18 HTM
10/09/01 08 36a 4,205 VIEW-IB HTM
13 Fιle(s) 27,145 bytes
Directory of D \SECURE\TOOLS\GLOSSARY\MASKING\MASKS 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\GLOSSARY\MASKING\MASKS\l 10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 10/09/01 08 36a 4,297 MASKS XML
3 Fιle(s) 4,297 bytes Directory of D \SECURE\TOOLS\GLOSSARY\MASKING\TMPL
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SE( :URE\TOOLS\GLOSSARY\MA
10/09/01 02 36p <DIR>
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-11. 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
1 13 File(s) 26,687 bytes
Directory of D:\SECURE\TOOLS\GZ DI-19
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 353 ADD EM~3.HTM
10/09/01 08:36a 337 ADD~5.HTM
10/09/01 08:36a 347 ADMIN -7.HTM
10/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
10/09/01 08:36a 355 EMPLO~lA.HTM
10/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 VIEW~3A.HTM
24 File(s) 42,031 bytes
Directory of D :\SECURE\TOOLS\GZ_DI~ 19\M ASKING
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\GZ_DI~19\MASKINGMNCLUDES 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\GZ_DI~l 9\MASKING\TNCLUDES\1
10/09/01 02:36p <DIR>
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 L158 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-1A.PHP
10/09/01 08:36a 2,407 HOME~lD.HTM i 10/09/01 08:36a 3,700 M0DIF~1F.HTM
10/09/01 08:36a 8,222 MODIF~22.HTM
10/09/01 08:36a 5,368 SEARC~25.HTM
10/09/01 08:36a 884 UNPUB~27.HTM
10/09/01 08:36a 13,414 VIEW~29.HTM
) 18 File(s) 73,252 bytes
Directory of D:\SECURE\TOOLS\GZ_DI~l 9\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\GZ_DI~l 9\MASKING\MASKS\1 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
10/09/01 08:36a 8,320 MASKS.XML
3 File(s) 8,320 bytes
Directory of D:\SECURE\TOOLS\GZ_DI~19\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\GZ DI~19\MASKING\TMPL\1
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/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-1A.PHP
10/09/01 08:36a 2,385 HOME~lD.HTM
10/09/01 08:36a 3,767 MODIF~lF.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 UMPUB~27.HTM
10/09/01 08:36a 13,795 VIEW~29.HTM
18 File(s) 74,344 bytes
Directory of D:\SECURE\TOOLS\LINKS
10/09/01 02:36p <DIR>
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
10/09/01 08:36a 62 RESUL~19.HTM
10/09/01 08:36a 278 UNPUB~1B.HTM
10/09/01 08:36a 721 VIEW~1E.HTM
14 File(s) 11,689 bytes
Directory of D:\SECURE\TOOLS\LINKS\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\LINKS\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\TOOLS\LINKS\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
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\TOOLSVLINKS\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\LINKS\MASKING\MASKS\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 1,988 MASKS.XML
3 File(s) 1,988 bytes
Directory of D:\SECURE\TOOLS\LINKS\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\LINKS\MASKING\TMPL\l
10/09/01 02:36p <DIR>
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\TOOLS\LOCAT~lF 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 339 ADD~3.HTM
10/09/01 08:36a 13,030 CLASSL-5.PHP
10/09/01 08:36a 267 ERRORS-7.PHP
10/09/01 08:36a 248 HEADER-A.PHP
10/09/01 08:36a 341 HOME~D.HTM
10/09/01 08:36a 472 LOCA.TI~F.SQL
10/09/01 08:36a 491 LOCAT-13.SQL
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 343 MODIF~18.HTM
10/09/01 08:36a 62 RESUL~1A.HTM
10/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\TOOLS\LOCAT~lF\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\TOOLSVLOCAT~lF\MASKING\INCLUDES 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\LOCAT~lF\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
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\TOOLS\LOCAT~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\TOOLS\LOCAT~lF\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR>
10/09/01 08:36a 2,709 MASKS.XML
3 File(s) 2,709 bytes
Directory of D :\SECURE\TOOLS\LOCAT~ 1 F\M ASKINGYTMPL
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\TOOLS\LOCAT~lF\MASKING\TMPL\l 10/09/01 02:36p <DIR> 10/09/01 02 36p <DIR>
10/09/01 08 36a 5,977 ADD-3 HTM
10/09/01 08 36a 693 ERRORS-5 PHP
10/09/01 08 36a 3,844 HOME-8 HTM 10/09/01 08 36a 7,800 MODIFY-A HTM
10/09/01 08 36a 4,293 SEARCH-C HTM
10/09/01 08 36a 934 UNPUBL-F HTM
10/09/01 08 36a 3,680 VIEW- 11 HTM
9 Fιle(s) 27,221 bytes
Directory of D \SECURE\TOOLS\M AILI-21
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 3,155 CLASSM-3 PHP 10/09/01 08 36a 281 COMPOS-6 HTM
10/09/01 08 36a 277 ERRORS-8 PHP
10/09/01 08 36a 171 HEADER-B PHP
10/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 Fιle(s) 4,204 bytes
Directory of D \SECURE\TOOLS\M AILI-21\M ASKING 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 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\MAILI~21\MASKING\INCLUDES
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\MAILI~21\MASKING\INCLUDES\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 Fιle(s) 7,207 bytes Directory of D \SECURE\TOOLS\MAILI~21 \M ASKINGVMASKS
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\MAILI~21\MASKING\MASKS\l
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 1,185 MASKS XML 3 Fιle(s) 1,185 bytes
Directory of D \SECURE\TOOLS\MAILI~21\MASKING\TMPL
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 10/09/01 02 36p <DIR> 1
3 Fιle(s) 0 bytes Directory of D:\SECURE\TOOLS\MAILI~21\MASKING\TMPL\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 6,974 COMPOS~3.HTM
10/09/01 08:36a 209 ERRORS-5.PHP
4 File(s) 7,183 bytes
Directory of D:\SECURE\TOOLS\MEDIA~24
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 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
: L5 File(s) 16,904 bytes
Directory of D:\SECURE\TOOLS\MEDIA~24\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\MEDIA~24\MASKING\INCLUDES 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\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 2,014 ADD~3.HTM
10/09/01 08:36a 1,498 ERRORS-5.PHP
10/09/01 08:36a 2,697 HOME~8.HTM
10/09/01 08:36a 8,892 MODIFY-A.HTM
10/09/01 08:36a 4,443 POSITI~C.HTM
10/09/01 08:36a 9,291 PUBLIS~F.HTM
10/09/01 08:36a 893 UNPUB~11.HTM
10/09/01 08:36a 3,170 UNPUB~14.HTM
10/09/01 08:36a 3,532 VIEW~16.HTM
11 File(s) 36,430 bytes Directory of D:\SECURE\TOOLS\MEDIA~24\MASKTNG\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\MEDIA~24\MASKING\MASKS\1 10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 08 36a 5,231 MASKS XML
3 Fιle(s) 5,231 bytes
Directory of D \SECURE\TOOLS\MEDIA~24\MASKING\TMPL
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1 3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\MEDIA-24\MASKING\TMPL\l
10/09/01 02 36p <DIR>
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
U Fιle(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
10/09/01 08 36a 418 NEWSS-13 SQL
10/09/01 08 36a 421 NEWSS-16 SQL
10/09/01 08 36a 62 RESUL-19 HTM
10/09/01 08 36a 283 UNPUB-1B HTM
10/09/01 08 36a 280 VIEW-IE HTM
14 Fιle(s) 14,759 bytes
Directory < ofD \SEC :URE\TOOLSVNEWS\MASKIN<
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 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\NEWS\MASKING\INCLUDES
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR>
10/09/01 02 36p <DIR> 1 3 Fιle(s) 0 bytes
Directory of D \SECURE\TOOLS\NEWS\MASKING\INCLUDES\l 10/09/01 02 36p <DIR> 10/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 91 1 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\TOOLSVNEWS\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\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\NEWS\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\TOOLS\PRODUCTS
10/09/01 02:36p <DIR>
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
10/09/01 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
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
1 l6 File(s) 20,003 bytes
Directory of D:\SEC ;URE\TOOLS\PRODUCTS\MA
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\PRODUCTS\MASKINGMNCLUDES 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\PRODUCTS\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
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:\SEC :URE\TOOLS\PRODUCTS\MA
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\PRODUCTS\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 4,083 MASKS.XML
3 File(s) 4,083 bytes
Directory of D:\SECURE\TOOLS\PRODUCTS\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\PRODUCTS\MASKING\TMPL\1
10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 3,413 ADD~3.HTM
10/09/01 08:36a 1,159 ERRORS-5.PHP 10/09/01 08:36a 3,138 HOME~7.HTM 10/09/01 08:36a 5,148 MODIFY-A.HTM 10/09/01 08:36a 2,267 RELATE~C.HTM 10/09/01 08:36a 908 UNPUBL~E.HTM 10/09/01 08:36a 2,946 UNREL~11.HTM 10/09/01 08:36a 2,216 VIEW~13.HTM 10 File(s) 21,195 bytes
Directory of D:\SECURE\TOOLS\QUOTES
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 326 ADD~3.HTM
10/09/01 08:36a 9,560 CLASSQ-5.PHP
10/09/01 08:36a 258 ERRORS-7.PHP
10/09/01 08:36a 244 HEADER-A.PHP
10/09/01 08:36a 336 HOME~D.HTM
10/09/01 02:36p <DIR> MASKING
10/09/01 08:36a 334 MODIF~l l.HTM 10/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\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\QUOTES\MASKING\INCLUDES 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\QUOTES\MASKING\INCLUDES\l
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 3,509 ADD~3.HTM
10/09/01 08:36a 912 ERRORS-5.PHP
10/09/01 08:36a 2,697 HOME~7.HTM
10/09/01 08:36a 5,072 MODIFY-A.HTM
10/09/01 08:36a 911 UNPUBL~C.HTM
10/09/01 08:36a 1,765 VIEW~E.HTM
8 File(s) 14,866 bytes
Directory of D:\SECURE\TOOLS\QUOTES\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\QUOTES\MASKING\MASKS\l 10/09/01 02:36p <DIR> 10/09/01 02:36p <DIR> 10/09/01 08:36a 2,416 MASKS.XML
3 File(s) 2,416 bytes Directory of D:\SECURE\TOOLS\QUOTES\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:\SE( :URE\TOOLS\QUOTES\MASK]
10/09/01 02:36p <DIR>
10/09/01 02:36p <DIR>
10/09/01 08:36a 3,588 ADD~3.HTM
10/09/01 08:36a 693 ERRORS-5. PHP
10/09/01 08:36a 2,675 HOME~7.HTM
10/09/01 08:36a 5,153 MODIFY-A.HTM
10/09/01 08:36a 927 UNPUBL~C.HTM
10/09/01 08:36a 1,791 VIE W~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 method comprising: identifying a tool from among a predetermined set of tools for use by the user for editing an item of information, if the item is marked in the computer as being editable by a group of users to which the user belongs; and storing data identifying the item as being editable by the user using the tool in a storage medium.
2. The method of claim 1, further comprising: automatically performing the acts of claim 1 in response to receiving data identifying the user.
3. The method of claim 1, further comprising: identifying the group to which the user belongs from among a plurality of groups using the data identifying the user.
4. The method of claim 1, wherein the user is previously assigned to the group.
5. The method of claim 1, wherein each tool in the predetermined set enables a user to edit a particular type of item.
6. The method of claim 1, further comprising: repeating the act of identifying a tool for each item published to a group to which a user belongs, each tool identified included in a subset of the predetermined tools; and storing data in the storage medium identifying the items as being editable by the user using the tools identified in the previous act.
7. The method of claim 1 , wherein the item is marked in the computer as being editable by the group of users to which the user belongs if an edit permission is associated with the item.
8. The method of claim 1, the tool in claim 1 being "first tool," further comprising: identifying a second tool from among the predetermined set of tools for use by the user for creating an item of information; and storing data associating the user with the second tool as an item creation tool in the storage medium.
9. The method of claim 8, wherein the second tool is previously assigned to a group to which the user belongs.
10. The method of claim 8, further comprising: repeating the act of identifying a second tool, wherein each identified second tool is included in a subset of the predetermined set of tools, each second tool enabling a user to create an item of a type corresponding to the second tool.
11. The method of claim 10, wherein identifying the second tool includes: determining all of the groups to which the user belongs; determining all of the tools previously assigned to the groups determined in the previous act.
12. The method of claim 1, further comprising: sending a first link to the tool to the user, wherein the first link describes the tool and, if selected by the user, causes an instruction to be sent to the computer causing the computer to send a second link to an item editable by the user using the tool.
13. The method of claim 12, wherein the instruction causes the computer to send a second link to each item editable by the user using the tool.
14. The method of claim 12, wherein the sending is performed automatically in response to receiving data identifying the user.
15. The method of claim 12, further comprising: receiving a selection of the first link; and in response to receiving the selection of the first link, sending the second link to the user.
16. The method of claim 15, further comprising: receiving a selection of the second link from the user; and in response to receiving the selection of the second link, providing editable access by the user to the item linked by the second link.
17. The method of claim 16, wherein providing editable access includes sending a webpage displaying information included in the item, wherein the webpage is programmed to allow the user to edit the information.
18. The method of claim 8, further comprising: sending a first link to the second tool to the user, wherein the first link describes the second tool, and the second tool enables the user to create a new item using the second tool.
19. The method of claim 18, further comprising: receiving a selection of the first link by the user; providing access to the second tool by the user for creating a new item with the second tool.
20. The method of claim 19, wherein providing access to the second tool includes sending a webpage programmed to receive data from the user to be included in the new item.
21. A method for a user to interact with a computer, the method comprising: identifying a first subset of tools from among a predetermined set of tools for use by the user for editing a plurality of items, wherein each item in the plurality is marked in the computer as being editable by a group of users to which the user belongs; identifying a second subset of tools from among the predetermined tools previously assigned to a group of users to which the user belongs, wherein each tool in the second subset enables a user to create a new item of information of a type corresponding to the tool; sending a first link to each tool in the first subset and the second subset to the user; receiving a selection of one of the first links from the user; if the tool linked by the selected first link is included in the first subset: sending a second link to an item editable using the tool; and if the tool linked by the selected first link is included in the first subset: sending a third link to the tool for creating a new item using the tool.
22. A method for user a to interact with a computer via a display device, the method comprising: selecting a tool from among a set of tools; creating an item with the tool; selecting one or more groups to which the item is to be published; for each selected group, setting one or more access privileges for the item; selecting one or more categories to which the item is to be published; and publishing the item to the selected groups.
23. The method of claim 22, further comprising: generating one or more information creation screens in response to the tool selection; and wherein the creating includes populating the information creation screens using the display device.
24. The method of claim 22, wherein populating the information creation screens includes entering one or more links to data constituting the to-be-created item.
25. The method of claim 24, wherein the link is an address.
26. The method of claim 22, wherein the creating includes entering a date on which the item will be automatically published to the groups.
27. The method of claim 22, wherein the creating includes entering a date on which the item will be automatically de-published from the groups.
28. The method of claim 22, wherein the group is selected from among a plurality of groups.
29. The method of claim 28, wherein the plurality of groups is structured as a tree with a plurality of nodes, including a root node, and wherein each node represents a group.
30. The method of claim 29, further comprising: displaying the group tree on the display device.
31. The method of claim 22, wherein the access privileges include a view privilege allowing a user to view the item, and an edit privilege allowing the user to view and edit the item.
32. The method of claim 22, wherein setting the access privileges includes one of the following: setting a view privilege; setting an edit privilege; and setting the view and the edit privileges.
33. The method of claim 22, wherein the categories are selected from among a plurality of categories.
34. The method of claim 33, wherein the plurality of categories is structured as one or more trees having a plurality of nodes, wherein each tree includes a root node, and each node represents a category.
35. The method of claim 34, further comprising: displaying the category tree on the display device.
36. The method of claim 22, further comprising: receiving the set of tools in response to entering identifying information about the user.
37. A computer-readable storage medium encoded with a table used in a database, the table comprising: a first column identifying a tool used for accessing an item of information; and a second column identifying the item.
38. The computer-readable storage medium of claim 37, wherein the table further comprises: a third column identifying a right to use the item by a user.
39. The computer-readable storage medium of claim 38, wherein the right to use the item includes one of the following: a right to view the item or a right to edit the item.
40. The computer-readable storage medium of claim 38, wherein the right to use the item includes a right to view the item and a right to edit the item.
41. The computer-readable storage medium of claim 37, wherein the table further comprises: a third column identifying one or more categories to which the item of information is published.
42. The computer-readable storage medium of claim 37, wherein the table further comprises: a third column identifying one or more groups of users to which the item is published.
43. The computer-readable storage medium of claim 37 , wherein the table further comprises: a third column identifying a to-be-published date on which the item of information is automatically published.
44. The computer-readable storage medium of claim 37, wherein the table further comprises: a third column identifying an expiration date on which the item of information is automatically de-published.
45. The computer-readable storage medium of claim 37, wherein the table further comprises: a third column identifying one or more categories to which the item of information is published.
46. The computer-readable storage medium of claim 45, wherein the table further comprises: a fourth column identifying one or more groups of users to which the item is published.
47. The computer-readable storage medium of claim 45, wherein the table further comprises: a fourth column identifying a right to use the item by a user.
48. The computer-readable storage medium of claim 45, wherein the table further comprises: a fourth column identifying a to-be-published date on which the item of information is automatically published.
49. 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; a second column identifying the item; a third column identifying one or more groups of users to which the item is published; a fourth column identifying a tool used for using the item; and a fifth column identifying a right to use the item by a user.
50. The computer-readable storage medium of claim 49, wherein the right to use the item includes one of the following: a right to view the item or a right to edit the item.
51. The computer-readable storage medium of claim 49, wherein the right to use the item includes a right to view the item and a right to edit the item.
52. The computer-readable storage medium of claim 49, wherein the table further comprises: a third column identifying one or more groups of users to which the item is published.
53. The computer-readable storage medium of claim 49, wherein the table further comprises: a third column identifying a to-be-published date on which the item of information is automatically published.
54. The computer-readable storage medium of claim 49, wherein the table further comprises: a third column identifying an expiration date on which the item of information is automatically de-published.
55. The computer-readable storage medium of claim 49, wherein the table further comprises: a third column identifying one or more groups of users to which the item is published; and a fourth column identifying a right to use the item by a user.
56. The computer-readable storage medium of claim 49, wherein the table further comprises: a third column identifying one or more groups of users to which the item is published; and a fourth column identifying a to-be-published date on which the item of information is automatically published.
57. The computer-readable storage medium of claim 49, wherein the table further comprises: a third column identifying one or more groups of users to which the item is published; and a fourth column identifying an expiration date on which the item of information is automatically de-published.
PCT/US2002/031282 2001-10-09 2002-09-30 Data driven access to tools WO2003032111A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002334770A AU2002334770A1 (en) 2001-10-09 2002-09-30 Data driven access to tools

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US97393501A 2001-10-09 2001-10-09
US09/973,935 2001-10-09

Publications (2)

Publication Number Publication Date
WO2003032111A2 true WO2003032111A2 (en) 2003-04-17
WO2003032111A3 WO2003032111A3 (en) 2003-12-18

Family

ID=25521393

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2002/031282 WO2003032111A2 (en) 2001-10-09 2002-09-30 Data driven access to tools

Country Status (2)

Country Link
AU (1) AU2002334770A1 (en)
WO (1) WO2003032111A2 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5313387A (en) * 1989-06-30 1994-05-17 Digital Equipment Corporation Re-execution of edit-compile-run cycles for changed lines of source code, with storage of associated data in buffers
US5335320A (en) * 1990-10-22 1994-08-02 Fuji Xerox Co., Ltd. Graphical user interface editing system
US5495613A (en) * 1994-08-18 1996-02-27 Unisys Corporation Method and apparatus for extending the capability of a system editor using high-level language transforms
US5696914A (en) * 1992-07-22 1997-12-09 Bull S.A. Using an embedded interpreted language to develop an interactive user-interface description tool
US5844554A (en) * 1996-09-17 1998-12-01 Bt Squared Technologies, Inc. Methods and systems for user interfaces and constraint handling configurations software
US6230309B1 (en) * 1997-04-25 2001-05-08 Sterling Software, Inc Method and system for assembling and utilizing components in component object systems

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5313387A (en) * 1989-06-30 1994-05-17 Digital Equipment Corporation Re-execution of edit-compile-run cycles for changed lines of source code, with storage of associated data in buffers
US5335320A (en) * 1990-10-22 1994-08-02 Fuji Xerox Co., Ltd. Graphical user interface editing system
US5696914A (en) * 1992-07-22 1997-12-09 Bull S.A. Using an embedded interpreted language to develop an interactive user-interface description tool
US5495613A (en) * 1994-08-18 1996-02-27 Unisys Corporation Method and apparatus for extending the capability of a system editor using high-level language transforms
US5844554A (en) * 1996-09-17 1998-12-01 Bt Squared Technologies, Inc. Methods and systems for user interfaces and constraint handling configurations software
US6230309B1 (en) * 1997-04-25 2001-05-08 Sterling Software, Inc Method and system for assembling and utilizing components in component object systems

Also Published As

Publication number Publication date
AU2002334770A1 (en) 2003-04-22
WO2003032111A3 (en) 2003-12-18

Similar Documents

Publication Publication Date Title
US6249291B1 (en) Method and apparatus for managing internet transactions
US6795826B2 (en) Fuzzy content network management and access
US7630974B2 (en) Multi-language support for enterprise identity and access management
US20060165040A1 (en) System, method, computer program products, standards, SOA infrastructure, search algorithm and a business method thereof for AI enabled information communication and computation (ICC) framework (NetAlter) operated by NetAlter Operating System (NOS) in terms of NetAlter Service Browser (NSB) to device alternative to internet and enterprise &amp; social communication framework engrossing universally distributed grid supercomputing and peer to peer framework
EP1643382A2 (en) System and method for unified navigation in Web pages
US20030225853A1 (en) Method and system for constructing a database-driven website
US20020174201A1 (en) Dynamic configuration of context-sensitive personal sites and membership channels
US20060136469A1 (en) Creating a logical table from multiple differently formatted physical tables having different access methods
US20110004621A1 (en) Techniques for integrating parameterized information request into a system for for collaborative work
Kobsa et al. An LDAP-based user modeling server and its evaluation
EP1836662A1 (en) A method and system for institution of information communication and computation framework
EP1512094A1 (en) Method and system for multiple virtual portals
US8225202B2 (en) Connected templates in connection with a content management server system or the like
Suleman Open digital libraries
WO2002069196A2 (en) System for logging on to servers through a portal computer
US20090210399A1 (en) Method and apparatus for presenting, searching, and viewing directories
WO2010065227A1 (en) Multi-level secure information retrieval system
US7149960B1 (en) Method and apparatus for controlling creation and management of pages of portal content in a directory
EP1589398B1 (en) Method and system for displaying and managing security information
US20070294370A1 (en) Scheduling and information sharing and distribution system and method
CA2436529A1 (en) Method and apparatus for managing publication and sharing of data
US20060212559A1 (en) Data source access editor and network data management method
WO2003032111A2 (en) Data driven access to tools
Wilson Building Node Applications with MongoDB and Backbone: Rapid Prototyping and Scalable Deployment
WO2003032153A1 (en) Data driven access to categories

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG UZ VC VN YU ZA ZM

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: COMMUNICATION UNDER RULE 69 EPC (EPO FORM 1205A DATED 23.07.2004)

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP