JP2007249747A - Common format creation program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily create a standardized common format. <P>SOLUTION: A computer 1 acquires an item A and an item B of a hierarchy A of the common format 2 to be edited as an edit target item 2a, and acquires an item C, an item D, and an item E of a hierarchy B as an edit target item 2b. The computer 1 acquires a list of models 3a-3c created from the existing common format, having the same items as the edit target items 2a, 2b. A model for replacing the edit target item 2a or the edit target item 2b is selected on the basis of a use frequency of the model and a matching count between the edit target items and the items existing in the models 3a-3c. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a common format creation program, and more particularly to a common format creation program for creating a common format used when data is linked between a plurality of systems.

  A method is known in which a common format is defined when data is linked between a plurality of systems, and data is linked via the format. At that time, it is known that items in a plurality of tables constituting a format are displayed in an arbitrary format by mapping (associating) with each other (see, for example, Patent Document 1).

FIG. 51 is a diagram showing conventional data linkage.
The format conversion unit 91b converts the format 91a of the system 91 into the common format 95. Similarly, the format conversion units 92b and 93b respectively convert the format 92a of the system 92 into the common format 95, and convert the format 93a of the system 93 into the common format 95. Further, the system 94 uses the common format 95 as its own format as it is.

One example of a method for constructing such a system will be described with reference to FIG.
(1) First, the formats (input / output formats) 91a, 92a, 93a respectively corresponding to the systems 91, 92, 93 are defined based on the table design information of the systems 91, 92, 93 for which data linkage is desired.

  (2) Based on the formats 91a, 92a, and 93a created in (1), the items of the formats 91a, 92a, and 93a are provided, and a common format 95 that links them to each other is defined.

(3) Information (format conversion information) for mapping the formats 91a, 92a, 93a and the common format 95 is defined.
(4) Create a query for acquiring data of the system for which data linkage is desired.

Here, when creating the common format 95, it is preferable to unify items having the same meaning with the same item name and hierarchical structure. In addition, it is preferable that items that are likely to be added later are previously defined in the common format 95 or modeled. Thereby, a system with high expandability and versatility can be constructed.
JP 2001-243098 A

  By the way, when adding a new system (format) to an already constructed system, it is necessary to change the created common format (common format 95 in FIG. 51). Because it is affected, it is necessary to modify that part.

FIG. 52 is a diagram illustrating a case where a new system is linked.
When a new format 96 a of the system 96 is to be linked, it is necessary to change the common format 95 in order to add a new item to the common format 95.

  However, since the change of the common format 95 also affects the format conversion units 91b, 92b, 93b and the system 94 that use the common format 95, the format conversion unit 91b corresponds to the changed common format 95. 92b, 93b and the system 94 (within the dotted line frame in FIG. 52) need to be changed. In other words, it is necessary to modify the language (for example, SQL (Structured Query Language)) in the application of each system over a wide range. In this case, as described above, it is preferable to previously define items that are likely to be added in preparation for the change of the common format 95 in advance (create a standardized common format). The problem is that its definition largely depends on the skill of the manager.

  The present invention has been made in view of these points, and an object thereof is to provide a common format creation program that can easily create a standardized common format.

In order to solve the above problem, the present invention provides a common format creation program for causing a computer to execute the process shown in FIG.
The common format creation program according to the present invention is a program for creating a common format used when data is linked between a plurality of systems, and a computer that executes the common format creation program has the following functions.

  The computer 1 acquires items A and B in the hierarchy A of the common format 2 to be edited as the edit target item 2a, and acquires items C, item D, and item E in the hierarchy B as the edit target item 2b. Further, the computer 1 acquires a list of templates 3a to 3c that are created from an existing common format and have the same items as the editing target items 2a and 2b. Then, a template that replaces the editing target item 2a or the editing target item 2b is selected based on the number of matches between the items existing in the templates 3a to 3c and the editing target item and the number of times the template is used. In FIG. 1, since the edit target item 2b and the template 3c match, the template 3c is selected as a template to replace the hierarchy B. Thereafter, the hierarchy B is replaced with the template 3c.

  According to such a common format creation program, the edit target items 2a and 2b are acquired by the common format management means 1a (step S1), a list of templates 3a to 3c is acquired (step S2), and templates 3a to 3c are acquired. The template 3c that replaces the editing target item 2b is selected based on the number of matches between the items existing therein and the items of the common format to be edited and the number of times the template is used (step S3), and the editing target item 2b is selected. It is replaced with the template 3c (step S4).

  According to the present invention, a standardized common format can be easily created by applying a template created from an existing common format to a new common format. As a result, it is possible to construct a system that has less influence on the surroundings due to the change and that can be easily maintained.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
First, the outline of the invention applied to the embodiment will be described, and then the specific contents of the embodiment will be described.

FIG. 1 is a schematic diagram showing an invention applied to the embodiment.
The computer 1 shown in FIG. 1 includes common format management means 1a that executes the following functions.

  The common format management unit 1a acquires items A and B included in the hierarchy A of the common format 2 to be edited as the edit target item 2a, and items C, item D, and item E included in the hierarchy B as the edit target item 2b. get. One item to be edited is composed of items for one hierarchy of a child hierarchy or a sibling hierarchy.

  Further, the common format management unit 1a acquires from the template DB 3 a list of templates 3a to 3c created from the existing common format and including at least one identical item among the editing target items 2a and 2b. Then, based on the number of matches between the items existing in the templates 3a to 3c and the editing target item 2a and the number of uses of the templates 3a to 3c, a template for replacing the editing target item 2a is selected. Similarly, a template for replacing the editing target item 2b is selected based on the number of matches between the items existing in the templates 3a to 3c and the editing target item 2b, and the number of uses of the templates 3a to 3c. Thereafter, the hierarchy B is replaced with the template 3c.

  Here, the number of times the template is used refers to the number of common formats in which the template is used. In FIG. 1, since the edit target item 2b and the template 3c match, the template 3c is selected as a template to replace the edit target item 2b. Even if they do not match, the similarity is calculated based on the number of matches between the items existing in the templates 3a to 3c and the editing target item 2a (2b) and the number of times the templates 3a to 3c are used. It is preferable to select the template having the highest number as the template to be replaced with the editing target item 2a (2b).

  According to such a common format creation program, the edit target items 2a and 2b are acquired by the common format management means 1a (step S1), a list of templates 3a to 3c is acquired (step S2), and templates 3a to 3c are acquired. The template 3c that replaces the editing target item 2b is selected based on the number of matches between the item existing in the item and the editing target item and the number of times the template is used (step S3), and the editing target item 2b is replaced with the selected template 3c. (Step S4). Thus, by replacing the editing target item with a template, a standardized common format can be easily created regardless of the skill of the administrator.

Hereinafter, embodiments of the present invention will be specifically described.
FIG. 2 is a diagram illustrating a system configuration example of the present embodiment.
In FIG. 2, a plurality of basic systems 21, 22, 23, 24,... The basic systems 21, 22, 23, 24,... Have basic DBs (databases) 21a, 22a, 23a, 24a,. In the core DBs 21a, 22a, 23a, 24a,..., Data handled by the core systems 21, 22, 23, 24,..., And a link format for performing data link between the core systems are stored. Has been.

  A management device 100 is further connected to the network 10. The management apparatus 100 creates a linkage format unique to the core systems 21, 22, 23, 24,... And distributes them to the core systems 21, 22, 23, 24,.

  Further, the management apparatus 100 creates a common format for the core systems 21, 22, 23, 24,... Based on the cooperation format distributed to the core systems 21, 22, 23, 24,. Each of the core systems 21, 22, 23, 24,... Performs data linkage with other backbone systems through its own linkage format and common format. When creating the common format, the management apparatus 100 creates mapping information that defines the coupling relationship set in the item in order to associate the linkage format with the common format. By creating mapping information in this way, it is possible to refer to and share each other's data. For this reason, it is not necessary to have the same item in a plurality of databases, and an efficient database can be constructed with a minimum capacity.

Furthermore, the management apparatus 100 creates a query for issuing commands such as data search, update, and deletion.
The function of the computer 1 shown in FIG. 1 is provided in the management apparatus 100.

FIG. 3 is a diagram illustrating a hardware configuration example of the management apparatus.
The entire management apparatus 100 is controlled by a CPU (Central Processing Unit) 101. A random access memory (RAM) 102, a hard disk drive (HDD) 103, a graphic processing device 104, an input interface 105, and a communication interface 106 are connected to the CPU 101 via a bus 107.

  The RAM 102 temporarily stores at least part of an OS (Operating System) program and application programs to be executed by the CPU 101. The RAM 102 stores various data necessary for processing by the CPU 101. The HDD 103 stores an OS and application programs. A program file is stored in the HDD 103.

  A monitor 11 is connected to the graphic processing device 104. The graphic processing device 104 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 101. A keyboard 12 and a mouse 13 are connected to the input interface 105. The input interface 105 transmits a signal transmitted from the keyboard 12 or the mouse 13 to the CPU 101 via the bus 107.

  The communication interface 106 is connected to the network 10. The communication interface 106 transmits / receives data to / from another computer via the network 10.

  With the hardware configuration as described above, the processing functions of the present embodiment can be realized. In order to create a common format in a system having such a hardware configuration, the management apparatus 100 is provided with the following functions.

FIG. 4 is a block diagram illustrating functions of the management apparatus.
The management apparatus 100 includes an interface unit 110, a linked format editing unit 120, a common format management unit 130, and a similar word management unit 140.

The interface unit 110 receives an operation of the administrator and reflects the operation content on each unit of the management apparatus 100. In addition, the administrator is made to recognize feedback from each unit.
The linked format editing unit 120 is connected to the format creating unit 120a, the linked format DB 120c, and the common format DB 130a.

  The linkage format editing unit 120 creates a linkage format for linking the backbone systems 21, 22, 23, 24,... To the common format for each of the backbone systems 21, 22, 23, 24,. At this time, the link format editing unit 120 acquires the original format that is the basis of the link format from the format creation unit 120a.

  The linked format editing unit 120 includes a GUI (Graphical User Interface), and displays a format editing screen for editing the original format on the monitor 11. When there is a request to save the edited original format, the edited original format is stored in the cooperative format DB 120c and the common format DB 130a as a cooperative format.

  The format creation unit 120a extracts table definition information and creates an original format using this information. This table definition information is composed of information having a hierarchical structure such as an ER diagram (Entity Relation Diagram).

  The extraction information DB (database) 120b stores the table definition information extracted by the format creation unit 120a and the original format created from the table definition information by the format creation unit 120a.

  Extraction information extracted from the table definition information is stored in the extraction information DB 120b as table information, item information, primary key information, unique key information, reference information, and reference item information. Each of these pieces of information is tabulated and stored in the extraction information DB 120b.

First, the table information stored in the extraction information DB 120b will be described.
FIG. 5 is a diagram illustrating a data structure example of table information stored in the extraction information DB.
The table information table 121b is provided with item name and key columns, and information arranged in the horizontal direction of each column is associated with each other.

A table-specific ID is stored in the table ID column. The primary key is set in the table ID key field.
The table name column stores the name of the table that uniquely identifies this table.

  The reference key set ID column stores the ID of the reference key set held by the table item. If there is no reference key, null is stored. In FIG. 5, the external key is stored in the key field of the reference key set ID.

  Here, the primary key refers to a column or a set of columns that can completely uniquely identify each row of the table, and does not include a null value in all columns. The foreign key is permitted as data when the key value of the table matches the key value of the related table. Logical association between tables is performed to ensure that a value (parent key) exists for a foreign key. The foreign key can have a parent table value or null. The parent key of the foreign key must be a unique key that uniquely constrains each row other than the primary key or table null.

Next, item information stored in the extraction information DB 120b will be described.
FIG. 6 is a diagram illustrating a data structure example of item information stored in the extraction information DB.
The item information table 122b is provided with item name and key columns, and information arranged in the horizontal direction of each column is associated with each other.

In the table ID column, a table-specific ID is stored.
The primary key is set in the table ID key field.
The item ID column stores an ID unique to each item in the table.

The table name column stores the name of the table that uniquely identifies this table.
The item physical name column stores the item physical name.
The item logical name column stores the logical name of the item.

The item data type column stores the data type (character string, numerical value, etc.) of the item. If the item type is other than “item” or “primary key item”, null is stored.
The item data length column stores the data length of the item. If the item type is other than “item” or “primary key item”, null is stored.

Next, primary key information stored in the extracted information DB 120b will be described.
FIG. 7 is a diagram illustrating an example of the data structure of primary key information stored in the extraction information DB.
The main key information table 123b is provided with item name and key columns, and information arranged in the horizontal direction of each column is associated with each other.

The table ID column stores an ID unique to this table. The primary key is set in the table ID key field.
The item ID column stores an ID unique to each item in the table. The main key is set in the item ID key column.

Next, unique key information stored in the extraction information DB 120b will be described.
FIG. 8 is a diagram illustrating a data structure example of the unique key information stored in the extraction information DB.
The unique key information table 124b is provided with item name and key fields, and information arranged in the horizontal direction of each field is associated with each other.

The table ID column stores an ID unique to this table. The primary key is set in the table ID key field.
The unique key set ID field stores an ID indicating a set of unique keys in one table. The primary key is set in the key field of the unique key set ID.

The item ID column stores an ID unique to each item in the table. The main key is set in the item ID key column.
Next, reference information stored in the extraction information DB 120b will be described.

FIG. 9 is a diagram illustrating a data structure example of the reference information stored in the extraction information DB.
The reference information table 125b is provided with item name and key fields, and information arranged in the horizontal direction of each field is associated with each other.

The reference key set ID column stores an ID unique to the reference key set. A primary key is set in the key field of the reference key set ID.
The reference source table ID column stores the reference source table ID.

The table of the reference destination is stored in the column of the reference destination table ID.
Next, reference information stored in the extraction information DB 120b will be described.
FIG. 10 is a diagram illustrating a data structure example of reference information stored in the extraction information DB.

The reference item information table 126b is provided with item name and key columns, and information arranged in the horizontal direction of each column is associated with each other.
The reference key set ID column stores an ID unique to the reference key set. The primary key is set in the table ID key field.

In the column of the reference source item ID, the item ID of the reference source is stored. The primary key is set in the key field of the reference source item ID.
In the column of the reference destination item ID, the reference destination item ID is stored. A primary key is set in the key field of the reference destination item ID.

Returning to FIG. 4, the description will be continued.
The format creation unit 120a automatically defines the hierarchical structure as the original format depending on how the reference keys between the tables are pasted. The hierarchical structure will be described later.

The common format management unit 130 is connected to the cooperative format DB 120c, the common format DB 130a, and the synonym DB 140a.
The common format management unit 130 creates a common format based on the cooperation format extracted from the cooperation format DB 120c, and stores the created common format in the common format DB 130a. In addition, the common format management unit 130 creates mapping information indicating which item corresponds between the cooperation format and the common format, and stores the created mapping information in the mapping DB 130b.

  Here, when creating the common format, the common format management unit 130 extracts a portion that can be a template in the created common format, creates template item information, and stores it in the template DB 130c. Then, it is determined whether there is an item to which the template can be applied in the common format being created. If there is an item to which the template can be applied, the template is applied to the item. Further, by referring to the existing common format, it is determined whether or not there is an item that is likely to be added in the common format being created, and an item that is likely to be added is added to the common format being created.

Furthermore, the common format management unit 130 stores information necessary for learning synonyms in the synonym DB 140a when mapping information is created.
The synonym word management unit 140 is connected to the synonym DB 140a.

  The synonym word management unit 140 extracts information necessary for learning the synonym word from the synonym DB 140a, and creates a synonym word dictionary creation process for the information, thereby creating the latest synonym word list. To do.

Next, the editing operation of the cooperative format editing unit 120 will be described.
FIG. 11 is a diagram illustrating an example of a format editing screen.
The format editing screen 50 includes a linked format name input unit 51a, a hierarchical structure display unit 52a, a save button 53a, an add button 53b, a delete button 53c, an edit button 53d, a read button 53e, and an extract button 53f. And an end button 53g.

The user can edit the format editing screen 50 using the keyboard 12 and the mouse 13.
The cooperative format name input unit 51a can input a cooperative format name for identifying the cooperative format.

  When the user extracts the table definition information, the user presses the read button 53e or the extract button 53f. When the read button 53e is pressed, the already created cooperation format can be read. When the extraction button 53f is pressed, the format creation unit 120a performs an original format extraction operation for extracting the original format from the table definition information, and transmits the original format to the cooperative format editing unit 120. Then, the cooperative format editing unit 120 acquires the original format information and displays it on the hierarchical structure display unit 52a.

  The hierarchical structure display section 52a displays item physical names and item logical names respectively corresponding to the format item type and the format item type constituting the tree structure. The item physical name is displayed on the right side in FIG. 11 of the format item type, and the item logical name is displayed in parentheses on the right side of the item physical name. In FIG. 11, item physical names and item logical names corresponding to the format item types 55a to 55e and the format item types 55a to 55e are displayed.

  The user can select the item physical name and the item logical name using the keyboard 12 and the mouse 13. In FIG. 11, “employee ID” is selected as the item physical name and the item logical name.

  When the user edits the hierarchy or item (node) selected in the original format, the user presses one of the add button 53b, the delete button 53c, and the edit button 53d. When the add button 53b is pressed, an item is added to the child of the selected node. When the delete button 53c is pressed, the selected node is deleted. When the edit button 53d is pressed, the selected node can be edited.

Next, the format item type will be described.
FIG. 12 is a diagram illustrating format item types.
Key items are indicated by black circles. The key item is a key item that has only one key and the same value.

Items are indicated by open circles.
The group hierarchy is indicated by white square marks. A group hierarchy can hold a hierarchy and items belonging to the same category, and can have only one set of subordinate items. For example, “employee information of employee 1”, “employee information of employee 2”, “employee information of employee 3”,. Thus, the structure can be easily understood by putting similar types of information in the same group hierarchy.

  The list hierarchy is indicated by a black square mark. The list hierarchy repeatedly holds data having the same structure as that defined below the hierarchy. For example, “employee list hierarchy” holds “employee information of employee 1,” “employee information of employee 2,” “employee information of employee 3,” and so on. The employee list hierarchy shown in FIG. 11 has job IDs under the employee ID, employee name, and job group hierarchy under the employee list hierarchy, but when the list hierarchy is used, there may be a plurality of this hierarchy corresponding to the number of employees. it can.

  The recursive hierarchy is represented by a mark having a white square in a white square. The recursive hierarchy can recursively hold data having the same structure as the structure under this hierarchy.

The recursive list hierarchy is represented by a mark having a black square inside an open square. Has functions of recursive hierarchy and list hierarchy.
Next, a hierarchical structure to which the above-described format item type is applied will be described.

First, the group hierarchy will be described.
FIG. 13 is a diagram for explaining the group hierarchy.
In FIG. 13, an employee table 1211 and a post table 1212 which are two pieces of table information selected by the user are displayed. A reference key is set for the position ID described in the employee table 1211, and a main key is set for the position ID of the position table 1212. Therefore, it can be seen that the post ID of the employee table 1211 refers to the post ID of the post table 1212. When creating cooperative format information using the two table information, first, the parent table is determined. In FIG. 13, since the job ID of the employee table 1211 refers to the job ID of the job table 1212, the employee table 1211 is a parent and the job table 1212 is a child. In FIG. 13, the reference key of the employee table 1211 and the main key of the post table 1212 are the same number. In other words, there is only one position for each employee. A relationship in which one reference destination exists for one reference source is referred to as a “one-to-one relationship”.

  When the employee table 1211 has repeated items, that is, when there are a plurality of employees, a list hierarchy in which a plurality of job table 1212 is attached to the employee table 1211 is created. Since a primary key is set in the employee ID key column, it is defined as a key item. Since the employee name is an ordinary item, it is defined as an item. Since the post ID of the employee table 1211 and the post ID of the post table 1212 have a one-to-one relationship, a group hierarchy is created. In FIG. 13, a position group hierarchy is created, and each item position ID and position name are created therein. Here, since the post ID is the main key, it is defined as a key item. The title is defined as an item.

Next, the list hierarchy will be described.
FIG. 14 is a diagram for explaining the list hierarchy.
14 is different from FIG. 13 in that a job title language ID exists in the job title table 1213. When job title language IDs are created for item names in the job title table, job titles in different languages, such as Japanese job title “section manager” and English job title “a section manager”, are defined. be able to. In this case, the number of item names for which the primary key is set in the key column of the post table 1213 does not match the number of item names for which the reference key is set in the key column of the employee table 1211 ( Because each does not correspond), there will be multiple title information for each employee. A relationship in which a plurality of reference destinations exist for one reference source is referred to as “one-to-other relationship”. In this case, in the example of FIG. 13, the post group hierarchy is defined, but this time, it is defined as a post list hierarchy. As described above, when the numbers of the reference key and the primary key do not match, the post table 1213 is set as a list hierarchy.

Next, the loop hierarchy will be described.
FIG. 15 is a diagram for explaining a loop hierarchy.
In the employee table 1214, the supervisor ID refers to the employee ID of his / her table. This indicates that the reference operation is repeated until the top boss ID is reached. In the case of FIG. 15, since the employee ID referred to by the boss ID is in a one-to-one relationship, a boss loop hierarchy is created as a recursive hierarchy, and the hierarchy of the table referenced by the reference key is subordinate to it. Define the employee list hierarchy.

Next, the recursive list hierarchy will be described.
FIG. 16 is a diagram for explaining the recursive list hierarchy.
In the employee table 1215, when the supervisor ID for which the reference key is set in the key column tries to recur, the number of the reference key and the primary key does not correspond (due to one-to-other relationship). The recursive list hierarchy of the loop hierarchy and the list hierarchy is created, and the hierarchy of the table referred to by the reference key, that is, the employee list hierarchy is defined under the loop hierarchy.

Returning to FIG. 11, the description will be continued.
When the user saves the edited linkage format, the user presses the save button 53a. When the save button 53a is pressed, the original format edited by the link format editing unit 120 (format information displayed in the hierarchical structure display unit 52a when the save button 53a is pressed) constitutes the link format. It is stored in the linkage format DB 120c as format information and item information.

  When the user ends the collaborative format editing, the user presses the end button 53g. When the end button 53g is pressed, the cooperative format editing unit 120 ends the cooperative format editing operation.

  Next, format information and item information stored in the cooperation format DB 120c will be described. In the cooperative format DB 120c, format information and item information are stored in a table.

FIG. 17 is a diagram illustrating a data structure example of format information stored in the cooperation format DB.
The format information table 121c is provided with item name and key fields, and information arranged in the horizontal direction of each field is associated with each other.

In the column of the cooperation format ID, an ID unique to the cooperation format is stored. This ID is automatic numbering. The primary key is set in the column of the cooperation format ID key.
The column of the cooperation format name stores the name of the table that uniquely identifies this cooperation format.

FIG. 18 is a diagram illustrating a data structure example of item information stored in the cooperation format DB.
The item information table 122c is provided with item name and key fields, and information arranged in the horizontal direction of each field is associated with each other.

In the column of the cooperation format ID, an ID unique to the cooperation format is stored. This ID is automatic numbering.
The format item ID column stores an ID unique to the format item. This ID is automatic numbering.

In the format item type column, one of “item”, “primary key item”, “group hierarchy”, “list hierarchy”, “recursive hierarchy”, and “recursive list hierarchy” is stored.
The item physical name column stores the item physical name.

The item logical name column stores the logical name of the item.
The item data type column stores the data type (character string, numerical value, etc.) of the item. If the item type is other than “item” or “primary key item”, null is stored.

The item data length column stores the data length of the item. If the item type is other than “item” or “primary key item”, null is stored.
In the parent format item ID column, the format item ID of the parent node is stored. If self is the root, null is stored.

In the recursive format item ID column, the format item ID that is recursed is stored only in the case of “recursive hierarchy” and “recursive list hierarchy”.
A numerical value indicating the display order in the same hierarchy is stored in the display order column. The larger the value, the later it will be displayed.

The valid / invalid flag field stores a flag indicating whether or not this item is to be linked.
Next, the cooperative format creation operation will be described.

FIG. 19 is a flowchart showing the cooperative format creation operation.
First, the format creation unit 120a executes format extraction processing (step S11).

  Next, the cooperation format editing unit 120 uses the original format (format information and item information constituting the original format) obtained by the format extraction process, and the existing cooperation format (format information constituting the cooperation format and the format information included in the cooperation format DB 120c). An environment for reading the item information) and executing the editing of the cooperation format is prepared (step S12).

  When the editing operation of the cooperative format is executed by the user and the save button 53a is pressed, the cooperative format editing unit 120 stores the format information and item information of the cooperative format in the cooperative format DB 120c (step S13).

This completes the cooperative format creation operation.
Next, the format extraction process in step S11 will be described.
FIG. 20 is a flowchart showing the format extraction process.

First, table definition information is acquired (step S21).
Next, the user waits for an instruction to set the reference relationship of the extraction table (step S22). Specifically, the table information to be used is selected by the user, and it is determined whether or not the parent-child relationship (reference relationship) of the selected table information has been set (step S22). When there is a single table to be extracted, since there is no parent-child relationship, it is possible to instruct not to set a reference relationship. When there is an instruction to set a reference relationship (Yes in step S22), the item information of the cooperation format being created stored in the cooperation format DB 120c is initialized (step S23).

Next, a format definition creation process is performed (step S24).
The format extraction process is thus completed.
Next, a format definition creation process will be described.

FIG. 21 is a flowchart showing format definition creation processing.
First, the table information T [x] to be formatted is acquired (step S31).
Next, one piece of unselected table information T is extracted from the table information T [x], and reference information of the table is acquired (step S32).

Next, it is determined whether or not the table information T is referred to by another table of the table information T [x] (step S33).
When the table information T is referred to by another table of the table information T [x] (Yes in step S33), the process proceeds to step S37. On the other hand, when the table information T is not referred to by another table of the table information T [x] (No in step S33), the table information T is set as a root item (step S34). Here, as the item information of the table information T set in the root item, the table physical name of the table information T is set as the item physical name, the table logical name of the table information T is set as the item logical name, A group hierarchy is set for the format item type, null is set for the parent item format ID, and valid is set for the valid / invalid flag.

Next, cooperative format item creation processing is performed to create item information, and the created item information is stored in the cooperative format DB 120c (step S35).
Next, cooperative format hierarchy creation processing is performed to create item information, and the created item information is stored in the cooperative format DB 120c (step S36).

  Next, it is determined whether or not all the table information T in the table information T [x] has been verified (step S37). If all the table information T has not been verified (No in step S37), the process proceeds to step S32, where new table information T is extracted and the operation is continued. On the other hand, when all the table information T is verified (Yes in step S37), the mapping information stored in the mapping DB 130b described later is initialized (step S38). This completes the format definition process.

Next, cooperative format item creation processing will be described.
FIG. 22 is a flowchart showing the linked format item creation process.
First, one item I belonging to the table information is acquired from the item information stored in the extraction information DB 120b (step S41).

  Next, it is determined whether item I is a reference key (step S42). When the item I is a reference key (Yes in step S42), the process proceeds to step S47. On the other hand, if item I is not a reference key (No in step S42), it is determined whether item I is a primary key (step S43). When the item I is a primary key (Yes in step S43), the format item type is set to “primary key item” (step S44), and the process proceeds to step S46. On the other hand, when the item I is not the primary key (No in step S43), the format item type is set to “item” (step S45), and the process proceeds to step S46.

Next, the cooperation format item is added to the item information and stored in the cooperation format DB 120c (step S46).
Next, it is determined whether or not all items I have been verified (step S47). If all items I have not been verified (No in step S47), the process proceeds to step S41, and the linked format item creation process is continued. On the other hand, when all the items I have been verified (Yes in step S47), the cooperative format item creation process ends.

Next, the cooperative format hierarchy creation process will be described.
FIG. 23 is a flowchart showing the cooperative format hierarchy creation processing.
First, a list of reference information Ft [x] using the table information T [x] as a reference source is obtained from the extracted information DB 120b (step S51).

Next, one piece of reference information Ft is acquired from the list Ft [x] (step S52).
Next, a list Fi [y] of reference item information is obtained using the reference key set ID of the reference information Ft as a key (step S53).

Next, a recursive loop check is performed to determine whether recursion is looping (step S54). The recursive loop check will be described later.
When recursion is looping (Yes in step S54), it is determined whether or not there is a one-to-other relationship (step S55). If there is a one-to-other relationship (Yes in step S55), the format item type is added as a recursive list hierarchy (step S56), and the process proceeds to step S62. If there is no one-to-other relationship (No in step S55), the format item type is added as a recursive hierarchy (step S57), and the process proceeds to step S62.

  On the other hand, if the recursion is not looped (No in step S54), it is determined whether or not the primary key corresponding to the reference key of the table information has a one-to-other relationship (step S58). If there is a one-to-other relationship (Yes in step S58), the format item type is added as a recursive list hierarchy (step S59), and the process proceeds to step S61. If there is no one-to-other relationship (No in step S58), the format item type is added as a recursive hierarchy (step S60), and the process proceeds to step S61.

Next, the cooperative format item creation process is recursively executed (step S61).
Then, it is determined whether or not all the reference information Ft has been verified (step S62).
If all the reference information Ft has not been verified (No in step S62), the process proceeds to step S52 to continue the cooperative format hierarchy creation process. On the other hand, when all the reference information Ft is verified (Yes in step S62), the cooperative format hierarchy creation process is terminated.

Next, the recursive loop check in step S54 will be described.
In the recursive loop check, when the route of the table information subjected to the recursive processing loops, it is determined that the recursion has looped.

FIG. 24 is a diagram for explaining the recursive loop check.
In FIG. 24, table information A to G is shown. For example, in the case of the route A → B → A and the route A → C → B → A, it is determined that it is a loop because it has passed A once again.

It is determined that there is no loop in the directions A → D → E and A → F → G. In the route A → D → D, since it passes again through D once passed, it is determined as a loop.
Next, the check process in steps S55 and S58 shown in FIG. 23 will be described.

FIG. 25 is a flowchart showing the check process.
First, it is determined whether the type of the reference destination item is a primary key or a unique key (step S71).

  When the type of the reference destination item is the primary key (primary key in step S71), the primary key item list Fi2 [z] is acquired from the primary key information using the reference destination table ID of the reference information Ft as a key. (Step S72). Thereafter, the process proceeds to step S74. On the other hand, if the type of the reference destination item is a unique key (unique key) (step S71 unique key), a list of unique key items from the unique key information using the reference destination table ID of the reference information Ft as a key. Fi2 [z] is acquired (step S73).

  Then, it is determined whether or not all items present in the list Fi2 [z] are present in the items of the list Fi [y] of the reference item information (step S74). When all are not present (No in step S74), it is determined that there is a one-to-one relationship (step S75). On the other hand, if all exist (Yes in step S74), it is determined that there is a one-to-other relationship (step S76).

This completes the check process.
In this way, a linkage format can be created.
By the way, when creating a common format from the created cooperation format, the user displays a common format / mapping editing screen on the monitor 11. The common format management unit 130 performs a management operation for creating a common format and mapping information in accordance with a user operation on the common format / mapping editing screen.

FIG. 26 is a diagram illustrating an example of a common format / mapping editing screen.
The common format / mapping editing screen 50a includes a link format name input unit 51b, a common format name input unit 51c, hierarchical structure display units 52b and 52c, a save button 54a, an add button 54b, a delete button 54c, and an edit. A button 54d, an end button 54e, a constant addition button 54f, a list node addition button 54g, a format reading button 54h, an automatic import button 54i, an auto mapping button 54j, and a flexibility button 54k. Yes.

In the following description, the description of the same items as the format editing screen 50 is omitted.
The cooperative format name input unit 51b can input a cooperative format name that uniquely identifies the cooperative format. In the common format name input unit 51c, a cooperative format name that uniquely identifies the common format can be input.

The hierarchical structure display unit 52b displays the hierarchical structure of the cooperation format. The hierarchical structure display portion 52c displays the hierarchical structure of the common format.
When the user reads the linkage format and the common format, the user presses the format read button 54h. When the format reading button 54h is pressed, a list of cooperative formats stored in the cooperative format DB 120c is displayed on the common format / mapping editing screen 50a (not shown). When the cooperative format is selected by the user, the cooperative format is read, and the hierarchical structure of the read cooperative format is displayed on the hierarchical structure display unit 52b. Thereafter, a list of common formats stored in the common format DB 130a is displayed on the common format / mapping edit screen 50a (not shown). When the user selects a common format, the common format is read, and the hierarchical structure of the read common format is displayed on the hierarchical structure display unit 52c.

  The user can select and edit the node of the hierarchical structure display unit 52c using the keyboard 12 or the mouse 13. The node of the hierarchical structure display section 52b can be selected but cannot be edited. In FIG. 26, the employee ID of the hierarchical structure display unit 52b and the employee ID of the hierarchical structure display unit 52c are selected.

  When the user wants to import the hierarchical structure of the cooperative format displayed in the hierarchical structure display unit 52b into the hierarchical structure display unit 52c, the user presses the automatic import button 54i with the node of the hierarchical structure display unit 52b selected. When the automatic capture button 54i is pressed, the node selected in the hierarchical structure display unit 52b is captured in the hierarchical structure display unit 52c. That is, the hierarchy or item selected in the linkage format is copied under the hierarchy selected in the common format. Also, mapping is performed after copying. If the same item already exists, only mapping is performed.

  When the user edits the selected node of the format information, the user presses one of the add button 54b, the delete button 54c, and the edit button 54d. When the add button 53b is pressed, an item is added to the child of the selected node. When the delete button 54c is pressed, the selected node is deleted. When the edit button 54d is pressed, the selected link format information can be edited.

Next, functions of the constant addition button 54f and the list node addition button 54g will be described.
FIG. 27 is a diagram illustrating constants and list groups. In FIG. 27, a part of FIG. 26 is omitted.

  For example, for a linked format that has two data, “employee name” and “employee name / kana” as items, if these data are each one item in a common format, for example, “employee name” When adding the item “English”, the common format is changed again, resulting in a common format with low versatility (extensibility). When adding new items later, it is preferable to create a list hierarchy in advance. In this case, an item group that is not a list hierarchy can be converted to a list hierarchy by creating a node called a list group between the linkage format and the common format and reorganizing the mapping.

  A list group is composed of one or a plurality of list nodes. When the user wants to add a list node, the list node addition button 54g is pressed. When the list node addition button 54g is pressed, the common format management unit 130 adds a list node. In FIG. 27, a list node 526 and a list node 527 are added.

  Constants are used when you want to enter a constant value. When the user wants to add a constant, the user presses the constant addition button 54f. When the constant addition button 54f is pressed, the common format management unit 130 adds a constant. In FIG. 27, “regular employee” is added as a constant. As a result, the item physical name “employee type ID” is added to the item physical name “employee list hierarchy” displayed in the hierarchical structure display section 52c.

  In addition, a constant “kanji” is added to the list node 526, and a constant “kana” is added to the list node 527. As a result, a list hierarchy of the item physical name “employee name list” is created as a child of the physical item name “employee list hierarchy” displayed in the hierarchical structure display section 52c. In addition, as an item of the list hierarchy of the item physical name “employee name list”, the item physical name “employee name / kana” displayed in the hierarchical structure display portion 52b is a key of the item physical name “language ID”. Reorganized as an item and item physical name “employee name” item.

  The constant information is stored in the mapping DB 130b as mapping constant information, and the list node information is stored in the mapping DB 130b as list node item information.

Returning again to FIG.
When the user performs auto mapping, the user presses the auto mapping button 54j. When the auto-mapping button 54j is pressed, the common format management unit 130 calculates the similarity between the affiliated format item and the common format item, and performs an auto-mapping process for mapping items having a certain similarity. .

  In FIG. 26, the link part 521b and the link part 521c are linked, and the link part 522b and the link part 522c are linked. By displaying the state of the link on the screen, the user can easily determine which item corresponds to which item.

In the hierarchical structure display section 52b and the hierarchical structure display section 52c, link sections 521b to 525b and 521c to 525c corresponding to the respective nodes are displayed.
Separately from the auto mapping, the user can manually perform mapping by selecting any one of the link units 521b to 525b using the mouse 13, for example, and dragging the link unit 521c to 525c. Thereby, the item of a cooperation format can be matched with the item of a common format. In FIG. 26, the link units 521b and 521c are mapped, and the link units 522b and 522c are mapped.

  When the user performs flexibility, the user presses the flexibility button 54k. When the flexible button 54k is pressed, the common format management unit 130 applies a template prepared in advance to the common format, so that the common format can be made more flexible (general purpose). Perform flexible processing to change to a format with high characteristics.

  The common format management unit 130 searches for a portion having the same item name in the same hierarchical structure in the common format being created in the saving process described later. When there is a part having the same item name in the same hierarchical structure, the part is extracted as a model and stored in the model DB 130c.

  When saving the common format edited by the user, the save button 54a is pressed. When the save button 54a is pressed, the common format edited by the common format management unit 130 (the common format displayed in the hierarchical structure display unit 52c when the save button 54a is pressed) and the mapping information are displayed in the common format DB 130a. Stored in At this time, the common format is stored in the common format DB 130a as format information and item information different from the linkage format.

  Next, format information and item information stored in the common format DB 130a will be described. In the common format DB 130a, format information and item information are stored in a table.

FIG. 28 is a diagram illustrating a data structure example of format information stored in the common format DB.
The format information table 131a has columns of item names and keys, and information arranged in the horizontal direction of each column is associated with each other.

An ID unique to the common format is stored in the common format ID column. This ID is automatic numbering. A primary key is set in the common format ID key field.
The common format name column stores the name of a table that uniquely identifies the common format.

Next, item information stored in the common format DB 130a will be described.
FIG. 29 is a diagram illustrating a data structure example of item information stored in the common format DB.

In the following description, the description of the same part as the item information table 122c is omitted.
The item information table 132a has columns of item names and keys, and information arranged in the horizontal direction of each column is associated with each other.

An ID unique to the common format is stored in the common format ID column. This ID is automatic numbering. Also, a primary key is set in the common format ID key field.
Returning again to FIG.

  When the user ends the common format / mapping editing, the user presses the end button 54e. When the end button 54e is pressed, the common format management unit 130 ends the common format / mapping editing operation.

Next, the auto mapping process will be described in detail.
FIG. 30 is a flowchart showing the auto mapping process.
First, one item “ItemX” is extracted from the linkage format (step S101).

Next, one item “ItemY” is extracted from the common format (step S102).
Next, the similarity S “X” “Y” between “ItemX” and “ItemY” is calculated (step S103).

  Next, it is determined whether or not the similarity S “X” “Y” is equal to or greater than a threshold value (step S104). When the similarity S “X” “Y” is not equal to or greater than the threshold (No in step S104), the process proceeds to step S107. On the other hand, if the similarity S “X” “Y” is equal to or greater than the threshold (Yes in step S104), whether or not “ItemY” is mapped as the condition 1 or the similarity S “X” “Y” is “ It is determined whether or not the similarity is higher than the item already mapped to “ItemY” (step S105). When the condition 1 is not satisfied, that is, “ItemY” is mapped, and the similarity S “X” “Y” is less than or equal to the similarity of the item already mapped to “ItemY” (step S105) No), the process proceeds to step S107. On the other hand, when the condition 1 is satisfied, that is, “ItemY” is not mapped, or the similarity S “X” “Y” is larger than the similarity of the items already mapped to “ItemY” (step (Yes in S105), “ItemX” and “ItemY” are mapped (step S106). At this time, if there is an item mapped to “ItemY”, the item (existing item) is deleted.

  Next, it is determined whether or not all items in the common format have been verified (step S107). If not all items of the common format have been verified (No in step S107), the process proceeds to step S102 and the auto mapping process is continued. On the other hand, when all items of the common format have been verified (Yes in step S107), it is determined whether all items of the cooperation format have been verified (step S108). When all the items of the cooperation format are not verified (No in step S108), the process proceeds to step S101 and the auto mapping process is continued. On the other hand, when all the items of the cooperation format have been verified (Yes in step S108), the auto mapping process is terminated.

Next, the similarity calculation processing in step S103 of FIG. 30 will be described.
FIG. 31 is a flowchart showing similarity calculation processing.
First, the similarity Sp of each “item physical name” of “ItemX” and “ItemY” is calculated (step S121).

Next, the similarity S1 of each “item logical name” of “ItemX” and “ItemY” is calculated (step S122).
Next, the similarity St of each “item type” of “ItemX” and “ItemY” is determined (step S123). Specifically, the similarity St is set to “1” if the “item types” of “ItemX” and “ItemY” are the same, and the similarity St is set to “0” if they are not the same.

  Next, the similarity Ss of each “item length” of “ItemX” and “ItemY” is determined (step S124). Specifically, the similarity Ss is set to “1” if the “item length” of “ItemX” and “ItemY” are the same, and the similarity Ss is set to “0” if they are not the same.

  Next, (W1 × Sp) + (W2 × Sl) + (W3 × St) + (W4 × Ss) is calculated, and this value is used as the similarity S “X” “Y” between “ItemX” and “ItemY”. (Step S125). Here, W1 to W4 indicate predetermined weighting factors.

This completes the similarity calculation process.
Next, the calculation process of the similarity Sp in step S111 in FIG. 30 will be described.
FIG. 32 is a flowchart showing the calculation process of the similarity Sp.

First, arrays X [i] and Y [i] obtained by dividing item names X and Y in units of words are respectively created (step S131).
Next, a synonym word table (to be described later) in the synonym DB 140a is searched using each word in the arrays X [i] and Y [i] as a synonym word (step S132). If there is a representative word corresponding to the synonym word, the word in the array X [i] is replaced with the representative word.

  Next, the overlapping ratio R of the words in the array X [i] and the array Y [i] is calculated (step S133). Here, the ratio R is “a value obtained by dividing the number of overlapping words by the larger of the number of words of item name X and the number of words of item name Y”.

The similarity Sp calculation process is thus completed.
According to the calculation process of the similarity Sp, for example, when the item of the cooperation format is “employee ID” and the item of the common format is “employee code”, when divided into words, “employee | ID” , "Employee | Code". Here, when the representative word is “employee number”, “employee | ID” is replaced with “employee | number”. Also replace “employee | code” with “employee | number”. As a result, the ratio R is 1.

Next, the saving process of the common format management unit 130 when the save button 54a is pressed by the user will be described in detail.
FIG. 33 is a flowchart showing the storage process.

First, the common format is stored in the common format DB 130a, and the mapping information is stored in the mapping DB 130b (step S141).
Next, template update processing is performed to update template item information (step S142).

  Next, it is determined whether or not two mapped items have different item physical names (step S143). If there are items with different item physical names (Yes in step S143), these are stored in the synonym DB 140a as "synonyms 1" and "synonyms 2" (step S144), and the process proceeds to step S145. Here, the synonym phrase means a similar “phrase (combination of words)” such as “employee code” and “employee ID”. If there are no items with different item physical names (No in step S143), the process proceeds to step S145.

  Next, it is determined whether there are items with different item logical names (step S145). If there are items with different item logical names (Yes in step S145), these are stored in the synonym DB 140a as "synonyms 1" and "synonyms 2" (step S146), and the saving operation ends. On the other hand, if there is no item with a different item logical name (No in step S145), the storage process is terminated.

  Next, mapping information stored in the mapping DB 130b by the saving process will be described. The mapping information is stored in the mapping DB 130b as map information, mapping item information, mapping constant information, and list node item information. Each of these pieces of information is tabulated and stored in the mapping DB 130b.

First, map information will be described.
FIG. 34 is a diagram illustrating a data structure example of map information.
The map information table 131b is provided with item name and key fields, and pieces of information arranged in the horizontal direction of the fields are associated with each other.

In the common format ID column, an ID unique to the common format is stored. This ID is automatic numbering. A primary key is set in the common format ID key field.
The cooperation format ID column stores the cooperation format ID. The primary key is set in the column of the cooperation format ID key.

Next, the mapping item information will be described.
FIG. 35 is a diagram illustrating an example data structure of mapping item information.
The mapping item information table 132b is provided with item name and key fields, and information arranged in the horizontal direction of each field is associated with each other.

An ID unique to the common format is stored in the common format ID column.
The cooperation format ID column stores the cooperation format ID.
In the column of the mapping source item type, any one of the linked format item / common format item / constant / list node is set.

  In the field of mapping source item ID, when the mapping source item type is “cooperation format item” or “common format item”, “format item ID” is set, and when it is “constant”, “constant ID” is set. In the case of “list node”, “list node ID” is set.

In the field of mapping destination item type, any one of linked format item / common format item / constant / list node is set.
In the field of mapping destination item ID, when the mapping destination item type is “cooperation format item” or “common format item”, “format item ID” is set, and when it is “constant”, “constant ID” is set. In the case of “list node”, “list node ID” is set.

Primary keys are set in the key fields of all items in the mapping item information table 132b.
Next, mapping constant information will be described.

FIG. 36 is a diagram illustrating a data structure example of mapping constant information.
The mapping constant information table 133b is provided with item name and key columns, and information arranged in the horizontal direction of each column is associated with each other.

An ID unique to the common format is stored in the common format ID column.
The cooperation format ID column stores the cooperation format ID.
A constant unique ID is set in the constant ID column. This ID is automatic numbering.

A constant value is stored in the constant value column.
Primary keys are set in the key fields of all items in the mapping constant information table 133b.

Next, list node item information will be described.
FIG. 37 is a diagram illustrating an example of a data structure of list node item information.
The list node item information table 134b is provided with item name and key columns, and information arranged in the horizontal direction of each column is associated with each other.

An ID unique to the common format is stored in the common format ID column.
The cooperation format ID column stores the cooperation format ID.
The item ID of the list node is set in the list node ID column. This ID is automatic numbering.

In the serial number column, a numerical value indicating the item number of the list node is stored.
Primary keys are set in the key fields of all items in the list node item information table 134b.

Next, the template item information table stored in the template DB 130c will be described.
FIG. 38 is a diagram showing an example of the data structure of model item information.
The template item information table 131c is provided with item name and key fields, and information arranged in the horizontal direction of each field is associated with each other.

  In the item name column, model ID, format item ID, format item type, item physical name, item logical name, item data type, item data length, parent format item ID, recursive format item ID, display order, number used Is stored.

  In the following description, the template item information table 131c stores the same information for the same items as the item information table 132a in the common format, so the description of the same parts as the item information table 132a is omitted. To do.

A template-specific ID is stored in the template ID column. This ID is automatic numbering. A primary key is set in the key field of the template ID.
The number of common formats in which this template is used is stored in the used number column.

Next, the template update process in step S142 of FIG. 33 will be described.
In the template update process, each layer is extracted from the common format created this time, and it is checked whether the same hierarchical structure exists in other parts of the common format created this time. If it exists, it is determined whether or not this hierarchical structure already exists in the template DB. If it does not exist, this hierarchical structure is registered as a new template. This operation is performed for each hierarchy.

39 and 40 are flowcharts showing the template update process.
First, the template item information table of the template DB 130c is initialized (step S151).
Next, the route Y of the created common format X is acquired (step S152).

Next, the number C of common formats having the same structure as the route Y is searched to determine whether the number C exists (step S153).
When the number C exists (Yes in step S153), it is determined whether or not the route Y has been registered in the template item information table. (Step S154). When the route Y has already been registered in the template item information table (Yes in step S154), the process proceeds to step S157. If the route Y has not been registered in the template item information table (No in step S154), it is determined whether or not a sibling node or a child node exists in the route Y (step S155). When there is no sibling node or child node in the route Y (No in step S155), the process proceeds to step S157. When a sibling node or a child node exists in the route Y (Yes in step S155), the route Y is added to the template item information in the template item information table 131c (step S156). At this time, the value of the number C is set in the used number column of the template item information table 131c.

  Next, it is determined whether or not there is another sibling node in the route Y (step S157). Here, the sibling node of the node P (P is arbitrary) means a child node of the parent node of the node P. When another sibling node exists in the route Y (Yes in step S157), the sibling node is set as the route Y (step S158), and the process proceeds to step S152 to continue the template update process. If there is no other sibling node in the route Y (No in step S157), the template update process is terminated.

  On the other hand, if the number C does not exist in step S153 (No in step S153), it is determined whether or not a sibling node exists in the route Y (step S159). If there is a sibling node in the route Y (Yes in step S159), this sibling node is set as the root Y (step S160), and the process proceeds to step S152 to continue the template update process. If no sibling node exists in the route Y (No in step S159), it is determined whether or not a child node exists in the route Y (step S161). When there is a child node in the route Y (Yes in step S161), the child node is set as the route Y (step S162), and the process proceeds to step S152 to continue the template update process. If there is no child node in the route Y (No in step S161), the template update process is terminated.

Next, the softening process of the common format management unit 130 when the softening button 54k is pressed by the user will be described in detail.
FIG. 41 is a flowchart showing the softening process.

First, a list of items for one child hierarchy or one sibling hierarchy is acquired (step S171).
Next, an arbitrary item is applied to the acquired hierarchy, and a template item conversion process is performed to determine whether or not there is a template that can be applied (step S172).

Next, a hierarchical item conversion process is performed in which an item that is likely to be added later is predicted and the item is added as necessary (step S173).
Next, it is determined whether or not all hierarchies have been verified (step S174). When not verifying all the hierarchies (No in step S174), the process proceeds to step S171 and the softening process is continued. When all the hierarchies are verified (Yes in step S174), the softening process is terminated.

Next, the template item conversion process in step S172 will be described.
In the template item conversion process, an item in the hierarchy is brought up, and a process of searching for a candidate that can be applied only to the template is performed.

FIG. 42 is a flowchart showing a template item conversion process.
First, a list H [j] of templates using items I [i] in the list is acquired (step S181).

  Next, the accuracy of which template is appropriate to be applied from the template list H [j] is obtained (step S182). The accuracy is obtained as the sum of the product of the weight W5 and the number of items of the item I existing in the list H [j] and the product of the weight W6 and the number of times the template is used. The values of the weight W5 and the weight W6 are set in advance by the user.

  Next, the template is replaced in order from the item with the highest accuracy (step S183). In other words, a template that includes more items to be softened and that has a high degree of use is selected. Also, a converted flag is set for the item replaced with the template. No replacement is performed for items with a converted flag. Thereby, it is possible to prevent an item once replaced with a template from being replaced with another template. When the template is replaced, the value in the column for the number of times of use of the replaced template is incremented by one. This completes the template item conversion process.

Next, the hierarchical item conversion process in step S173 will be described.
FIG. 43 is a flowchart showing the hierarchy item conversion process.
First, one common format C other than the common format being edited is acquired (step S191).

  Next, if there is an item in the common format C that is similar to or similar to the item being edited, a flag is set (step S192). At this time, for similar items, the degree of similarity is obtained by the same method as the template update process described above, and the item having the highest degree of similarity and a threshold value equal to or greater than a certain value is set as a similar item.

  Next, a subtree group is extracted by extracting the hierarchy holding the flagged item from the common format C for each parent node. Then, the “number of flags” and “number of items” are obtained for each extracted subtree group (step S193).

  Next, it is determined whether or not all common formats have been verified (step S194). If all the common formats have not been verified (No in step S194), the process proceeds to step S191 to continue the hierarchical item conversion process. When all the common formats have been verified (Yes in step S194), the items being edited are replaced with subtrees in order from the subtree having the highest “number of flags” (step S195). If there are multiple subtrees with the same number of flags, the one with the smaller “number of items” is given priority. However, conversion is not performed for items for which the “converted flag” is set. In addition, a “converted flag” is set for the replaced item.

Next, the hierarchical item conversion process described above will be described using a specific example.
FIG. 44 is a diagram illustrating an example of a hierarchical item conversion process.
As a common format to be flexible, a common format 139a that has been subjected to template item conversion processing having “contact”, “address”, “data update date / time”, and “address type” as items is acquired.

Next, the common format C1 is acquired as another common format.
Next, a flag is set for a portion corresponding to the item of the common format 139a of the other common format C1. Then, the subtree group of the common format C1 is extracted. In FIG. 44, four subtrees Ca1, Ca2, Ca3, and Ca4 are extracted. When comparing the numbers of flags of the subtrees Ca1, Ca2, Ca3, and Ca4, it can be seen that the number of flags of the subtree Ca3 is 2, which is the largest. Therefore, in this case, the common format 139a is replaced with the subtree Ca3. Then, a converted flag F1 is set for the replaced item (in this case, address type, address).

Next, the operation of the similar word management unit 140 will be described.
As described above, the synonym word management unit 140 retrieves information necessary for learning the synonym word from the synonym DB 140a, and performs synonym word dictionary creation processing on the information, thereby obtaining the latest synonym. Create a list of words.

  The synonym DB 140a has an unresolved synonym phrase table storing “synonyms 1” and “synonyms 2” stored in the synonym DB 140a by the storing operation, and a synonym word table storing synonyms in advance. . Here, synonymous words are words that are similar to each other such as “employee” and “employee”, “code” and “ID”. The synonym word table may be updated manually by the user, or a synonym dictionary or the like may be read.

Next, the unresolved synonym phrase table and the synonym word table stored in the synonym DB 140a will be described.
FIG. 45 is a diagram illustrating an example of a data structure of an unresolved synonym phrase.

The unresolved synonym phrase table 141a is provided with fields for item names and keys, and the information arranged in the horizontal direction of each field is associated with each other.
Synonyms are stored in the item name column. In the example of FIG. 45, “synonym 1” is stored as a synonym of synonym 2, and “synonym 2” is stored as a synonym of synonym 1. Key attributes are set in the key column. In the example of FIG. 45, a primary key is set for each.

FIG. 46 is a diagram illustrating a data structure example of similar words.
The synonym word table 142a is provided with columns of item names and keys, and information arranged in the horizontal direction of each column is associated with each other.

  The item name column stores a representative word that is a representative word of the similar word and a similar word that is a word having a similar meaning to the representative word. Key attributes are set in the key column. In the example of FIG. 45, a primary key is set for each.

FIG. 47 is a diagram showing an outline of the synonym word dictionary creation processing.
The synonym word management unit 140 creates the latest synonym word table 142c from the synonym word table 142b and the unresolved synonym phrase table 141b by performing a synonym word dictionary creation process.

Next, the synonym word dictionary creation process will be described in detail.
FIG. 48 is a flowchart showing similar word dictionary creation processing.
First, a sorted unresolved synonym phrase is created from an unresolved synonym phrase (step S211). Specifically, the synonym phrase is divided into words, and the divided words are replaced with representative words. At this time, the particles are removed. After replacement, duplicate synonyms are removed from the list.

Next, a list S [i] in which synonyms having the same meaning are grouped is created (step S212).
Next, a list Sg of one synonym group is extracted from the created list S [i] (step S213).

Next, a synonym word extraction process for extracting synonym words from the list Sg is performed (step S214).
Next, it is determined whether all the lists S [i] have been verified (step S215). When all the lists S [i] have not been verified (No in step S215), the process proceeds to step S213, and the synonym word dictionary creation process is continued. When all the lists S [i] are verified (Yes in step S215), it is determined whether or not a newly extracted similar word exists (step S216). If a newly extracted synonym word exists (Yes in step S216), the process proceeds to step S211 and the synonym word dictionary creation process is continued. If there is no newly extracted synonym word (No in step S216), the synonym word dictionary creation process is terminated.

Next, the similar word extraction process in step S214 will be described.
FIG. 49 is a flowchart showing similar word extraction processing.
First, it is determined from the synonym phrase list Sg whether or not there are synonym phrase sets X and Y having the same number of word combinations and different word combinations (step S221). If the sets X and Y do not exist (No in step S221), the synonym word extraction process ends. When the sets X and Y exist (Yes in step S221), the character strings of words different from the sets X and Y are set as character strings x and y, respectively (step S222).

  Next, a synonym word is registered (step S223). Specifically, when the character string x is a representative word, “representative word: character string x” and “synonymous word: character string y” are used. When the character string y is a representative word, “representative word: character string y” and “similar word: character string x” are used. When the character string x is a synonym word and the character string y is an unregistered word, “representative word: representative word of character string x” and “synonymous word: character string y” are used. When the character string y is a synonym word and the character string x is an unregistered word, “representative word: representative word of the character string y” and “synonymous word: character string x” are assumed. When both the character string x and the character string y are unregistered words, “representative word: character string x” and “synonymous word: character string y” are used.

Next, the synonym phrase of the character string y is deleted from the unresolved synonym phrase table 141a and the list Sg, respectively (step S224).
Next, the words of the character strings x and y in the list Sg are replaced with the representative words of the character strings x and y, respectively (step S225).

Next, duplicate word combinations are removed from the list Sg (step S226).
Then, it transfers to step S221 and continues a similar word extraction process.
Next, the synonym word dictionary creation processing will be described using a specific example.

FIG. 50 is a diagram illustrating a specific example of the synonym word dictionary creation process.
In FIG. 50, the same parts as those in FIG. 47 are denoted by the same reference numerals.
First, the synonym word management unit 140 retrieves the unresolved synonym phrase table 141b and the synonym word table 142b. Then, the unresolved synonym phrase 143a is created by dividing the unresolved synonym phrase into words using the synonym word table 142b (corresponding to step S212). For example, since there is a clerk in the old synonym word list, the clerk name is divided into a clerk and a name. Then, duplicate combinations are removed and particles are removed. Further, it is replaced with a representative word. The clerk replaces the employee.

Next, the sorted unresolved synonyms are grouped to create a list S [1] 144 (grouped synonyms).
Then, the list Sg1 is extracted, and a list having the same number of word combinations and a different word combination is found from the list Sg1. In FIG. 50, “employee | name” and “employee | name” have two word combinations, the “name” portion is the same, and “employee” and “employee” are different. | Name "and" employee | name "correspond to the sets X and Y in step S221.

  Since “employee” is a representative word, “employee” is registered in the synonym word table 142b as a synonym word. Since “employee” and “employee” are synonymous words, the “employee” portion of “employee | name” in the list Sg1 is replaced with “employee”. Then, “employee | name” is replaced with “employee | name”. This time, when comparing “employee | name” with “employee | name”, the part of “employee” is the same and “name” is different from “name”, so “employee | name” and “employee | name” are the same as those in step S221. Corresponds to set X, Y. Since the representative word does not exist in the synonym word table 142b, it is registered in the synonym word table 142b as the representative word “name” and the synonym word “name”. In this way, synonym phrases are sequentially extracted and registered in the synonym word table 142b. Similar operations are performed for the lists Sg2 and Sg3. In this way, a similar word table 142c to which a new similar word is added (registered) is finally created.

  As described above, according to the management device 100, the common format management unit 130 selects a template to be applied to an item from the template list H [j] by performing template item conversion processing when creating the common format, By replacing the applicable items with templates, a standardized (highly uniform) common format can be created. Therefore, for example, a common format or template created by a highly skilled administrator is stored in advance in the common format DB 130a or template DB 130c, and the user simply presses the flexible button 54k when creating a new common format thereafter. Therefore, it is possible to create a common format that is highly expandable (general versatility) regardless of the skill of the user, that is, is not easily affected by specification changes even when a new backbone system is added. As a result, a system that can be easily maintained can be constructed.

  Also, by performing hierarchical item conversion processing, the number of sibling nodes of the item increases, so that omission of items can be complemented when applying a template, and a more extensible (generic) common format can be created .

Also, by performing the template update process, a portion having the same structure in the common format can be easily extracted as a template.
In addition, when the user presses the extraction button 53f, the format creation unit 120a executes the format extraction process, so that a linked format can be efficiently created.

  In addition, when the user presses the auto mapping button 54j, the common format management unit 130 executes the auto mapping process. Therefore, new mapping information can be easily created based on the past mapping information.

  Further, when executing the softening process and creating the map information, the synonym word table 142a stored in the synonym DB 140a can be used to identify items with high conversion efficiency.

  In addition, the synonym word management unit 140 performs the synonym word dictionary creation process, so that the synonym word table can be easily updated, thereby reducing the user's trouble of manually registering synonym words. can do.

Although the preferred embodiment of the present invention has been described in detail above, the present invention is not limited to the specific embodiment.
The main part of the above processing function can be realized by a computer (by causing the computer to execute a predetermined common format creation program). In that case, a program describing the processing contents of the functions that the management apparatus 100 should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory. Examples of the magnetic recording device include a hard disk device (HDD), a flexible disk (FD), and a magnetic tape. Examples of the optical disc include a DVD (Digital Versatile Disc), a DVD-RAM (Random Access Memory), a CD-ROM (Compact Disc Read Only Memory), and a CD-R (Recordable) / RW (ReWritable). Examples of the magneto-optical recording medium include an MO (Magneto-Optical disk).

  When distributing the program, for example, a portable recording medium such as a DVD or a CD-ROM in which the program is recorded is sold. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  A computer that executes the common format creation program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

(Supplementary note 1) In a common format creation program for creating a common format used when data is linked between a plurality of systems,
On the computer,
Acquire each item of each layer of the common format to be edited as the item to be edited,
Create a list of templates that are created from an existing common format and have the same items as the item to be edited,
Based on the number of matches between the items present in the template and the item to be edited, and the number of times the template is used, select a template to replace the item to be edited,
Replacing the item to be edited with the selected template;
A common format creation program characterized by causing processing to be executed.

(Additional remark 2) The hierarchy provided with the item same as the said edit object item of the said existing common format is extracted as a subtree,
The common format creation program according to supplementary note 1, wherein a structure of a subtree having the largest number corresponding to the edit target item among the extracted subtrees is applied as a hierarchy of the common format of the edit target.

(Supplementary Note 3) Extracting the hierarchical structures of the common format of the editing target that match each other,
The common format creation program according to appendix 1, wherein the extracted structure is added to the list of templates as a template.

(Supplementary note 4) The common format creation program according to supplementary note 3, wherein the number of the extracted structures is the number of times the template added to the template list is used.
(Appendix 5) Prepare a unique linkage format for each system,
For each item of the common format to be edited, calculate the similarity with each item of the linkage format,
The common format creation program according to supplementary note 1, wherein for each item of the common format to be edited, mapping is performed with an item having the highest similarity in the linkage format.

  (Supplementary Note 6) The similarity is calculated by dividing the item of the common format to be edited and the item of the linkage format into units of words and calculating the ratio of the overlapping words. Appendix 5 Common format creation program.

  (Supplementary note 7) The common format according to supplementary note 1, wherein when the edit target item is replaced with the selected template, a converted flag is set to prevent the replacement of the item replaced with the template again. Creation program.

(Supplementary note 8) The common format creation program according to supplementary note 1, wherein the common format item to be edited is identified using synonym information.
(Supplementary Note 9) In a common format creation method for creating a common format used when data is linked between a plurality of systems,
Acquire each item of each layer of the common format to be edited as the item to be edited,
Create a list of templates that are created from an existing common format and have the same items as the item to be edited,
Based on the number of matches between the items present in the template and the item to be edited, and the number of times the template is used, select a template to replace the item to be edited,
Replacing the item to be edited with the selected template;
A common format creation method characterized by the above.

(Supplementary Note 10) In a common format creation device for creating a common format used when data is linked between a plurality of systems,
Edit target item acquisition means for acquiring items of each layer of the common format to be edited as edit target items,
A template list acquisition means for acquiring a list of templates created from an existing common format and having the same items as the item to be edited;
Selection means for selecting a template to replace the editing target item based on the number of matches between the item existing in the template and the editing target item, and the number of times the template is used;
Replacement means for replacing the item to be edited with the selected template;
A common format creation device.

It is a schematic diagram which shows the invention applied to embodiment. It is a figure which shows the system configuration example of this Embodiment. It is a figure which shows the hardware structural example of a management apparatus. It is a block diagram which shows the function of a management apparatus. It is a figure which shows the example of a data structure of the table information stored in extraction information DB. It is a figure which shows the example of a data structure of the item information stored in extraction information DB. It is a figure which shows the data structure example of the primary key information stored in extraction information DB. It is a figure which shows the example of a data structure of the unique key information stored in extraction information DB. It is a figure which shows the example of a data structure of the reference information stored in extraction information DB. It is a figure which shows the example of a data structure of the reference information stored in extraction information DB. It is a figure which shows the example of a format edit screen. It is a figure explaining a format item classification. It is a figure explaining a group hierarchy. It is a figure explaining a list hierarchy. It is a figure explaining a loop hierarchy. It is a figure explaining a recursive list hierarchy. It is a figure which shows the data structure example of the format information stored in cooperation format DB. It is a figure which shows the example of a data structure of the item information stored in cooperation format DB. It is a flowchart which shows cooperation format creation operation | movement. It is a flowchart which shows a format extraction process. It is a flowchart which shows the creation process of a format definition. It is a flowchart which shows a cooperation format item creation process. It is a flowchart which shows a cooperation format hierarchy preparation process. It is a figure explaining a recursive loop check. It is a flowchart which shows a check process. It is a figure which shows the example of a common format mapping editing screen. It is a figure explaining a constant and a list group. It is a figure which shows the example of a data structure of the format information stored in common format DB. It is a figure which shows the example of a data structure of the item information stored in common format DB. It is a flowchart which shows an auto mapping process. It is a flowchart which shows the calculation process of similarity. It is a flowchart which shows the calculation process of similarity Sp. It is a flowchart which shows a preservation | save process. It is a figure which shows the data structure example of map information. It is a figure which shows the data structure example of mapping item information. It is a figure which shows the data structure example of mapping constant information. It is a figure which shows the data structure example of list node item information. It is a figure which shows the example of a data structure of model item information. It is a flowchart which shows a model update process. It is a flowchart which shows a model update process. It is a flowchart which shows a softening process. It is a flowchart which shows a template item conversion process. It is a flowchart which shows a hierarchy item conversion process. It is a figure which shows an example of a hierarchy item conversion process. It is a figure which shows the example of a data structure of an unresolved synonym phrase. It is a figure which shows the data structure example of a synonym word. It is a figure which shows the outline | summary of a similar word dictionary creation process. It is a flowchart which shows a similar word dictionary creation process. It is a flowchart which shows a similar word extraction process. It is a figure which shows the specific example of a similar word dictionary creation process. It is a figure which shows the cooperation of the conventional data. It is a figure which shows the case where a new system is made to cooperate.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Computer 1a Common format management means 2 Common format 2a, 2b of edit object Editable item 3 Model DB
3a to 3c Model 100 Management Device 110 Interface Unit 120 Cooperation Format Editing Unit 120a Format Creation Unit 120b Extraction Information DB
120c Cooperation format DB
130 Common format manager 130a Common format DB
130b Mapping DB
130c Model DB
140 Synonym Word Management Unit 140a Synonym DB

Claims (5)

In a common format creation program that creates a common format used when data is linked between multiple systems.
On the computer,
Acquire each item of each layer of the common format to be edited as the item to be edited,
Create a list of templates that are created from an existing common format and have the same items as the item to be edited,
Based on the number of matches between the items present in the template and the item to be edited, and the number of times the template is used, select a template to replace the item to be edited,
Replacing the item to be edited with the selected template;
A common format creation program characterized by causing processing to be executed. Extracting a hierarchy having the same item as the item to be edited in the existing common format as a subtree;
The common format creation program according to claim 1, wherein a structure of a subtree having the largest number corresponding to the item to be edited among the extracted subtrees is applied as a hierarchy of the common format to be edited. Extracting a structure of a hierarchy of the common format to be edited,
The common format creation program according to claim 1, wherein the extracted structure is added to the list of templates as a template.   4. The common format creation program according to claim 3, wherein the number of the extracted structures is the number of times the template added to the template list is used. Prepare a unique linkage format for each system,
For each item of the common format to be edited, calculate the similarity with each item of the linkage format,
2. The common format creation program according to claim 1, wherein for each item of the common format to be edited, mapping is performed with an item having the highest similarity in the linkage format.

Images