|Publication number||US6233583 B1|
|Application number||US 09/151,088|
|Publication date||May 15, 2001|
|Filing date||Sep 10, 1998|
|Priority date||Sep 10, 1998|
|Publication number||09151088, 151088, US 6233583 B1, US 6233583B1, US-B1-6233583, US6233583 B1, US6233583B1|
|Inventors||Robert Aloise Hoth|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (5), Non-Patent Citations (11), Referenced by (86), Classifications (18), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates generally to a report generation program for generating reports within a homogeneous or heterogeneous database system, and more particularly to a report generation program for generating reports within Lotus Notes.
Modern data processing environments often distribute a user's data among a plurality of databases each having a unique data format and unique data manipulation procedures. Such database systems are referred to as “heterogeneous database systems” and include systems such as Lotus Notes produced by Lotus Incorporated.
A particular disadvantage of storing data within Lotus Notes is the time, skill and cost associated with generating reports based on the stored data. Specifically, to generate reports within Lotus Notes a user must learn the database structure (e.g., field names, organization, acronym meanings, etc.) of each database containing relevant data, the location of each database (e.g., which server stores the database and the connection path thereto), the query syntax of Lotus Notes, as well as how to program Lotus Notes to collect, sort and display data. Additionally, each user within the database system must be notified each time the structure of a given database is changed (e.g., when a field is added to or removed from the database), and each time a database is added or deleted from the system. When such a change occurs each user must adjust his or her query syntax accordingly, and must revise the program used to sort and display the data.
Alternatively, reports can be generated from Lotus Notes databases using a second database program (such as data warehousing or data mining products that have reporting features). However, additional costs are incurred to purchase the additional database software, and to train users in its operation. Use of a second database program requires data stored in the Lotus Notes databases to be copied to a second database (associated with the second database program); the use of a second database program therefore requires added administrative effort as the structure of the second database must be revised each time the structure of a corresponding Lotus Notes database is revised. Therefore additional operating time is required for both initial data migration and for data refresh steps that ensure data contained in the second database is updated as new data is stored in the Lotus Notes database. Moreover, to see the data being reported on, a user must transfer from the second database program to Lotus Notes, making report generation with the second database program awkward and inconvenient.
Accordingly, there is a need for simplified report generation within Lotus Notes.
The present invention, provides for simplified report generation within a Lotus Notes database system. The inventive report generator provides two user paths, a general user path and an administrative user path. As described below, a general user need not learn the specific content, structure or location of any database within the system, and neither a general user nor an administrative user need learn Lotus Notes query syntax or programming methods.
In operation, before report generation can begin, an administrative user enters initial information regarding his or her specific database environment in an initialization file within the inventive report generator. The initial information includes the name of each database within the user's database system, the location (server and path) of each database, the number of, and a list of the fields to be read from each database during database searching (i.e., the retrieved field list), and the field categories and the fields within each category (i.e., the field category options) the administrative user designates as searchable and is preferably saved in a table (i.e., an Initialization Table). Typically this initial information is entered once and only is altered if the database environment changes.
Preferably the administrative user also enters initial information in the initialization file regarding report format. Specifically, the inventive report generator preferably provides a blank Report Template in which the administrative user enters field names in the order the administrative user wishes the field names to be displayed in a report, and then saves the Report Template with an identifiable name. A plurality of saved Report Templates, containing varying field names in varying orders, provides a user a plurality of report formats from which to choose. Thus, the administrative user fills out the blank Report Template and saves the Report Template as many times as desired to provide a plurality of report format options. After the user-specific initial information is provided in the Initialization Table and in the saved Report Templates, the report generator is ready to generate reports for a general user. Specifically, the report generator displays a form from which a general user can select databases and fields to search, and can select a report format for the information collected during the search. Thus, as used herein, user-selected, user-selectable and the like describe selection which does not require the user to manually generate program code. Likewise, user-provided or user-specified information is information provided or specified without requiring the user to manually generate program code.
As is apparent from the above description, the inventive report generator allows a general user to generate reports within either a heterogeneous or a homogenous Lotus Notes database system, without requiring a general user to know the content, structure or location of the various databases in the system. Moreover, a user, whether general or administrative, generates reports within Lotus Notes without writing any Lotus Notes programming code, and searches Lotus Notes databases without manually generating a single query string. The report generator locates the databases, generates the query strings, searches the databases, retrieves the desired information and organizes and displays the information, allowing for customized report generation with merely a few clicks of a mouse.
The structure and content of the initialization file, allows the report generator to adapt easily to any database environment. The Initialization Table and the Report Template Forms may be updated at any time and the report generator adapts dynamically. Further, the inventive report generator realizes quick report generation times as data is stored and manipulated within Lotus Notes and no data migration occurs.
Other objects, features and advantages of the present invention will become more fully apparent from the following detailed description of the preferred embodiments, the appended claims and the accompanying drawings.
The present invention is described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left-most digit of a reference number identifies the drawing in which the reference number first appears.
FIG. 1 is a block diagram illustrating a computer network which stores and runs a Lotus Notes database system with an inventive Report Engine operatively coupled therein;
FIG. 2 is a schematic diagram illustrating the Report Engine and the flow of commands and information among the Lotus Notes source databases and the Report Engine;
FIGS. 3A-E are an operational flow diagram for the Report Engine of FIG. 2;
FIG. 4 is a representative Report Definition Form generated by the Report Engine of FIG. 2;
FIG. 5 is a representative Report Template for use with the Report Engine of FIG. 2; and
FIG. 6 is a representative Report Document generated by the Report Engine of FIG. 2.
It will be understood with reference to the following description of the Report Engine's operation, that Lotus Notes Script Code within the Report Engine controls the operations described. Accordingly, armed with the following description, a Lotus Notes programmer of ordinary skill will be able to provide Lotus Notes Script Code for performing the operations described herein.
To generate a report, a user executes the inventive report generator, hereinafter the “Report Engine”, (e.g., by double clicking a Report Engine Icon within Lotus Notes), and a Report Definition Form (described below) is displayed on the user's computer screen. Preferably the user may open a new Report Definition Form or a previously saved Report Definition Form (containing previously selected databases, field category options and report formatting options as described below). The Report Definition Form displayed by the Report Engine contains the user-provided database names (previously provided in the Initialization Table by the administrative user) and a user selects one or more databases to search. The Report Definition Form also contains the searchable field categories and searchable field category options (provided in the Initialization Table), and the user then selects the field category options to search for within each selected database. Also displayed on the Report Definition Form are the names of the Report Templates previously saved by the administrative user. The user selects one of the displayed Report Template names, thereby determining the display format for the report.
The Report Engine generates a Lotus Notes query string based on the user-selected field category options, and instructs Lotus Notes to execute a full text search against each selected database using the query string and the database location information provided in the Initialization Table. Lotus Notes identifies the desired documents (e.g., those which contain the user-selected field category options) within each user-selected database. Instead of retrieving the entire contents of each identified document, for each identified document the Report Engine stores (within a random-access file) only the field information for each field listed in the Initialization Table's retrieved field list. Thus, for each identified document, the random-access file contains only a “retrieved information list” rather than the entire identified document.
Thereafter, the Report Engine organizes the retrieved information lists (corresponding to the identified documents). Specifically, because each identified document's retrieved information list may comprise many fields, the Report Engine assigns each retrieved information list an identifying key (comprising a concatenated list of field category values for the field categories employed within the selected Report Template). The Report Engine then assigns each key a pointer which points to the retrieved information list identified by the key, and the Report Engine sorts the keys (e.g., alphabetically, or as otherwise specified). The information to be displayed (previously provided in the saved Report Template by the administrative user) is obtained from among the retrieved information lists (retrieved from the documents identified during the full text search), and is displayed as a report in the order of the sorted keys and in the overall layout of the selected Report Template. The use of keys allows the Report Engine to quickly and easily organize the information collected from the identified documents. That is, the keys allow the Report Engine to quickly and easily organize the retrieved information lists without sorting or reordering the retrieved information lists themselves (which may contain hundreds of fields).
FIG. 1 is a block diagram illustrating a computer network 111 which stores and runs a Lotus Notes database system 113 with an inventive Report Engine 115 operatively coupled therein. The computer network 111 includes a plurality of computers 117 a-c, each computer 117 a-c respectively containing various hardware components such as a central processing unit (CPU) 119 a-c, a random access memory (RAM) 121 a-c and an input/output (I/O) interface 123 a-c. Each computer 117 a-c includes an operating system 125 a-c, suitable for executing a Lotus Notes application. Such operating systems are well known and include OS/2, DOS, DOS/Windows, etc.
The database system 113 includes a first Lotus Notes database 127 a, a second Lotus Notes database 127 b, and a Lotus Notes application 129 running on the first computer 117 a. The Lotus Notes application 129 may be stored on the hard drive (not shown) of the first computer 117 a or on a floppy disc, compact disc or similar storage medium. For convenience, the Lotus Notes application 129 is illustrated as being physically connected to the first computer 117 a.
A communication network 133, such as a local area network (LAN) or a wide area network (WAN), operatively couples each of the computers 117 a-c, such that the computers 117 a-c can communicate with each other over the communication network 133. The communication network 133 therefore operatively couples the inventive Report Engine 115 to the Lotus Notes databases 127 a-b and to the Lotus Notes application 129. The Lotus Notes databases 127 a-b and the inventive Report Engine 115 can be located on any computer (having an operating system suitable for Lotus Notes execution) coupled to the communication network 133; the computer network 111 and the database system 113 of FIG. 1 merely exemplify one possible configuration.
The Report Engine 115 is a computer program product comprising a computer readable media or carrier 130 having computer program logic recorded thereon. The Report Engine 115 is read by a storage device such as a floppy drive unit, a hard drive unit, a tape backup unit, etc., represented generally by the reference numeral 131. The storage device 131 may store the Report Engine 115, or alternatively, the computer program logic within the Report Engine 115 may be loaded from the carrier to another storage location via the storage device 131. Thereafter, the CPU 119 a of the first computer 117 a can execute the Report Engine 115's computer program logic, enabling the first computer 117 a, in conjunction with the Lotus Notes application 129, to generate reports within the database system 113 as described with reference to FIG. 2.
FIG. 2 is a schematic diagram illustrating the Report Engine 115 and the flow of commands and information among the Lotus Notes source databases 127 a-b and the inventive Report Engine 115. Referring to FIG. 2, the Report Engine 115 comprises a Lotus Notes database containing Lotus Notes Script Code and a plurality of files 211 a-b and a plurality of arrays 211 c-d. As used herein, a file may comprise a conventional file (such as a random access file) or a Lotus Notes document. The files 211 a-b and the arrays 211 c-d are illustrated adjacent the Report Engine 115 so that data transfer to/from the files 211 a-b and the arrays 211 c-d may be clearly represented. The remaining components of FIG. 2 are described with reference to the general operation of the inventive Report Engine 115.
In operation the Report Engine 115 is loaded into the storage device 131 of the third computer 117 c, and is executed by the Lotus Notes application 129 running on the first computer 117 a. Computer program logic within the Report Engine 115 causes one or more icons to be displayed on the screen 117 a′ of the first computer 117 a. By double clicking a first icon (not shown) an administrative user opens an Initialization Table within an initialization file 211 a (preferably a Lotus Notes document stored within the database of the Report Engine 115 on the third computer 117 c). The administrative user then enters initial information regarding the environment of the database system 113 as indicated by arrow 1. The initial information includes the names of the Lotus Notes databases 127 a-b, the identification of the computer or “server” which stores the Lotus Notes databases 127 a-b (the second and third computers 117 b, 117 c, respectively), and the data path between the first and second computers 117 b, 117 c and the communication network 133. The administrative user also enters a list of the field categories and field category options that are searchable, and the number of and a list of fields the Report Engine 115 will collect during searching each of the Lotus Notes databases 127 a-b (e.g., the previously described retrieved field list). After the administrative user enters the initial information in the initialization file 211 a, a general user with no specific knowledge of the database system 113's structure or content can generate reports. Typically this initial information is entered once and only is altered if the database system 113 changes.
A general user, working from the first computer 117 a, opens the Report Engine 115 by double clicking an icon which the Lotus Notes application 129 displays on the first computer 117 a's screen 117 a′. The Report Engine 115 reads (indicated by arrow 2) the Initialization Table contained in the initialization file 211 a and uses the initial information contained therein to display a Report Definition Form (listing searchable databases, field categories and field category options) on the first computer 117 a's screen. Preferably the user may open a new Report Definition Form or a previously saved Report Definition Form (containing previously selected databases, field category options, and report formatting options). The user then selects from the Report Definition Form databases and field category options to search (arrow 3). The user also selects a Report Template and, if desired, may select other formatting options.
The Report Engine 115 generates a query string based on the user's selections, and, using the database location information in the initialization file 211 a, instructs the Lotus Notes application 129 to execute a full text search on one of or both of the Lotus Notes databases 127 a-b (arrows 4 a and 4 b, respectively), based on the query string. Documents 213 a-b (within Lotus Notes databases 127 a-b, respectively) containing the selected field category options are identified and the fields in the Initialization Table's retrieved field list are collected from each database as concatenated strings 213 a′-b′, respectively (arrows 5 a and 5 b). The Report Engine 115 stores the collected concatenated strings 213 a′-b′ (e.g., retrieved information lists 213 a′-b′) in a random-access data file 211 b (arrow 6) on the hard disk of the first computer 117 a. The retrieved information lists 213 a′-b′ also may be stored in a semicolon delimited text file (not shown) for viewing via a spread sheet if desired. Thereafter, the Report Engine 115 parses the desired information (e.g., the information to be displayed) from each retrieved information list 213 a′-b′.
The Report Engine 115 operates significantly faster if the fields in the retrieved field list are transferred from each database as a single concatenated string rather than transferring only the desired field information on a field-by-field basis. This is true even though much of the retrieved field information may never be displayed (e.g., depending on the chosen Report Template). However, field-by-field transfer may be employed if desired.
To organize the retrieved information lists 213 a′-b′ within the random-access file 211 b, the Report Engine 115 reads the user-selected Report Template (preferably stored with the Report Engine 115 on the third computer 117 c). The Report Engine 115 determines an appropriate identifying key format for the retrieved information lists 213 a′-b′ by compiling a set of field categories within the selected Report Template. The Report Engine 115 then generates an identifying key (based on field categories within the selected Report Template and the corresponding field category values within the retrieved information list) for each retrieved information list in the random-access file 211 b, as will be more fully understood with reference to the example of FIGS. 3A-E. The Report Engine 115 assigns each key a pointer which points to the retrieved information list (within the random-access file 211 b) identified by the key, and the Report Engine 115 stores (arrow 7) the unsorted key/pointer list within an unsorted key array 211 c.
The Report Engine 115 then sorts the keys within the unsorted key array 211 c, either in a default order such as numerical and alphabetical, or, according to a user elected order. The sorted keys are stored in a sorted key array 211 d (arrow 8). Preferably the sorted key array 211 d replaces the sorted key array 211 c. The unsorted and sorted key arrays 211 c, 211 d, respectively, are shown as separate arrays in FIG. 2 only to aid in the understanding of the Report Engine 115's operation. Thereafter during report generation, the Report Engine 115 obtains information from each retrieved information list from the random-access file 211 b in the sequence of the ordered keys within the sorted key array 211 d, and displays desired information on the first computer 117 a's screen (arrow 9) according to the selected Report Template.
The operation of the inventive Report Engine 115 of FIG. 2 is further described with reference to the operational flow diagram of FIGS. 3A-E and the exemplary tables described below. The operational flow diagram of FIGS. 3A-E shows portions of FIG. 2 where appropriate to further facilitate understanding of the inventive Report Engine 115.
In the FIGS. 3A-E example, the first database 127 a of FIG. 2 contains sales information for ABC Company for the months of January and February 1998, as shown in TABLE 1 below. The sales information within the first database 127 a is organized by department within ABC Company and comprises the following field categories: department name, first-line manager name, second-line manager name, product name, product description, vendor name, sales for January 1998 and sales for February 1998, hereinafter referred to as dept, manager1, manager 2, product, proddesc, vendor, Jan. and Feb., respectively. The first database 127 a is located on a first server (server 1) at Path=path1\database1.nsf.
FIRST DATABASE 127a
Database *1: (Path = path1\database1.nsf)
The second database 127 b of FIG. 2 also contains sales information for ABC Company, organized by department, as shown in TABLE 2 below. The second database 127 b is located on a second server (server 2) at Path=path2\database2.nsf. In this example, the first and second databases 127 a-b are homogeneous databases (e.g., both Lotus Notes databases). It will be understood, however, that heterogeneous databases may be employed.
SECOND DATABASE 127b
Database #2: (Path = path2\database2.nsf)
Referring to the flow diagram of FIGS. 3A-E, to generate a report based on the information contained within the first and second databases 127 a-b, the Report Engine 115 is executed in step 300 (e.g., by double-clicking a Report Engine icon while running the Lotus Notes application 129).
Thereafter, in step 301 the Report Engine 115 initializes its global variables (e.g., field categories and field category options to be displayed on the Report Definition Form of FIG. 4, described below), and establishes connections to the first and second databases 127 a-b. Variable initialization and database connections are performed by reading an Initialization Table (shown below as TABLE 3) that contains Database Connection Information, General Definition Information and Other Related Information. The Initialization Table may be contained within an initialization file such as the initialization file 211 a of FIG. 2.
Database Connection Information
Database 1 (database 127a)
Database 2 (database 127b)
General Definition Information
Field Category Name (on
Field Category Option
Report Definition Form)
Computer Monitor, Laptop
Monitor, Screen Saver
Monitor World, Monitor
Country, Monitor City
Other Related Information
Fields to be retrieved during
8, dept, manager1, manager2,
product, proddesc, vendor, Jan, Feb,
The Database Connection Information section of the Initialization Table comprises the name, server and path for both the first and second databases 127 a-b. Database name, server and path information is supplied/maintained by an administrative user and is transparent to a general user of the Report Engine 115. A significant advantage of the Initialization Table is that a database may be added to or subtracted from the Report Engine 115's list of searchable databases merely by adding the database to or deleting the database from the Database Connection Information section of the Initialization Table; no additional Lotus Notes Script Code need be written.
The General Definition Information section of the Initialization Table comprises the name of each user-searchable field category (as previously provided by the administrative user), the corresponding field category name that appears on the Report Definition Form (FIG. 4) and a list of user-searchable field category options for each user-searchable field category. Accordingly, user-searchable field categories and user-searchable field category options may be added to or subtracted from the Report Engine 115's list of searchable field categories and searchable field category options merely by adding the field categories and field category options to or deleting the field categories and field category options from the Initialization Table; no additional Lotus Notes Script Code need be written. The Report Definition Form will be updated accordingly either automatically by the Report Engine or manually by the administrative user, depending on the particular implementation.
The Other Related Information section of the Initialization Table (TABLE 3) comprises a concatenated list of each field that is read from database documents during database searching (e.g., the retrieved field list), as described below. As previously stated, the present inventor has discovered that the Report Engine 115 operates much faster if all relevant information within a database document is transferred to the Report Engine 115 in a concatenated string rather than on a field-by-field basis.
Thereafter, the Report Engine parses the information to be displayed from the concatenated string. For instance, in the Other Related Information section of the Initialization Table (TABLE 3), next to the “Fields to be retrieved during searching” cell, is a cell containing a concatenated list “8, dept, manager1, manager2, product, proddesc, vendor, Jan., Feb.,” that represents the fields of information retrieved (e.g., the retrieved field list) from database documents during searching, and thus lists all fields of information that may be displayed by a user. The “8” represents the number of fields of information in the list. Depending on the Report Template selected by the user, only a portion of the fields of information within the retrieved field list may be displayed. However, all these fields of information are retrieved by the Report Engine 115 for each document containing the field category options selected by the user. If an additional field of information is added to the first and/or second database 127 a-b, the field of information can be rendered “displayable” by the Report Engine 115 by changing the number 8 to 9 and by adding an appropriate field name to the concatenated list within the Other Related Information section of the Initialization Table. No additional Lotus Notes Script Code is required.
Once the variable initialization and database connections are performed, control is passed to step 302. In step 302 a Report Definition Form 401 (shown in FIG. 4) is displayed on the user's computer screen. As described below, the Report Definition Form 401 is a graphical user interface that presents a user of the Report Engine 115 with selectable search criteria based on the contents of the Initialization Table (TABLE 3). The first portion of the Report Definition Form 401 comprises a list of user-selectable, source databases 403 that the user may search (e.g., a list of each database defined in the Initialization Table (TABLE 3)). In FIG. 4, the first database 127 a and the second database 127 b (the only databases defined in the Initialization Table—TABLE 3), are displayed on the Report Definition Form 401.
A Report Criteria Section 405 of the Report Definition Form 401 follows the list of source databases 403. The Report Criteria Section 405 comprises a list of searchable field categories 407 a-c (e.g., “Department” 407 a, “Vendor” 407 b and “Product” 407 c) and a list of one or more searchable field category options 409 a-c, respectively, for each field category. The Report Criteria Section 405, for example, contains a list (complied from the Initialization Table—TABLE 3) of searchable departments 409 a including each department within the first and second databases 127 a-b (e.g., Keyboard, Motherboard and Video), a list of searchable vendors 409 b (e.g., Monitor World, Monitor Country and Monitor City), and a list of searchable products 409 c (e.g., Computer Monitor, Laptop Monitor and Screen Saver). Preferably only the vendors and products relevant to a selected department are displayed. A user thereafter may select from the field category option lists 409 a-c the field category options (e.g., department options, vendor options and/or product options) to be searched by placing an “X” thereby (e.g., Department “Video”, Vendor “Monitor World” and Products “Computer Monitor” and “Screen Saver” in FIG. 4). Field category options also may be explicitly excluded from a search via NOT logic (i.e., “NOT-selected”) if desired by placing a “!” (not shown) adjacent a field category option.
Following the Report Criteria Section 405, a Report Format Section 411 specifies how and what information retrieved from the first and second databases 127 a-b is displayed. The Report Format Section 411 comprises a list of one or more previously saved, selectable Report Templates 413, and beginning/ending dates 415 for the information displayed. Preferably the choices among Report Templates 413 and the beginning/ending dates 415 are displayed via pop-up dialog boxes. Each selectable Report Template is generated by an administrative user from a blank Report Template and describes how and what field categories are displayed on a Report Document as described with reference to FIG. 5.
FIG. 5 is a representative Report Template 501 for use with the Report Engine 115. In addition to a name block 503 (e.g., “Dept/Vend/Product”) and a description block 505, the Report Template 501 comprises a Categories Section 507 and a Computable Section 509. Within the Categories Section 507, field category names (e.g., dept, manager1, vendor, product) are arranged on the line and in the order the field category names are to be displayed in a Report Document (FIG. 6). As shown in FIG. 5, the first line of a Report Document (FIG. 6) employing the Report Template 501 will display department and manager information, the second line of the Report Document will display vendor information and the third line of the Report Document will display product information.
Preferably the name of the Report Template 501 (e.g., Dept/Vend/Product) identifies the information that will be displayed by the template. For instance, if “Dept” is used as an acronym for [dept] [manager1], “Vend” is used as an acronym for [vendor], and “Product” is used as an acronym for [product], a user will know that a Report Template having the name “Dept/Vend/Product” will display department, first-line manager, vendor and product information. Similarly, a user will know that a Report Template having the name “Dept/Vend” will display department, first-line manager and vendor information only. Within the computable section 505, field category names (e.g., vendor and product or any other information a user wishes to display) are arranged next to database information on which computations (e.g., the total number of each product sold to a vendor in the months of January and February 1998) are to be performed.
In addition to the above-described Report Definition Form 401 entries, other advanced options preferably are provided that affect report format (e.g., rounding, field width, landscape/portrait display). These other options may be provided via pull-down menus or the like.
Once a user has selected the databases to search, the departments, vendors, and products for which to search, and the report format options from the Report Definition Form 401, the user “runs” the Report Definition Form 401 and control passes to step 303. Preferably the user also has the option to save the Report Definition Form 401, run the Report Definition Form 401 based on a sample of the information retrieved from the first database 127 a and/or from the second database 127 b, or may exit without running the Report Definition Form 401.
In step 303, the field category options selected from the Report Definition Form 401 are arranged to form a Lotus Notes full text search query string based on the following logic rules:
1. for each field category having user-selected field category options, OR each selected or NOT-selected field category option within the field category to form an ORed option set; and
2. AND each ORed option set.
Applying these logic rules to the user-selected field category options from the Report Definition Form 401 (FIG. 4), the resulting query string is:
query string=(Field dept=“Video”) AND (Field vendor=“Monitor World”) AND (Field product=“Computer Monitor” OR Field product=“Screen Saver”)
Thereafter, in step 304 the Report Engine 115 directs Lotus Notes to perform a full text search of the first and second databases 127 a-b, based on the query string, and to identify the documents that meet the search criteria specified on the Report Definition Form 401 (FIG. 4).
In step 305, the Report Engine 115 retrieves the information listed in the retrieved field list of the Initialization Table (TABLE 3) for each identified document and stores the retrieved information (e.g., a retrieved information list) in a random-access file 211 b (hereinafter “RAF 211 b”). An additional file 211 b′ (FIG. 3C) may be generated which contains the number of documents identified by the search and the query string employed. TABLE 5 shows the contents of the RAF 211 b when the first and second databases 127 a-b are searched based on the above query string. Note the “RAF 211 b list #” column is provided for reference purposes only and is not an actual column of information stored in the RAF 211 b.
RAF 211b Results:
In step 306, global variables (e.g., conventional accumulator arrays) used during processing of the collected information are initialized.
In step 307, the Report Engine 115 processes the Report Template 501 selected by the user, identifying desired information to be displayed and computations to be performed. Based on the acronyms employed within the name block 503 of the Report Template 501 a key is generated for each retrieved information list within the RAF 211 b. For instance, the Report Template 501's name comprises acronyms Dept, Vend, and Product which represent [dept] [manager1], [vendor] and [product], respectively. The key for each retrieved information list within the RAF 211 b, therefore, is a concatenated string containing the list's field category values for “dept manager1 vendor product.” It will be understood that any suitable key for identifying each retrieved information list may be similarly employed.
In step 308, an unsorted index table shown below as TABLE 5 is generated which lists the key for each retrieved information list in the RAF 211 b and which includes a pointer for mapping each key to the corresponding retrieved information list from which the key originated. The unsorted index table is stored in the unsorted key array 211 c as previously described. The order of the keys in the unsorted index table is the same order as the order of the retrieved information lists in the RAF 211 b.
corresponding RAF 211b
Dept. Manager1 Vendor Product
Video Doe J MonitorWorld Computer Monitor
Video Doe J MonitorWorld Screen Saver
Video Doe J MonitorWorld Computer Monitor
In step 309, the unsorted index table is sorted using a conventional MergeSort algorithm so as to generate a sorted (e.g., in alphabetical or user-specified order) index table as shown in TABLE 6. The sorted index table is stored in the sorted key array 211 d. Because the key index tables (TABLES 5 and 6) contain only a few fields of information the unsorted key index table may be sorted much faster than the RAF 211 b which may contain retrieved information lists having hundreds of fields. As described below, the sorted key index table (TABLE 6) is used to organize the display of information from the retrieved information lists in the RAF 211 b as the information is displayed on a Report Document.
corresponding RAF 211b
Dept. Manager1 Vendor Product
Video Doe J MonitorWorld Computer Monitor
Video Doe J MonitorWorld Computer Monitor
Video Doe J MonitorWorld Screen Saver
To aid in computation of the computable data within a Report Document (e.g., total sales per month per department, per vendor or per product), in step 310 a data range table (TABLE 7) is computed from the sorted index table (TABLE 6). A “data range” is the number of retrieved information lists (in RAF 211 b) having the same field category value (e.g., video) for the same field category (e.g., department). Accordingly, the data range is “three” for the “department” field category (e.g., retrieved information lists 1-3 have the same department field value—“video”), is three for the “vendor” field category (e.g., retrieved information lists 1-3 have the same vendor field value—“monitor world”), and is two for the “product” field category (e.g., retrieved information lists 1-2 have the same product field value—“computer monitor”).
In step 311, the Report Engine 115 employs the Report Template 501 (FIG. 5), the RAF 211 b, the sorted index table (TABLE 6) and the data range table (TABLE 7) to generate/display a Report Document 601 as shown in FIG. 6. The Report Document 601 (FIG. 6) comprises a General Information Section 603 and a Report Information Section 605. The General Information Section 603 may contain any or no information, and preferably comprises such information as the company name (e.g., ABC Company), the name of the Report Template 501 used (e.g., Dept/Vend/Product), the dates covered by the data within the Report Document 601 (e.g., Jan./98 to Feb./98), the name of the person generating the Report Document 601 (e.g., John Doe) and a description of the Report Document 601.
The Report Information Section 605 comprises search information 607 read from the file 211 b′ such as the number of documents identified and the query string used during searching, and also comprises report data 609 derived from the RAF 211 b, displayed in the order specified by the sorted index table (TABLE 6) and arranged as specified by the Report Template 501. For instance, line 609 a of the report data 609 is organized as specified by the first-line of the Report Template 501 (e.g., department and first line manager information on the same line). Similarly, the second line 609 b is organized as specified by the second line of the Report Template 501 (e.g., vendor information), and the third and fourth lines 609 c, 609 d are organized as specified by the third line of the Report Template 501 (e.g., product information).
Also shown on the Report Document 601 are the total sales per month on a per vendor basis and on a per product basis. To compute these values, the data range table (TABLE 7) is employed. For example, to compute the total sales to the vendor “Monitor World” for January 1998 the following steps are performed:
1. the “Vend” column of the data range table (TABLE 7) is consulted;
2. because the data range is three, the field values for January (e.g., Jan.) for all three retrieved information lists within the RAF 211 b are obtained; and
3. the three field values are added (e.g., via a conventional accumulator array) and the total is displayed.
The data range table (TABLE 7) thus informs the Report Engine 115 which retrieved information lists must be read for each computation. Similar operations are performed for each entry in the Jan. and Feb. columns of the report data section 609 of FIG. 6.
After the Report Document 601 is displayed, in step 312 the Report Engine 115's operation terminates.
Accordingly, a user of the Report Engine 115 can generate a customizable (e.g., via Report Templates and other options that affect report format) Report Document 601 (FIG. 6) based on a variety of search criteria (e.g., selected via the Report Definition Form 401 of FIG. 4) for any Lotus Notes database system. The user generates custom reports without knowledge of the structure of any database within the database system, without manually generating a single query string and without knowing Lotus Notes Script Code. The inventive Report Engine adapts easily to a user's specific database environment, dynamically incorporating changes made to the Initialization Table and to the Report Templates.
The foregoing description discloses only the preferred embodiments of the invention, modifications of the above disclosed apparatus and method which fall within the scope of the invention will be readily apparent to those of ordinary skill in the art. For instance, any of the database names, field categories, field category options or Report Template names may be hard coded on the Report Definition Form 401 rather than employing an Initialization Table. Additionally, Report Definition Form selections may be stored and employed as the default selections on subsequent Report Definition Forms to expedite multiple searches involving few changes in user selections between searches.
If desired, a password may be required for a user to access database information. If the Report Definition Form is configured so that a user types information (e.g., rather than checking a box), a validation procedure may be employed wherein the Report Engine verifies the typed information and obtains supporting information about the typed information (e.g., the structure of a department, which products are produced by the department, who works in the department, etc.) so as to affect the field category options displayed on the Report Definition Form. As used herein, a computer program product's “carrier” includes any medium for storage or retrieval such as a floppy disc, a compact disc, a digital versatile disc, a World Wide Web server or a hyperlink, and the like. Further, the Report Engine can operate with any database that can be searched by Lotus Notes (whether Lotus Notes based or not). Additionally, multiple blank Report Templates having various data formatting options (e.g., different arrangement or computation options) may be provided.
Accordingly, while the present invention has been disclosed in connection with the preferred embodiments thereof, it should be understood that other embodiments may fall within the spirit and scope of the invention, as defined by the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5832208 *||Sep 5, 1996||Nov 3, 1998||Cheyenne Software International Sales Corp.||Anti-virus agent for use with databases and mail servers|
|US5966707 *||Dec 2, 1997||Oct 12, 1999||International Business Machines Corporation||Method for managing a plurality of data processes residing in heterogeneous data repositories|
|US6064977 *||Jun 19, 1998||May 16, 2000||International Business Machine Corporation||Web server with integrated scheduling and calendaring|
|US6070190 *||May 11, 1998||May 30, 2000||International Business Machines Corporation||Client-based application availability and response monitoring and reporting for distributed computing environments|
|US6094655 *||Sep 18, 1997||Jul 25, 2000||International Business Machines Corporation||Method of creating and using notes decision capsules|
|1||"IBM Visual Warehouse User's Guide Release 2", Contents pp. iii-xii, Chapter 1-Introducing the IBM Visual Warehouse, pp. 2-20, Chapter 8-Using the Business View icon, pp. 179-255 and pp. 262-264, 1995.|
|2||"Lotus Notes Release 4 The Power of People Working Together" Application Developer's Guide, Contents pp. iii and x-xiv, Chapter 1 Introduction to Notes Development, pp. 1-3, Chapter 5 Designing Views and Folders, pp. 207-303, 1995.|
|3||"IBM Visual Warehouse User's Guide Release 2", Contents pp. iii-xii, Chapter 1—Introducing the IBM Visual Warehouse, pp. 2-20, Chapter 8—Using the Business View icon, pp. 179-255 and pp. 262-264, 1995.|
|4||Berthold Reinwald , C. Mohan, "Structured workflow management with lotus Notes Release 4", IEEE, pp. 451-457, Jan. 1996.*|
|5||Bucky Pope, "Characterizing Lotus Notes Email Clients", IEEE, pp. 128-132, 03/98.*|
|6||James E. Powell; "Mastering Approach 3 for Windows"; Chapter 11, Reports, pp. 370-404; Chapter 12, Finding and Sorting Data, pp. 411 -437, 1995.|
|7||Paul Cummings, "Enhancing Lotus Notes for carrier Grade hosting", IEEE, pp. 488-407, Jan. 1996.*|
|8||Russ Kiger, "Expert system & Lotus Notes applications for retrieval of problem-solving knowledge & information", IEEE, pp. 344-350, May 1996.*|
|9||Schultze et al., "Hard and Soft information Genres: An Analysis of two Notes Databases", pp. 40-49, 1/97.*|
|10||Stephan Schoening, "Supporting a software engineering course with lotus notes", IEEE, pp. 304-311, Sep. 1998.*|
|11||Vandenbosch et al. "Lotus Notes and Collaboration: le plus ca change", IEEE, pp. 61-71, Jan. 1996.*|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6341286 *||Oct 26, 1998||Jan 22, 2002||Bsp International Corporation||Method and apparatus for generating and distributing reports|
|US6393418 *||Jan 4, 2000||May 21, 2002||Sony Corporation||Method of and apparatus for sorting a file|
|US6557004 *||May 2, 2000||Apr 29, 2003||Microsoft Corporation||Method and apparatus for fast searching of hand-held contacts lists|
|US6651017||Apr 30, 2001||Nov 18, 2003||General Electric Company||Methods and systems for generating a quality enhancement project report|
|US6996568 *||Apr 11, 2002||Feb 7, 2006||Microstrategy Incorporated||System and method for extension of data schema|
|US7031979 *||Aug 31, 2001||Apr 18, 2006||Hewlett-Packard Development Company, L.P.||Report generation system and method|
|US7051038||Jun 28, 2002||May 23, 2006||Microsoft Corporation||Method and system for a reporting information services architecture|
|US7065532||Oct 31, 2002||Jun 20, 2006||International Business Machines Corporation||System and method for evaluating information aggregates by visualizing associated categories|
|US7080082||Oct 31, 2002||Jul 18, 2006||International Business Machines Corporation||System and method for finding the acceleration of an information aggregate|
|US7082436 *||Jan 5, 2000||Jul 25, 2006||Nugenesis Technologies Corporation||Storing and retrieving the visual form of data|
|US7103609||Oct 31, 2002||Sep 5, 2006||International Business Machines Corporation||System and method for analyzing usage patterns in information aggregates|
|US7130844||Oct 31, 2002||Oct 31, 2006||International Business Machines Corporation||System and method for examining, calculating the age of an document collection as a measure of time since creation, visualizing, identifying selectively reference those document collections representing current activity|
|US7249123||Oct 31, 2002||Jul 24, 2007||International Business Machines Corporation||System and method for building social networks based on activity around shared virtual objects|
|US7257569||Oct 31, 2002||Aug 14, 2007||International Business Machines Corporation||System and method for determining community overlap|
|US7264150||Jul 22, 2004||Sep 4, 2007||Tidel Engineering, L.P.||Computerized drop safe and control software|
|US7315864 *||Mar 2, 2001||Jan 1, 2008||Valentine Edmund L||System and method for creating a book of reports over a computer network|
|US7428985||Jun 13, 2007||Sep 30, 2008||Tidel Engineering, L.P.||Computerized drop safe and control software|
|US7644088||Nov 12, 2004||Jan 5, 2010||Tamale Software||Systems and methods for retrieving data|
|US7657552 *||Feb 12, 2003||Feb 2, 2010||Microsoft Corporation||Declarative sequenced report parameterization|
|US7716253 *||Feb 3, 2005||May 11, 2010||Microsoft Corporation||Centralized KPI framework systems and methods|
|US7844570||Mar 8, 2005||Nov 30, 2010||Microsoft Corporation||Database generation systems and methods|
|US7853594||Oct 31, 2002||Dec 14, 2010||International Business Machines Corporation||System and method for determining founders of an information aggregate|
|US7886284||Sep 5, 2006||Feb 8, 2011||International Business Machines Corporation||Using a backend simulator to test and develop xforms templates before linking the xforms templates to backend data processing systems|
|US7937401||May 3, 2011||Microsoft Corporation||Multidimensional database query extension systems and methods|
|US8112401 *||May 25, 2005||Feb 7, 2012||Ecteon, Inc.||Analyzing externally generated documents in document management system|
|US8145629 *||May 28, 2004||Mar 27, 2012||International Business Machines Corporation||Method and system for business reporting|
|US8266138 *||Jul 18, 2008||Sep 11, 2012||Salesforce.Com, Inc.||On-demand database service system, method and computer program product for generating a custom report|
|US8321435 *||Aug 12, 2009||Nov 27, 2012||Apple Inc.||Quick find for data fields|
|US8380742||Oct 10, 2006||Feb 19, 2013||Microsoft Corporation||Integration of database reporting with ERP systems|
|US8479093||Mar 1, 2007||Jul 2, 2013||Microsoft Corporation||Metamodel-based automatic report generation|
|US8775277||Apr 21, 2006||Jul 8, 2014||International Business Machines Corporation||Method, system, and program product for electronically validating invoices|
|US8849840||Oct 19, 2012||Sep 30, 2014||Apple Inc.||Quick find for data fields|
|US8868620 *||Jun 8, 2007||Oct 21, 2014||International Business Machines Corporation||Techniques for composing data queries|
|US8886671||Aug 14, 2013||Nov 11, 2014||Advent Software, Inc.||Multi-tenant in-memory database (MUTED) system and method|
|US8918773 *||Sep 22, 2011||Dec 23, 2014||Verizon Patent And Licensing Inc.||Partially upgradable application and performing database operations with the application|
|US8943397||Oct 13, 2006||Jan 27, 2015||International Business Machines Corporation||Configurable column display of information at a web client|
|US9043358 *||Mar 9, 2011||May 26, 2015||Microsoft Technology Licensing, Llc||Enterprise search over private and public data|
|US20010037334 *||Mar 2, 2001||Nov 1, 2001||Valentine Edmund L.||System and method for creating a book of reports over a computer network|
|US20020194186 *||Mar 18, 2002||Dec 19, 2002||Foundation Software, Inc.||Report design and data manipulation system and method of operation|
|US20030046264 *||Aug 31, 2001||Mar 6, 2003||Kauffman Mark Bykerk||Report generation system and method|
|US20040064353 *||Aug 29, 2002||Apr 1, 2004||Kim Yeong-Ho||System and method for creating personalized template for monitoring workflows|
|US20040088275 *||Oct 31, 2002||May 6, 2004||International Business Machines Corporation||System and method for finding the acceleration of an information aggregate|
|US20040088287 *||Oct 31, 2002||May 6, 2004||International Business Machines Corporation||System and method for examining the aging of an information aggregate|
|US20040088312 *||Oct 31, 2002||May 6, 2004||International Business Machines Corporation||System and method for determining community overlap|
|US20040088322 *||Oct 31, 2002||May 6, 2004||International Business Machines Corporation||System and method for determining connections between information aggregates|
|US20040088323 *||Oct 31, 2002||May 6, 2004||International Business Machines Corporation||System and method for evaluating information aggregates by visualizing associated categories|
|US20040088325 *||Oct 31, 2002||May 6, 2004||International Business Machines Corporation||System and method for building social networks based on activity around shared virtual objects|
|US20040158557 *||Feb 12, 2003||Aug 12, 2004||Microsoft Corporation||Declarative sequenced report parameterization|
|US20050086204 *||Nov 20, 2002||Apr 21, 2005||Enrico Coiera||System and method for searching date sources|
|US20050108024 *||Nov 13, 2003||May 19, 2005||Fawcett John Jr.||Systems and methods for retrieving data|
|US20050108262 *||Nov 12, 2004||May 19, 2005||Fawcett John Jr.||Systems and methods for retrieving data|
|US20050257135 *||May 14, 2004||Nov 17, 2005||Robert Listou||Computer generated report comprised of names, text descriptions, and selected parametric values of designated text data objects listed on data tables|
|US20060010102 *||May 28, 2004||Jan 12, 2006||Labossiere Paul R||Method and system for business reporting|
|US20060010164 *||Feb 3, 2005||Jan 12, 2006||Microsoft Corporation||Centralized KPI framework systems and methods|
|US20060020619 *||Mar 8, 2005||Jan 26, 2006||Microsoft Corporation||Database generation systems and methods|
|US20060020933 *||Apr 28, 2005||Jan 26, 2006||Microsoft Corporation||Multidimensional database query extension systems and methods|
|US20060045355 *||Aug 16, 2005||Mar 2, 2006||Kyocera Corporation||Mobile terminal, and computer controlling method and program for use in the same|
|US20060053161 *||Jul 12, 2002||Mar 9, 2006||Lee John C||Method to organize and track information according to chronological and priority order|
|US20060074860 *||Jul 8, 2003||Apr 6, 2006||Matsushita Electric Industrial Co., Ltd.||Data search device|
|US20060271519 *||May 25, 2005||Nov 30, 2006||Ecteon, Inc.||Analyzing externally generated documents in document management system|
|US20060277193 *||Jun 2, 2005||Dec 7, 2006||Moncreiff Craig T||System and method for internet-based financial analysis and data processing for the creation of financial reports|
|US20060288033 *||Jun 16, 2005||Dec 21, 2006||Digital Fuel Technologies, Inc.||System for pre-caching reports of streaming data|
|US20070094347 *||May 9, 2006||Apr 26, 2007||Teamon Systems, Inc.||System for obtaining image using xslt extension and related method|
|US20070233680 *||Mar 31, 2006||Oct 4, 2007||Microsoft Corporation||Auto-generating reports based on metadata|
|US20070250416 *||Apr 21, 2006||Oct 25, 2007||International Business Machines Corporation||Method, system, and program product for electronically validating invoices|
|US20080086495 *||Oct 10, 2006||Apr 10, 2008||Microsoft Corporation||Integration of Database Reporting with ERP Systems|
|US20080092033 *||Oct 13, 2006||Apr 17, 2008||International Business Machines Corporation||Configurable column display of information at a web client|
|US20080126925 *||Sep 5, 2006||May 29, 2008||International Business Machines Corporation||Using a backend simulator to test and develop xforms templates before linking the xforms templates to backend data processing systems|
|US20080215621 *||Mar 1, 2007||Sep 4, 2008||Karthik Ravindran||Metamodel-based automatic report generation|
|US20080306910 *||Jun 8, 2007||Dec 11, 2008||Hardeep Singh||Method and process for end users to query hierarchical data|
|US20090112743 *||Oct 31, 2007||Apr 30, 2009||Mullins Christine M||System and method for reporting according to eu vat related legal requirements|
|US20110040745 *||Feb 17, 2011||Oleg Zaydman||Quick find for data fields|
|US20110238707 *||Sep 29, 2011||Salesforce.Com, Inc.||System, method and computer program product for creating an object within a system, utilizing a template|
|US20120233209 *||Mar 9, 2011||Sep 13, 2012||Microsoft Corporation||Enterprise search over private and public data|
|US20130081006 *||Sep 22, 2011||Mar 28, 2013||Verizon Patent And Licensing Inc.||Partially upgradable application and performaing database operations with the application|
|US20130124985 *||Nov 10, 2011||May 16, 2013||Microsoft Corporation||Conditional Localization of Singular and Plural Words|
|US20150186442 *||Dec 31, 2013||Jul 2, 2015||Elton WILDERMUTH||In-place index repair|
|CN100392647C||Jul 8, 2003||Jun 4, 2008||松下电器产业株式会社||Data search device|
|CN103092890A *||Nov 8, 2011||May 8, 2013||苏州中茵泰格科技有限公司||System and method for automatic generation and sending of reports|
|EP1425685A1 *||Aug 29, 2002||Jun 9, 2004||Handysoft Co., Ltd.||System and method for creating personalized template for monitoring workflows|
|EP1553505A1 *||Jul 8, 2003||Jul 13, 2005||Matsushita Electric Industrial Co., Ltd.||Data search device|
|WO2003067474A2 *||Feb 5, 2003||Aug 14, 2003||Bellis Joseph De||Search-on-the fly report generator|
|WO2004003768A1 *||May 5, 2003||Jan 8, 2004||Hulslander Ralph||System and method for preparing and using automated forms|
|WO2006080913A1 *||Jan 26, 2005||Aug 3, 2006||Efunds Corp||Report generating systems and methods|
|U.S. Classification||707/752, 707/999.102, 707/769, 707/802, 707/999.007, 707/999.003, 707/999.004, 707/999.201, 707/999.002|
|Cooperative Classification||Y10S707/99933, Y10S707/99932, Y10S707/99937, Y10S707/99952, Y10S707/99943, Y10S707/99934, G06F17/30398|
|Sep 10, 1998||AS||Assignment|
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HOTH, ROBERT ALOISE;REEL/FRAME:009457/0711
Effective date: 19980909
|Sep 22, 2004||FPAY||Fee payment|
Year of fee payment: 4
|Nov 24, 2008||REMI||Maintenance fee reminder mailed|
|May 15, 2009||LAPS||Lapse for failure to pay maintenance fees|
|Jul 7, 2009||FP||Expired due to failure to pay maintenance fee|
Effective date: 20090515