CA2669479C - Generating end-user presentations from structured data - Google Patents
Generating end-user presentations from structured data Download PDFInfo
- Publication number
- CA2669479C CA2669479C CA2669479A CA2669479A CA2669479C CA 2669479 C CA2669479 C CA 2669479C CA 2669479 A CA2669479 A CA 2669479A CA 2669479 A CA2669479 A CA 2669479A CA 2669479 C CA2669479 C CA 2669479C
- Authority
- CA
- Canada
- Prior art keywords
- data
- template
- presentation
- file
- data source
- Prior art date
- Legal status (The legal status 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 status listed.)
- Expired - Fee Related
Links
- 238000012545 processing Methods 0.000 claims abstract description 129
- 238000000034 method Methods 0.000 claims abstract description 34
- 230000008859 change Effects 0.000 claims description 16
- 238000003780 insertion Methods 0.000 claims description 12
- 230000037431 insertion Effects 0.000 claims description 12
- 230000004044 response Effects 0.000 claims description 12
- 238000001514 detection method Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 abstract description 10
- 238000010586 diagram Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 3
- 238000001914 filtration Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 241000283986 Lepus Species 0.000 description 1
- 230000002730 additional effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000013078 crystal Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000000063 preceeding effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 230000000284 resting effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/174—Form filling; Merging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
Abstract
In one aspect a presentation generator may access a data source structured into data fields. The generator may process a template file with the data source based on one or more tags associated with the template file and one or more processing instructions embedded in the template file, the one or more processing instructions indicating how the data source is processed to build a presentation file.
Description
GENERATING END-USER PRESENTATIONS FROM STRUCTURED DATA
BACKGROUND OF THE INVENTION
This invention relates to a software system, specifically to a system that automatically generates a presentation, document, or other formatted product in an application format for an end user based on a template and structured data.
. Users of computer systems desire to see and share data with familiar uses-friendly computer products, such as word processors, spreadsheets, databases and presentation software. Computer systems themselves often do not have the abili#y to produce products in such user-friendly formats. In the few systems that allow data to be exported to such user-friendly products, users have littie control in customizing the results since formatting is usually hard coded within the system. Such hard coded solutions also result in support of only a single type of data structure.
Thus, when the end user wishes to see and share data in a user-friendly product based on another of the system's data files, this new use must also be hard coded.
What is needed is a way to allow a computer end user to generate a slide show, document, spreadsheet or other presentation using a word processor or other user-friendly product, based (in part) upon structured data from a software system.
Such an innovation should allow the end user to specify the layout of the presentation as well as how to organize the data records and which data records to include.
TRADITIONAL MAIL MERGE FUNCTIONS AND THEIR LIMITATIONS
Microsoft WORD currently provides a mail merge helper feature. Variations of the mail merge feature are also available in other word processing software systems.
The mail merge is designed to assist a user to create form letter documents and associated envelopes or mailing labels. As WORD's help file explains, mail merge feature guides the user through organizing the address data, merging it into a generic document, and printing the resulting personalized documents.
To allow for a comparison between current systems and the novel features offered by the present invention, the WORD mail merge helper feature will now be discussed at length, with the example of using the feature to generate form letters to a set of customers. As one in the art is aware, Microsoft Corporation produces the ubiquitous OFFICE suite of software products, which includes WORD for word processing, POWERPOINT for slide shows and other presentations, and EXCEL for spreadsheets. While the present document specifically discusses Microsoft products, the present invention may also be compared to, and implemented in connection with other computer-based applications available to end users. For example, end users may also enjoy the present invention (in various embodiments) with WordPerfect's office suite that includes the WORDPERFECT word processor, QUATTRO PRO
spreadsheet, PRESENTATIONS slide show creator and the PARADOX database product. Or end users may choose to use software from other vendors, such as CRYSTAL REPORTS or the STAROFFICE suite from Sun Microsystems, to name but a few. Some embodiments of the present invention may support using web portlets (i.e., modules that can be plugged into a web portal for real-time data searching capabilities), exporting to web. services in XML or other format, or leveraging the ODBC protocol for access to other types of data sources.
Figure 1 shows the dialog box 10 for WORD's mail merge helper feature. The user may use the "Get Data" button 12 to associate a data file with the mail merge.
Figure 2 shows the EXCEL spreadsheet data file 20 that is being used as the data file in this example. Here, each column is given a field name and each row represents one data record. Thus, the second row contains the data for Steven Lieske and the third row contains the information for Mike Bennett. The mail merge feature can also use a database file, a text file or a table in a WORD document as the data file.
Once the data file has been set up, the user creates or edits the main document 14, which is the template for the merge. Figure 3 shows a sample document created in WORD. The document includes generic text that will be included in each form letter, such as the sentence: "We are updating our computer records." The document also contains a series of merge tags 32 and 34 that are used to personalize each form letter. The merge tags may be a placeholder to a data field or may be a simple processing instruction. Figure 4 shows WORD's "Insert Merge Field" button 40, which allows the user to see a[i of the field names from the spreadsheet 20 and to choose which field names should be included in the template.
BACKGROUND OF THE INVENTION
This invention relates to a software system, specifically to a system that automatically generates a presentation, document, or other formatted product in an application format for an end user based on a template and structured data.
. Users of computer systems desire to see and share data with familiar uses-friendly computer products, such as word processors, spreadsheets, databases and presentation software. Computer systems themselves often do not have the abili#y to produce products in such user-friendly formats. In the few systems that allow data to be exported to such user-friendly products, users have littie control in customizing the results since formatting is usually hard coded within the system. Such hard coded solutions also result in support of only a single type of data structure.
Thus, when the end user wishes to see and share data in a user-friendly product based on another of the system's data files, this new use must also be hard coded.
What is needed is a way to allow a computer end user to generate a slide show, document, spreadsheet or other presentation using a word processor or other user-friendly product, based (in part) upon structured data from a software system.
Such an innovation should allow the end user to specify the layout of the presentation as well as how to organize the data records and which data records to include.
TRADITIONAL MAIL MERGE FUNCTIONS AND THEIR LIMITATIONS
Microsoft WORD currently provides a mail merge helper feature. Variations of the mail merge feature are also available in other word processing software systems.
The mail merge is designed to assist a user to create form letter documents and associated envelopes or mailing labels. As WORD's help file explains, mail merge feature guides the user through organizing the address data, merging it into a generic document, and printing the resulting personalized documents.
To allow for a comparison between current systems and the novel features offered by the present invention, the WORD mail merge helper feature will now be discussed at length, with the example of using the feature to generate form letters to a set of customers. As one in the art is aware, Microsoft Corporation produces the ubiquitous OFFICE suite of software products, which includes WORD for word processing, POWERPOINT for slide shows and other presentations, and EXCEL for spreadsheets. While the present document specifically discusses Microsoft products, the present invention may also be compared to, and implemented in connection with other computer-based applications available to end users. For example, end users may also enjoy the present invention (in various embodiments) with WordPerfect's office suite that includes the WORDPERFECT word processor, QUATTRO PRO
spreadsheet, PRESENTATIONS slide show creator and the PARADOX database product. Or end users may choose to use software from other vendors, such as CRYSTAL REPORTS or the STAROFFICE suite from Sun Microsystems, to name but a few. Some embodiments of the present invention may support using web portlets (i.e., modules that can be plugged into a web portal for real-time data searching capabilities), exporting to web. services in XML or other format, or leveraging the ODBC protocol for access to other types of data sources.
Figure 1 shows the dialog box 10 for WORD's mail merge helper feature. The user may use the "Get Data" button 12 to associate a data file with the mail merge.
Figure 2 shows the EXCEL spreadsheet data file 20 that is being used as the data file in this example. Here, each column is given a field name and each row represents one data record. Thus, the second row contains the data for Steven Lieske and the third row contains the information for Mike Bennett. The mail merge feature can also use a database file, a text file or a table in a WORD document as the data file.
Once the data file has been set up, the user creates or edits the main document 14, which is the template for the merge. Figure 3 shows a sample document created in WORD. The document includes generic text that will be included in each form letter, such as the sentence: "We are updating our computer records." The document also contains a series of merge tags 32 and 34 that are used to personalize each form letter. The merge tags may be a placeholder to a data field or may be a simple processing instruction. Figure 4 shows WORD's "Insert Merge Field" button 40, which allows the user to see a[i of the field names from the spreadsheet 20 and to choose which field names should be included in the template.
In the example shown in figure 3, the fields 32 called NAME, ADDRESS, CITY, STATE and ZIP are all included in the template.
The mail merger helper feature also supports nine merge instructions that are accessed by the "Insert Word Field" button 50 shown in Figure 5. The ASK and FILL-IN merge instructions can be inserted in a template to require the user to type in information from the keyboard as the merge is generating the form ietters.
With these two instructions, the user must be an active participant during the merge process since his or her keyboard input is required for each letter.
The IF-THEN-ELSE merge instruction provides conditional processing for text in the form letters. The template shown in Figure 3 includes one of these IF-THEN-ELSE merge instructions 34. This instruction 34 tests the PHONE field for the record being used for each form letter. If the PHONE field is not blank (i.e., <>
then the text "Our records indicate your phone number is" is added to the form letter followed by the value of the present record's PHONE field. If, however, the PHONE field is blank, then the 'else' portion of the merge instruction causes the text "We do not have your phone number on file"to be added to the form letter.
The MERGE-RECORD-# merge instrucfiion simply includes in the resulting form letter the number of the record being processed. For example, if the merge feature is using the fifth record's information to create the fifth form letter, then the number "5" is inserted where the MERGE-RECORD-# instruction is placed in the template.
In similar fashion, the MERGE-SEQUENCE-# merge instruction 'inserts in the form letter the total number of records being processed. For example, if the user decides to generate 10 form letters by processing records one through ten, then the number "10" is inserted where the MERGE-SEQUENCE-# instruction is placed in the template.
The NEXT-RECORD merge instruction causes the mail merge feature to proceed to the next record in the data file 20. This may allow a form letter to be a list reporting the data from several records. For example, the merged form letter may be set up to print the NAME and PHONE on a single page. The NEXT-RECORD-IF and SKIP-RECORD-.[F merge instructions are similarly used to proceed to the next record on a single page, but these instructions provide a condition that must be met for either the next record to be processed or the next record to be skipped. The conditions allowed by these two merge instructions are similar to the IF portion of the ELSE merge instruction discussed above.
The final merge instruction supported by WORD's mail merge helper is the SET-BOOKMARK merge instruction, which inserts the text associated to a specified bookmark.
Once the template has been created with the desired merge fields and word fields, the user may set up a query 16 to instruct which records should be included in the merge and how they should be sorted. Figure 6 shows the FILTER RECORDS
60 dialog box that allows the user to select the criteria for inclusion in the form letters.
Here, only records that have the STATE field set to MN will be used. Figure 7 shows the SORT RECORDS 70 dialog box that allows the user to select the sorting rules for the form letters. Here, the records will be sorted by the NAME field.
Once the template is finished and the data file is selected, and once any filters or sorting requirements are set up, the user may generate the merged form letters 18.
As the data file from Figure 2 only includes two records with the STATE equal to MN, only two form letters are generated. Figure 8, shows the results for the second form letter 80. Unfortunately, the chosen data file, the filters and the sorting requirements are all details that the user must set up each time the mail merge is processed. The data file name, the filters and the query itself may not be embedded within the template. What is needed is a way to embed such information into the template.
Furthermore, what is needed is a wayto allow the template to requery the data or to query a second data source as part of merging the data.
The mail merge helper uses data from a text file or WORD table in much the same way as data from an Excel spreadsheet is used. These types of data files present information as a series sequential data records that are then processed in turn. The template must be set up to generate a single ietter, label or address for each processed record. What is needed is way to present highly structured data in an advanced format.
The mail merge helper includes two aspects that may seem to offer such functionalitjr, These are the catalog merge type and the ACCESS database data source. But even these are quite limited, as is shown in Figures 9 through 14.
A computer user may use ACCESS or similar relational database to store data, such as the data for company employees, for example. As one skilled in the art knows, such a relationa( database is a collection of data items organized as a set of formally-described tables from which data can be accessed or reassembled in many different ways without having to reorganize the database tables.
Figure 9 shows two tables set up in ACCESS for storing information about employees. The design for the Employees table 90 states that it stores the empioyee's ID, name, start date and job titfe. The design of the Contactinfo tabie 92 states that it stores the address, city, state, ZIP and phone for a contact.
Employees may have several contacts. For example, an employee may have a home address, a work address, and perhaps a sabbatical address. Figure 10 displays the Ernpfoyees table 100 and Contactlnfo table 102 with data for two employees. Per the relationship between the tables shown in Figure 9, the ID field of the Employees table 100 is used as the foreign key (i.e., EmployeeFK) for the Contactinfo table 102. Thus, the Steven Lieske employee has three Contactinfo records (i.e., 1, 2 and 3) and the Mike Bennett employee has two Contactlnfo records (i.e., 4 and 5).
Figure 11 illustrates a report 112 created in ACCESS that prints out the full information for both of the employees. Here one sees the employee information for each employee as well as al1 associated contact information. Notice that while Steven Lieske has three contact addresses, his name only appears once rather than three times. In other words, the reports displays the data for each employee in a non- repetitive, easy-to-understand format. With such a report, even if Mike Bennett had 100 contact addresses set up in the database, they would all be included in the report without any addifional programming effort.
The mail merger helper feature also supports nine merge instructions that are accessed by the "Insert Word Field" button 50 shown in Figure 5. The ASK and FILL-IN merge instructions can be inserted in a template to require the user to type in information from the keyboard as the merge is generating the form ietters.
With these two instructions, the user must be an active participant during the merge process since his or her keyboard input is required for each letter.
The IF-THEN-ELSE merge instruction provides conditional processing for text in the form letters. The template shown in Figure 3 includes one of these IF-THEN-ELSE merge instructions 34. This instruction 34 tests the PHONE field for the record being used for each form letter. If the PHONE field is not blank (i.e., <>
then the text "Our records indicate your phone number is" is added to the form letter followed by the value of the present record's PHONE field. If, however, the PHONE field is blank, then the 'else' portion of the merge instruction causes the text "We do not have your phone number on file"to be added to the form letter.
The MERGE-RECORD-# merge instrucfiion simply includes in the resulting form letter the number of the record being processed. For example, if the merge feature is using the fifth record's information to create the fifth form letter, then the number "5" is inserted where the MERGE-RECORD-# instruction is placed in the template.
In similar fashion, the MERGE-SEQUENCE-# merge instruction 'inserts in the form letter the total number of records being processed. For example, if the user decides to generate 10 form letters by processing records one through ten, then the number "10" is inserted where the MERGE-SEQUENCE-# instruction is placed in the template.
The NEXT-RECORD merge instruction causes the mail merge feature to proceed to the next record in the data file 20. This may allow a form letter to be a list reporting the data from several records. For example, the merged form letter may be set up to print the NAME and PHONE on a single page. The NEXT-RECORD-IF and SKIP-RECORD-.[F merge instructions are similarly used to proceed to the next record on a single page, but these instructions provide a condition that must be met for either the next record to be processed or the next record to be skipped. The conditions allowed by these two merge instructions are similar to the IF portion of the ELSE merge instruction discussed above.
The final merge instruction supported by WORD's mail merge helper is the SET-BOOKMARK merge instruction, which inserts the text associated to a specified bookmark.
Once the template has been created with the desired merge fields and word fields, the user may set up a query 16 to instruct which records should be included in the merge and how they should be sorted. Figure 6 shows the FILTER RECORDS
60 dialog box that allows the user to select the criteria for inclusion in the form letters.
Here, only records that have the STATE field set to MN will be used. Figure 7 shows the SORT RECORDS 70 dialog box that allows the user to select the sorting rules for the form letters. Here, the records will be sorted by the NAME field.
Once the template is finished and the data file is selected, and once any filters or sorting requirements are set up, the user may generate the merged form letters 18.
As the data file from Figure 2 only includes two records with the STATE equal to MN, only two form letters are generated. Figure 8, shows the results for the second form letter 80. Unfortunately, the chosen data file, the filters and the sorting requirements are all details that the user must set up each time the mail merge is processed. The data file name, the filters and the query itself may not be embedded within the template. What is needed is a way to embed such information into the template.
Furthermore, what is needed is a wayto allow the template to requery the data or to query a second data source as part of merging the data.
The mail merge helper uses data from a text file or WORD table in much the same way as data from an Excel spreadsheet is used. These types of data files present information as a series sequential data records that are then processed in turn. The template must be set up to generate a single ietter, label or address for each processed record. What is needed is way to present highly structured data in an advanced format.
The mail merge helper includes two aspects that may seem to offer such functionalitjr, These are the catalog merge type and the ACCESS database data source. But even these are quite limited, as is shown in Figures 9 through 14.
A computer user may use ACCESS or similar relational database to store data, such as the data for company employees, for example. As one skilled in the art knows, such a relationa( database is a collection of data items organized as a set of formally-described tables from which data can be accessed or reassembled in many different ways without having to reorganize the database tables.
Figure 9 shows two tables set up in ACCESS for storing information about employees. The design for the Employees table 90 states that it stores the empioyee's ID, name, start date and job titfe. The design of the Contactinfo tabie 92 states that it stores the address, city, state, ZIP and phone for a contact.
Employees may have several contacts. For example, an employee may have a home address, a work address, and perhaps a sabbatical address. Figure 10 displays the Ernpfoyees table 100 and Contactlnfo table 102 with data for two employees. Per the relationship between the tables shown in Figure 9, the ID field of the Employees table 100 is used as the foreign key (i.e., EmployeeFK) for the Contactinfo table 102. Thus, the Steven Lieske employee has three Contactinfo records (i.e., 1, 2 and 3) and the Mike Bennett employee has two Contactlnfo records (i.e., 4 and 5).
Figure 11 illustrates a report 112 created in ACCESS that prints out the full information for both of the employees. Here one sees the employee information for each employee as well as al1 associated contact information. Notice that while Steven Lieske has three contact addresses, his name only appears once rather than three times. In other words, the reports displays the data for each employee in a non- repetitive, easy-to-understand format. With such a report, even if Mike Bennett had 100 contact addresses set up in the database, they would all be included in the report without any addifional programming effort.
The mail merge helper in WORD supports ACCESS database data.
However, it does not support even as much functiona(ity as the report writer does in ACCESS. As a first step, Figure 12 shows a SQL query 120 and query result 122 to gather all of the information that is found in the report shown in Figure 11.
Figure 1.3 shows the mail merge heiper 132 again, but this time the data source selected is the ACCESS database. As the mail merge helper does not support databases very well, one must choose a query defined in the database or else set up such a query on the fly. Here, the Listinfo query 130 from Figure 12 is selected. Once again, only one query is allowed and it must be set up by the end user just before performing the merge. The query may not be embedded wi#hin and saved as part of the template file.
The mail merger helper 132 also shows that the merge type is "Catalog" for this example rather than form letter. This type of merge is used when information from several records is gathered together rather than each record producing a separate document. Figure 14 shows the template 140 that may be set up and then the resulting merged document 142 that is generated by merging the results of the ACCESS query 120 with the catalog template 140. Comparing these merged results 142 with the report shown in Figure 11, one can see the limitations of the mail merge helper. Rather than grouping the data in a logical format, the mail merge creates repetition with each row including the redundant employee name and job title.
The functionality shown in Figures 1 through 14 illustrate some of the shortcomings of the present art. While the WORD mail merge helper does well in producing standard form letters, envelopes and mailing labels, it does not offer various advanced features that are also lacking elsewhere in the art. Mail merge only allows for the creation of WORD documents. What is needed is a way to merge data into templates created with other desktop applications to produce other types of documents.
Mail merge oniy supports spreadsheets, databases, text files and WORD
tables as the data source. Unfortunately, most business systems do not store their data in one of these formats. What is needed is a system that accepts structured data in other formats, such as XML data files.
However, it does not support even as much functiona(ity as the report writer does in ACCESS. As a first step, Figure 12 shows a SQL query 120 and query result 122 to gather all of the information that is found in the report shown in Figure 11.
Figure 1.3 shows the mail merge heiper 132 again, but this time the data source selected is the ACCESS database. As the mail merge helper does not support databases very well, one must choose a query defined in the database or else set up such a query on the fly. Here, the Listinfo query 130 from Figure 12 is selected. Once again, only one query is allowed and it must be set up by the end user just before performing the merge. The query may not be embedded wi#hin and saved as part of the template file.
The mail merger helper 132 also shows that the merge type is "Catalog" for this example rather than form letter. This type of merge is used when information from several records is gathered together rather than each record producing a separate document. Figure 14 shows the template 140 that may be set up and then the resulting merged document 142 that is generated by merging the results of the ACCESS query 120 with the catalog template 140. Comparing these merged results 142 with the report shown in Figure 11, one can see the limitations of the mail merge helper. Rather than grouping the data in a logical format, the mail merge creates repetition with each row including the redundant employee name and job title.
The functionality shown in Figures 1 through 14 illustrate some of the shortcomings of the present art. While the WORD mail merge helper does well in producing standard form letters, envelopes and mailing labels, it does not offer various advanced features that are also lacking elsewhere in the art. Mail merge only allows for the creation of WORD documents. What is needed is a way to merge data into templates created with other desktop applications to produce other types of documents.
Mail merge oniy supports spreadsheets, databases, text files and WORD
tables as the data source. Unfortunately, most business systems do not store their data in one of these formats. What is needed is a system that accepts structured data in other formats, such as XML data files.
Mail merge may use a query to choose the records to apply to the merge as well as its ordering. What is needed is a system that can include multiple queries and that can altemate between reporting data on a record by record basis and reporting data aggregated in a table (or with bullets or a list).
BRIEF SUMMARY OF THE INVENTION
In accordance with one aspect of the invention there is provided a system for generating a presentation file. The system includes provisions for accessing a data source includes a plurality of data records structured into a plurality of data fields, and provisions for providing an end user of a computer with a listing of a plurality of tags. The tag is associated to one of the data fields in the data source. The system also includes provisions for choosing a template file, where the template file includes at least one of the plura(ity of tags, and at least one processing instruction for indicating how the data source is processed to build the presentation file. The system further includes provisions for processing the template file with the data source based on the at least one of the plurality of tags and the at least one processing instruction, for building the presentation file for reporting information from the data source.
At least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template.
At least one of the processing instructions may be a second query embedded in the template file.
The first query may be for a first data source and the second query is for a second data source.
The at least one processing instruction queries the data source for presenting more than one data record on a single page in the presentation file.
The provisions for processing the template file with the data source based on the at least one processing instruction may include provisions for grouping a first template page and a second template page from the template file, provisions for determining a break-on condition for one of the plurality of data fields, where the break-on condition may be satisfied when data associated with the data field changes, provisions for creating pages in the presentation file based on the first and second template pages, and provisions for repeating the step of creating pages based on the first and second template pages when the break-on condition is met.
The provisions for processing the template file with the data source based on the at least one processing instruction may further include provisions for querying the data source for presenting more than one data record on a single page in the presentation file.
The at least one processing instruction may be stored in a notes region of the template file.
The at least one processing instruction may be stored in a comments region of the template file.
In accordance with another aspect of the invention there is provided a system for generating a presentation. The system includes provisions for accessing a data source includes a plurality of data records structured into a plurality of data fields, and provisions for accessing a template file includes at least one tag and at least one processing instruction. The tag is associated to one of the data fields in the data source. The system also includes provisions for processing the template file and the data source based on the at least one tag and the at least one processing instruction, for building the presentation file for reporting information from the data source. At least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template.
The query may be embedded in the template file as a smart tag for allowing an end user to re-query the data source from the presentation file to update the presentation file.
-7a-In accordance with a further aspect of the invention there is provided a method for generating a plurality of presentation pages in a presentation file, the method comprising:
(a) utilizing a desktop application to generate a presentation template in a file format related to a document produced by the desktop application;
(b) accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged locations;
(d) embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field; and (e) processing the first template group and the second template group with the data source to generate a presentation- output file comprising an ordered set of presentation output pages structured and ordered -based on the first and second template groups, including:
(i) processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
--7b-(ii) processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page; and (iii) each time the first break-on condition is met, repeating processing step (e)(ii) to generate an additional presentation page using the plurality of embedded processing instructions of the second template page.
The second presentation output page may include data and formatting structured and presented different from the first presentation output 'page.
The embedded processing instructions of at least one of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The second data field of the plurality of data fields may be different from the first data field.
The embedded processing instructions of each of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The method may further involve repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file.in response to detection of a change in the second data field through execution of the order-based processing instruction.
The method may further involve repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
-7c-The method may further involve embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field. The second break-on condition may be satisfied in response to a change in the data associated with the third data field. In another variation of the method, each time the second break-on condition is met, the method may include repeating processing step (e) to generate an additional ordered set of presentation output pages structured and ordered based on the first and second template groups.
In accordance with another aspect there is provided a computer readable medium encoded with codes for causing a computing device to execute any one of the embodiments of the method set out above.
In accordance with a further aspect of the invention there is provided a system for generating a pluraliiy of presentation pages in a presentation file, the system comprising:
(a) means for utilizing a desktop application to generate a presentation template 'in a file format related to a document produced by the desktop application;
(b) means for accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) means for selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged location,s;
-7d-(d) means for embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field; and (e) means for processing the first template group and the second template group with the data source to generate a presentation output file comprising an ordered set of presentation output pages structured and ordered based on the first and second template groups, including:
(i) means for processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
(ii) means for processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page;
and (iii) means for generating an additional presentation page using the plurality of embedded processing instructions of the second template page each time the break-on condition is met .
The second presentation output page may include data and formatting structured and presented different from the first presentation output page.
The embedded processing instructions of at least one of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The second data field of the plurality of data fields may be different from the first data field.
-7e-The embedded processing instructions of each of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The second data field of the plurality of data fields may be different from the first data field.
The system may further include means for generating an additional ordered set of presentation output pages for insertion into the presentation output file in response to detection of a change in the second data field through execution of the order-based processing instruction.
The system may further include means for generating an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
The system may further include means for embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field, wherein the second break-on condition is satisfied in response to a change in the data associated with the third data field.
The system may further include means for generating an additional ordered set of presentation output pages structured and ordered based on the first and second template groups each time the second break-on condition is met.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 shows the prior art system of the mail merge helper from WORD.
-7f-Figure 2 shows the. prior art system of data set up in EXCEL.
Figure 3 shows the prior art system template in WORD.
Figure 4 shows the prior art system's Insert Merge Field button.
Figure 5 shows the prior art system's Insert Word Field buiton.
Figures 6 and 7 show the prior art system Query Options feature of the mail merge helper.
Figure 8 shows the prior art system's merged letter from a template and data_ Figure 9 shows the prior art system as two related tables in ACCESS.
Figure 10 shows the prior art system as data in the two ACCESS tables.
Figure 11 shows the prior art system as an ACCESS report.
Figure 12 shows the prior-art system as a SQL query and its results in ACCESS.
Figure 13 shows the prior art system mail merge helper accessing the ACCESS database.
Figure 14 shows the prior art system's catalog-type template and resuking merged document.
Figure 15 shows a flowchart of one embodiment of the invention generating a presentation.
Figure 16 shows a diagram of one embodiment of the invention interfacing with PowerPoint and Word to generate a presentation.
Figures 17, 18 and 19 are dialog boxes available in one embodiment of the invention.
Figure 20 is a block diagram showing a system and a computer program for one embodiment of the invention.
BRIEF SUMMARY OF THE INVENTION
In accordance with one aspect of the invention there is provided a system for generating a presentation file. The system includes provisions for accessing a data source includes a plurality of data records structured into a plurality of data fields, and provisions for providing an end user of a computer with a listing of a plurality of tags. The tag is associated to one of the data fields in the data source. The system also includes provisions for choosing a template file, where the template file includes at least one of the plura(ity of tags, and at least one processing instruction for indicating how the data source is processed to build the presentation file. The system further includes provisions for processing the template file with the data source based on the at least one of the plurality of tags and the at least one processing instruction, for building the presentation file for reporting information from the data source.
At least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template.
At least one of the processing instructions may be a second query embedded in the template file.
The first query may be for a first data source and the second query is for a second data source.
The at least one processing instruction queries the data source for presenting more than one data record on a single page in the presentation file.
The provisions for processing the template file with the data source based on the at least one processing instruction may include provisions for grouping a first template page and a second template page from the template file, provisions for determining a break-on condition for one of the plurality of data fields, where the break-on condition may be satisfied when data associated with the data field changes, provisions for creating pages in the presentation file based on the first and second template pages, and provisions for repeating the step of creating pages based on the first and second template pages when the break-on condition is met.
The provisions for processing the template file with the data source based on the at least one processing instruction may further include provisions for querying the data source for presenting more than one data record on a single page in the presentation file.
The at least one processing instruction may be stored in a notes region of the template file.
The at least one processing instruction may be stored in a comments region of the template file.
In accordance with another aspect of the invention there is provided a system for generating a presentation. The system includes provisions for accessing a data source includes a plurality of data records structured into a plurality of data fields, and provisions for accessing a template file includes at least one tag and at least one processing instruction. The tag is associated to one of the data fields in the data source. The system also includes provisions for processing the template file and the data source based on the at least one tag and the at least one processing instruction, for building the presentation file for reporting information from the data source. At least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template.
The query may be embedded in the template file as a smart tag for allowing an end user to re-query the data source from the presentation file to update the presentation file.
-7a-In accordance with a further aspect of the invention there is provided a method for generating a plurality of presentation pages in a presentation file, the method comprising:
(a) utilizing a desktop application to generate a presentation template in a file format related to a document produced by the desktop application;
(b) accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged locations;
(d) embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field; and (e) processing the first template group and the second template group with the data source to generate a presentation- output file comprising an ordered set of presentation output pages structured and ordered -based on the first and second template groups, including:
(i) processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
--7b-(ii) processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page; and (iii) each time the first break-on condition is met, repeating processing step (e)(ii) to generate an additional presentation page using the plurality of embedded processing instructions of the second template page.
The second presentation output page may include data and formatting structured and presented different from the first presentation output 'page.
The embedded processing instructions of at least one of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The second data field of the plurality of data fields may be different from the first data field.
The embedded processing instructions of each of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The method may further involve repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file.in response to detection of a change in the second data field through execution of the order-based processing instruction.
The method may further involve repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
-7c-The method may further involve embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field. The second break-on condition may be satisfied in response to a change in the data associated with the third data field. In another variation of the method, each time the second break-on condition is met, the method may include repeating processing step (e) to generate an additional ordered set of presentation output pages structured and ordered based on the first and second template groups.
In accordance with another aspect there is provided a computer readable medium encoded with codes for causing a computing device to execute any one of the embodiments of the method set out above.
In accordance with a further aspect of the invention there is provided a system for generating a pluraliiy of presentation pages in a presentation file, the system comprising:
(a) means for utilizing a desktop application to generate a presentation template 'in a file format related to a document produced by the desktop application;
(b) means for accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) means for selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged location,s;
-7d-(d) means for embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field; and (e) means for processing the first template group and the second template group with the data source to generate a presentation output file comprising an ordered set of presentation output pages structured and ordered based on the first and second template groups, including:
(i) means for processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
(ii) means for processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page;
and (iii) means for generating an additional presentation page using the plurality of embedded processing instructions of the second template page each time the break-on condition is met .
The second presentation output page may include data and formatting structured and presented different from the first presentation output page.
The embedded processing instructions of at least one of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The second data field of the plurality of data fields may be different from the first data field.
-7e-The embedded processing instructions of each of the first and second template pages may further include an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
The second data field of the plurality of data fields may be different from the first data field.
The system may further include means for generating an additional ordered set of presentation output pages for insertion into the presentation output file in response to detection of a change in the second data field through execution of the order-based processing instruction.
The system may further include means for generating an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
The system may further include means for embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field, wherein the second break-on condition is satisfied in response to a change in the data associated with the third data field.
The system may further include means for generating an additional ordered set of presentation output pages structured and ordered based on the first and second template groups each time the second break-on condition is met.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 shows the prior art system of the mail merge helper from WORD.
-7f-Figure 2 shows the. prior art system of data set up in EXCEL.
Figure 3 shows the prior art system template in WORD.
Figure 4 shows the prior art system's Insert Merge Field button.
Figure 5 shows the prior art system's Insert Word Field buiton.
Figures 6 and 7 show the prior art system Query Options feature of the mail merge helper.
Figure 8 shows the prior art system's merged letter from a template and data_ Figure 9 shows the prior art system as two related tables in ACCESS.
Figure 10 shows the prior art system as data in the two ACCESS tables.
Figure 11 shows the prior art system as an ACCESS report.
Figure 12 shows the prior-art system as a SQL query and its results in ACCESS.
Figure 13 shows the prior art system mail merge helper accessing the ACCESS database.
Figure 14 shows the prior art system's catalog-type template and resuking merged document.
Figure 15 shows a flowchart of one embodiment of the invention generating a presentation.
Figure 16 shows a diagram of one embodiment of the invention interfacing with PowerPoint and Word to generate a presentation.
Figures 17, 18 and 19 are dialog boxes available in one embodiment of the invention.
Figure 20 is a block diagram showing a system and a computer program for one embodiment of the invention.
Figures 21 and 22 are matrices listing sample data.
Figures 23A, 23B and 23C show three pages in a template that can be processed by one embodiment of the invention.
Figures 24 to 28 show five pages from a presentation generated based on the template of figures 23A, 23B and 23C and the data of figures 21 and 22.
Figure 29 shows one page from a presentation template that may be processed by the present invention.
Figure 30 through 36 are dialog boxes available in another embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
The present invention enabies an end user to use a template to create a presentation file based on one or more data sources. The template includes one or more tags that are mapped to fields in the data sources as well as one or more processing instructions that control how the data sources are queried and how the regions of the template are positioned within the presentation. One skilled in the art may create various software systems to accomplish the methodology of the present invention. One of the many various software systems is shown starting with figure 15.
In such an embodiment, a system parses one or more data files 150 or other data sources to determine the field structure of the data. A user may choose to create a new template, revise an already existing template, or rely entirely on an already .
existing template 152 & 154. If the user chooses to create a new template 154, the user accesses a user-friendly software application to set up the template. In one embodiment, the user may choose from any of a number of user-friendly software applications, such as those developed by Microsoft (including the WORD word-processor, the EXCEL spreadsheet program and the POWERPOINT slide presentation program) or other vendors. Other embodiments of the invention may support other user-friendly applications.
Figures 23A, 23B and 23C show three pages in a template that can be processed by one embodiment of the invention.
Figures 24 to 28 show five pages from a presentation generated based on the template of figures 23A, 23B and 23C and the data of figures 21 and 22.
Figure 29 shows one page from a presentation template that may be processed by the present invention.
Figure 30 through 36 are dialog boxes available in another embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
The present invention enabies an end user to use a template to create a presentation file based on one or more data sources. The template includes one or more tags that are mapped to fields in the data sources as well as one or more processing instructions that control how the data sources are queried and how the regions of the template are positioned within the presentation. One skilled in the art may create various software systems to accomplish the methodology of the present invention. One of the many various software systems is shown starting with figure 15.
In such an embodiment, a system parses one or more data files 150 or other data sources to determine the field structure of the data. A user may choose to create a new template, revise an already existing template, or rely entirely on an already .
existing template 152 & 154. If the user chooses to create a new template 154, the user accesses a user-friendly software application to set up the template. In one embodiment, the user may choose from any of a number of user-friendly software applications, such as those developed by Microsoft (including the WORD word-processor, the EXCEL spreadsheet program and the POWERPOINT slide presentation program) or other vendors. Other embodiments of the invention may support other user-friendly applications.
' = , To set up the template, the user may insert processing instructions, such as special tags into the location of the template where certain data fields should be inserted for the resulting presentation. In one embodiment, the user may insert such tags using the drag-and-drop technique with a listing of available tags. In another embodiment, the user may type the tags manually using a supported notation. In addition to arranging field tags in the template, the processing instructions may be queries, sorting requirements, etc. The processing instructions may also provide the system with information on how a series of pages or sections of the template are grouped or how they relate to the data. In one embodiment, such processing instructions are entered by the user in a specific location of the template, such as a notes section or a comments section.
Referring back to figure 15, once the template set up, the user may initiate an instruction for the system to generate the presentation. To do this, the system may retrieve the template 156 and parse the processing/merge instructions 158.
Based on these processing instructions, the system may create a presentation 159 of one or more pages by inserting the desired data fields in the tagged locations of the template. The term "pages" is not fimited to the traditional meaning of a page, but also means "slide", "chapter", "section" or some other type of dividing unit within the presentation.
Figure 16 shows a diagram of one embodiment of the invention interfacing with PowerPoint and Word to generate a presentation. As shown in the figure, data from a computer system may be accessed as an XML file 163. The attribute names from the XML file's attribute-value pairs can be used to create and modify PowerPoint templates 164.1 and Word templates 164.2. In embodiments accepting such XML
data files, an XSD or other definition file that defines the data structure of the XML file may be accessed. A generator application 160 may be written in VB.NET or other computer language. The generator application 160 may be kicked off by a Java application 161 to either create/modify templates or to generate the presentations. A
user may interact with the GUI interface to the generator application 160 to indicate which template and which XML file to process. The generator 160 may then spawn automation objects 165. For example, a PowerPoint automation object 165.1 may load the appropriate PowerPoint template 164.1 and process the instructions to generate a PowerPoint slide show file 166.1 made up of a series of slides.
GENERATING A PRESENTATION
Figure 17 shows the first tabbed dialog-box for one embodiment of the user interface of the present invention. As shown in figure 17, the data source (i.e., "plan") from which the presentation (i.e., "briefing") is to be generated may be displayed in the 'Select a Plan File' area 172. On clicking the 'Browse' button next to this field, a File Chooser window may open to allow the user to browse through the file directory and specify an XML file that will be used to generate a briefing presentation.
When the user seiects a file and clicks OK, the filename may populate the Plan File field 172. The file that the user selects may be validated before processing.
The template(s) to be used for the briefing presentation generation may be displayed in the "Select a Template' field 174 as a list. The end user may add templates to the list using the 'Browse' button. This button may bring up a File Chooser window to allow the user to browse through the file director and specify a .pot or .dot file. When the user selects a file and clicks OK, the filename may be displayed in the template Iist. The user may delete one or more templates from the list by selecting the template(s) to be deleted, and clicking the 'Delete' button. This may remove the templates from the list, but not delete the template(s) from the hard drive or other secondary storage device. The user may edit a template by highEighting the template to be edited and clicking the `Edit' button.
In one embodiment of the present invention, commonly used settings, such as plan files and templates may be saved to a file, to a collaborative web service, etc. so that such settings may be used among a group of users. This sharing may increase the ease of use of the invention.
Once a plan data source file 172 has been loaded, and a template 174 has been selected, the user may click on the 'Generate' 176 button to start the process of generating the merged briefing presentation. A date filtering window may display at this point, allowing the user to enter the specific date range for which he/she wants to generate the briefing. After entering the date range and clicking'OK', a progress window may display for showing status descriptions to the user. The data source file may be first converted to a hierarchical format and stored in memory. If the conversion to hierarchical format completes successfully, the converted data source may be filtered based on the date filters specified.
The process differs now depending on the type of presentation is being created. If the presentation is a Microsoft WORD or similar document, Microsoft Word (or other program) may start and the briefing may be generated based on the template and the data from the data sources.
If however, the presentation is a Microsoft POWERPOINT slide show or similar presentation slide show document, then a dialog box may display on top of the progress bar, informing the user of the estimated number of slides that will be generated, and the estimated time for compietion. If a successful generation is not guaranteed, the user may be alerted at this point, so that he/she can cancel the process. The number of slides may be estimated based on the processing instructions in the template. The time may be estimated based on the complexity of the template and the plan using a formula, such as: Time in seconds = ((No.
of' rowslTabfes + No. of slides) * Common factor)/60. In one embodiment, the common factor may be set up at perhaps 4.65.
A "no guarantee" message may be displayed on the screen if the number of processes is greater than 3200 or the total number of table rows is greater than 800, for example. The number. of processes may be calculated by adding the number of rows per table with the number of slides in the template. If the user clicks 'Cancel' on the estimate window, the generation may be canceled. If the user clicks 'Ok', Microsoft PowerPoint may open up and the generation may take place.
The second tabbed dialog window of one embodiment is shown in Figure 18.
Here, the Plan File tab may contain a tree-view structure of the selected XML
plan file(s) (data sources). The user may expand and collapse nodes (see 182 and 184) to see the whole plan. When the user clicks on the `Generate' button in the Main tab to generate a briefing, the Plan File tab may be updated to show the tree-view structure of the converfed hierarchical data source. While customizing templates, the user may drag and drop elements from the Plan File tab to the Word template, and a reference to the path of the element may be displayed in the template. For example, if the user drags and drops the `assumptions' field from the `Plan File' tab to a template, the processing instrucfion {plan/assumptions} may be inserted in the tempiate file.
One embodiment of the present invention may allow nicknames to be used rather than actual data field names. For example, rather than showing in this tree-view structure the field "cciNdata", the invention may allow the nickname "Commander's lntent" to be used in place of cciNdata. Or such nicknames may be supported in the slides themselves so that a user may more readily understand the slide template.
As one skilled in the art will recognize, the use of a tree-view or other view of the data may assist the user in building searches across multidimensional structured data, and is not limited to only two-dimensional data results, such as those found in relational databases.
The third tabbed dialog window of one embodiment is shown in Figure 19.
Here, the Plan File Structure tab may contain a tree-view structure of the selected data source. The user may expand and collapse nodes to see the whole plan.
When the user clicks on the `Generate' button in the Main tab to generate a briefing, the Plan File Structure tab may be updated to show the tree-view structure of the converted hierarchical data source file. While customizing templates, the user may drag and drop elements from the Plan File tab to the Word template, and a reference to the_ element will be displayed in the template. For example, if the user drags and drops the `assumptions' field from the `Plan File Structure' tab to a template, the {assumptions} processing instruction tag may be inserted in the template.
In addition to mapping the data structure using a tree-view method where the data fields are shown as a hierarchy, one embodiment may provide a relational mapping method, where data in one entity links or relates to data in another entity. In such an embodiment, the links or relationships may be based on a key or other ID, for example.
Referring back to figure 15, once the template set up, the user may initiate an instruction for the system to generate the presentation. To do this, the system may retrieve the template 156 and parse the processing/merge instructions 158.
Based on these processing instructions, the system may create a presentation 159 of one or more pages by inserting the desired data fields in the tagged locations of the template. The term "pages" is not fimited to the traditional meaning of a page, but also means "slide", "chapter", "section" or some other type of dividing unit within the presentation.
Figure 16 shows a diagram of one embodiment of the invention interfacing with PowerPoint and Word to generate a presentation. As shown in the figure, data from a computer system may be accessed as an XML file 163. The attribute names from the XML file's attribute-value pairs can be used to create and modify PowerPoint templates 164.1 and Word templates 164.2. In embodiments accepting such XML
data files, an XSD or other definition file that defines the data structure of the XML file may be accessed. A generator application 160 may be written in VB.NET or other computer language. The generator application 160 may be kicked off by a Java application 161 to either create/modify templates or to generate the presentations. A
user may interact with the GUI interface to the generator application 160 to indicate which template and which XML file to process. The generator 160 may then spawn automation objects 165. For example, a PowerPoint automation object 165.1 may load the appropriate PowerPoint template 164.1 and process the instructions to generate a PowerPoint slide show file 166.1 made up of a series of slides.
GENERATING A PRESENTATION
Figure 17 shows the first tabbed dialog-box for one embodiment of the user interface of the present invention. As shown in figure 17, the data source (i.e., "plan") from which the presentation (i.e., "briefing") is to be generated may be displayed in the 'Select a Plan File' area 172. On clicking the 'Browse' button next to this field, a File Chooser window may open to allow the user to browse through the file directory and specify an XML file that will be used to generate a briefing presentation.
When the user seiects a file and clicks OK, the filename may populate the Plan File field 172. The file that the user selects may be validated before processing.
The template(s) to be used for the briefing presentation generation may be displayed in the "Select a Template' field 174 as a list. The end user may add templates to the list using the 'Browse' button. This button may bring up a File Chooser window to allow the user to browse through the file director and specify a .pot or .dot file. When the user selects a file and clicks OK, the filename may be displayed in the template Iist. The user may delete one or more templates from the list by selecting the template(s) to be deleted, and clicking the 'Delete' button. This may remove the templates from the list, but not delete the template(s) from the hard drive or other secondary storage device. The user may edit a template by highEighting the template to be edited and clicking the `Edit' button.
In one embodiment of the present invention, commonly used settings, such as plan files and templates may be saved to a file, to a collaborative web service, etc. so that such settings may be used among a group of users. This sharing may increase the ease of use of the invention.
Once a plan data source file 172 has been loaded, and a template 174 has been selected, the user may click on the 'Generate' 176 button to start the process of generating the merged briefing presentation. A date filtering window may display at this point, allowing the user to enter the specific date range for which he/she wants to generate the briefing. After entering the date range and clicking'OK', a progress window may display for showing status descriptions to the user. The data source file may be first converted to a hierarchical format and stored in memory. If the conversion to hierarchical format completes successfully, the converted data source may be filtered based on the date filters specified.
The process differs now depending on the type of presentation is being created. If the presentation is a Microsoft WORD or similar document, Microsoft Word (or other program) may start and the briefing may be generated based on the template and the data from the data sources.
If however, the presentation is a Microsoft POWERPOINT slide show or similar presentation slide show document, then a dialog box may display on top of the progress bar, informing the user of the estimated number of slides that will be generated, and the estimated time for compietion. If a successful generation is not guaranteed, the user may be alerted at this point, so that he/she can cancel the process. The number of slides may be estimated based on the processing instructions in the template. The time may be estimated based on the complexity of the template and the plan using a formula, such as: Time in seconds = ((No.
of' rowslTabfes + No. of slides) * Common factor)/60. In one embodiment, the common factor may be set up at perhaps 4.65.
A "no guarantee" message may be displayed on the screen if the number of processes is greater than 3200 or the total number of table rows is greater than 800, for example. The number. of processes may be calculated by adding the number of rows per table with the number of slides in the template. If the user clicks 'Cancel' on the estimate window, the generation may be canceled. If the user clicks 'Ok', Microsoft PowerPoint may open up and the generation may take place.
The second tabbed dialog window of one embodiment is shown in Figure 18.
Here, the Plan File tab may contain a tree-view structure of the selected XML
plan file(s) (data sources). The user may expand and collapse nodes (see 182 and 184) to see the whole plan. When the user clicks on the `Generate' button in the Main tab to generate a briefing, the Plan File tab may be updated to show the tree-view structure of the converfed hierarchical data source. While customizing templates, the user may drag and drop elements from the Plan File tab to the Word template, and a reference to the path of the element may be displayed in the template. For example, if the user drags and drops the `assumptions' field from the `Plan File' tab to a template, the processing instrucfion {plan/assumptions} may be inserted in the tempiate file.
One embodiment of the present invention may allow nicknames to be used rather than actual data field names. For example, rather than showing in this tree-view structure the field "cciNdata", the invention may allow the nickname "Commander's lntent" to be used in place of cciNdata. Or such nicknames may be supported in the slides themselves so that a user may more readily understand the slide template.
As one skilled in the art will recognize, the use of a tree-view or other view of the data may assist the user in building searches across multidimensional structured data, and is not limited to only two-dimensional data results, such as those found in relational databases.
The third tabbed dialog window of one embodiment is shown in Figure 19.
Here, the Plan File Structure tab may contain a tree-view structure of the selected data source. The user may expand and collapse nodes to see the whole plan.
When the user clicks on the `Generate' button in the Main tab to generate a briefing, the Plan File Structure tab may be updated to show the tree-view structure of the converted hierarchical data source file. While customizing templates, the user may drag and drop elements from the Plan File tab to the Word template, and a reference to the_ element will be displayed in the template. For example, if the user drags and drops the `assumptions' field from the `Plan File Structure' tab to a template, the {assumptions} processing instruction tag may be inserted in the template.
In addition to mapping the data structure using a tree-view method where the data fields are shown as a hierarchy, one embodiment may provide a relational mapping method, where data in one entity links or relates to data in another entity. In such an embodiment, the links or relationships may be based on a key or other ID, for example.
Figure 20 shows a block diagram of one embodiment of a computer system using a computer program to generate presentations. In figure 20, a PC or other general purpose computing device (such as a PDA or laptop) 200 has stored on it one or more computer programs 201 that provide the functionaiity of the present invention in one of its embodiments. Data to be used to build the presentations may be extracted from one or more databases 202, other computing systems 205, web services 204, data files 206, or other data sources, for example. Templates and the resulting presentations may be stored on a disk 203 or other storage.
Figures=21 and 22 are matrices that show a representation of data fields and data that may be accessed from a database 202, data file 206, other computing system 205, etc. The sample data shown in figure 21 is shown for illustrative purposes on how a presentation may be generated using data that represents a series of projects being handled by an organization. Each project has a level, type, name, description and other data fields. Figure 22 is a second listing showing further sample data for the projects first shown in figure 21. As indicated by these two figures, the data used by embodiments of the present invention may exist in more than one database table, data file, web service, etc. A person skilled in the art will readily understand the numerous ways in which data can be stored and transmitted.
For example, one embodiment of the invention may include an XML parser so that the data can be represented in XML format. For example, data for the first project shown in figure 21 may be structured as a series of XML tags having attribute-value pairs, such as the tags shown in Table 1.
<project>
<attribute name='id' value='1'/> </attribute>
<attribute name='level' value='national`/> </attribute>
<attribute name='type' value='military'/> </attribute>
<attribute name='name' value-'mil-ops-3829'/> </attribute>
<attribute name='description' value='D1?'/> </attribute>
<attribute name='rationale' value='R1?1/> </attribute>
<attribute name='priority' value='high'/> </attribute>
<attribute name='startDate' value='3-5-2003'/> </attribute>
<attribute name='endDate' = value''12-31-2003'/> </attribute>
<attribute name='indicator'>
<attribute name='label' value='yl'/> </attribute>
<attribute name='description' value='D1'/> </attribute>
<attribute name='value' value='V1'/> </attribute>
</attribute <attribute name='indicator'>
Figures=21 and 22 are matrices that show a representation of data fields and data that may be accessed from a database 202, data file 206, other computing system 205, etc. The sample data shown in figure 21 is shown for illustrative purposes on how a presentation may be generated using data that represents a series of projects being handled by an organization. Each project has a level, type, name, description and other data fields. Figure 22 is a second listing showing further sample data for the projects first shown in figure 21. As indicated by these two figures, the data used by embodiments of the present invention may exist in more than one database table, data file, web service, etc. A person skilled in the art will readily understand the numerous ways in which data can be stored and transmitted.
For example, one embodiment of the invention may include an XML parser so that the data can be represented in XML format. For example, data for the first project shown in figure 21 may be structured as a series of XML tags having attribute-value pairs, such as the tags shown in Table 1.
<project>
<attribute name='id' value='1'/> </attribute>
<attribute name='level' value='national`/> </attribute>
<attribute name='type' value='military'/> </attribute>
<attribute name='name' value-'mil-ops-3829'/> </attribute>
<attribute name='description' value='D1?'/> </attribute>
<attribute name='rationale' value='R1?1/> </attribute>
<attribute name='priority' value='high'/> </attribute>
<attribute name='startDate' value='3-5-2003'/> </attribute>
<attribute name='endDate' = value''12-31-2003'/> </attribute>
<attribute name='indicator'>
<attribute name='label' value='yl'/> </attribute>
<attribute name='description' value='D1'/> </attribute>
<attribute name='value' value='V1'/> </attribute>
</attribute <attribute name='indicator'>
<attribute name='label' value='L2'/> </attribute <attribute name=`description' value='D2'/> </attribute <attribute name='value' value='V2'/> </attribute </attribute <attribute name='indicator'>
<attribute name='1abe1' value='L3'/> </attribute <attribute name='description' value='D3'/> </attribute <attribute name='value' value='V3'/> </attribute </attribute <attribute name='indicator'>
<attribute name='label' value='L4'/> </attribute <attribute name='description' value='D4'/> </attribute <attribute name='value' value='V4'/> </attribute </attribute <attribute name='indicator'>
<attribute name='label' value='L5'/> </attribute <attribute name='description' value='D5'/> </attribute <attribute name='value' value='V5'/> </attribute </attribute </project>
Table I
To explain how the data listed in figures 21 and 22 or table I can be accessed by processing instructions in the template to generate a presentation in PowerPoint, figures 23A, 23B and 23C show three pages that are part of a multi-slide template 230. Figure 24 illustrates how PowerPoint may displays the first slide page of the template 230. Text and other display objects may be inserted by the end user in the slide pane area 232 of the template. The user may also insert processing instruction tags 236 corresponding to fields in the data source. Various means may be used to insert such tags. In figure 24, the user encloses plain text in braces {} to indicate a tag. Add-itional parameters may also be enclosed by the brackets. For example, the template page in figure 23A indicates that the TYPE data field should be inserted below the text "National Objectives" and then all of the NAME data fields should be listed as bullet points. The plus-sign in the example of figure 24 may indicate that all pertinent records should be included rather than just the current record.
In one embodiment, the user does not need to type the brackets and text in order to insert tags. Rather, in such an embodiment the GUI shown in figures 17 to 19 may be used and the user may simply click on one of the field names, and then drag-and-drop a tag for that field into the proper location of the template.
-1 b-Figure 23A also shows the standard PowerPoint notes pane 234 below the slide pane 232. One embodiment of the invention leverages the notes pane 234 to store processing instructions. Other embodiments allow the user to set up the processing instructions in different ways, such as in a comments section, within the main portion of the template, etc.
In yet another embodiment, the processing instructions may be associated with one or more smart tags and placed in the resulting presentation file. in such a presentation file, the end user may use the smart tag to update one section, mulfiple sections, or the entire presentation by re-querying the data source. Of course in yet other embodiments the processing instructions may be embedded in the presentation file itself not with smart tags but with other features that one skilled in the art may choose to leverage.
The processing instructions in the notes pane 234 of the example in figure 23A include five lines. In this example, XPath query language is shown. In other embodiments, other protocols may be used. The first line ("# Group Filter...") sets the context of the slide (or group of slides). For example, here only records for which the LEVEL field is set to 'National' are to be included in the presentation.
One skilled in the art will recognize that setting the context (i.e., determining what data to extract from the data source) may be implemented to offer various features. Three possible features are to sort by frequency, sort by structural .
elements, and to.sort by a combinations of structural elements and relational links. In sorting by frequency, in one embodiment, data from the data source may be sorted according to some frequency requirement. The highest 10 resufts, the most common results, the lowest 15 different results are three examples of how frequency may be used in building the presentation.
In sorting by structural elements, the structure of the data source may itself be a sorting/filtering requirement. For example, one may choose to only report in the presentation items where more than two child elements exist. Or, the presentation may dictate that a data element should only be shown when its child elements have data for priority filed. In yet a third example, a user may use an instruction that a data entity should be listed in addition to its child entities.
In sorting by a combination of structural elements and relational links, the status of structural elements (such as choosing those with two or more child links) may be used in combination with the more traditional relational requirements (i.e., where the foreign key in one table is the primary key in a second table).
Some embodiments of the invention may also provide an analysis feature whereby the structure and data source may be proactively analyzed to determine commonly and likely queries that a user may find helpful. As data sources may be complex in structure, pre-built queries may allow the use of the invention to be much more user friendly.
Returning now to figure 23A, the second line ("Group sort...") includes information on how the context is to be sorted. Here, the data (and hence the presentation) will be sorted by the TYPE data field. The third line in the instructions ("Slides in Group...") informs the generator how many slide templates exist for the current grouping of slides. In figure 23A, the processing instructions indicate that there is only the one slide making up its own group.
The fourth instruction line ("New Slide Per...") is the break-on condition, stating when to break to a new slide group. Figure 23A's slide template will break once the TYPE data field changes. The fifth and final instruction ("Order Bullets...") sets up the ordering format for any bullets or numbered list displaying on the template.
Comparing the data of figures 21 and 22 against the first template shown in figure 23A, one skilled in the art will understand that the generator program will work on only data for which the LEVEL field is set to "NationaP" (i.e., rows with ID of 1 to 7).
From these seven records, the generator will sort by TYPE (hence the records would first process the Economic, then the Military, then the Political, and finally the Social fields). Assuming that the presentation generating is currently processing the Military records, the figure 23A template will cause the names of row lDs 1, 2 and 3 to be shown as the bullet points. Figure 24 shows such a resulting slide from the template and the buileted data 244.
Figures 23B and 23C illustrate how a user may set up a second group of slide templates for the presentation in PowerPoint. In these two figures, the processing instructions in the notes pane 234 indicate that there are two slides that make up the group. Thus, these two templates will cause two slides to be inserted in the presentation file for each processed record. Figures 25 and 26 illustrate the resulting portion of the presentation based on the template slides of figures 23B and 23C for the "mil-ops-3829" project and figures 27 and 28 correspond to the "mil-ops-922'0"
project.
If a template consists of the three slides shown in figures 23A, 23B and 23C, and if only the "NationaP" level data shown in figures 21 and 22 are to be included, then the final presentation will consist of the following 18 siides, in this order.
slide # template records included in used slide Type Name 1 23A ID = 6 economic con-ops-3892 2 23B ID = 6 economic econ-ops-3892 3 23C ID = 6 economic econ-ops-3892 4 3A ID = 3, 1 and 2 mil-ops-0989, mil-ops-3829 &
military mil-ops-9220 238 ID = 3 ifitary mil-ops-0989 6 3C ID = 3, 110 and 111 military ihops-0989 7 23B ID = 9 military mil-ops-3829 8 23C ID = 1, 101, 102, 103, 104 and 105 military il-ops-3829 9 23B ID = 2 military mil-ops-9220 23C ID = 2, 106 and 107 ifitary mil-ops-9220 11 3A ID = 5& 4 polifical pol-ops-7739 & pol-ops-8328 12 23B ID = 5 olitical o{-ops-7739 13 23C ID = 5 political pol-ops-7739 14 3B iD = 4 olitical pol-ops-8328 13C ID = 4 political pol-ops-8328 16 3A ID = 7 social oc-ops-0558 17 3B ID = 7 5ocial soc-ops-0558 18 3C ID = 7 ocia( oc-ops-0558 Table 2 Notice in table 2 how for each set of data processed from the data source, there is a slide based on the Figure 23A template followed by two slides from the grouped templates of figures 23B and 23C.
To better understand the coding shown in the figures, a short explanation of XPath functionality will now be provided. First, the "/" item may be used to represent an absolute path to a data element. The item may be used to further specify an element. The "//" item may be used to select all elements in the document that satisfy the criteria quei-ied: The "../" item may be used to select the parent of the current node. The "ancestor::" item may be used to select all of the ancestors (such as the parent and the grandparent) of the current node. The "preceding::" item may be used to select everything in the document before the starting tag of the current node.
In addition to the standard XPath features shown in figures 23A, 23B and 23C, in one embodiment, additional specialized support to provided for parsing the following processing instruction elements: ?, @, and +. In one embodiment, the "?"
item may act as a placeholder for'unique objects' that are queried within an XML
document. Each new object id may then represent a new set of slides to follow for that object. The "@" item may act like a'carriage return' for information to be repeated (at the parent level) within a presentation (such as a PowerPoint slide or a Word document). The "+" item may act like a'carriage return' for information to be repeated at the child level if it is used in conjunction with the "@" item.
The use of these processing elements may be shown in operation by the template shown in figure 29 and explained in table 3 below:
Table 3 Query Code Parsed .. Explain Code in English # .. ..
I # begin queries Group Filter ://branch for all branches...
/phase dis la those hases...
t those that...
not excep uni ueOb'ectld = have a unique Object ID
preceding::phase/ that has been found before.
uni ueOb'ectid , (In other words, for query 1, find all of the Phases within a Branch, but don't duplicate an .
2 Group Sort: sort the slide group ../uni ueOb'ectld , by Branches having a unique Object ID
Slides in Grou : 1, the group contains a single slide 3 New Slide Per: Create a new slide...
{./uniqueObjectld}, for each Phase that has a unique Object ID
4 Order Bullets/Rows by: Order the rows in the slide ...
../ riori , by the Priori field Row Per Each row is...
//branch for all Branches ...
/phase display all Phases ...
[./uniqueObjectid='?'] and create a placeholder that is for each Phase that has a unique Object ID ...
Ilob'ective and display those Ob'ectives ...
not except for those that ...
(uniqueObjectld= have a unique Object ID ...
preceeding::phase//objective/uni that have been found before in a queObjectid)] preceding Phase...
/label and dis ia the name ...
[../level='Tacticai']} of those Objectives which have a level of 'Tacticai' end Queries The five queries for the template of figure 29 begin with the first query being executed against the data source. As shown in the "Explain Query in English"
column of table 3, the data for all of the Phases in a Branch are retrieved (without duplicates), stored and the cursor is located at the "Phase" level within the XML
source file.
Queries 2 and 3 begin where this cursor was placed at the termination of query 1(i.e., at the Phase level). Query #2 reads its query, and looks for its information one level up (i.e., at the "Branch" level, which is one level higher than where Query #1 concluded) and stores the appropriate data (i.e., sorting the slide group by Branch). Query #3 reads its query to, looks for its information at the "Phase"
level (i.e. the same level where Query #1 concluded) and stores the appropriate data.
Query #5 is then read and stored with the cursor resting at the overall "level"
for Objectives within the XML file. Lastly, query #4 reads its query and searches for its information at the "Objective" level within the XML file (one step up from where Query #5 concluded which was at the overall "level" for Objectives).
Figures 30 through 36 illustrate a more robust embodiment of the present invention than that shown in figures 17 through 19 and discussed above. As shown starting in figure 17, this embodiment of the invention has a four-tabbed user interface. The overview tab allows the user to store information about the presentatiori, such as its classfication 3005, its tifle 3010, notes about it 3015, a point of contact 3020, dates of creation and modification 3025, and location of the template file 3030 and data sources 3035. Such an embodiment may include a preview region 3040 where a user may see a thumbnail of some of the slides in the template.
This feature may help the user to quickly find the correct template.
Figure 31 shows the slides tab where a list of queries saved within the template are listed 3105 for the user to activate or deactivate. Details about the .template may also be stored here 3110.
Figure 32 is the queries tab where queries may be added, or saved queries may be used (with or without modification) 3205. The query's format 3210 and details about its structure 3215 may be modified through this tab. Figure 33 shows how a dropdown menu may assist the user in choosing filtering for the query 3305.
Figure 34 shows how a dropdown menu may assist the user in choosing the level, which determines what (if any) data from children should be included with the query 3405.
Figure 35 shows a linking setup window 3505, which may be used to identify relational linking entities of one entity that then link two other entities.
This feature may allow relationships that do not follow a tree hierarchy. This linking setup window is further shown in figure 36, where one entity is linked to another entity 3605.
The foregoing description addresses embodiments encompassing the principles of the present invention. The embodiments may be changed, modified and/or impiemented using various types of arrangements. Those skilled in the art will readily recognize various modifications and changes that may be made to the invention without strictly following the exemplary embodiments and appficafions illustrated and described herein, and without depar6ng from the scope of the invention. For example, one embodiment of the invention provides functionality to enable the user to refresh individual pieces of data. Another embodiment enables the user to specify on the template that a hyperlink should be generated linked to another slide in the presentation. In yet another embodiment, the presentation generator's GUI allows the user the see the representative data on the template rather than the symbolic field tags.
<attribute name='1abe1' value='L3'/> </attribute <attribute name='description' value='D3'/> </attribute <attribute name='value' value='V3'/> </attribute </attribute <attribute name='indicator'>
<attribute name='label' value='L4'/> </attribute <attribute name='description' value='D4'/> </attribute <attribute name='value' value='V4'/> </attribute </attribute <attribute name='indicator'>
<attribute name='label' value='L5'/> </attribute <attribute name='description' value='D5'/> </attribute <attribute name='value' value='V5'/> </attribute </attribute </project>
Table I
To explain how the data listed in figures 21 and 22 or table I can be accessed by processing instructions in the template to generate a presentation in PowerPoint, figures 23A, 23B and 23C show three pages that are part of a multi-slide template 230. Figure 24 illustrates how PowerPoint may displays the first slide page of the template 230. Text and other display objects may be inserted by the end user in the slide pane area 232 of the template. The user may also insert processing instruction tags 236 corresponding to fields in the data source. Various means may be used to insert such tags. In figure 24, the user encloses plain text in braces {} to indicate a tag. Add-itional parameters may also be enclosed by the brackets. For example, the template page in figure 23A indicates that the TYPE data field should be inserted below the text "National Objectives" and then all of the NAME data fields should be listed as bullet points. The plus-sign in the example of figure 24 may indicate that all pertinent records should be included rather than just the current record.
In one embodiment, the user does not need to type the brackets and text in order to insert tags. Rather, in such an embodiment the GUI shown in figures 17 to 19 may be used and the user may simply click on one of the field names, and then drag-and-drop a tag for that field into the proper location of the template.
-1 b-Figure 23A also shows the standard PowerPoint notes pane 234 below the slide pane 232. One embodiment of the invention leverages the notes pane 234 to store processing instructions. Other embodiments allow the user to set up the processing instructions in different ways, such as in a comments section, within the main portion of the template, etc.
In yet another embodiment, the processing instructions may be associated with one or more smart tags and placed in the resulting presentation file. in such a presentation file, the end user may use the smart tag to update one section, mulfiple sections, or the entire presentation by re-querying the data source. Of course in yet other embodiments the processing instructions may be embedded in the presentation file itself not with smart tags but with other features that one skilled in the art may choose to leverage.
The processing instructions in the notes pane 234 of the example in figure 23A include five lines. In this example, XPath query language is shown. In other embodiments, other protocols may be used. The first line ("# Group Filter...") sets the context of the slide (or group of slides). For example, here only records for which the LEVEL field is set to 'National' are to be included in the presentation.
One skilled in the art will recognize that setting the context (i.e., determining what data to extract from the data source) may be implemented to offer various features. Three possible features are to sort by frequency, sort by structural .
elements, and to.sort by a combinations of structural elements and relational links. In sorting by frequency, in one embodiment, data from the data source may be sorted according to some frequency requirement. The highest 10 resufts, the most common results, the lowest 15 different results are three examples of how frequency may be used in building the presentation.
In sorting by structural elements, the structure of the data source may itself be a sorting/filtering requirement. For example, one may choose to only report in the presentation items where more than two child elements exist. Or, the presentation may dictate that a data element should only be shown when its child elements have data for priority filed. In yet a third example, a user may use an instruction that a data entity should be listed in addition to its child entities.
In sorting by a combination of structural elements and relational links, the status of structural elements (such as choosing those with two or more child links) may be used in combination with the more traditional relational requirements (i.e., where the foreign key in one table is the primary key in a second table).
Some embodiments of the invention may also provide an analysis feature whereby the structure and data source may be proactively analyzed to determine commonly and likely queries that a user may find helpful. As data sources may be complex in structure, pre-built queries may allow the use of the invention to be much more user friendly.
Returning now to figure 23A, the second line ("Group sort...") includes information on how the context is to be sorted. Here, the data (and hence the presentation) will be sorted by the TYPE data field. The third line in the instructions ("Slides in Group...") informs the generator how many slide templates exist for the current grouping of slides. In figure 23A, the processing instructions indicate that there is only the one slide making up its own group.
The fourth instruction line ("New Slide Per...") is the break-on condition, stating when to break to a new slide group. Figure 23A's slide template will break once the TYPE data field changes. The fifth and final instruction ("Order Bullets...") sets up the ordering format for any bullets or numbered list displaying on the template.
Comparing the data of figures 21 and 22 against the first template shown in figure 23A, one skilled in the art will understand that the generator program will work on only data for which the LEVEL field is set to "NationaP" (i.e., rows with ID of 1 to 7).
From these seven records, the generator will sort by TYPE (hence the records would first process the Economic, then the Military, then the Political, and finally the Social fields). Assuming that the presentation generating is currently processing the Military records, the figure 23A template will cause the names of row lDs 1, 2 and 3 to be shown as the bullet points. Figure 24 shows such a resulting slide from the template and the buileted data 244.
Figures 23B and 23C illustrate how a user may set up a second group of slide templates for the presentation in PowerPoint. In these two figures, the processing instructions in the notes pane 234 indicate that there are two slides that make up the group. Thus, these two templates will cause two slides to be inserted in the presentation file for each processed record. Figures 25 and 26 illustrate the resulting portion of the presentation based on the template slides of figures 23B and 23C for the "mil-ops-3829" project and figures 27 and 28 correspond to the "mil-ops-922'0"
project.
If a template consists of the three slides shown in figures 23A, 23B and 23C, and if only the "NationaP" level data shown in figures 21 and 22 are to be included, then the final presentation will consist of the following 18 siides, in this order.
slide # template records included in used slide Type Name 1 23A ID = 6 economic con-ops-3892 2 23B ID = 6 economic econ-ops-3892 3 23C ID = 6 economic econ-ops-3892 4 3A ID = 3, 1 and 2 mil-ops-0989, mil-ops-3829 &
military mil-ops-9220 238 ID = 3 ifitary mil-ops-0989 6 3C ID = 3, 110 and 111 military ihops-0989 7 23B ID = 9 military mil-ops-3829 8 23C ID = 1, 101, 102, 103, 104 and 105 military il-ops-3829 9 23B ID = 2 military mil-ops-9220 23C ID = 2, 106 and 107 ifitary mil-ops-9220 11 3A ID = 5& 4 polifical pol-ops-7739 & pol-ops-8328 12 23B ID = 5 olitical o{-ops-7739 13 23C ID = 5 political pol-ops-7739 14 3B iD = 4 olitical pol-ops-8328 13C ID = 4 political pol-ops-8328 16 3A ID = 7 social oc-ops-0558 17 3B ID = 7 5ocial soc-ops-0558 18 3C ID = 7 ocia( oc-ops-0558 Table 2 Notice in table 2 how for each set of data processed from the data source, there is a slide based on the Figure 23A template followed by two slides from the grouped templates of figures 23B and 23C.
To better understand the coding shown in the figures, a short explanation of XPath functionality will now be provided. First, the "/" item may be used to represent an absolute path to a data element. The item may be used to further specify an element. The "//" item may be used to select all elements in the document that satisfy the criteria quei-ied: The "../" item may be used to select the parent of the current node. The "ancestor::" item may be used to select all of the ancestors (such as the parent and the grandparent) of the current node. The "preceding::" item may be used to select everything in the document before the starting tag of the current node.
In addition to the standard XPath features shown in figures 23A, 23B and 23C, in one embodiment, additional specialized support to provided for parsing the following processing instruction elements: ?, @, and +. In one embodiment, the "?"
item may act as a placeholder for'unique objects' that are queried within an XML
document. Each new object id may then represent a new set of slides to follow for that object. The "@" item may act like a'carriage return' for information to be repeated (at the parent level) within a presentation (such as a PowerPoint slide or a Word document). The "+" item may act like a'carriage return' for information to be repeated at the child level if it is used in conjunction with the "@" item.
The use of these processing elements may be shown in operation by the template shown in figure 29 and explained in table 3 below:
Table 3 Query Code Parsed .. Explain Code in English # .. ..
I # begin queries Group Filter ://branch for all branches...
/phase dis la those hases...
t those that...
not excep uni ueOb'ectld = have a unique Object ID
preceding::phase/ that has been found before.
uni ueOb'ectid , (In other words, for query 1, find all of the Phases within a Branch, but don't duplicate an .
2 Group Sort: sort the slide group ../uni ueOb'ectld , by Branches having a unique Object ID
Slides in Grou : 1, the group contains a single slide 3 New Slide Per: Create a new slide...
{./uniqueObjectld}, for each Phase that has a unique Object ID
4 Order Bullets/Rows by: Order the rows in the slide ...
../ riori , by the Priori field Row Per Each row is...
//branch for all Branches ...
/phase display all Phases ...
[./uniqueObjectid='?'] and create a placeholder that is for each Phase that has a unique Object ID ...
Ilob'ective and display those Ob'ectives ...
not except for those that ...
(uniqueObjectld= have a unique Object ID ...
preceeding::phase//objective/uni that have been found before in a queObjectid)] preceding Phase...
/label and dis ia the name ...
[../level='Tacticai']} of those Objectives which have a level of 'Tacticai' end Queries The five queries for the template of figure 29 begin with the first query being executed against the data source. As shown in the "Explain Query in English"
column of table 3, the data for all of the Phases in a Branch are retrieved (without duplicates), stored and the cursor is located at the "Phase" level within the XML
source file.
Queries 2 and 3 begin where this cursor was placed at the termination of query 1(i.e., at the Phase level). Query #2 reads its query, and looks for its information one level up (i.e., at the "Branch" level, which is one level higher than where Query #1 concluded) and stores the appropriate data (i.e., sorting the slide group by Branch). Query #3 reads its query to, looks for its information at the "Phase"
level (i.e. the same level where Query #1 concluded) and stores the appropriate data.
Query #5 is then read and stored with the cursor resting at the overall "level"
for Objectives within the XML file. Lastly, query #4 reads its query and searches for its information at the "Objective" level within the XML file (one step up from where Query #5 concluded which was at the overall "level" for Objectives).
Figures 30 through 36 illustrate a more robust embodiment of the present invention than that shown in figures 17 through 19 and discussed above. As shown starting in figure 17, this embodiment of the invention has a four-tabbed user interface. The overview tab allows the user to store information about the presentatiori, such as its classfication 3005, its tifle 3010, notes about it 3015, a point of contact 3020, dates of creation and modification 3025, and location of the template file 3030 and data sources 3035. Such an embodiment may include a preview region 3040 where a user may see a thumbnail of some of the slides in the template.
This feature may help the user to quickly find the correct template.
Figure 31 shows the slides tab where a list of queries saved within the template are listed 3105 for the user to activate or deactivate. Details about the .template may also be stored here 3110.
Figure 32 is the queries tab where queries may be added, or saved queries may be used (with or without modification) 3205. The query's format 3210 and details about its structure 3215 may be modified through this tab. Figure 33 shows how a dropdown menu may assist the user in choosing filtering for the query 3305.
Figure 34 shows how a dropdown menu may assist the user in choosing the level, which determines what (if any) data from children should be included with the query 3405.
Figure 35 shows a linking setup window 3505, which may be used to identify relational linking entities of one entity that then link two other entities.
This feature may allow relationships that do not follow a tree hierarchy. This linking setup window is further shown in figure 36, where one entity is linked to another entity 3605.
The foregoing description addresses embodiments encompassing the principles of the present invention. The embodiments may be changed, modified and/or impiemented using various types of arrangements. Those skilled in the art will readily recognize various modifications and changes that may be made to the invention without strictly following the exemplary embodiments and appficafions illustrated and described herein, and without depar6ng from the scope of the invention. For example, one embodiment of the invention provides functionality to enable the user to refresh individual pieces of data. Another embodiment enables the user to specify on the template that a hyperlink should be generated linked to another slide in the presentation. In yet another embodiment, the presentation generator's GUI allows the user the see the representative data on the template rather than the symbolic field tags.
Claims (31)
PROPERTY OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A system for generating a presentation file, the system comprising:
means for accessing a data source comprising a plurality of data records structured into a plurality of data fields;
means for providing an end user of a computer with a listing of a plurality of tags, wherein the tag is associated to one of the data fields in the data source;
means for choosing a template file, where the template file comprises:
at least one of the plurality of tags;, and at least one processing instruction for indicating how the data source is processed to build the presentation file;
means for processing the template file with the data source based on the at least one of the plurality of tags and the at least one processing instruction, for building the presentation file for reporting information from the data source; and wherein at least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template file.
means for accessing a data source comprising a plurality of data records structured into a plurality of data fields;
means for providing an end user of a computer with a listing of a plurality of tags, wherein the tag is associated to one of the data fields in the data source;
means for choosing a template file, where the template file comprises:
at least one of the plurality of tags;, and at least one processing instruction for indicating how the data source is processed to build the presentation file;
means for processing the template file with the data source based on the at least one of the plurality of tags and the at least one processing instruction, for building the presentation file for reporting information from the data source; and wherein at least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template file.
2. The system of claim 1, wherein at least one of the processing instructions is a second query embedded in the template file.
3. The system of claim 2, wherein the first query is for a first data source and the second query is for a second data source.
4. The system of any one of claims 1 to 3, wherein the at least one processing instruction queries the data source for presenting more than one data record on a single page in the presentation file.
5. The system of any one of claims 1 to 4, wherein the means for processing the template file with the data source based on the at least one processing instruction comprises:
means for grouping a first template page and a second template page from the template file;
means for determining a break-on condition for one of the plurality of data fields, where the break-on condition is satisfied when data associated with the data field changes;
means for creating pages in the presentation file based on the first and second template pages; and means for repeating the step of creating pages based on the first and second template pages when the break-on condition is met.
means for grouping a first template page and a second template page from the template file;
means for determining a break-on condition for one of the plurality of data fields, where the break-on condition is satisfied when data associated with the data field changes;
means for creating pages in the presentation file based on the first and second template pages; and means for repeating the step of creating pages based on the first and second template pages when the break-on condition is met.
6. The system of claim 5, wherein the means for processing the template file with the data source based on the at least one processing instruction further comprises means for querying the data source for presenting more than one data record on a single page in the presentation file.
7. The system of any one of claims 1 to 6, wherein the at least one processing instruction is stored in a notes region of the template file.
8. The system of any one of claims 1 to 6, wherein the at least one processing instruction is stored in a comments region of the template file.
9. A system for generating a presentation, the system comprising:
means for accessing a data source comprising a plurality of data records structured into a plurality of data fields;
means for accessing a template file comprising at least one tag and at least one processing instruction, wherein the tag is associated to one of the data fields in the data source;
means for processing the template file and the data source based on the at least one tag and the at least one processing instruction, for building the presentation file for reporting information from the data source; and wherein at least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template file.
means for accessing a data source comprising a plurality of data records structured into a plurality of data fields;
means for accessing a template file comprising at least one tag and at least one processing instruction, wherein the tag is associated to one of the data fields in the data source;
means for processing the template file and the data source based on the at least one tag and the at least one processing instruction, for building the presentation file for reporting information from the data source; and wherein at least one of the processing instructions is a query embedded in the template file, for allowing the end user to associate the data source to the template file.
10. The system of claim 9, wherein the query is embedded in the template file as a smart tag for allowing an end user to re-query the data source from the presentation file to update the presentation file.
11. A method for generating a plurality of presentation pages in a presentation file, the method comprising:
(a) utilizing a desktop application to generate a presentation template in a file format related to a document produced by the desktop application;
(b) accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged locations;
(d) embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field; and (e) processing the first template group and the second template group with the data source to generate a presentation output file comprising an ordered set of presentation output pages structured and ordered based on the first and second template groups, including:
(i) processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
(ii) processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page; and (iii) each time the first break-on condition is met, repeating processing step (e)(ii) to generate an additional presentation page using the plurality of embedded processing instructions of the second template page.
(a) utilizing a desktop application to generate a presentation template in a file format related to a document produced by the desktop application;
(b) accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged locations;
(d) embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field; and (e) processing the first template group and the second template group with the data source to generate a presentation output file comprising an ordered set of presentation output pages structured and ordered based on the first and second template groups, including:
(i) processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
(ii) processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page; and (iii) each time the first break-on condition is met, repeating processing step (e)(ii) to generate an additional presentation page using the plurality of embedded processing instructions of the second template page.
12. The method of claim 11, wherein the second presentation output page comprises data and formatting structured and presented different from the first presentation output page.
13. The method of claim 11 or 12, wherein the embedded processing instructions of at least one of the first and second template pages further comprises an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
14. The method of claim 13, wherein the second data field of the plurality of data fields is different from the first data field.
15. The method of claim 11 or 12, wherein the embedded processing instructions of each of the first and second template pages further comprises an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
16. The method of claim 15, wherein the second data field of the plurality of data fields is different from the first data field.
17. The method of any one of claims 13 to 16, further comprising:
(f) repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file in response to detection of a change in the second data field through execution of the order-based processing instruction.
(f) repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file in response to detection of a change in the second data field through execution of the order-based processing instruction.
18. The method of any one of claims 13 to 16, further comprising:
(f) repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
(f) repeating processing step (e) to generate an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
19. The method of any one of claims 11 to 18, further comprising:
(g) embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field, wherein the second break-on condition is satisfied in response to a change in the data associated with the third data field.
(g) embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field, wherein the second break-on condition is satisfied in response to a change in the data associated with the third data field.
20. The method of claim 19, further comprising:
(h) each time the second break-on condition is met, repeating processing step (e) to generate an additional ordered set of presentation output pages structured and ordered based on the first and second template groups.
(h) each time the second break-on condition is met, repeating processing step (e) to generate an additional ordered set of presentation output pages structured and ordered based on the first and second template groups.
21. A computer readable medium encoded with codes for causing a computing device to execute any one of the methods of claims 11 to 20.
22. A system for generating a plurality of presentation pages in a presentation file, the system comprising:
(a) means for utilizing a desktop application to generate a presentation template in a file format related to a document produced by the desktop application;
(b) means for accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) means for selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged locations;
(d) means for embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field;
and (e) means for processing the first template group and the second template group with the data source to generate a presentation output file comprising an ordered set of presentation output pages structured and ordered based on the first and second template groups, including:
(i) means for processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
(ii) means for processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page; and (iii) means for generating an additional presentation page using the plurality of embedded processing instructions of the second template page each time the break-on condition is met.
(a) means for utilizing a desktop application to generate a presentation template in a file format related to a document produced by the desktop application;
(b) means for accessing a data source having a plurality of data records structured into a plurality of data fields, wherein the data source is structured into a parsable data output;
(c) means for selecting a first template group and second template group each related to the presentation file format of the desktop application, the first template group comprising a first template page, the second template group comprising a second template page, the first and second template pages each comprising:
(i) a plurality of tagged locations; and (ii) a plurality of embedded processing instructions configured to control querying of the data source and configured to control processing and insertion of data from the data source into the plurality of tagged locations;
(d) means for embedding a first break-on condition in at least one of the first and second template pages for a first data field of the plurality of data fields, wherein the first break-on condition is satisfied in response to a change in the data associated with the first data field;
and (e) means for processing the first template group and the second template group with the data source to generate a presentation output file comprising an ordered set of presentation output pages structured and ordered based on the first and second template groups, including:
(i) means for processing the plurality of embedded processing instructions of the first template page with the data source to generate a first presentation output page in a format readable by the desktop application for reporting information from the data source;
(ii) means for processing the plurality of embedded processing instructions of the second template page with the data source to generate a second presentation output page in a format readable by the desktop application for reporting information from the data source, wherein the second presentation output page comprises data and formatting different from the first presentation output page; and (iii) means for generating an additional presentation page using the plurality of embedded processing instructions of the second template page each time the break-on condition is met.
23. The system of claim 22, wherein the second presentation output page comprises data and formatting structured and presented different from the first presentation output page.
24. The system of claim 22 or 23, wherein the embedded processing instructions of at least one of the first and second template pages further comprises an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
25. The system of claim 24, wherein the second data field of the plurality of data fields is different from the first data field.
26. The system of claim 22 or 23, wherein the embedded processing instructions of each of the first and second template pages further comprises an order-based processing instruction for producing sets of presentation output pages ordered based on a second data field of the plurality of data fields.
27. The system of claim 26, wherein the second data field of the plurality of data fields is different from the first data field.
28. The system of any one of claims 24 to 27, further comprising:
(f) means for generating an additional ordered set of presentation output pages for insertion into the presentation output file in response to detection of a change in the second data field through execution of the order-based processing instruction.
(f) means for generating an additional ordered set of presentation output pages for insertion into the presentation output file in response to detection of a change in the second data field through execution of the order-based processing instruction.
29. The system of any one of claims 24 to 27, further comprising:
(f) means for generating an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
(f) means for generating an additional ordered set of presentation output pages for insertion into the presentation output file each time the processing of the order-based processing instruction results in detection of a change in the second data field.
30. The system of any one of claims 22 to 29, further comprising:
(g) means for embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field, wherein the second break-on condition is satisfied in response to a change in the data associated with the third data field.
(g) means for embedding a second break-on condition in at least one of the first and second template pages for a third data field of the plurality of data fields different from the first data field, wherein the second break-on condition is satisfied in response to a change in the data associated with the third data field.
31. The system of claim 30, further comprising:
(h) means for generating an additional ordered set of presentation output pages structured and ordered based on the first and second template groups each time the second break-on condition is met.
(h) means for generating an additional ordered set of presentation output pages structured and ordered based on the first and second template groups each time the second break-on condition is met.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US49460603P | 2003-08-12 | 2003-08-12 | |
| US60/494,606 | 2003-08-12 | ||
| CA2535093A CA2535093C (en) | 2003-08-12 | 2004-08-11 | Generating end-user presentations from structured data |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2535093A Division CA2535093C (en) | 2003-08-12 | 2004-08-11 | Generating end-user presentations from structured data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2669479A1 CA2669479A1 (en) | 2005-02-17 |
| CA2669479C true CA2669479C (en) | 2010-06-01 |
Family
ID=34135348
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2671284A Expired - Fee Related CA2671284C (en) | 2003-08-12 | 2004-08-11 | Generating end-user presentations from structured data |
| CA2535093A Expired - Fee Related CA2535093C (en) | 2003-08-12 | 2004-08-11 | Generating end-user presentations from structured data |
| CA2669479A Expired - Fee Related CA2669479C (en) | 2003-08-12 | 2004-08-11 | Generating end-user presentations from structured data |
Family Applications Before (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2671284A Expired - Fee Related CA2671284C (en) | 2003-08-12 | 2004-08-11 | Generating end-user presentations from structured data |
| CA2535093A Expired - Fee Related CA2535093C (en) | 2003-08-12 | 2004-08-11 | Generating end-user presentations from structured data |
Country Status (4)
| Country | Link |
|---|---|
| US (3) | US7363581B2 (en) |
| EP (2) | EP1661030A2 (en) |
| CA (3) | CA2671284C (en) |
| WO (1) | WO2005015378A2 (en) |
Families Citing this family (192)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7389472B2 (en) * | 2003-05-07 | 2008-06-17 | Microsoft Corporation | Connected templates in connection with a content management server system or the like |
| US7363581B2 (en) | 2003-08-12 | 2008-04-22 | Accenture Global Services Gmbh | Presentation generator |
| US9171100B2 (en) | 2004-09-22 | 2015-10-27 | Primo M. Pettovello | MTree an XPath multi-axis structure threaded index |
| US7739309B2 (en) * | 2004-09-30 | 2010-06-15 | Microsoft Corporation | Method, system, and computer-readable medium for merging data from multiple data sources for use in an electronic document |
| US20060080610A1 (en) * | 2004-10-12 | 2006-04-13 | Kaminsky David L | Methods, systems and computer program products for outline views in computer displayable presentations |
| US20060085449A1 (en) * | 2004-10-19 | 2006-04-20 | Juergen Sattler | Method and system for generating presentation materials |
| US7734670B2 (en) * | 2004-12-15 | 2010-06-08 | Microsoft Corporation | Actionable email documents |
| US7634492B2 (en) * | 2004-12-20 | 2009-12-15 | Microsoft Corporation | Aggregate data view |
| EP1896969A2 (en) * | 2005-05-31 | 2008-03-12 | Ipifini, Inc. | Computer program for identifying and automating repetitive user inputs |
| US7890452B2 (en) * | 2005-07-13 | 2011-02-15 | Sap Ag | Methods for enterprise-level data and process access and presentation |
| US20070028174A1 (en) * | 2005-07-29 | 2007-02-01 | Moore Dennis B | Grid processing dynamic screensaver |
| US20070028175A1 (en) * | 2005-07-29 | 2007-02-01 | Moore Dennis B | Grid processing user tools |
| US7925985B2 (en) | 2005-07-29 | 2011-04-12 | Sap Ag | Methods and apparatus for process thumbnail view |
| US7797325B2 (en) * | 2005-08-22 | 2010-09-14 | International Business Machines Corporation | Lightweight generic report generation tool |
| US20070050237A1 (en) * | 2005-08-30 | 2007-03-01 | Microsoft Corporation | Visual designer for multi-dimensional business logic |
| US8099674B2 (en) | 2005-09-09 | 2012-01-17 | Tableau Software Llc | Computer systems and methods for automatically viewing multidimensional databases |
| US7664742B2 (en) * | 2005-11-14 | 2010-02-16 | Pettovello Primo M | Index data structure for a peer-to-peer network |
| US20070112607A1 (en) * | 2005-11-16 | 2007-05-17 | Microsoft Corporation | Score-based alerting in business logic |
| US20070143174A1 (en) * | 2005-12-21 | 2007-06-21 | Microsoft Corporation | Repeated inheritance of heterogeneous business metrics |
| US20070143161A1 (en) * | 2005-12-21 | 2007-06-21 | Microsoft Corporation | Application independent rendering of scorecard metrics |
| US20070143175A1 (en) * | 2005-12-21 | 2007-06-21 | Microsoft Corporation | Centralized model for coordinating update of multiple reports |
| EP1987446A4 (en) * | 2006-01-13 | 2013-08-14 | Barclays Capital Inc | Method and system for integrating calculation and presentation technologies |
| US20070174309A1 (en) * | 2006-01-18 | 2007-07-26 | Pettovello Primo M | Mtreeini: intermediate nodes and indexes |
| US8082496B1 (en) * | 2006-01-26 | 2011-12-20 | Adobe Systems Incorporated | Producing a set of operations from an output description |
| US20070186167A1 (en) * | 2006-02-06 | 2007-08-09 | Anderson Kent R | Creation of a sequence of electronic presentation slides |
| US7716592B2 (en) | 2006-03-30 | 2010-05-11 | Microsoft Corporation | Automated generation of dashboards for scorecard metrics and subordinate reporting |
| US7840896B2 (en) | 2006-03-30 | 2010-11-23 | Microsoft Corporation | Definition and instantiation of metric based business logic reports |
| US8261181B2 (en) | 2006-03-30 | 2012-09-04 | Microsoft Corporation | Multidimensional metrics-based annotation |
| US8190992B2 (en) | 2006-04-21 | 2012-05-29 | Microsoft Corporation | Grouping and display of logically defined reports |
| US7716571B2 (en) * | 2006-04-27 | 2010-05-11 | Microsoft Corporation | Multidimensional scorecard header definition |
| US20070255681A1 (en) * | 2006-04-27 | 2007-11-01 | Microsoft Corporation | Automated determination of relevant slice in multidimensional data sources |
| US7870485B2 (en) * | 2006-07-27 | 2011-01-11 | Intuit Inc. | Method and apparatus for generating multiple documents using a template and a data source |
| US8561019B2 (en) * | 2006-08-11 | 2013-10-15 | Adaptive Intelligence Llc | System and method for data abstraction using formatted system variables |
| US20080104515A1 (en) * | 2006-10-30 | 2008-05-01 | Dan Dumitru | System and method for slide presentation |
| US7962495B2 (en) | 2006-11-20 | 2011-06-14 | Palantir Technologies, Inc. | Creating data in a data store using a dynamic ontology |
| US8515912B2 (en) | 2010-07-15 | 2013-08-20 | Palantir Technologies, Inc. | Sharing and deconflicting data changes in a multimaster database system |
| US9058307B2 (en) | 2007-01-26 | 2015-06-16 | Microsoft Technology Licensing, Llc | Presentation generation using scorecard elements |
| US8321805B2 (en) | 2007-01-30 | 2012-11-27 | Microsoft Corporation | Service architecture based metric views |
| US20080183564A1 (en) * | 2007-01-30 | 2008-07-31 | Microsoft Corporation | Untethered Interaction With Aggregated Metrics |
| US8495663B2 (en) | 2007-02-02 | 2013-07-23 | Microsoft Corporation | Real time collaboration using embedded data visualizations |
| US8930331B2 (en) | 2007-02-21 | 2015-01-06 | Palantir Technologies | Providing unique views of data based on changes or rules |
| US8126928B2 (en) * | 2007-06-27 | 2012-02-28 | Sap Ag | Systems and methods for merging data into documents |
| US20090031215A1 (en) * | 2007-07-23 | 2009-01-29 | Collier Ii James Patrick | Method and apparatus for generating an electronic learning presentation in a network computing environment |
| US7941399B2 (en) | 2007-11-09 | 2011-05-10 | Microsoft Corporation | Collaborative authoring |
| US8028229B2 (en) * | 2007-12-06 | 2011-09-27 | Microsoft Corporation | Document merge |
| US8825758B2 (en) | 2007-12-14 | 2014-09-02 | Microsoft Corporation | Collaborative authoring modes |
| US8301588B2 (en) * | 2008-03-07 | 2012-10-30 | Microsoft Corporation | Data storage for file updates |
| US8352870B2 (en) * | 2008-04-28 | 2013-01-08 | Microsoft Corporation | Conflict resolution |
| US8429753B2 (en) | 2008-05-08 | 2013-04-23 | Microsoft Corporation | Controlling access to documents using file locks |
| US8825594B2 (en) | 2008-05-08 | 2014-09-02 | Microsoft Corporation | Caching infrastructure |
| US20090300047A1 (en) * | 2008-05-30 | 2009-12-03 | Microsoft Corporation | Automatically assigning data bindings in visual designers |
| US20090300524A1 (en) * | 2008-05-30 | 2009-12-03 | Microsoft Corporation | Automatically assigning data bindings in visual designers |
| US9449055B1 (en) * | 2008-06-02 | 2016-09-20 | Veritas Technologies Llc | Technique for estimating report generation time at launch in client-server applications |
| US8719245B2 (en) * | 2008-06-02 | 2014-05-06 | International Business Machines Corporation | Query templates with functional template blocks |
| US8661342B2 (en) * | 2008-06-17 | 2014-02-25 | Microsoft Corporation | Mail merge integration techniques |
| US8417666B2 (en) | 2008-06-25 | 2013-04-09 | Microsoft Corporation | Structured coauthoring |
| JP5121599B2 (en) * | 2008-06-30 | 2013-01-16 | キヤノン株式会社 | Image processing apparatus, image processing method, program thereof, and storage medium |
| US8676800B2 (en) * | 2008-07-02 | 2014-03-18 | Pacific Knowledge Systems Pty Ltd | Method and system for generating text |
| AU2011247830B2 (en) * | 2008-07-02 | 2014-04-03 | Beamtree Pty. Ltd. | Method and system for generating text |
| US9600459B2 (en) * | 2008-07-16 | 2017-03-21 | International Business Machines Corporation | Visual macro showing how some icon or object or text was constructed |
| US20100031152A1 (en) * | 2008-07-31 | 2010-02-04 | Microsoft Corporation | Creation and Navigation of Infinite Canvas Presentation |
| US8108777B2 (en) * | 2008-08-11 | 2012-01-31 | Microsoft Corporation | Sections of a presentation having user-definable properties |
| US9348499B2 (en) | 2008-09-15 | 2016-05-24 | Palantir Technologies, Inc. | Sharing objects that rely on local resources with outside servers |
| US8346768B2 (en) | 2009-04-30 | 2013-01-01 | Microsoft Corporation | Fast merge support for legacy documents |
| JP5632593B2 (en) * | 2009-07-01 | 2014-11-26 | キヤノン株式会社 | Information processing apparatus, control method, and program |
| US8543619B2 (en) * | 2009-09-15 | 2013-09-24 | Oracle International Corporation | Merging XML documents automatically using attributes based comparison |
| US8631028B1 (en) | 2009-10-29 | 2014-01-14 | Primo M. Pettovello | XPath query processing improvements |
| US8572496B2 (en) * | 2010-04-27 | 2013-10-29 | Go Daddy Operating Company, LLC | Embedding variable fields in individual email messages sent via a web-based graphical user interface |
| US9547693B1 (en) | 2011-06-23 | 2017-01-17 | Palantir Technologies Inc. | Periodic database search manager for multiple data sources |
| US9092482B2 (en) | 2013-03-14 | 2015-07-28 | Palantir Technologies, Inc. | Fair scheduling for mixed-query loads |
| US8799240B2 (en) | 2011-06-23 | 2014-08-05 | Palantir Technologies, Inc. | System and method for investigating large amounts of data |
| US8898592B2 (en) * | 2011-06-30 | 2014-11-25 | International Business Machines Corporation | Grouping expanded and collapsed rows in a tree structure |
| US9396167B2 (en) | 2011-07-21 | 2016-07-19 | Flipboard, Inc. | Template-based page layout for hosted social magazines |
| US8732574B2 (en) | 2011-08-25 | 2014-05-20 | Palantir Technologies, Inc. | System and method for parameterizing documents for automatic workflow generation |
| US8504542B2 (en) | 2011-09-02 | 2013-08-06 | Palantir Technologies, Inc. | Multi-row transactions |
| US8538934B2 (en) * | 2011-10-28 | 2013-09-17 | Microsoft Corporation | Contextual gravitation of datasets and data services |
| US9722972B2 (en) | 2012-02-26 | 2017-08-01 | Oracle International Corporation | Methods and apparatuses for secure communication |
| US9141596B2 (en) * | 2012-05-02 | 2015-09-22 | Google Inc. | System and method for processing markup language templates from partial input data |
| US9348677B2 (en) | 2012-10-22 | 2016-05-24 | Palantir Technologies Inc. | System and method for batch evaluation programs |
| US9081975B2 (en) | 2012-10-22 | 2015-07-14 | Palantir Technologies, Inc. | Sharing information between nexuses that use different classification schemes for information access control |
| US8892576B2 (en) * | 2012-10-26 | 2014-11-18 | International Business Machines Corporation | Ordering and presenting a set of data tuples |
| US9501761B2 (en) | 2012-11-05 | 2016-11-22 | Palantir Technologies, Inc. | System and method for sharing investigation results |
| US9123086B1 (en) | 2013-01-31 | 2015-09-01 | Palantir Technologies, Inc. | Automatically generating event objects from images |
| US10037314B2 (en) | 2013-03-14 | 2018-07-31 | Palantir Technologies, Inc. | Mobile reports |
| US9740369B2 (en) | 2013-03-15 | 2017-08-22 | Palantir Technologies Inc. | Systems and methods for providing a tagging interface for external content |
| US10275778B1 (en) | 2013-03-15 | 2019-04-30 | Palantir Technologies Inc. | Systems and user interfaces for dynamic and interactive investigation based on automatic malfeasance clustering of related data in various data structures |
| US8937619B2 (en) | 2013-03-15 | 2015-01-20 | Palantir Technologies Inc. | Generating an object time series from data objects |
| JP6480908B2 (en) | 2013-03-15 | 2019-03-13 | オラクル・インターナショナル・コーポレイション | Protected communication between computers between applications |
| US8909656B2 (en) | 2013-03-15 | 2014-12-09 | Palantir Technologies Inc. | Filter chains with associated multipath views for exploring large data sets |
| US8868486B2 (en) | 2013-03-15 | 2014-10-21 | Palantir Technologies Inc. | Time-sensitive cube |
| US9965937B2 (en) | 2013-03-15 | 2018-05-08 | Palantir Technologies Inc. | External malware data item clustering and analysis |
| US9344422B2 (en) | 2013-03-15 | 2016-05-17 | Oracle International Corporation | Method to modify android application life cycle to control its execution in a containerized workspace environment |
| US9898167B2 (en) | 2013-03-15 | 2018-02-20 | Palantir Technologies Inc. | Systems and methods for providing a tagging interface for external content |
| US8917274B2 (en) | 2013-03-15 | 2014-12-23 | Palantir Technologies Inc. | Event matrix based on integrated data |
| US8903717B2 (en) | 2013-03-15 | 2014-12-02 | Palantir Technologies Inc. | Method and system for generating a parser and parsing complex data |
| US10366149B2 (en) * | 2013-03-15 | 2019-07-30 | Wolfram Research, Inc. | Multimedia presentation authoring tools |
| US9129112B2 (en) | 2013-03-15 | 2015-09-08 | Oracle International Corporation | Methods, systems and machine-readable media for providing security services |
| US8930897B2 (en) | 2013-03-15 | 2015-01-06 | Palantir Technologies Inc. | Data integration tool |
| US8788405B1 (en) | 2013-03-15 | 2014-07-22 | Palantir Technologies, Inc. | Generating data clusters with customizable analysis strategies |
| US20140298243A1 (en) * | 2013-03-29 | 2014-10-02 | Alcatel-Lucent Usa Inc. | Adjustable gui for displaying information from a database |
| US8799799B1 (en) | 2013-05-07 | 2014-08-05 | Palantir Technologies Inc. | Interactive geospatial map |
| US20140366091A1 (en) * | 2013-06-07 | 2014-12-11 | Amx, Llc | Customized information setup, access and sharing during a live conference |
| US9529790B2 (en) | 2013-07-09 | 2016-12-27 | Flipboard, Inc. | Hierarchical page templates for content presentation in a digital magazine |
| US9223773B2 (en) | 2013-08-08 | 2015-12-29 | Palatir Technologies Inc. | Template system for custom document generation |
| US8713467B1 (en) | 2013-08-09 | 2014-04-29 | Palantir Technologies, Inc. | Context-sensitive views |
| US10990924B2 (en) * | 2013-08-30 | 2021-04-27 | Messagepoint Inc. | System and method for variant content management |
| CA2863748C (en) | 2013-09-19 | 2023-06-27 | Prinova, Inc. | System and method for variant content navigation |
| US8938686B1 (en) | 2013-10-03 | 2015-01-20 | Palantir Technologies Inc. | Systems and methods for analyzing performance of an entity |
| US9116975B2 (en) | 2013-10-18 | 2015-08-25 | Palantir Technologies Inc. | Systems and user interfaces for dynamic and interactive simultaneous querying of multiple data stores |
| US8924872B1 (en) | 2013-10-18 | 2014-12-30 | Palantir Technologies Inc. | Overview user interface of emergency call data of a law enforcement agency |
| US9021384B1 (en) | 2013-11-04 | 2015-04-28 | Palantir Technologies Inc. | Interactive vehicle information map |
| US8868537B1 (en) | 2013-11-11 | 2014-10-21 | Palantir Technologies, Inc. | Simple web search |
| US20150143210A1 (en) * | 2013-11-18 | 2015-05-21 | Microsoft Corporation | Content Stitching Templates |
| US9105000B1 (en) | 2013-12-10 | 2015-08-11 | Palantir Technologies Inc. | Aggregating data from a plurality of data sources |
| US9727622B2 (en) | 2013-12-16 | 2017-08-08 | Palantir Technologies, Inc. | Methods and systems for analyzing entity performance |
| US9552615B2 (en) | 2013-12-20 | 2017-01-24 | Palantir Technologies Inc. | Automated database analysis to detect malfeasance |
| US10356032B2 (en) | 2013-12-26 | 2019-07-16 | Palantir Technologies Inc. | System and method for detecting confidential information emails |
| US8832832B1 (en) | 2014-01-03 | 2014-09-09 | Palantir Technologies Inc. | IP reputation |
| US9483162B2 (en) | 2014-02-20 | 2016-11-01 | Palantir Technologies Inc. | Relationship visualizations |
| US9727376B1 (en) | 2014-03-04 | 2017-08-08 | Palantir Technologies, Inc. | Mobile tasks |
| US8935201B1 (en) | 2014-03-18 | 2015-01-13 | Palantir Technologies Inc. | Determining and extracting changed data from a data source |
| US9857958B2 (en) | 2014-04-28 | 2018-01-02 | Palantir Technologies Inc. | Systems and user interfaces for dynamic and interactive access of, investigation of, and analysis of data objects stored in one or more databases |
| US9619557B2 (en) | 2014-06-30 | 2017-04-11 | Palantir Technologies, Inc. | Systems and methods for key phrase characterization of documents |
| US9565147B2 (en) | 2014-06-30 | 2017-02-07 | Go Daddy Operating Company, LLC | System and methods for multiple email services having a common domain |
| US9535974B1 (en) | 2014-06-30 | 2017-01-03 | Palantir Technologies Inc. | Systems and methods for identifying key phrase clusters within documents |
| US9256664B2 (en) | 2014-07-03 | 2016-02-09 | Palantir Technologies Inc. | System and method for news events detection and visualization |
| US9202249B1 (en) | 2014-07-03 | 2015-12-01 | Palantir Technologies Inc. | Data item clustering and analysis |
| US9836203B2 (en) | 2014-07-25 | 2017-12-05 | Axiom One Ltd. | Grid-based visual design environment |
| US9454281B2 (en) | 2014-09-03 | 2016-09-27 | Palantir Technologies Inc. | System for providing dynamic linked panels in user interface |
| CN106663018B (en) | 2014-09-24 | 2020-09-15 | 甲骨文国际公司 | System, method, medium, and device for modifying a lifecycle of a mobile device application |
| US9767172B2 (en) | 2014-10-03 | 2017-09-19 | Palantir Technologies Inc. | Data aggregation and analysis system |
| US9501851B2 (en) | 2014-10-03 | 2016-11-22 | Palantir Technologies Inc. | Time-series analysis system |
| US9984133B2 (en) | 2014-10-16 | 2018-05-29 | Palantir Technologies Inc. | Schematic and database linking system |
| US10846336B2 (en) | 2014-10-30 | 2020-11-24 | Microsoft Technology Licensing, Llc | Authoring tools for synthesizing hybrid slide-canvas presentations |
| US9229952B1 (en) | 2014-11-05 | 2016-01-05 | Palantir Technologies, Inc. | History preserving data pipeline system and method |
| US9043894B1 (en) | 2014-11-06 | 2015-05-26 | Palantir Technologies Inc. | Malicious software detection in a computing system |
| US10552994B2 (en) | 2014-12-22 | 2020-02-04 | Palantir Technologies Inc. | Systems and interactive user interfaces for dynamic retrieval, analysis, and triage of data items |
| US9348920B1 (en) | 2014-12-22 | 2016-05-24 | Palantir Technologies Inc. | Concept indexing among database of documents using machine learning techniques |
| US9367872B1 (en) | 2014-12-22 | 2016-06-14 | Palantir Technologies Inc. | Systems and user interfaces for dynamic and interactive investigation of bad actor behavior based on automatic clustering of related data in various data structures |
| US10362133B1 (en) | 2014-12-22 | 2019-07-23 | Palantir Technologies Inc. | Communication data processing architecture |
| US9817563B1 (en) | 2014-12-29 | 2017-11-14 | Palantir Technologies Inc. | System and method of generating data points from one or more data stores of data items for chart creation and manipulation |
| US9870205B1 (en) | 2014-12-29 | 2018-01-16 | Palantir Technologies Inc. | Storing logical units of program code generated using a dynamic programming notebook user interface |
| US9335911B1 (en) | 2014-12-29 | 2016-05-10 | Palantir Technologies Inc. | Interactive user interface for dynamic data analysis exploration and query processing |
| US10372879B2 (en) | 2014-12-31 | 2019-08-06 | Palantir Technologies Inc. | Medical claims lead summary report generation |
| US10803106B1 (en) | 2015-02-24 | 2020-10-13 | Palantir Technologies Inc. | System with methodology for dynamic modular ontology |
| US9727560B2 (en) | 2015-02-25 | 2017-08-08 | Palantir Technologies Inc. | Systems and methods for organizing and identifying documents via hierarchies and dimensions of tags |
| EP3070622A1 (en) | 2015-03-16 | 2016-09-21 | Palantir Technologies, Inc. | Interactive user interfaces for location-based data analysis |
| US9886467B2 (en) | 2015-03-19 | 2018-02-06 | Plantir Technologies Inc. | System and method for comparing and visualizing data entities and data entity series |
| US9454785B1 (en) | 2015-07-30 | 2016-09-27 | Palantir Technologies Inc. | Systems and user interfaces for holistic, data-driven investigation of bad actor behavior based on clustering and scoring of related data |
| US9996595B2 (en) | 2015-08-03 | 2018-06-12 | Palantir Technologies, Inc. | Providing full data provenance visualization for versioned datasets |
| US9456000B1 (en) | 2015-08-06 | 2016-09-27 | Palantir Technologies Inc. | Systems, methods, user interfaces, and computer-readable media for investigating potential malicious communications |
| US9600146B2 (en) | 2015-08-17 | 2017-03-21 | Palantir Technologies Inc. | Interactive geospatial map |
| US10489391B1 (en) | 2015-08-17 | 2019-11-26 | Palantir Technologies Inc. | Systems and methods for grouping and enriching data items accessed from one or more databases for presentation in a user interface |
| US10853378B1 (en) | 2015-08-25 | 2020-12-01 | Palantir Technologies Inc. | Electronic note management via a connected entity graph |
| US11150917B2 (en) | 2015-08-26 | 2021-10-19 | Palantir Technologies Inc. | System for data aggregation and analysis of data from a plurality of data sources |
| US9485265B1 (en) | 2015-08-28 | 2016-11-01 | Palantir Technologies Inc. | Malicious activity detection system capable of efficiently processing data accessed from databases and generating alerts for display in interactive user interfaces |
| US10706434B1 (en) | 2015-09-01 | 2020-07-07 | Palantir Technologies Inc. | Methods and systems for determining location information |
| US9576015B1 (en) | 2015-09-09 | 2017-02-21 | Palantir Technologies, Inc. | Domain-specific language for dataset transformations |
| US10430501B2 (en) | 2015-09-18 | 2019-10-01 | International Business Machines Corporation | Mapping of documents with global tagging map |
| US10296617B1 (en) | 2015-10-05 | 2019-05-21 | Palantir Technologies Inc. | Searches of highly structured data |
| US9542446B1 (en) | 2015-12-17 | 2017-01-10 | Palantir Technologies, Inc. | Automatic generation of composite datasets based on hierarchical fields |
| US9823818B1 (en) | 2015-12-29 | 2017-11-21 | Palantir Technologies Inc. | Systems and interactive user interfaces for automatic generation of temporal representation of data objects |
| US9612723B1 (en) | 2015-12-30 | 2017-04-04 | Palantir Technologies Inc. | Composite graphical interface with shareable data-objects |
| US10248722B2 (en) | 2016-02-22 | 2019-04-02 | Palantir Technologies Inc. | Multi-language support for dynamic ontology |
| US10698938B2 (en) | 2016-03-18 | 2020-06-30 | Palantir Technologies Inc. | Systems and methods for organizing and identifying documents via hierarchies and dimensions of tags |
| US10007674B2 (en) | 2016-06-13 | 2018-06-26 | Palantir Technologies Inc. | Data revision control in large-scale data analytic systems |
| US10324609B2 (en) | 2016-07-21 | 2019-06-18 | Palantir Technologies Inc. | System for providing dynamic linked panels in user interface |
| US10719188B2 (en) | 2016-07-21 | 2020-07-21 | Palantir Technologies Inc. | Cached database and synchronization system for providing dynamic linked panels in user interface |
| US10437840B1 (en) | 2016-08-19 | 2019-10-08 | Palantir Technologies Inc. | Focused probabilistic entity resolution from multiple data sources |
| US10102229B2 (en) | 2016-11-09 | 2018-10-16 | Palantir Technologies Inc. | Validating data integrations using a secondary data store |
| US10318630B1 (en) | 2016-11-21 | 2019-06-11 | Palantir Technologies Inc. | Analysis of large bodies of textual data |
| US9946777B1 (en) | 2016-12-19 | 2018-04-17 | Palantir Technologies Inc. | Systems and methods for facilitating data transformation |
| US10460602B1 (en) | 2016-12-28 | 2019-10-29 | Palantir Technologies Inc. | Interactive vehicle information mapping system |
| US9922108B1 (en) | 2017-01-05 | 2018-03-20 | Palantir Technologies Inc. | Systems and methods for facilitating data transformation |
| US10956406B2 (en) | 2017-06-12 | 2021-03-23 | Palantir Technologies Inc. | Propagated deletion of database records and derived data |
| US10691729B2 (en) | 2017-07-07 | 2020-06-23 | Palantir Technologies Inc. | Systems and methods for providing an object platform for a relational database |
| CN107169250A (en) * | 2017-07-12 | 2017-09-15 | 九江海天设备制造有限公司 | A kind of method for determining marine air intensity |
| US10403011B1 (en) | 2017-07-18 | 2019-09-03 | Palantir Technologies Inc. | Passing system with an interactive user interface |
| US10956508B2 (en) | 2017-11-10 | 2021-03-23 | Palantir Technologies Inc. | Systems and methods for creating and managing a data integration workspace containing automatically updated data models |
| US11599369B1 (en) | 2018-03-08 | 2023-03-07 | Palantir Technologies Inc. | Graphical user interface configuration system |
| US10754822B1 (en) | 2018-04-18 | 2020-08-25 | Palantir Technologies Inc. | Systems and methods for ontology migration |
| US10885021B1 (en) | 2018-05-02 | 2021-01-05 | Palantir Technologies Inc. | Interactive interpreter and graphical user interface |
| US11461355B1 (en) | 2018-05-15 | 2022-10-04 | Palantir Technologies Inc. | Ontological mapping of data |
| US11119630B1 (en) | 2018-06-19 | 2021-09-14 | Palantir Technologies Inc. | Artificial intelligence assisted evaluations and user interface for same |
| US11657061B2 (en) * | 2018-06-22 | 2023-05-23 | Otsuka America Pharmaceutical, Inc. | Application programming interface using digital templates to extract information from multiple data sources |
| US11295073B2 (en) | 2018-08-01 | 2022-04-05 | Microsoft Technology Licensing, Llc | Cross-application ingestion and restructuring of spreadsheet content |
| US11182538B2 (en) * | 2018-08-01 | 2021-11-23 | Microsoft Technology Licensing, Llc | Conversational user interface logic for cross-application ingestion and restructuring of content |
| US11681760B2 (en) | 2018-08-01 | 2023-06-20 | Microsoft Technology Licensing, Llc | Cross-application ingestion and restructuring of content |
| US11113447B2 (en) | 2018-08-01 | 2021-09-07 | Microsoft Technology Licensing, Llc | Cross-application ingestion and restructuring of slide presentation content |
| US11461535B2 (en) * | 2020-05-27 | 2022-10-04 | Bank Of America Corporation | Video buffering for interactive videos using a markup language |
| US11900052B2 (en) * | 2020-11-11 | 2024-02-13 | Microsoft Technology Licensing, Llc | Automatic generation of transformations of formatted templates using deep learning modeling |
| US11507628B1 (en) * | 2021-05-13 | 2022-11-22 | Onspring Technologies LLC | Process automation platform using document database |
Family Cites Families (31)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5729730A (en) * | 1995-03-28 | 1998-03-17 | Dex Information Systems, Inc. | Method and apparatus for improved information storage and retrieval system |
| US5963938A (en) * | 1996-05-17 | 1999-10-05 | Novell Inc. | Automatic, context-organizing, query interface |
| US5913214A (en) * | 1996-05-30 | 1999-06-15 | Massachusetts Inst Technology | Data extraction from world wide web pages |
| US5794247A (en) * | 1996-10-25 | 1998-08-11 | International Business Machines Corporation | Method for representing data from non-relational, non-object-oriented datastores as queryable datastore persistent objects |
| US6085190A (en) * | 1996-11-15 | 2000-07-04 | Digital Vision Laboratories Corporation | Apparatus and method for retrieval of information from various structured information |
| US6192381B1 (en) * | 1997-10-06 | 2001-02-20 | Megg Associates, Inc. | Single-document active user interface, method and system for implementing same |
| JP3912895B2 (en) * | 1998-04-15 | 2007-05-09 | 富士通株式会社 | Structured data management system, computer-readable recording medium on which structured data management program is recorded, and structured data management method |
| US6360246B1 (en) * | 1998-11-13 | 2002-03-19 | The Nasdaq Stock Market, Inc. | Report generation architecture for remotely generated data |
| US6529217B1 (en) * | 1999-06-15 | 2003-03-04 | Microsoft Corporation | System and method for graphically displaying a set of data fields |
| US6601071B1 (en) * | 1999-08-04 | 2003-07-29 | Oracle International Corp. | Method and system for business to business data interchange using XML |
| US6694321B1 (en) * | 1999-09-23 | 2004-02-17 | Affymetrix, Inc. | System, method, and product for development and maintenance of database-related software applications |
| US6766330B1 (en) * | 1999-10-19 | 2004-07-20 | International Business Machines Corporation | Universal output constructor for XML queries universal output constructor for XML queries |
| US6826727B1 (en) * | 1999-11-24 | 2004-11-30 | Bitstream Inc. | Apparatus, methods, programming for automatically laying out documents |
| JP3879350B2 (en) | 2000-01-25 | 2007-02-14 | 富士ゼロックス株式会社 | Structured document processing system and structured document processing method |
| US6785673B1 (en) * | 2000-02-09 | 2004-08-31 | At&T Corp. | Method for converting relational data into XML |
| US6725426B1 (en) * | 2000-03-17 | 2004-04-20 | Broadvision, Inc. | Mechanism for translating between word processing documents and XML documents |
| US7213017B2 (en) * | 2000-03-17 | 2007-05-01 | Microsoft Corporation | Systems and methods for transforming query results into hierarchical information |
| US6934712B2 (en) * | 2000-03-21 | 2005-08-23 | International Business Machines Corporation | Tagging XML query results over relational DBMSs |
| US6684204B1 (en) * | 2000-06-19 | 2004-01-27 | International Business Machines Corporation | Method for conducting a search on a network which includes documents having a plurality of tags |
| US6948134B2 (en) * | 2000-07-21 | 2005-09-20 | Microsoft Corporation | Integrated method for creating a refreshable Web Query |
| US7260777B2 (en) * | 2001-08-17 | 2007-08-21 | Desknet Inc. | Apparatus, method and system for transforming data |
| US7233940B2 (en) * | 2000-11-06 | 2007-06-19 | Answers Corporation | System for processing at least partially structured data |
| US6925631B2 (en) * | 2000-12-08 | 2005-08-02 | Hewlett-Packard Development Company, L.P. | Method, computer system and computer program product for processing extensible markup language streams |
| EP1430389A4 (en) * | 2001-08-23 | 2008-04-16 | Efunds Corp | Method and apparatus for formatting a data grid for the display of a view |
| GB2383662B (en) | 2001-11-26 | 2005-05-11 | Evolution Consulting Group Plc | Creating XML documents |
| US7146564B2 (en) * | 2001-12-21 | 2006-12-05 | Xmlcities, Inc. | Extensible stylesheet designs using meta-tag and/or associated meta-tag information |
| US7035837B2 (en) * | 2002-01-30 | 2006-04-25 | Benefitnation | Document component management and publishing system |
| AUPS084902A0 (en) | 2002-03-01 | 2002-03-28 | Speedlegal Holdings Inc | A document assembly system |
| US20060041839A1 (en) * | 2003-04-03 | 2006-02-23 | Peter Kassan | System and method for providing formatted print pages |
| US7558841B2 (en) * | 2003-05-14 | 2009-07-07 | Microsoft Corporation | Method, system, and computer-readable medium for communicating results to a data query in a computer network |
| US7363581B2 (en) | 2003-08-12 | 2008-04-22 | Accenture Global Services Gmbh | Presentation generator |
-
2004
- 2004-08-10 US US10/915,082 patent/US7363581B2/en active Active
- 2004-08-11 CA CA2671284A patent/CA2671284C/en not_active Expired - Fee Related
- 2004-08-11 EP EP04764068A patent/EP1661030A2/en not_active Ceased
- 2004-08-11 CA CA2535093A patent/CA2535093C/en not_active Expired - Fee Related
- 2004-08-11 EP EP08168868A patent/EP2068253A3/en not_active Ceased
- 2004-08-11 CA CA2669479A patent/CA2669479C/en not_active Expired - Fee Related
- 2004-08-11 WO PCT/EP2004/009071 patent/WO2005015378A2/en active Search and Examination
-
2008
- 2008-02-26 US US12/037,181 patent/US7761784B2/en not_active Expired - Fee Related
-
2010
- 2010-06-04 US US12/793,811 patent/US8429519B2/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| US20090006459A1 (en) | 2009-01-01 |
| US20100241657A1 (en) | 2010-09-23 |
| WO2005015378A2 (en) | 2005-02-17 |
| US7761784B2 (en) | 2010-07-20 |
| CA2669479A1 (en) | 2005-02-17 |
| CA2535093A1 (en) | 2005-02-17 |
| CA2671284C (en) | 2011-10-25 |
| EP2068253A3 (en) | 2009-07-01 |
| WO2005015378A3 (en) | 2005-08-11 |
| US7363581B2 (en) | 2008-04-22 |
| US20050039119A1 (en) | 2005-02-17 |
| EP2068253A2 (en) | 2009-06-10 |
| CA2535093C (en) | 2010-04-13 |
| EP1661030A2 (en) | 2006-05-31 |
| CA2671284A1 (en) | 2005-02-17 |
| US8429519B2 (en) | 2013-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2669479C (en) | Generating end-user presentations from structured data | |
| US7114123B2 (en) | User controllable data grouping in structural document translation | |
| US7308458B2 (en) | System for normalizing and archiving schemas | |
| US7143344B2 (en) | Transformation stylesheet editor | |
| US5603025A (en) | Methods for hypertext reporting in a relational database management system | |
| US7634492B2 (en) | Aggregate data view | |
| US8887036B2 (en) | Automatic linking of documents | |
| US20040181543A1 (en) | Method of using recommendations to visually create new views of data across heterogeneous sources | |
| US8527867B2 (en) | Enabling users to edit very large XML data | |
| US7401075B2 (en) | System for viewing and indexing mark up language messages, forms and documents | |
| US6915303B2 (en) | Code generator system for digital libraries | |
| US7827205B2 (en) | Bi-directional data mapping tool | |
| US20090313539A1 (en) | Information processor, information processing method, and recording medium | |
| JP2004240954A (en) | Method for presenting hierarchical data | |
| US20170154019A1 (en) | Template-driven transformation systems and methods | |
| US7747628B2 (en) | System and method for automated construction, retrieval and display of multiple level visual indexes | |
| JP3842576B2 (en) | Structured document editing method and structured document editing system | |
| EP1304630A2 (en) | Report generating system | |
| WO2001031427A9 (en) | Method and system for automatically generating an application program based upon data characteristics | |
| Škrbić et al. | Bibliographic records editor in XML native environment | |
| Zoller et al. | WEBCON: a toolkit for an automatic, data dictionary based connection of databases to the WWW | |
| AU2003270989B2 (en) | Method of Using Recommendations to Visually Create New Views of Data Across Heterogeneous Sources | |
| Wempen | Teach Yourself VISUALLY Access 2010 | |
| Peake et al. | Oracle Application Express End User's Guide, Release 4.2 E35124-04 | |
| Bands | Bands and Groups |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20220811 |