The present invention generally relates to data processing and more particularly to processing of GUI based specification for form processing and database mapping.
Forms are used to collect data in field about various activities (e.g., field surveys or maintenance checks). The data captured in forms format needs to be stored in a computer database. However, the data form and its field structure needs to be mapped to a database schema, which may not be identical to the field structure and layout of the form.
One approach would be to enable manual mapping of forms with their layout structure into a database mapping when designing databases. However, addition of new forms or changes to the older forms and databases is a possibility over time and hence can require a change in the mapping between the forms and the database schema. Hence, there is a need for a technique(s) for conveniently mapping a form data layout to a database schema.
A database maintainer can manually design or map a table that maps to forms which are used to collect data. However, the process would be relatively laborious if the number of forms is significant and/or if the forms contain detailed table structures in them. Hence, there is a need for an interactive and convenient system that can enable faster mapping of forms to databases.
In one aspect of the invention, a GUI (Graphical User Interface) supported specification method for form field extraction and database mapping in a computer system includes converting a form file into a fixed electronic document format by using GUI which is used to specify the form file and conversion parameters. Fields are extracted from the fixed electronic document format by using the GUI that is used to specify the fields to be extracted; and mapping is performed for the fields into the database schema by using a GUI, which is used to specify the mapping between the fields and the database schema.
In another aspect of the invention, a multi-layer form field extraction and database mapping process is disclosed that includes converting a form file into a first layer format and then extracting fields from the first layer format through a graphical user interface by selecting portions of the first layer format and storing the selected portions in a second layer format. The fields stored in the second layer are mapped to a database schema.
Exemplary embodiments of the present invention are described with reference to the accompanying drawings, of which:
The exemplary embodiments of the present invention will be described with reference to the appended drawings.
The below steps 12-16 for converting, extracting and mapping are performed using a Graphical User Interface (GUI). At a step 12, a datasheet is converted from an electronic format (e.g., a word processor format) to a fixed document format (e.g., a Portable Document Format file—PDF) to maintain the internal alignment and appearance of the document. This converted PDF file forms a first layer of the form data processing and is performed through a GUI with user specifying the files to convert. The conversion process can be controlled through parameters. For example, conversion parameters can be the length of the file to be converted, batch processing of files, etc.
At a step 14, the converted PDF file is processed to create forms in an XML (extendible Markup Language) format as a first layer of processed form data. The XML format file is created by an extraction process that extracts information fields (e.g., header fields, radio fields, table row/column, entry fields, footer fields, etc.) in the PDF file. This extracted XML file forms a second layer of the form data processing and can be used to directly map the fields in the first layer (PDF file) onto a database table(s) for either importing or exporting data to the database. This step 14 is performed through a GUI with user specifying the field areas that are to be extracted.
At a step 16 a XML form to database mapping is performed to map the various information fields in the XML form that are extracted, for example, the header fields, radio fields, table row/column, entry fields, footer fields, etc., are mapped onto fields in database tables on a database(s). A multi-layer form data processing uses PDF and XML layers to enable a user to create a mapping from an electronic document format to a database. This step 16 is performed through a GUI with the user specifying the mapping between the extracted fields and the database tables.
A datasheet form file is shown as loaded in the interface 18 and can be divided into different fields, for example, into header fields 22, radio fields 24, tables 26, entry fields 28 and footer fields 30. Those skilled in the art will appreciate that the fields mentioned above are only examples and any other types of fields on a form can be extracted to be mapped into a database.
Upon a user giving a command to extract the fields, the form extractor 20 plug-in extracts the field information and stores in XML format for data collection in the fields using a data-collector procedure (not shown) Each type of field can be extracted individually through user commands to build a database mapping.
Similar to the above extraction of header fields 34, the radio fields 24 (See
The table dialog box 40 shows the table fields 42 that were extracted from the table 44. To map the extracted table fields 42 to a particular table, a drop down list of available tables 46 allows user to map a field from the table 44 to any of the available tables 46. This enables the user to map the fields of the table 44 in the datasheet form 32 to multiple different tables. Thereafter a column list 48 is displayed to choose a column from the selected table from the tables 46 to which the one selected field 42 should be mapped to. This process is repeated for all the fields in the rows of the table 44 if necessary.
Entry fields 28 can also be similarly extracted from a user demarcating the entry areas and then extracting the fields in that area that can be associated with appropriate tables.
Database mapping is performed through GUI selections described above for header fields, footer fields, tables and other fields in the PDF file form. The table in the form with groups 52 and 54 is mapped on to the database table 64's fields style number 66b, serial number 68b and PM 70b which map directly to the table fields style number 66a, serial number 68a and PM 70a. The header field 74b is mapped to the database table 64's field “chargeNo” 74a; the radio fields of disassembly 76b and assembly 78b map to database field 64's fields 76a and 76b. The footer fields of 78b and 80b “reviewed by” and “date” map onto database fields 78b and 80b.
The computer platform 101 also includes an operating system and micro instruction code. The various processes and functions described herein may either be part of the micro instruction code or part of the application program (or a combination thereof) which is executed via the operating system. In addition, various other peripheral devices may be connected to the computer platform such as an additional data storage device and a printing device.
It is to be further understood that, because some of the constituent system components and method steps depicted in the accompanying figures may be implemented in software, the actual connections between the system components (or the process steps) may differ depending upon the manner in which the present invention is programmed in an exemplary embodiment of the invention. Given the teachings of the present invention provided herein, one of ordinary skill in the related art will be able to contemplate these and similar implementations or configurations of the present invention.
While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims.
This application claims the benefit of U.S. Provisional Application No. 60/568,809 filed on May 6, 2004, titled as “GUI Support Specifications for Automating Form Field Extraction with Database Mapping”, contents of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5283887 | Zachery | Feb 1994 | A |
5708828 | Coleman | Jan 1998 | A |
5781914 | Stork et al. | Jul 1998 | A |
5956422 | Alam | Sep 1999 | A |
6003048 | Fallside | Dec 1999 | A |
6031625 | Sherman et al. | Feb 2000 | A |
6173073 | Wang | Jan 2001 | B1 |
6202072 | Kuwahara | Mar 2001 | B1 |
6336124 | Alam et al. | Jan 2002 | B1 |
6408302 | Lee et al. | Jun 2002 | B1 |
6442573 | Schiller et al. | Aug 2002 | B1 |
6549922 | Srivastava et al. | Apr 2003 | B1 |
6662186 | Esquibel et al. | Dec 2003 | B1 |
6725426 | Pavlov | Apr 2004 | B1 |
6757870 | Stinger | Jun 2004 | B1 |
6996589 | Jayaram et al. | Feb 2006 | B1 |
20010054046 | Mikhailov et al. | Dec 2001 | A1 |
20020116371 | Dodds et al. | Aug 2002 | A1 |
20020129006 | Emmett et al. | Sep 2002 | A1 |
20020178183 | Meding | Nov 2002 | A1 |
20030140055 | Doney et al. | Jul 2003 | A1 |
20030140311 | Lemon et al. | Jul 2003 | A1 |
20030142128 | Reulein et al. | Jul 2003 | A1 |
20040019693 | Grow et al. | Jan 2004 | A1 |
20040181746 | McLure et al. | Sep 2004 | A1 |
20050034062 | Bufkin et al. | Feb 2005 | A1 |
20050071347 | Chau et al. | Mar 2005 | A1 |
20060031757 | Vincent, III | Feb 2006 | A9 |
Number | Date | Country |
---|---|---|
1143357 | Oct 2001 | EP |
1253530 | Oct 2002 | EP |
WO 03083700 | Oct 2003 | WO |
WO 03088032 | Oct 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20050273573 A1 | Dec 2005 | US |
Number | Date | Country | |
---|---|---|---|
60568809 | May 2004 | US |