Program, information processing method, and information processing apparatus

Abstract

The present invention provides a program, an information processing method, and an information processing device that enhance the convenience of processing using tabular data and a layout that defines the relationships between each cell of that tabular data. [Solution] In a system in which an information processing device and an information processing terminal transmit and receive information via a network such as the Internet, the program obtains a tabular file containing tabular data associated with a layout that defines the relationships between multiple cells, extracts layout-defined data included in the tabular data that is defined as being the target of the layout, outputs a list of header candidates for an integrated table that combines the extracted multiple layout-defined data, and causes the server device, which is an information processing device, to execute a process to generate the integrated table based on the list of header candidates.

Description

Technical Field

[0001] The present invention relates to a program, an information processing method, and an information processing apparatus.

Background Art

[0002] Patent Document 1 discloses an apparatus for converting data in a spreadsheet format into data in a semi-structured data format.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Data users such as data scientists often require data creators such as researchers who input experimental data and the like to input data in a predetermined tabular data format in order to efficiently use data such as experimental data. However, data creators may sometimes use a partially modified tabular data format according to the type and number of experiments, and in such cases, it has been difficult to efficiently use the data.

[0005] In one aspect of the present disclosure, a program or the like that further enhances the convenience of processing using a layout that defines the relationship between tabular data and each cell of the tabular data is provided.

Means for Solving the Problems

[0006] The program in the first aspect is a program that causes a computer to perform the following processes: acquire a tabular file containing tabular data associated with a layout that defines the relationships between multiple cells; extract layout-defined data included in the tabular data that is defined as being subject to the layout; output a list of header candidates for an integrated table that combines the extracted multiple layout-defined data; and generate the integrated table based on the list of header candidates. In one aspect of this disclosure, the use of tabular data and a layout that defines the relationships between each cell in the tabular data can be made more convenient.

[0007] The program in the second perspective is the program described in the first perspective, which accepts one or more of the following as a split unit: the tabular file, one or more sheets contained in the tabular file and containing the tabular data, and a table which is the layout-defined data defined as a table within the tabular data; extracts header candidates for the integrated table from the layout-defined data contained in the split unit; and outputs a list of the header candidates.

[0008] The program in the third perspective is the program described in the second perspective, which, when the tabular file is used as the division unit, includes the sheet name of the sheet in the header name of the header candidate.

[0009] The program in the fourth aspect is the program described in the second or third aspect, which outputs metadata as one of the header candidates, and outputs, as header candidates included in the metadata, either the folder path of the folder where the tabular file is saved, the file name of the tabular file, the sheet name of the sheet, or a table path that is a combination of the file name, the sheet name, and the table headers or a combination of

[0010] The program according to the fifth perspective is the program according to the fourth perspective, which adds the sheet name to the metadata when the sheet is used as the division unit, and adds the sheet name and the table path to the metadata when the table is used as the division unit.

[0011] The program of the sixth perspective is the program described in any of the first to fifth perspectives, wherein the layout includes one or more of a header parser that defines values ​​and headers for the values, and a table parser that defines a table, and outputs either the header of the header parser or the header of the table parser as a header candidate in a list.

[0012] The program of the seventh aspect is the program described in the sixth aspect, which identifies the header of the header parser and the header of the table parser, which are the header candidates, as different header types, and displays the header types together with the header candidates in association with them.

[0013] The program of the eighth aspect is the program of the sixth or seventh aspect, wherein the layout includes a sequence parser that defines the order, and if the cells related to the sequence parser are the headings of the heading parser, then the headings of the heading parser are the header candidates, and other cells related to the sequence parser to which the heading parser is not applied are the header candidates.

[0014] The program of the ninth aspect is the program described in the eighth aspect, which identifies the heading for the sequence parser from which the header candidates have been extracted as the header type of the sequence parser, and displays the header type together with the header candidates in association with them.

[0015] The program according to the tenth perspective is a program according to any one of the first to sixth perspectives, which displays the number of times the header candidate appears as a heading or header in a plurality of the layout-defined data, along with the header candidate.

[0016] The eleventh aspect of information processing is an information processing method that obtains a tabular file containing tabular data associated with a layout that defines the relationships between multiple cells, extracts layout-defined data that is included in the tabular data and is defined as being the target of the layout, outputs a list of header candidates for an integrated table that combines the extracted multiple layout-defined data, and generates the integrated table based on the list of header candidates.

[0017] The information processing device in the twelfth aspect comprises a control unit, which acquires a tabular file containing tabular data associated with a layout defining the relationships between a plurality of cells, extracts layout-defined data included in the tabular data that is defined as being the target of the layout, outputs a list of header candidates for an integrated table that combines the extracted plurality of layout-defined data, and generates the integrated table based on the list of header candidates. [Brief explanation of the drawing]

[0018] [Figure 1] This is an overview diagram of the system relating to one aspect of this disclosure. [Figure 2] This is a block diagram showing an example of a server device configuration. [Figure 3] This diagram shows an example of the structure of a management file. [Figure 4] This is a block diagram showing an example configuration of a terminal device. [Figure 5] This is an explanatory diagram to describe the layout. [Figure 6] This is a flowchart illustrating an example of server device processing. [Figure 7] This diagram shows an example of the structure of a tabular file. [Figure 8] This diagram shows an example of a screen that includes a list of header candidates. [Figure 9] This diagram shows an example of a merged table displayed in the preview area. [Figure 10] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "sheet". [Figure 11] A diagram showing another example of an integrated table displayed when the division unit is a "sheet". [Figure 12] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "table". [Figure 13] A diagram showing an example of the configuration of a tabular file. [Figure 14] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "file". [Figure 15] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "sheet". [Figure 16] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "table". [Figure 17] A diagram showing an example of the configuration of a tabular file. [Figure 18] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "file". [Figure 19] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "sheet". [Figure 20] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "table". [Figure 21] A diagram showing an example of the configuration of a tabular file. [Figure 22] An explanatory diagram showing an example list of header candidates and an integrated table when the division unit is a "sheet".

Embodiments for Carrying Out the Invention

[0019] The following describes in detail, with reference to drawings, a system that is an example of a program, information processing device, and information processing method relating to one aspect of this disclosure. In the description, similar elements are denoted by the same reference numerals, and redundant explanations are omitted as appropriate.

[0020] Figure 1 is an overview diagram of a system relating to one aspect of this disclosure. The system relating to this form of disclosure includes an information processing device 1 and an information processing terminal 2, which can send and receive information via a network 3 such as the Internet.

[0021] Information Processing Device 1 is an information processing device that processes, stores, and transmits various types of information. Information Processing Device 1 may be configured as, for example, a server, a personal computer, a tablet terminal, or a smartphone. Information Processing Device 1 may be composed of multiple information processing devices, or it may be configured as one of multiple virtual devices (virtual machines) within a single information processing device. In this embodiment of the disclosure, to avoid complexity in the explanation, Information Processing Device 1 will be described as Server Device 1. However, Information Processing Device 1 is not limited to a server device and may be configured as any of the above-described types of information processing devices.

[0022] The information processing terminal 2 can display, download, and edit tabular data files (hereinafter referred to as "tabular files") stored in the server device 1 via the network 3. Here, tabular data or files can be used synonymously with spreadsheet data or files. The information processing terminal 2 can be, for example, a personal computer, smartphone, mobile phone, wearable device, or tablet. In this disclosure, to avoid complexity in explanation, the information processing terminal 2 will be read and described as terminal device 2.

[0023] Figure 2 is a block diagram showing an example configuration of server device 1. Server device 1 can be an information processing device composed mainly of electronic circuits using semiconductor circuit elements. Server device 1 has a control unit 11, a communication unit 12, a reading unit 13, and a storage unit 14. The control unit 11, communication unit 12, reading unit 13, and storage unit 14 are connected to each other via a bus 19 or the like. Note that server device 1 may have other configurations, such as not having a reading unit 13.

[0024] The control unit 11 can be configured to have one or more processing units such as a CPU (Central Processing Unit), MPU (Micro-Processing Unit), GPU (Graphics Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), and quantum processor. The control unit 11 reads and executes the program (or program product) 1P stored in the storage unit 14.

[0025] The communication unit 12 is a communication module for performing communication-related processing and can send and receive information with terminal devices 2, etc., via the network 3. The reading unit 13 can read portable storage media 15 such as CD (Compact Disc)-ROM (Read Only Memory), DVD (Digital Versatile Disc)-ROM, and USB (Universal Serial Bus) memory. The control unit 11 may read program 1P from the portable storage media 15 via the reading unit 13 and save it to the storage unit 14. Alternatively, the control unit 11 may download program 1P from another computer via the network 3, etc., and save it to the storage unit 14.

[0026] The storage unit 14 includes volatile storage units such as RAM (Random Access Memory), and non-volatile storage units such as ROM, HDD (Hard Disk Drive), and flash memory. As shown in Figure 2, the storage unit 14 stores, for example, program 1P and tabular linked data 60. Program 1P is a program executed by the control unit 11. In this embodiment, program 1P may also be referred to as program product 1P.

[0027] The tabular linked data 60 consists of a management file 61, a tabular file storage unit 62, and a layout file storage unit 63. The management file 61 stores which layout file stored in the layout file storage unit 63 is linked to the tabular file stored in the tabular file storage unit 62.

[0028] The tabular file storage unit 62 stores tabular data files (hereinafter referred to as "tabular files"). The layout file storage unit 63 stores files containing layouts (hereinafter referred to as "layout files"). Layouts will be described later.

[0029] Figure 3 shows an example of the configuration of the management file 61. As shown in this figure, the management file 61 can be configured in a table format. The management file 61 may be stored as a database table, or as a spreadsheet or text file. The management file 61 has columns for identifier, tabular file, and layout file. The identifier column stores a string that identifies the tabular file. The tabular file column stores the location (file path) where the tabular file is stored. The layout file column stores the location (file path) where the layout file is stored.

[0030] This allows the layout file of the layout applied to the saved tabular file to be extracted using an identifier or the location (file path) where the tabular file is saved as a key. Note that the configuration for linking a tabular file to a corresponding layout or layout file is not limited to this configuration. For example, information linking to the corresponding layout or layout file may be stored within the tabular file, or other forms can be used to indicate the linking, such as the tabular file and layout file being stored in the same folder.

[0031] Figure 4 is a block diagram showing an example configuration of terminal device 2. Here, terminal device 2 can be an information processing device composed mainly of electronic circuits using semiconductor circuit elements. Terminal device 2 may have a control unit 21, a communication unit 22, a reading unit 23, a storage unit 24, a display unit 26, and an input unit 27. The components of the control unit 21, communication unit 22, reading unit 23, storage unit 24, display unit 26, and input unit 27 are connected to each other so as to be able to communicate with one another by a bus 29 or the like.

[0032] The control unit 21 can be configured to include one or more processing units such as a CPU, MPU, GPU, FPGA, DSP, and quantum processor. The control unit 21 reads and executes the program stored in the storage unit 24.

[0033] The communication unit 22 is a communication module for performing communication-related processing and can send and receive information with the server device 1, etc., via the network 3. The reading unit 23 can read portable storage media 25 such as CD-ROMs, DVD-ROMs, and USB memory sticks. The control unit 21 can read programs and / or data from the portable storage media 25 via the reading unit 23 and save them to the storage unit 24. The control unit 21 can also download programs from other computers via the network 3, etc., and save them to the storage unit 24.

[0034] The storage unit 24 includes volatile storage devices such as RAM, and non-volatile storage devices such as ROM, HDD, and flash memory. The display unit 26 can be a liquid crystal display or an organic EL (Electro-Luminescence) display, etc. The input unit 27 can be an input device such as a keyboard, mouse, touch panel, and camera.

[0035] Figure 5 is an explanatory diagram illustrating the layout. In Figure 5, tabular data is displayed, along with the layout displayed on top of the tabular data. Tabular data can be stored in or stored in a tabular file. Tabular data consists of columns and rows, and data elements, or cells, are located at the intersections of rows and columns. Cells are identified by sequentially specifying the column, which is identified by an alphabet, and the row, which is identified by a number (for example, "cell A1"). In Figure 5, for example, the string "Experimental Equipment" is stored as the value of cell B3, and the string "Tammann Tube" is stored as the value of cell D3.

[0036] The layout is primarily depicted using thick lines and arrows in Figure 5. In this embodiment, the elements that constitute the layout are called parsing objects. In this embodiment, the parsing objects are the header parser 92, the sequence parser 93, and the table parser 95. However, other parsing objects may also be present. Furthermore, the layout may not include any or all of these parsing objects.

[0037] The heading parser 92 is an arrow extending from the cell indicating the heading to the cell or table parser 95 that contains the heading's content. The heading parser 92 connects two cells, or a cell and a table parser 95. In Figure 5, the heading parser 92 is represented, for example, by a triangular-tipped arrow extending from cell B3 to cell D3. The heading parser 92 may also indicate an inclusion relationship.

[0038] The table parser 95 is a parsing object that specifies a table whose data content is structured in rows and columns. The table parser 95 consists of a whole table section 951 that shows the entire table and a table data section 952 that shows the data portion. In this embodiment, the whole table section 951 that is not included in the table data section 952 is referred to as the header or header area.

[0039] In Figure 5, the entire table portion 951 of the table parser 95 is represented by a rectangle with cells B9 and D13 as its diagonal vertices, while the table data portion 952 is represented by a rectangle with cells C10 through D13 as its diagonal vertices. Here, the upper left and lower right corners of the table data portion 952 are shown as black-filled triangles to distinguish the entire table portion 951 from the table data portion 952.

[0040] The sequence parser 93 is a parsing object that connects cells and represents the order in the direction indicated by the arrows. In Figure 5, for example, the sequence parser 93 is shown for cells C16, C18, and C20 by arrows extending from cell C16 to cell C18 and from cell C18 to cell C20. To distinguish the sequence parser 93 from the header parser 92, in this embodiment, each arrow has a V-shaped tip.

[0041] These parsing objects are included in the layout corresponding to the tabular data and are stored as a layout file in the layout file storage unit 63. The management file 61 can also store the file path of the corresponding layout file in the record of the corresponding tabular file. The layout file may store the layout structure information by converting each parsing object placed in the tabular data into a string or the like. For example, the layout structure information can be stored in the layout file by describing the header parser 92 extending from cell B3 to cell D3 using a predetermined syntax such as "Header:B3:D3".

[0042] Server device 1 may convert tabular data into semi-structured data based on the parsing objects described above. Semi-structured data can be output by applying a layout to tabular data. For example, it can be data written in JSON (JavaScript® Object Notation) format and XML (eXtensible Markup Language) format. Semi-structured data is data that explicitly defines and describes combinations of data names and the content of data related to those names, and can also describe inclusion relationships in a nested format. Furthermore, semi-structured data cannot be managed as a single relational database or tabular data, but can be defined as data that is structured to a certain extent.

[0043] For example, the header parser 92, which extends from cell B3 to cell D3, can be written in JSON format as follows: {"key": "Laboratory equipment", "value": [{"key": "Tammann tube"}]} By performing this conversion to create semi-structured data, it becomes possible to search for and easily extract necessary information from tabular data with different layouts.

[0044] Furthermore, rules for converting parsing objects other than the header parser 92 into semi-structured data can be appropriately defined. The rules for converting to semi-structured data do not have to be rules for converting to JSON format; they may also be rules for converting to XML format or other semi-structured data formats. The parsing objects are not limited to the header parser 92, sequence parser 93, and table parser 95, and can be defined as appropriate, and the rules for converting each parsing object into semi-structured data can be appropriately defined. In this embodiment, even when the conversion of semi-structured data is not described, it is permissible to convert to semi-structured data using tabular data and layouts, or to convert to tabular data and layouts based on semi-structured data, as appropriate.

[0045] Figure 6 is a flowchart illustrating an example of the processing performed by the server device 1. As shown in this figure, the server device 1 first accepts the selection of a tabular file in which tabular data is stored (step S11). The selection of a tabular file can be done by displaying the folder hierarchy structure on the display unit 26 of the user's terminal device 2, displaying the tabular files in the selected folder, and allowing the user to select a displayed tabular file. Alternatively, tabular files related to keywords may be displayed through a search, and the user may select a tabular file from among them. The server device 1 may also be able to accept the selection of one or more tabular files simultaneously.

[0046] Next, the server device 1 extracts the layout-defined data from the selected tabular file (step S12). Here, the layout-defined data refers to the tabular data in which the header parser 92, table parser 95, and sequence parser 93 described above are placed, with the layout file associated with the tabular file applied to the tabular file. Subsequently, the server device 1 outputs a list of header candidates for the integrated table from the layout-defined data (step S13). The output list of header candidates is displayed on the display unit 26 of the terminal device 2. The list of header candidates for the integrated table that is displayed will be described later.

[0047] Next, the server device 1 accepts editing and selection of the displayed list of header candidates via the terminal device 2 (step S14). The server device 1 generates an integrated table using the selected header and displays the integrated table in the preview area 813 (Figure 8) (step S15). Alternatively, the server device 1 may directly display the integrated table after extracting the layout-defined data without displaying the list of header candidates.

[0048] Next, the server device 1 determines whether it has been instructed to save the previewed integrated table (step S17). If it determines that saving has been instructed (YES in step S17), the server device 1 performs the save process and terminates the process (step S18). In the save process, the tabular file and the layout file may be saved, and their respective file paths may be saved in a new record in the management file 61. If it determines that saving has not been instructed (NO in step S17), the server device 1 returns to step S14 and repeats the process.

[0049] In this way, server device 1 generates an integrated table based on the header selected from a list of header candidates created from the extracted multiple layout-defined data. This allows for consideration of whether to display or hide the headers of the displayed integrated table by viewing them in a list.

[0050] [1. Example when the number of tabular files is 1] Figure 7 shows an example of the structure of a tabular file 71. The tabular file 71 can be a tabular file stored in the tabular linked data 60, which is selected in step S11 of Figure 6. The tabular file 71 has sheets 711, 712, and 713 that contain tabular data.

[0051] Sheets 711, 712, and 713 are named "Experimental Information," "Experimental Results 1," and "Experimental Results 2," respectively. Sheet 711 contains layout-defined data 7111 defined by a heading parser 92 with "Person in Charge" as the heading and "Tanaka" as the content, and another heading parser 92 with "Sample Name" as the heading and "LaFeAs" as the content. Sheets 712 and 713 contain layout-defined data 7121 and 7131 defined by a table parser 95 with "Sample ID," "Electrical Resistivity (300K)," and "Transition Point" as the header names.

[0052] [1.1. Splitting unit: File] Figure 8 shows an example of screen 81, which includes a list of header candidates. Here, screen 81 is the screen displayed on the display unit 26 of terminal device 2 as a result of the output of step S13 in Figure 6, and is the screen for the tabular file 71 in Figure 7. As shown in this figure, screen 81 has a data division unit selection area 811, a header candidate list display area 812, a preview area 813, a save button 814, and a preview button 815.

[0053] Server device 1 accepts one of the following as the data division unit via the data division unit selection area 811: file, sheet, or table. Server device 1 arranges the layout-defined data 7111, 7121, and 7131 vertically or horizontally within the selected division unit (Figures 9-12). In the example in Figure 8, "file" is selected as the division unit. The header candidate list display area 812 has a header name field 8121, a count field 8122, a type field 8123, and an edit link 8124.

[0054] Server device 1 extracts the headings from the heading parser 92 as header candidates. Server device 1 also extracts the contents of each table header from the table parser 95 as header candidates. The header name column 8121 displays the header names of the extracted header candidates. Server device 1 also displays a checkbox adjacent to the header name to select whether to use that header candidate as the header of the integrated table.

[0055] Thus, the layout includes one or more of the following: a header parser 92 that defines values ​​and headers for the values, and a table parser 95 that defines tables. The server device 1 can output either the headers of the header parser 92 or the headers of the table parser 95 as header candidates in a list. This makes it possible to create an integrated table by combining the layout-defined data of the header parser 92 and the layout-defined data of the table parser 95.

[0056] In Figure 7, the table parser 95 of the tabular file 71 does not have a header parser 92 connected to it. Therefore, in the header candidate list display area 812 of Figure 8, the table name is displayed as "(blank)". However, if the header parser 92 is connected to the table parser 95, the header of the header parser 92 will be displayed as the table name in the header name column 8121.

[0057] As shown in Figure 8, when displaying the headers included in the table (for example, "Sample ID", "Electrical Resistivity (300K)", "Transition Point") in the header name field 8121, the server device 1 displays them by listing them with indentation immediately after the header candidate that will become the table heading (for example, "Experimental Results 1.Table:(blank)").

[0058] Here, the server device 1 displays the columns (or rows) of the integrated table in the order they are displayed in the header candidate list display area 812. Based on operations performed by the user of the terminal device 2, such as drag-and-drop using the input unit 27 of the terminal device 2 (e.g., a mouse), the server device 1 changes the order of the header candidates in the header candidate list display area 812. In this configuration, changing the display order of the header candidates in the header candidate list display area 812 is called "header editing." In this way, the server device 1 accepts editing of the position where the header candidates are displayed on the integrated table from the list of header candidates, accepts the selection of header candidates to display, and generates the integrated table based on the selected headers.

[0059] The count column 8122 displays the number of times the header name of a header candidate appears in the layout-defined data extracted from the selected tabular file. Server device 1 can display the number of times the header candidate appears as a heading or header in multiple layout-defined data, along with the header candidate itself. This allows users to check whether a header is identified as a common header in multiple layout-defined data and displayed in the same column of the integrated table.

[0060] The Type column 8123 primarily displays the type of layout (header type) from which header candidates for predefined data were extracted. Specifically, "Value" is displayed if the header candidate is based on a header from the Heading Parser 92, and "Table" is displayed if the header candidate is based on a header from the Table Parser 95.

[0061] In this way, server device 1 identifies the headers of the header parser and the table parser, which are header candidates, as different header types, and displays the header types together with the header candidates, associating them with the header candidates. This allows the user to confirm which layout type the displayed header candidates were in the original tabular file.

[0062] The metadata header candidate type field displays "metadata". The metadata header candidate has the header name "metadata" and is a header candidate for remembering either the folder path of the folder where the selected tabular file is saved, the file name of the tabular file, the sheet name of the sheet, or a table path that is a combination of the file name, sheet name, and table headers or a combination of these.

[0063] In Figure 8, when "file" is used as the unit of division, Server Device 1 displays header candidates for "Book," which displays the file name, and header candidates for "Folder Path," which displays the file path of the folder in which the file is stored. Server Device 1 lists the header candidates for "Book" and "Folder Path" with an indent immediately after the header candidate for "Metadata" in Header Name column 8121. Edit link 8124 accepts edits such as whether to display the integrated table vertically or horizontally.

[0064] The preview area 813 displays the table generated by the header selected in the header candidate list display area 812. The save button 814 is a button for sending a save command to the server device 1. When the user clicks the save button 814 or performs other actions, it sends a save command to the server device 1. Upon receiving the save command, the server device 1 saves the contents displayed in the preview area 813 as a tabular file or similar.

[0065] The preview button 815 is a button that sends an instruction to the server device 1 to output an integrated table using the header selected in the header candidate list display area 812 to the preview area 813. When the terminal device 2 receives an operation such as clicking the preview button 815 from the user, it sends a preview instruction to the server device 1. Upon receiving the preview instruction, the server device 1 creates an integrated table using the header selected in the header candidate list display area 812 and outputs it to the preview area 813.

[0066] In Figure 8, server device 1 accepts selection of "file" as the splitting unit. When a file (tabular file) is selected as the splitting unit, server device 1 includes the sheet name in the header name of the header candidate displayed in the header candidate list display area 812. Specifically, server device 1 displays a string in the header name of the header candidate that connects the sheet name and the header of the header parser 92 or the table parser 95 ("(blank)" in Figure 14) via a "." (period).

[0067] For example, in the display of the header name field 8121, the sheet name "Experiment Information" and the header name "Person in Charge" generated by the header parser 92 are connected by a "." (period), resulting in "Experiment Information.Person in Charge". By creating a header that combines the sheet name and the header from the header parser 92 in this way, even if there are header candidates with the same name on different sheets when "files" are used as the unit of division, the server device 1 can treat them as different headers and display them in the header candidate list display area 812.

[0068] Figure 9 shows an example of an integrated table displayed in the preview area 813. The integrated table displayed in the preview area 813 in Figure 9 is the same as the content displayed in the header candidate list display area 812 in Figure 8. When all of the displayed header candidates are selected (checked in the checkboxes), the server device 1 displays the integrated table by operating the preview button 815.

[0069] As shown in the integrated table in Figure 9, among the multiple levels of headers in the integrated table, Server Device 1 adopts the sheet name displayed before the "." (period) in the header candidate list display area 812 in Figure 8 as the upper-level header encompassing the header candidates within the sheet. Furthermore, Server Device 1 adopts the string displayed after the "." (period) in the header candidate list display area 812 as the lower-level header encompassed by the said sheet name header.

[0070] The headers in the lower rows will be headers where the Type field 8123 is set to "Value" or "Table". Furthermore, Server Device 1 adopts the header candidate (table header) displayed in indentation immediately after the header candidate where the Type field 8123 is set to "Table" in the Header Name field 8121 of Figure 8 as the header of the integrated table, as a header below the header where the Type field 8123 is set to "Table". In Figure 9, the integrated table is shown as a horizontal table with the header at the top, but it may also be a vertical integrated table with the header on the left.

[0071] As shown in this table, the partitioning unit is "file," and since the selected tabular file is a single tabular file 71, the server device 1 does not use a common header and outputs the data in a single row. Note that the integrated table may extend in the column direction by transposing rows and columns. In this way, the server device 1 arranges multiple tabular data with different headers sequentially in either the vertical or horizontal direction.

[0072] [1.2. Splitting unit: Sheet] Figure 10 is an explanatory diagram showing an example of a header candidate list and integrated table when the division unit is set to "sheet". In Figure 10, along with the header candidate list display area 812, the integrated table that will be displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. As shown in the header candidate list display area 812 of this figure, when the division unit is set to "sheet", the sheet name is not appended to the header name, and header names with the same string on different sheets are treated as common header candidates across sheets.

[0073] In Figure 7, the layout-defined data 7121 for sheet 712 and the layout-defined data 7131 for sheet 713, related to the table parser 95, have the same string header. Therefore, in the example of the header candidate list display area 812 in Figure 10, where the division unit is set to "sheet," the server device 1 uses the common header names for the layout-defined data 7121 and the layout-defined data 7131 as common header candidates. As a result, the header candidates "Sample ID," "Electrical Resistivity (300K)," and "Transition Point" extracted by the table parser 95 appear in both the layout-defined data 7121 and 7131, becoming common header candidates, and the display in the count column 8122 for these header candidates is 2.

[0074] Furthermore, as shown in the header candidate list display area 812 of Figure 10, even when the division unit is set to "sheet," the layout includes one or more of the header parser 92 that defines values ​​and value headings, and the table parser 95 that defines tables. The server device 1 can output either the headings of the header parser 92 or the headers of the table parser 95 as header candidates in the list. This makes it possible to create an integrated table by combining the layout-defined data of the header parser 92 and the layout-defined data of the table parser 95.

[0075] Furthermore, regarding metadata header candidates when "sheets" are used as the splitting unit, Server Device 1 displays header candidates with the same header names "Book" and "Folder Path" as when "files" are used as the splitting unit, as well as a header candidate with the header name "Sheet" that displays the sheet name, in the header candidate list display area 812. In this way, when (partially) sheets are used as the splitting unit, Server Device 1 can add the sheet name to the metadata. This allows users to navigate to the sheets in the original tabular file.

[0076] Here, the target tabular file 71 has layout-defined data 7111, 7121, and 7131 in three sheets, respectively (Figure 7). Since the division unit is "sheet," as shown in the integrated table in the preview area 813 of Figure 10, the server device 1 generates a three-row integrated table in the preview area 813, in which the layout-defined data 7111, 7121, and 7131 placed on each sheet are arranged vertically in order. Note that the integrated table may extend in the column direction by transposing the rows and columns.

[0077] Here, in the metadata, the "Book" column, which displays the file name for each row, is the same, while the "Sheet" column, which displays the sheet name, is different for each row. The metadata indicates that the contents of the cells in each row are data extracted from different sheets within the same file. In this way, server device 1 generates an integrated table by arranging the layout-defined data vertically (or horizontally) within the selected division unit.

[0078] Furthermore, as described above, Server Device 1 arranges multiple tabular data sets having common headers ("Sample ID," "Electrical Resistivity (300K)," and "Transition Point") sequentially in a first direction (vertical direction), which is either vertical or horizontal. Also, Server Device 1 arranges multiple tabular data sets having different headers ("Person in Charge" and "Sample Name") sequentially in a second direction (horizontal direction), which is either vertical or horizontal and different from the first direction. In the example in Figure 10, the different headers are arranged horizontally while also being moved vertically. This makes it possible to create an easy-to-read and comprehensive integrated table by arranging the contents of common headers in one direction for easy comparison, and describing non-common headers as separate information.

[0079] Figure 11 shows another example of an integrated table displayed when the division unit is set to "sheet". Server device 1 may determine that sheets 712 and 713 are sheets with the same attributes because the sheet names "Experimental Results 1" and "Experimental Results 2" are strings consisting of the same term and the numbers associated with that term. Alternatively, sheet 711, "Experimental Information," may be determined to be a sheet with different attributes from sheets 712 and 713.

[0080] In this case, as shown in the integrated table in Figure 11, sheets 712 and 713, which have common attributes, can be arranged vertically (or horizontally), and sheet 711, which has different attributes, can be arranged horizontally (or vertically). In this way, tabular data with common attributes can be arranged sequentially in a first direction, either vertically or horizontally, in units of division, and tabular data with different attributes can be arranged sequentially in a second direction, either vertically or horizontally, that is different from the first direction, in units of division.

[0081] This allows for the creation of a user-friendly and comprehensive integrated table by arranging the division units of common attributes in one direction for easy comparison, and displaying the division units of different attributes separately in a different direction. In the example in Figure 11, metadata is not selected in the header candidate list display area 812, and therefore metadata is not displayed in the integrated table.

[0082] Furthermore, even when multiple tabular data sets having a common header are arranged sequentially in a first direction, either vertically or horizontally, and tabular data sets having different headers are arranged in a second direction, either vertically or horizontally, that is different from the first direction, the server device 1 can output an integrated table like the one shown in Figure 11. For example, if metadata is not selected in the header candidate list display area 812 and metadata is not displayed in the integrated table, the server device 1 can output an integrated table like the one shown in Figure 11 by arranging tabular data sets having different headers (e.g., sheet name "Experiment Information") in the second direction (horizontal) without moving them in the first direction (vertical) relative to other tabular data sets (sheet name "Experiment Results 1").

[0083] [1.3. Unit of division: Table] Figure 12 is an explanatory diagram showing an example of a header candidate list and an integrated table when the division unit is set to "table". In Figure 12, along with the header candidate list display area 812, the integrated table that will be displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. As shown in the header candidate list display area 812 of this figure, when the division unit is set to "table", the headings of the heading parser 92 are not extracted as header candidates, just as when the division unit is set to "sheet", and header names with the same string in different tables are treated as common header candidates among the layout-defined data.

[0084] The target tabular file 71 has layout-defined data 7111, 7121, and 7131 in three sheets, respectively (Figure 7). However, since the division unit is "table," the server device 1 targets only the layout-defined data 7121 and 7131, including the table parser 95, as header candidates.

[0085] Similar to the case in Figure 10 where the division unit is "sheet," in the example of the header candidate list display area 812 in Figure 12, the server device 1 adopts the same string header names in the layout-defined data 7121 and 7131 in Figure 7 as common header candidates. Specifically, the header candidates "Sample ID," "Electrical Resistivity (300K)," and "Transition Point" extracted by the table parser 95 appear in both the layout-defined data 7121 and 7131, and therefore become common header candidates, resulting in a display of 2 in the count column 8122 for these header candidates.

[0086] Furthermore, when "tables" are used as the partitioning unit, Server Device 1 displays header candidates such as "Book," "Folder Path," and "Sheet" as metadata, similar to when "sheets" are used as the partitioning unit, and also displays header candidates for the header name "Key" to identify tables within a sheet.

[0087] As shown in the header candidate list display area 812 of Figure 12, the layout includes a table parser 95 that defines multiple tables, and the server device 1 can output the headers of the multiple table parsers 95 as header candidates in a list. This makes it possible to create an integrated table by combining the layout-defined data of multiple table parsers 95.

[0088] As described above, the integrated table created targets the layout-defined data 7121 and 7131, which have a table parser 95. As shown in the integrated table in the preview area 813 of Figure 12, the partitioning unit is a "table," so the server device 1 arranges the layout-defined data 7121 and 7131 based on the table parser 95 in order vertically to generate a two-row integrated table. The integrated table may also have two columns in the column direction by transposing the rows and columns.

[0089] Here, regarding the metadata of the integrated table, the contents of the "Book" column, which displays the file name for each row, are all the same, but the contents of the "Sheet" column, which displays the sheet name, are different from each other. This indicates that the contents of the cells in each row are data extracted from different sheets in the same file. In addition, Server Device 1 displays a combination of the file name and sheet name connected by a "." (period) in the "Key" column.

[0090] If a header parser 92 is further connected to the extracted table parser 95, the "Key" column may display the table header after the sheet name, separated by a period ("."). This allows the "Key" column to be displayed as a table path, which is a string that identifies the table. Alternatively, the "Key" column may display only the table header, without displaying the file name or sheet name. Furthermore, if one or more header parsers 92 are hierarchically connected to the header parser 92 connected to the table parser 95, the "Key" column may display the headers of each header parser connected in hierarchical order with periods ("."). In this way, when (partially) tables are used as the unit of division, the server device 1 can add the sheet name and table path to the metadata. This allows users to navigate through the sheets and tables of the original tabular file.

[0091] As described above, Server Device 1 acquires a tabular file containing tabular data associated with layouts that define the relationships between multiple cells, and extracts layout-defined data that is included in the tabular data and is defined as being subject to a layout. Server Device 1 also outputs a list of header candidates for an integrated table that combines the extracted multiple layout-defined data, and generates the integrated table based on the list of header candidates. This allows users to review the header candidates for the integrated table in a list before creating the integrated table. Therefore, the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data can be further enhanced.

[0092] Furthermore, the system accepts one of the following as a partitioning unit: a tabular file, one or more sheets contained within a tabular file that contain tabular data, or a table that is layout-defined data defined as a table within the tabular data. Server device 1 can extract header candidates for the integrated table from the layout-defined data contained in the accepted partitioning unit and output a list of header candidates. This allows the system to create an integrated table that meets the user's requirements.

[0093] [2. Example when there are 2 tabular files] Figure 13 shows an example of the configuration of tabular files 72 and 73. Tabular files 72 and 73 can be tabular files stored in the tabular linked data 60, which are selected in step S11 of Figure 6. Tabular file 72 has the file name "Super Z Inspection_1" and has sheets 721, 722, and 723 containing tabular data. Tabular file 73 has the file name "Super Z Inspection_2" and has sheets 731, 732, and 733 containing tabular data.

[0094] Sheets 721, 722, and 723 of the tabular file 72 are named "Experimental Information," "Process 1," and "Process 2," respectively. Sheet 721 contains layout-defined data 7211 defined by the heading parser 92, with headings "Person in Charge," "Sample Name," "Type," and "Overview," respectively. Sheet 722 contains layout-defined data 7221 defined by the heading parser 92, with headings "Process Name," "Contact Drying Time," and "Glass Transition Temperature," respectively.

[0095] Sheet 723 contains layout-defined data 7231A defined by the header parser 92 with "Process Name" as the header, and layout-defined data 7231B defined by the table parser 95 with "Shear Load Stress (MPa)" and "Breakage Time (hr)" as headers. Layout-defined data 7231A and 7231B are collectively referred to as layout-defined data 7231.

[0096] Sheets 731, 732, and 733 of tabular file 73 are named "Experimental Information," "Process 1," and "Process 2," respectively, similar to sheets 721, 722, and 723 of tabular file 72. Sheet 731 contains layout-defined data 7311, which has the same headings as layout-defined data 7211 of sheet 721. Sheet 732 contains layout-defined data 7321, which has the same headings as layout-defined data 7221 of sheet 722. Sheet 733 contains layout-defined data 7331A, which has the same headings as layout-defined data 7231 of sheet 723, and layout-defined data 7331B, which has the same headers as layout-defined data 7231B. Layout-defined data 7331A and 7331B are collectively referred to as layout-defined data 7331.

[0097] [2.1. Splitting unit: File] Figure 14 is an explanatory diagram showing an example of a list of header candidates and an integrated table when the division unit is set to "file". In Figure 14, along with the header candidate list display area 812, the integrated table that will be displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. Below, we will explain an example in step S11 of Figure 6 where tabular files 72 and 73 of Figure 13 are selected and the division unit is set to "file". As shown in the header candidate list display area 812 of Figure 14, when the division unit is set to "file (tabular file)", the server device 1 includes the sheet name of the sheet in the header name of the header candidate, similar to Figure 8.

[0098] Specifically, the server device 1 displays a string in the header name of a header candidate that connects the sheet name and the heading of the heading parser 92 or the heading of the table parser 95 (shown as "(blank)" in Figure 14) via a "." (period). For example, in the display of the header name field 8121, the sheet name "Experiment Information" and the header name "Person in Charge" from the heading parser 92 are connected by a "." (period), resulting in "Experiment Information.Person in Charge". By creating a header that combines the sheet name and the heading of the heading parser 92 in this way, even if there are header candidates with the same name on different sheets when "files" are used as the unit of division, the server device 1 can treat them as different headers and display them in the header candidate list display area 812.

[0099] Furthermore, since tabular files 72 and 73 have the same sheet name, the same heading parser 92, and the same table parser 95 with the same header, the count of each header candidate excluding metadata is 1 per sheet, totaling 2. The "metadata" in the header name column 8121 has header candidates with the header names "Book" and "folder path," similar to Figure 8.

[0100] As shown in the integrated table in preview area 813 of Figure 14, the server device 1, similar to Figure 8, adopts the sheet name before the "." (period) in the header candidate list display area 812 as the upper-level header that encompasses the header candidates within the sheet, among the multi-level headers in the integrated table. The server device 1 also adopts the string displayed after the "." (period) in the header candidate list display area 812 as the lower-level header that is contained within the said sheet name header.

[0101] The headers in the lower rows will be headers where the Type field 8123 is set to "Value" or "Table". Furthermore, Server Device 1 adopts the header candidate (table header) displayed in indentation immediately after the header candidate where the Type field 8123 is set to "Table" in the Header Name field 8121 of Figure 14 as the header of the integrated table, as a header below the header where the Type field 8123 is set to "Table". In Figure 14, the integrated table is shown as a horizontal table with the header at the top, but it may also be a vertical integrated table with the header on the left.

[0102] As shown in the header candidate list display area 812 of Figure 14, the layout includes one or more of the header parser 92 that defines values ​​and value headings, and the table parser 95 that defines tables. The server device 1 can output either the headings of the header parser 92 or the headers of the table parser 95 as header candidates in the list. This makes it possible to create an integrated table by combining the layout-defined data of the header parser 92 and the layout-defined data of the table parser 95.

[0103] As shown in the integrated table in preview area 813 of Figure 14, since the partitioning unit of server device 1 is "file," the data of tabular files 72 and 73 are arranged vertically on a file-by-file basis. On the other hand, the headers within each tabular file 72 and 73 are arranged horizontally. Specifically, server device 1 arranges the header candidates contained in the sheet names "Experiment Information," "Process 1," and "Process 2" horizontally. Meanwhile, headers with the same header name between each tabular file 72 and 73 are common, and the values ​​are displayed in the same header column. In the integrated table of Figure 14, since all headers except metadata are common, the data from header parser 92 and table parser 95 are displayed in the common header column, respectively.

[0104] Here, the layout-defined data 7231 and 7331 extracted by the table parser 95 each have three data entries per header. Therefore, the server device 1 displays the data using three rows for each of the tabular files 72 and 73. Also, since the selected tabular files are two files, tabular files 72 and 73, the contents of tabular files 72 and 73 are arranged vertically. In other words, it becomes a combined table with a total of six rows.

[0105] As described above, Server Device 1 arranges multiple tabular data sets having a common header in a first direction (vertical direction), which is either vertical or horizontal. Server Device 1 also arranges multiple tabular data sets having different headers in a second direction (horizontal direction), which is different from the first direction, either vertically or horizontally. In the example in Figure 14, data with different headers are arranged horizontally while also being moved vertically. This allows for the creation of a clear and comprehensive integrated table by arranging the contents of common headers in one direction for easy comparison, and treating non-common headers as separate information. The integrated table may also be created by transposing rows and columns and extending it in the column direction.

[0106] In the metadata, Server Device 1 displays the file name in the "Book" column and the folder path where the tabular file is saved in the "Folder Path" column.

[0107] [2.2. Splitting unit: Sheet] Figure 15 is an explanatory diagram showing an example of a header candidate list and integrated table when the division unit is set to "sheet". In Figure 15, along with the header candidate list display area 812, the integrated table that is displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. As shown in the header candidate list display area 812 of this figure, when the division unit is set to "sheet", the sheet name is not appended to the header name, and headers with the same string in different sheets are treated as common header candidates across sheets.

[0108] Aside from the absence of sheet names and metadata, the only difference between the header candidate list display area 812 in Figure 15 and the header candidate list display area 812 in Figure 14 is that the count for "Process Name" in the header name column 8121 is 4. In the header candidate list display area 812 in Figure 14, the sheet name was attached to the header name column 8121, so "Process Name" in the header name column 8121 was treated as different headers for the sheet names "Process 1" and "Process 2". However, when the division unit is set to "Sheet" in Figure 15, the server device 1 treats "Process Name," which has the same header name, as a common header candidate and displays it as a common header in the integrated table.

[0109] Furthermore, as shown in the header candidate list display area 812 of Figure 15, even when the division unit is set to "sheet," the layout includes one or more of the header parser 92 that defines values ​​and value headings, and the table parser 95 that defines tables. The server device 1 can output either the headings of the header parser 92 or the headers of the table parser 95 as header candidates in the list. This makes it possible to create an integrated table by combining the layout-defined data of the header parser 92 and the layout-defined data of the table parser 95.

[0110] The explanation of the metadata in Figure 15 is the same as the explanation for Figure 10, so redundant explanations will be omitted.

[0111] Here, the tabular file 72 in question has layout-defined data 7211, 7221, and 7231 in three sheets, respectively (Figure 13). Similarly, the tabular file 73 has layout-defined data 7311, 7321, and 7331 in three sheets, respectively. Because the division unit is "sheet," as shown in the integrated table in the preview area 813 of Figure 15, the server device 1 arranges the layout-defined data 7211, 7221, 7231, 7311, 7321, and 7331 vertically in order to form an integrated table of 10 rows.

[0112] Here, the header name "Process Name" is used as a common header, so the number of headers (columns) is one less compared to the integrated table in preview area 813 of Figure 14. In this way, server device 1 generates the integrated table by arranging the layout-defined data vertically in the selected division unit. Note that the integrated table may also be one in which the rows and columns have been transposed and extended in the column direction.

[0113] Furthermore, as described above, the server device 1 arranges multiple tabular data sets having a common header in a first direction (vertical direction), which is either vertical or horizontal. The server device 1 also arranges multiple tabular data sets having different headers in a second direction (horizontal direction), which is either vertical or horizontal and different from the first direction. Here, the second direction may involve moving in the first direction while arranging in the second direction. This allows for the creation of an easy-to-read and comprehensive integrated table by arranging the contents of common headers in one direction for easy comparison, and describing non-common headers as separate information.

[0114] [2.3. Unit of division: Table] Figure 16 is an explanatory diagram showing an example of a header candidate list and an integrated table when the division unit is set to "table". In Figure 16, along with the header candidate list display area 812, the integrated table that is displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. As shown in the header candidate list display area 812 of this figure, when the division unit is set to "table", the headers of the header parser 92 are not extracted as header names, and headers with the same string on different sheets are treated as common header candidates among the layout-defined data.

[0115] Of the target tabular files 72 and 73, the layout-defined data 7231 contained in sheet 723 and the layout-defined data 7331 contained in sheet 733 are eligible to be considered as header candidates. Excluding metadata, the header candidate list display area 812 in Figure 16 is the same as the list in the header candidate list display area 812 in Figure 15, excluding the header names with type "Value" in the type column 8123, and redundant explanations are omitted.

[0116] The explanation of the metadata in Figure 16 is the same as the explanation in Figure 12, so redundant explanations are omitted. As shown in the header candidate list display area 812 of Figure 16, the layout includes a table parser 95 that defines multiple tables, and the server device 1 can output the headers of the multiple table parsers 95 as header candidates in a list. This makes it possible to create an integrated table by combining the layout-defined data of the multiple table parsers 95.

[0117] Since the division unit is "table" and the target tables are the layout-defined data 7231B and 7331B in Figure 13, the integrated table will be a table in which the layout-defined data 7231B and 7331B are arranged vertically, as shown in the preview area 813 of Figure 16. Since the layout-defined data 7231B and 7331B have a common header, the values ​​will be displayed in the corresponding common headers. In this way, the server device 1 generates the integrated table by arranging the layout-defined data vertically in the selected division unit. The integrated table may also be arranged with the rows and columns transposed to extend in the column direction.

[0118] As described above, Server Device 1 acquires a tabular file containing tabular data associated with layouts that define the relationships between multiple cells, and extracts layout-defined data that is included in the tabular data and is defined as being subject to a layout. Server Device 1 also outputs a list of header candidates for an integrated table that combines the extracted multiple layout-defined data, and generates the integrated table based on the list of header candidates. This allows users to review the header candidates for the integrated table in a list before creating the integrated table. Therefore, the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data can be further enhanced.

[0119] Furthermore, the system accepts one of the following as a partitioning unit: a tabular file, one or more sheets contained within a tabular file that contain tabular data, or a table that is layout-defined data defined as a table within the tabular data. Server device 1 can extract header candidates for the integrated table from the layout-defined data contained in the accepted partitioning unit and output a list of header candidates. This allows the system to create an integrated table that meets the user's requirements.

[0120] [3. Example when there are 6 tabular files] Figure 17 shows an example of the structure of tabular files 74-79. Tabular files 74-79 can be tabular files stored in tabular linked data 60, which are selected in step S11 of Figure 6. Tabular file 74 has the file name "Super Z Inspection_1 Experiment Information" and has sheet 741. Sheet 741 has layout-defined data 7411 defined by a heading parser 92 with headings "Person in Charge", "Sample Name", "Type", and "Overview".

[0121] Tabular file 75 has the filename "Super Z Inspection_1 Process 1" and contains sheet 751. Sheet 751 contains layout-defined data 7511 defined by the header parser 92, with the headers "Process Name", "Contact Drying Time", and "Glass Transition Temperature". Tabular file 76 has the filename "Super Z Inspection_1 Process 2" and contains sheet 761. Sheet 761 contains layout-defined data 7611A defined by the header parser 92, with the header "Process Name". It also contains layout-defined data 7611B defined by the table parser 95, with the header names "Shear Load Stress (MPa)" and "Breakage Time (hr)". Layout-defined data 7611A and 7611B are referenced together with layout-defined data 7611.

[0122] Tabular file 77 has the filename "Super Z Inspection_2 Experiment Information" and contains sheet 771. Sheet 771, like sheet 741, contains predefined layout data 7711 defined by a heading parser 92 with headings "Person in Charge", "Sample Name", "Type", and "Overview". Tabular file 78 has the filename "Super Z Inspection_2 Process 1" and contains sheet 781. Sheet 781, like sheet 751, contains predefined layout data 7811 defined by a heading parser 92 with headings "Process Name", "Contact Drying Time", and "Glass Transition Temperature".

[0123] Tabular file 79 has the filename "Super Z Inspection_2nd Process 2" and contains sheet 791. Sheet 791, like sheet 761, contains layout-defined data 7911A defined by the header parser 92 with the header name "Process Name". It also contains layout-defined data 7911B defined by the table parser 95 with the header names "Shear Load Stress (MPa)" and "Breakage Time (hr)". Layout-defined data 7911A and 7911B are referenced together with layout-defined data 7911.

[0124] [3.1. Splitting unit: File] Figure 18 is an explanatory diagram showing an example of a header candidate list and integrated table when the division unit is set to "file". In Figure 18, along with the header candidate list display area 812, the integrated table that will be displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. The following describes an example in step S11 of Figure 6 where tabular files 74 to 79 are selected and the division unit is set to "file". As shown in the header candidate list display area 812 of Figure 18, when the division unit is set to "file (tabular file)", the server device 1 includes the sheet name of the sheet in the header name of the header candidate, as in the case of Figure 8.

[0125] Specifically, the server device 1 displays a string in the header name of the header candidate that is a combination of the sheet name "Sheet1" and the header of the header parser 92 or the table parser 95 (shown as "(blank)" in Figure 14) connected by a "." (period). This allows the server device 1 to treat them as different headers and display them in the header candidate list display area 812 even if there are header candidates with the same name on different sheets when "files" are used as the splitting unit.

[0126] Furthermore, tabular files 74-76 have the same sheet names, the same header parser 92, and the same header parser 95 as tabular files 77-79, respectively. Therefore, the total count for each header candidate, excluding metadata, is 2. However, the header name "Sheet1.Process Name" appears a total of 4 times in tabular files 75-76 and 78-79, so the count for header name 8121 for "Sheet1.Process Name" is 4.

[0127] The explanation of the metadata in Figure 18 is the same as that in Figures 8 and 9, so redundant explanations are omitted. As shown in the header candidate list display area 812 of Figure 18, the layout includes one or more of the header parser 92 that defines values ​​and value headings, and the table parser 95 that defines tables, and the server device 1 can output either the headings of the header parser 92 or the headers of the table parser 95 as header candidates in the list. This makes it possible to create an integrated table that combines the layout-defined data of the header parser 92 and the layout-defined data of the table parser 95.

[0128] As shown in the integrated table in preview area 813 of Figure 18, the server device 1, similar to Figure 8, adopts the sheet name before the "." (period) in the header candidate list display area 812 as the higher-level header encompassing the header candidates within the sheet, among the multi-level headers in the integrated table. In the case of Figure 18, since all sheet names are the same "Sheet1", the header for Sheet1 is used across all headers except metadata.

[0129] Furthermore, Server Device 1 adopts the string displayed after the "." (period) in the header candidate list display area 812 as the header for the next row below the sheet name header. The next row header will be the header with the type field 8123 set to "Value" or "Table". Additionally, Server Device 1 adopts the header candidate (table header) displayed with an indent immediately after the header candidate with the type field 8123 set to "Table" in the header name field 8121 of Figure 18 as the header for the integrated table, as a further lower-level header for the header with the type field 8123 set to "Table". In Figure 18, the integrated table is shown as a horizontal table with the header at the top, but it may also be a vertical integrated table with the header on the left.

[0130] As shown in the integrated table in preview area 813 of Figure 18, the division unit is "file," so server device 1 arranges the tabular data of tabular files 74-79 vertically on a file-by-file basis. On the other hand, as shown in header candidate list display area 812, tabular files 74-76 and tabular files 77-79 have a common header, so server device 1 arranges the headers horizontally in the order shown in header candidate list display area 812. Server device 1 arranges a total of six tabular files 74-79 vertically, but two of the six tabular files, tabular files 76 and 79, are 3-row tables, and the remaining one is a header parser 92 displayed on one row, resulting in an integrated table of 10 rows in total.

[0131] As described above, server device 1 arranges multiple tabular data sets having a common header in a first direction (vertical direction), which is either vertical or horizontal. Server device 1 also arranges multiple tabular data sets having different headers in a second direction (horizontal direction), which is different from the first direction, either vertical or horizontal. Here, the second direction may involve moving in the first direction while arranging in the second direction. This allows for the creation of a user-friendly and comprehensive integrated table, where the contents of common headers are arranged in one direction for easy comparison, while non-common headers are described as separate information. The integrated table may also be created by transposing rows and columns and extending it in the column direction.

[0132] [3.2. Splitting unit: Sheet] Figure 19 is an explanatory diagram showing an example of a header candidate list and integrated table when the division unit is set to "sheet". In Figure 19, along with the header candidate list display area 812, the integrated table that is displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. As shown in the header candidate list display area 812 of this figure, when the division unit is set to "sheet", the sheet name is not appended to the header name, and headers with the same string in different sheets are treated as common header candidates across sheets.

[0133] The header candidate list display area 812 and preview area 813 in Figure 19 are the same as the header candidate list display area 812 and preview area 813 in Figure 18, except that the sheet name is not displayed and metadata is not included; therefore, redundant explanations are omitted. Also, the explanation regarding the metadata in Figure 19 is the same as the explanation in Figure 10; therefore, redundant explanations are omitted.

[0134] As shown in the header candidate list display area 812 of Figure 19, even when the division unit is set to "sheet," the layout includes one or more of the header parser 92 that defines values ​​and value headings, and the table parser 95 that defines tables. The server device 1 can output either the headings of the header parser 92 or the headers of the table parser 95 as header candidates in the list. This makes it possible to create an integrated table by combining the layout-defined data of the header parser 92 and the layout-defined data of the table parser 95.

[0135] In this way, the server device 1 generates an integrated table by arranging the layout-defined data vertically in the selected division unit. The integrated table may also be one in which the rows and columns have been transposed and extended in the column direction.

[0136] Furthermore, as described above, the server device 1 arranges multiple tabular data sets having a common header in a first direction (vertical direction), which is either vertical or horizontal. The server device 1 also arranges multiple tabular data sets having different headers in a second direction (horizontal direction), which is either vertical or horizontal and different from the first direction. Here, the second direction may involve moving in the first direction while arranging in the second direction. This allows for the creation of an easy-to-read and comprehensive integrated table by arranging the contents of common headers in one direction for easy comparison, and describing non-common headers as separate information.

[0137] [3.3. Division Unit: Table] Figure 20 is an explanatory diagram showing an example of a header candidate list and an integrated table when the division unit is set to "table". In Figure 20, along with the header candidate list display area 812, the integrated table that will be displayed when all header candidates are selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow. As shown in the header candidate list display area 812 of this figure, when the division unit is set to "table", the headers of the header parser 92 are not extracted as header names, and headers with the same string on different sheets are treated as common header candidates among the layout-defined data.

[0138] Of the target tabular files 74-79, the layout-defined data 7611 contained in sheet 761 of tabular file 76, and the layout-defined data 7911 contained in sheet 791 of tabular file 79, are considered as header candidates. Excluding metadata, the header candidate list display area 812 in Figure 20 is the same as the header candidate list display area 812 in Figure 16, and redundant explanations are omitted.

[0139] The explanation of the metadata in Figure 20 is the same as the explanation in Figure 12, so redundant explanations are omitted. As shown in the header candidate list display area 812 of Figure 20, the layout includes a table parser 95 that defines multiple tables, and the server device 1 can output the headers of the multiple table parsers 95 as header candidates in a list. This makes it possible to create an integrated table by combining the layout-defined data of the multiple table parsers 95.

[0140] The preview area 813 in Figure 20 is the same as the preview area 813 in Figure 16, except for the metadata, so redundant explanations are omitted. The metadata differs in that, in the example of preview area 813 in Figure 16, the same sheet name is used in two files, while in the example of preview area 813 in Figure 20, the same sheet name is used in six files.

[0141] In this way, the server device 1 generates an integrated table by arranging the layout-defined data vertically in the selected division unit. The integrated table may also extend in the column direction by transposing the rows and columns.

[0142] As described above, Server Device 1 acquires a tabular file containing tabular data associated with layouts that define the relationships between multiple cells, and extracts layout-defined data that is included in the tabular data and is defined as being subject to a layout. Server Device 1 also outputs a list of header candidates for an integrated table that combines the extracted multiple layout-defined data, and generates the integrated table based on the list of header candidates. This allows users to review the header candidates for the integrated table in a list before creating the integrated table. Therefore, the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data can be further enhanced.

[0143] Furthermore, the system accepts one of the following as a partitioning unit: a tabular file, one or more sheets contained within a tabular file that contain tabular data, or a table that is layout-defined data defined as a table within the tabular data. Server device 1 can extract header candidates for the integrated table from the layout-defined data contained in the accepted partitioning unit and output a list of header candidates. This allows the system to create an integrated table that meets the user's requirements.

[0144] [4. Example of a case where an ordered parser is included] Figure 21 is a diagram showing an example of the structure of a tabular file 61. The tabular file 61 can be a tabular file stored in the tabular linked data 60, which is selected in step S11 of Figure 6. The tabular file 61 has a sheet 611, and the sheet 611 has layout-defined data 6111.

[0145] The predefined layout data 6111 has a sequence parser 93 that sequentially connects six cells whose content is "weighing," "grinding," "stirring," "vacuum sealing," "calcination," and "centrifugation." The first cell of the sequence parser 93, "weighing," is connected to a heading parser 92 whose heading is "experimental procedure."

[0146] Among the cells to which the sequence parser 93 is connected, the header parser 92 with the cell "Weighing" as its header is connected to the table parser 95 with the headers "Ti" and "Mn". The header parser 92 with the cell "Agitation" as its header is connected to the header parser 92 with the cell "Agitation Time" as its header. The header parser 92 with the cell "Baking" as its header is connected to the table parser 95 with the headers "Maximum Temperature" and "Baking Time". The header parser 92 with the cell "Centrifugal Separation" as its header is connected to the header parser 92 with the cell "Weight" as its header.

[0147] [4.1. Splitting unit: Sheet] Figure 22 is an explanatory diagram showing an example of a header candidate list and integrated table when the division unit is set to "sheet". In Figure 22, along with the header candidate list display area 812, the integrated table that will be displayed when a header candidate excluding metadata is selected in the header candidate list display area 812 and the preview button 815 is operated is shown in the preview area 813 below the arrow.

[0148] As shown in the header candidate list display area 812 of Figure 22, the server device 1 displays header candidates with the type "Procedure" and the header name "Experimental Procedure" based on the sequence parser 93 that connects the six cells in Figure 21. The server device 1 can use the heading "Experimental Procedure" of the first cell "Weighing" in the sequence parser 93 as the heading for the sequence parser 93.

[0149] Server device 1 displays the cells "Weighing," "Grinding," "Agitation," "Vacuum Sealing," "Castration," and "Centrifugal Separation," to which the sequence parser 93 is connected, as header candidates for the integrated table, with each cell having a header name. Server device 1 displays the header candidates with "Weighing," "Grinding," "Agitation," "Vacuum Sealing," "Castration," and "Centrifugal Separation" as lower-level header candidates indented from the header name "Experimental Procedure."

[0150] If a header parser 92, which has a cell to which a sequence parser 93 is connected, is connected to a table parser 95, the server device 1 displays the table headers related to the table parser 95 (for example, "Ti" and "Mn") with further indentation as candidates for the header of the integrated table.

[0151] Server device 1 extracts each of the contents of the cells to which the sequence parser 93 is connected as a header candidate. In this case, server device 1 can also display as a header candidate cells that are not headers of the header parser among the cells to which the sequence parser 93 is connected (for example, "crushing" or "vacuum sealing"). If none of the cells in the series to which the sequence parser 93 is connected are headers of the header parser, they do not need to be extracted as header candidates.

[0152] If a header parser 92 is connected to a cell to which a sequence parser 93 is connected, the server device 1 displays the cell to which the sequence parser 93 is connected (e.g., "Agitation") and the cell to which the header parser 92 is connected (e.g., "Agitation Time") connected via a "." (period). Here, the server device 1 may also display it as an indented lower header candidate instead of displaying it via a "." (period).

[0153] As shown in the preview area 813 of Figure 22, the server device 1 reflects the contents of the header candidate list display area 812 in the integrated table and outputs them to the preview area 813 based on the instructions given by the operation of the preview button 815. The server device 1 displays the "Experimental Procedure" header, which is the heading of a series of sequence parsers 93, as the header of the integrated table, as a higher-level header encompassing the header candidates of the cells connected by the sequence parser 93, and displays the cells "Weighing," "Grinding," "Agitation," "Vacuum Sealing," "Castration," and "Centrifugation," to which the sequence parser 93 is connected, as lower-level headers encompassed by the "Experimental Procedure" header.

[0154] Server device 1 displays the headers (e.g., "Ti", "Mn") or cells (e.g., "Agitation Time") of tables to which the sequential parser 93 is connected as headers, as lower-level headers. Server device 1 displays the contents of cells to which the sequential parser 93 is connected but to which no header parser 92 is connected (e.g., "Grinding", "Vacuum Sealing") as blank cells or cells with no content.

[0155] As described above, the layout includes a sequence parser 93 that defines the order, and when a header parser 92 uses cells related to the sequence parser 93 as headers, the server device 1 can also use other cells related to the sequence parser 93 to which the header parser is not applied (for example, "crushing" or "vacuum sealing") as header candidates. In this case, in the integrated table, the content of cells to which the header parser is not applied as headers can be blank cells or other cells with no content.

[0156] Furthermore, in the header candidate list display area 812, the server device 1 can identify the heading for the sequence parser 93 from which the header candidates were extracted as the header type "procedure" of the sequence parser 93, and display the header type together with the header candidates in association with them.

[0157] As described above, server device 1 can acquire a tabular file containing tabular data associated with layouts that define the relationships between multiple cells, extract layout-defined data that is included in the tabular data and is defined as being subject to a layout, and combine the extracted layout-defined data to generate an integrated table. This allows multiple different tabular data associated with layouts to be viewed together as an integrated table. Therefore, the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data can be further enhanced.

[0158] Furthermore, the server device 1 accepts one of the following as a partitioning unit: a tabular file, one or more sheets contained within a tabular file that contain tabular data, or a table which is layout-defined data defined as a table within the tabular data. By arranging the layout-defined data vertically or horizontally within the selected partitioning unit, it generates an integrated table. This makes it possible to create an integrated table that meets the user's requirements.

[0159] In the above configuration, program 1P and tabular linked data 60 are stored in the storage unit 14 of server device 1, and the control unit 11 of server device 1 executes the processing of program 1P. However, for example, program 1P and tabular linked data 60 may be stored in the storage unit 24 of terminal device 2, and the control unit 21 of terminal device 2 may execute the processing of program 1P in a standalone manner without using the network 3. Alternatively, part of program 1P may be executed in terminal device 2, and the other part of program 1P may be executed in server device 1, so that terminal device 2 and server device 1 work together.

[0160] According to the program 1P, the information processing method related to program 1P, and the information processing device (server device) 1 in the form of this disclosure, the convenience of processing that uses tabular data and a layout that defines the relationships between each cell of that tabular data can be further enhanced.

[0161] Furthermore, the program of Program 1P may be referred to as a program product, software, or software product, which may be provided on a recording medium or provided in a form distributed via a communication network.

[0162] The forms of this disclosure are illustrative in all respects and not restrictive. The scope of the invention is not limited to those shown in the above disclosure but is shown by the claims, and all modifications within the meaning and scope equivalent to the claims are intended.

[0163] Furthermore, the sequences shown in each embodiment described above are not limited, and within a reasonable scope, the order of each processing step may be changed, and multiple processes may be executed in parallel. The processing entity for each process is not limited, and within a reasonable scope, the processing of each device may be executed by other devices.

[0164] The matters described in each embodiment can be combined with each other. Furthermore, the independent claims and dependent claims described in the claims can be combined with each other in any combination, regardless of the form of reference. In addition, although the claims do not use the form of a multi-claim that further references a multi-claim (multi-multi-claim), it may be a combination that uses the form of a multi-multi-claim that references all higher-level claims. [Explanation of symbols]

[0165] 1. Information processing device (server device) 11 Control Unit 12 Communications Department 13 Reading Unit 14 Storage section 15 Portable storage media 19 bus 1P Program (Program Product) 2. Information processing terminal (terminal device) 21 Control Unit 22 Communications Department 23 Reading section 24 Memory section 25 Portable storage media 26 Display section 27 Input section 29 bus 3 Network 60 Tabular Linked Data 61 Management files 62 Tabular File Storage Section 63 Layout file storage section 81 screens 811 Data Partition Unit Selection Area 812 Header candidate list display area 8121 Header Name Field 8122 Count column 8123 Type field 8124 Edit Link 813 Preview Area 814 Save button 92 Headline Parser 93. Sequential Parser 95 Table Parlor 951 Entire Table 952 Table Data Section

Claims

1. Retrieve a tabular file containing tabular data associated with a layout that defines the relationships between multiple cells, Extract the layout-defined data that is included in the tabular data and is defined as being subject to the layout, Output a list of header candidates for the integrated table, which combines the extracted multiple layout-defined data. The integrated table is generated based on the list of header candidates. A program that instructs a computer to perform a process.

2. The system accepts, as a splitting unit, one or more of the aforementioned tabular file, sheets included in the aforementioned tabular file and containing the aforementioned tabular data, and tables which are layout-defined data defined as tables within the aforementioned tabular data. From the layout-defined data included in the division unit, a candidate header for the integrated table is extracted. Output a list of the aforementioned header candidates. The program according to claim 1.

3. When the tabular file is used as the division unit, the header name of the candidate header should include the sheet name of the sheet. The program according to claim 2.

4. The metadata is output as one of the header candidates mentioned above. The header candidates included in the metadata are: the folder path of the folder where the tabular file is saved, the file name of the tabular file, the sheet name of the sheet, and a table path which is a combination of the file name, the sheet name, and the table headers, or a combination of any or more of them. The program according to claim 2.

5. If the sheet is used as the division unit, the sheet name is added to the metadata; if the table is used as the division unit, the sheet name and the table path are added to the metadata. The program according to claim 4.

6. The layout includes one or more of the following: a header parser that defines values ​​and headers for those values, and a table parser that defines tables. Either the header of the header parser or the header of the table parser is output as a header candidate in the list. The program according to claim 1.

7. The header candidates, the header of the header parser and the table parser, are identified as different header types. The header type is associated with the header candidate and displayed together with the header candidate. The program according to claim 6.

8. The aforementioned layout includes an order parser that defines the order, If the header of the header parser, which uses the cell related to the sequence parser as the header, is to be used as the header candidate, then the other cells related to the sequence parser to which the header parser is not applied will be used as the header candidate. The program according to claim 6.

9. The headers extracted from the sequence parser are identified as the header types of the sequence parser. The header type is associated with the header candidate and displayed together with the header candidate. The program according to claim 8.

10. The number of times the header candidate appears as a heading or header in multiple predefined layout data is displayed along with the header candidate. The program according to claim 1.

11. Retrieve a tabular file containing tabular data associated with a layout that defines the relationships between multiple cells, Extract the layout-defined data that is included in the tabular data and is defined as being subject to the layout, Output a list of header candidates for the integrated table, which combines the extracted multiple layout-defined data. The integrated table is generated based on the list of header candidates. Information processing methods.

12. It includes a control unit, and the control unit is Retrieve a tabular file containing tabular data associated with a layout that defines the relationships between multiple cells, Extract the layout-defined data that is included in the tabular data and is defined as being subject to the layout, Output a list of header candidates for the integrated table, which combines the extracted multiple layout-defined data. The integrated table is generated based on the list of header candidates. Information processing device.

Images