JP2006119888A - Business form data conversion apparatus and business form data conversion program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a business form data conversion apparatus and a business form data conversion program capable of efficiently storing data to an RDB even from a business form in which data is frequently modified or a business form having a complex data structure. <P>SOLUTION: A business form data conversion apparatus 100 is provided with a business form input part 11 for acquiring a key and a value indicating an object specified by a user, a keyed data XML mapping table 3 for storing the key in an XML format, a business form XML data 5 for storing the value in the XML format, a screen-XML mapping part 12 for generating keyed data by obtaining the key and the value, a mapping part 15 for generating a keyed RDB mapping table 6 on the basis of the keyed data and an XML tag, a conversion part 16 for converting substitutably a subelement data into an SQL syntax when the XML tag includes the subelement data, and an RDB storage part 18 for storing the SQL syntax converted according to the object. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a form data conversion apparatus and a form data conversion program that can be efficiently stored in an RDB even from a form with many data changes or a form having a complicated data structure.

In the case of storing / retrieving a structured document such as XML (eXtensible Markup Language), there is a method using an RDB (relational database). At this time, there is a method of generating SQL (Structured Query Language) that directly writes XML into a database using an XML schema in order to reduce search costs (see, for example, Patent Document 1). In the apparatus used in this method, the search target determination unit determines whether or not the data input from the input device is stored in the RDB, and the XML-RDB mapping rule storage unit determines the target to be stored. .
JP 2003-256455 A

  However, the method of Patent Document 1 can handle only simple data such as text, and there is a problem that it is difficult to handle data accumulation with a complicated structure or modification of the accumulated data. . Furthermore, when there is a nested structure and the same tag name, it cannot be handled.

  The present invention has been made in view of the above problems, and is a form data conversion apparatus and form data conversion program that can be efficiently stored in an RDB even from a form with many data changes or a form with a complicated data structure. The purpose is to provide.

  In order to solve the above problems, the form data conversion apparatus according to the present invention includes: [a] a form input unit that obtains a key indicating an object designated by the user and a value corresponding to the key from the form data; Stored in keyed data XML mapping storage unit for storing keys in XML format, form XML data storage unit for storing values corresponding to [c] key in XML format, and [d] keyed data XML mapping storage unit A key that stores a key and a value corresponding to the key stored in the form XML data storage unit, and creates a key-attached data including the key and a value corresponding to the key, and an [e] created A mapping unit that creates keyed RDB mapping data including a key and an object name based on the keyed data and the XML tag acquired from the form XML data storage unit; When the XML tag includes child element data, a conversion unit that converts the child element data to be replaceable with an SQL syntax for storing a relational database, an RDB storage unit that stores the SQL syntax converted according to the [G] object, It is a summary to provide.

  A second feature of the present invention is that [a] a computer that converts form data causes a form input unit to acquire a key indicating an object designated by the user and a value corresponding to the key from the form data; [B] An instruction for storing the key in XML format in the keyed data XML mapping storage unit, an instruction for storing a value corresponding to the [c] key in the form XML data storage unit in the XML format, and [d] keyed data The key stored in the XML mapping storage unit and the value corresponding to the key stored in the form XML data storage unit are acquired, and the screen-XML mapping unit creates keyed data including the key and the value corresponding to the key. A key having a key and an object name in the mapping unit based on the command and [e] created keyed data and the XML tag acquired from the form XML data storage unit An instruction for creating attached RDB mapping data, and [f] an XML tag including child element data, an instruction for causing the conversion unit to convert the child element data into replaceable SQL syntax for relational database storage, and [g] The gist of the invention is that it is a form data conversion program that executes an instruction to store an SQL syntax converted in accordance with an object in an RDB storage unit.

  According to the present invention, even when a data format in which one piece of data is composed of a plurality of attributes is input from the input device, the data is keyed as an XML document using the mapping file, and the key is attached. Data can be stored in the RDB storage unit by mapping it with the RDB.

  Next, embodiments of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals. However, it should be noted that the drawings are schematic.

<First Embodiment>
(Form data converter)
As shown in FIG. 1, a form data conversion apparatus 100 according to an embodiment of the present invention includes a form management subsystem 1 that creates keyed data in which a key is added to data input from a form, and keyed data. The project information management subsystem 2 is configured to appropriately convert, aggregate, and store in the RDB.

  The keyed data refers to data in which a value (value) is bound to a key (name). For example, the keying data in HTML is “<input type =” text ”name =“ IDT_SYSTEM_OUTLINE ”value =” This system is “...” />, and the value (“IDT_SYSTEM_OUTLINE”) value) “This system is ...” is shown as bound data.

  The form management subsystem 1 includes a form management subsystem interface 10, a form input unit 11, a screen-XML mapping unit 12, a keyed data storage unit 13, and a form XML data storage unit 14.

  The form XML data storage unit 14 is an XML data storage unit for the entire form, and includes a keyed data XML mapping table 3 and a form XML data 5 which are keyed data XML mapping storage units. As shown in FIG. 2A, the keyed data XML mapping table 3 stores a key 4a, which is a form key input from the form input unit 11, in an XML format. As shown in FIG. 2C, the form XML data 5 stores the value 4b input from the form input unit 11 in the XML format.

  The keyed data storage unit 13 stores a keyed data table 4 (see FIG. 2B) created based on the keyed data XML mapping table 3 and the form XML data 5.

  The form management subsystem interface 10 is an interface for transmitting and receiving data between the project information management subsystems 2.

  The form input unit 11 prompts the user to input data. For example, an input screen as shown in FIG. 3 described in HTML or the like is presented to the user, and for example, “IDT_SYSTEM_OUTLINE” or the like as a “name” as a form key is entered in the form key field 22, and the system outline of FIG. The screen is displayed, and the user inputs, for example, “This system is ...” into the value column 23 as the value of the form key column 22, and clicks the save button 21. These input methods are examples, and the input may be performed by other methods.

  The screen-XML mapping unit 12 creates the keyed data XML mapping table 3 and the form XML data 5 based on the form key and the input value data. Further, the screen-XML mapping unit 12 generates the keyed data table 4 of FIG. 2B based on the keyed data XML mapping table 3 and the form XML data 5, and stores it in the keyed data storage unit 13. .

  For example, if the keyed data XML mapping table 3 in FIG. 2A is created, “IDT_SYSTEM_OUTLINE” in the <key> tag is determined as the key 4a, and the keyed data table 4 in FIG. To store. Further, if the form XML data 5 of FIG. 2C is created, “this system is ...” in the triple tag of <Root> <System> <Outline> is determined as a value 4b, and FIG. Map and store as shown in 2 (b).

  The project information management subsystem 2 includes a mapping unit 15, a conversion unit 16, an SQL generation unit 17, an RDB storage unit 18, a mapping RDB storage unit 19, and a project information management subsystem interface 20.

  The mapping RDB storage unit 19 stores a keyed RDB mapping table 6 in which keyed data is mapped so as to correspond to the RDB as shown in FIG.

  The RDB storage unit 18 stores an SQL sentence generated according to the object.

  The mapping unit 15 acquires the keyed data table 4 from the keyed data storage unit 13 via the form management subsystem interface 10 shown in FIG. 1, creates the keyed RDB mapping table 6 in FIG. Store in the RDB storage unit 19. Further, the mapping unit 15 appropriately acquires the keyed RDB mapping table 6 in the mapping RDB storage unit 19 and delivers it to the SQL generation unit 17.

  As shown in FIG. 5, the converting unit 16 creates SQL data for RDB storage from complex data that provides child elements of an XML tag, such as user ID, user name, Roman user name, user organization code, etc. A type that can be interpreted by the generation unit 17, for example, “user ID”, “user name”, etc. is converted into “userid”, “username”, etc.

  The SQL generation unit 17 is a module that automatically generates SQL from the data generated by the mapping unit 15 and generates information for storing in the RDB storage unit 18.

  The project information management subsystem interface 20 is an interface for exchanging data with the form management subsystem 1.

  The present invention is realized by a CPU (not shown) executing each module in the form management subsystem 1 and the project information management subsystem 2.

(Operation of form data conversion device)
Hereinafter, the operation of the form data conversion apparatus will be described with reference to the flowchart of FIG.

  (A) First, in step S101, the form input unit 11 presents the form input screen in FIG. 3 to the user, and inputs a value for the form name (form key). After the input, the start of the form input process is notified to the system, for example, by clicking the save button 21.

  (B) In step S102, the screen-XML mapping unit 12 receives the form key, and creates the keyed data XML mapping table 3 in FIG. In step S103, the screen-XML mapping unit 12 reads the “key” tag, “Xpath” tag, and “DataType” tag from the created keyed data XML mapping table 3, and in step S104, FIG. The form XML data 5 is read.

  (C) In step S105, the screen-XML mapping unit 12 determines whether “DataType” in the keyed data XML mapping table 3 is text. If there is a description of <DataType> Text </ DataType>, that is, the data type is text as shown in the upper part of FIG. 2A, the process proceeds to step S106. As shown in the lower part of FIG. If there is a description of UserData </ DataType>, that is, the data type is UserData other than text, etc., the process proceeds to step S107.

  (D) In step S106, the screen-XML mapping unit 12 follows <Root> <System> <OutLine> of the form XML data 5 in FIG. 2 (c) according to the path of the “Xpath” tag in FIG. 2 (a). "This system ..." at the position indicated by is acquired as data of value 4b. In step S107, the screen-XML mapping unit 12 follows the path of the “Xpath” tag in FIG. 2A and uses the special logic from the form XML data 5 in FIG. "Yamada", "Taro Yamada", "ABC", and "Director" respectively indicated by UserName>, <UserOrgCode>, and <UserPost> are acquired as data of value 4b. In step S108, each acquired data is stored in the keyed data table 4 of FIG. The processes in steps S105 to S108 are executed until the <Key> in the keyed data XML mapping table 3 disappears.

  (E) In step S109, the project information management subsystem interface 20 acquires the keyed data table 4 from the form management subsystem interface 10 and delivers it to the mapping unit 15. The mapping unit 15 creates the keyed RDB mapping table 6 of FIG. 4 based on the keyed data table 4. In the creation process, the key 4a “IDT_SYSTEM_OUTLINE” in FIG. 2B is mapped as a form key in the <FormKey> tag, and <DataType> is “com.Toshiba_sol. Map as "data.SystemInfo". The keyed RDB mapping table 6 is stored in the mapping RDB storage unit 19. In step S110, the keyed RDB mapping table 6 is acquired from the mapping RDB storage unit 19, and data indicated by each tag of <Key> <FormKey> <Data Type> <Converter> is read. The keyed RDB mapping table 6 is created when the XML data needs to be stored in the RDB storage unit 18, that is, when the data is to be counted.

  (F) In step S111, a conversion process is performed. Details will be described later. In step S112, the SQL generation unit 17 generates an SQL sentence based on the object created by the conversion process. In step S113, the SQL statement is stored in the RDB storage unit 18, and the project information is updated. In addition, when a key is not described, it is not stored in the storage unit 18 in the RDB without being counted.

  Next, the processing of the converting unit 16 in step S111 will be described with reference to the flowchart of FIG. It is assumed that the following processing is performed until there are no form keys to be processed.

  (A) In step S201, it is determined whether or not there is a key 4a (for example, “IDT_SYSTEM_OUTLINE”) designated by the form key in the keyed data table 4 in FIG. In step S202, the object specified by <Data Type> in the keyed data RDB mapping table 6, such as “com.Toshiba_sol.data.SystemInfo” or “com.Toshiba_sol.data.UserData” in FIG. ”Object.

  (B) In step S203, it is determined whether any of the read objects have a converter attribute specified. If the converter attribute is specified, the process proceeds to step S204. If the converter attribute is not specified, the process proceeds to step S209.

  (C) In step S204, the key 4a is extracted from the keyed data table 4 and set to the object “com.Toshiba_sol.data.UserData”. In step S205, as shown in FIG. 6A, a key 4c corresponding to the key 4a, such as “UID”, is set, and data of the key 4a, such as “yamada”, is read from the keyed data table 4. .

  (D) In step S206, the read data is set, and the object “com.Toshiba_sol.data.UserData” specified by <Data Type> is generated as shown in FIG.

  In step S207, a key that requires an object is obtained from the key 4a of the keyed data table 4, and the value 4b shown in FIG. 6 is associated with the described key 4c. In step S208, the acquired key is set for the object. That is, the associated data is set in the object generated in step S206.

  (E) Since the converter process is not performed in step S209, the key and its value specified in the generated object “com.Toshiba_sol.data.SystemInfo” are extracted from the keyed data table 4 as a normal process. Is set as shown in FIG.

  According to the above, even if complicated data is input from the form, the conversion unit 16 specified by the converter attribute can be stored in the RDB storage unit 18, so that the stored data can be easily aggregated. can do.

The structure figure which shows the internal structure of the form data conversion apparatus which concerns on embodiment of this invention. The figure which shows the data structure with which a form management subsystem is provided. The figure which shows the input screen of a form input part. The figure which shows the data structure in a mapping RDB memory | storage part. The figure which shows the data structure of the data provided with two or more child elements of an XML tag. The figure which shows an example of the object which a conversion part produces | generates. The flowchart which shows the whole operation | movement of a form data conversion apparatus. The flowchart which shows operation | movement of a conversion part.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Form management subsystem 2 ... Project information management subsystem 3 ... Mapping table 4 ... Data table with key 4a, 4c ... Key 4b ... Value 5 ... Form XML data 6 ... Mapping table 10 ... Form management subsystem interface 11 ... Form Input unit 12 XML mapping unit 13 Data storage unit with key 14 Data storage unit 15 Mapping unit 16 Conversion unit 17 SQL generation unit 18 RDB storage unit 19 Mapping RDB storage unit 20 Project information management subsystem Interface 100: Form data conversion device

Claims (2)

A form input unit for acquiring a key indicating an object specified by the user and a value corresponding to the key from the form data;
A keyed data XML mapping storage unit for storing the key in XML format;
A form XML data storage unit for storing a value corresponding to the key in an XML format;
A key stored in the keyed data XML mapping storage unit and a value corresponding to the key stored in the form XML data storage unit are acquired, and keyed data including the key and a value corresponding to the key is obtained. Screen to create-XML mapping part,
A mapping unit for creating keyed RDB mapping data including the key and the name of the object based on the created keyed data and the XML tag acquired from the form XML data storage unit;
When the XML tag includes child element data, a conversion unit that converts the child element data into a replaceable SQL syntax for relational database storage;
An RDB storage unit for storing the SQL syntax converted according to the object;
A form data conversion device characterized by comprising: On the computer that converts the form data,
A command that causes the form input unit to acquire a key indicating an object designated by the user and a value corresponding to the key from the form data;
An instruction for storing the key in XML format in a keyed data XML mapping storage unit;
A command for storing a value corresponding to the key in a form XML data storage unit in XML format;
A key stored in the keyed data XML mapping storage unit and a value corresponding to the key stored in the form XML data storage unit are obtained, and the key and a value corresponding to the key are acquired in a screen-XML mapping unit. An instruction to create keyed data comprising:
Based on the created keyed data and the XML tag acquired from the form XML data storage unit, a command for causing the mapping unit to create keyed RDB mapping data including the key and the name of the object;
When the XML tag includes child element data, an instruction that causes the conversion unit to convert the child element data into a replaceable SQL syntax for relational database storage;
An instruction for storing the SQL syntax converted according to the object in an RDB storage unit;
A form data conversion program characterized by causing

Images