Program, information processing method, and information processing apparatus

Abstract

This provides programs and other tools that enhance the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data. [Solution] The program outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. The program accepts the selection of a header for the integrated table from the list of header candidates and causes the computer to execute a process to output a preview of the integrated table based on the selected header.

Description

Technical Field

[0004] ,

[0006] , , , , , ,

[0005] , , ,

[0003] , , , , ,

[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, etc., 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 outputs a list of header candidates for an integrated table formed by combining multiple layout-defined data, which are tabular data to which a layout defining the relationships between multiple cells is applied; accepts the selection of a header for the integrated table from the list of header candidates; and causes the computer to execute a process that outputs a preview of the integrated table based on the selected header. In one aspect of this disclosure, the use of tabular data and a layout defining the relationships between each cell of that tabular data can be made more convenient.

[0007] The program in the second perspective accepts an operation to move one candidate from the list of header candidates to a higher or lower position than other candidates, and in the preview of the integrated table, the one candidate is displayed in a column to the left or right of the other candidates, respectively, as described in the first perspective.

[0008] The program in the third aspect is the program described in the first or second aspect which accepts the selection of the header in the list of header candidates or the display of the preview, and performs cell completion processing which inputs the same values ​​of the layout-defined data into multiple blank cells in the row or column identified by the selected header.

[0009] The program of the fourth aspect is the program of the first or second aspect that performs the cell completion process on all or more of the headers.

[0010] The program of the fifth perspective is a program according to any of the first to fourth perspectives, which, when integrating the layout-defined data, which is a table having both column headers and index headers, into the integrated table, accepts a selection of one of the following: displaying the integrated table with one column of the layout-defined data as one row of the integrated table; displaying one row of the layout-defined data as one row of the integrated table; or arranging the values ​​in the layout-defined data one-dimensionally and displaying each of the layout-defined data as one row; and based on the accepted selection, displays the preview of the integrated table and a list of header candidates.

[0011] The program of the sixth perspective is a program described in any of the first to fifth perspectives, which accepts one of the following as a splitting unit: a sheet containing the tabular data, a tabular file containing one or more of the sheets, and a table which is the layout-defined data defined as a table within the tabular data, and when the tabular file is used as the splitting unit, outputs the preview of the integrated table in which the sheet name of the sheet is set as a higher-level header that includes the header candidates contained in the sheet.

[0012] The program of the seventh perspective is the program of the sixth perspective which outputs metadata as one of the headers of the preview, and outputs 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, as subheaders included in the header of the metadata.

[0013] The program according to the eighth perspective is the program according to the seventh perspective, wherein when the sheet is used as the division unit, the sheet is added to the metadata, and when the table is used as the division unit, the sheet and the table path are added to the metadata.

[0014] The program of the ninth aspect is a program described in any of the first to eighth aspects, wherein the layout includes a table parser that defines a table, a sequence parser that defines a sequence, and a header parser that defines the headers of the cells, the table parser, and the sequence parser, and outputs a preview of the integrated table with the header of the table parser or the header of the sequence parser as a higher-level header that encompasses the header candidates within the table parser or the sequence parser, respectively.

[0015] The tenth aspect of information processing is an information processing method that outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data, which are tabular data to which a layout defining the relationships between multiple cells is applied; accepts the selection of a header for the integrated table from the list of header candidates; and outputs a preview of the integrated table based on the selected header.

[0016] The information processing device in the eleventh aspect comprises a control unit, which outputs a list of header candidates for an integrated table formed by combining multiple layout-defined data, which are tabular data to which a layout defining the relationships between multiple cells is applied, accepts the selection of a header for the integrated table from the list of header candidates, and outputs a preview of the integrated table based on the selected header. [Brief explanation of the drawing]

[0017] [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]It is a flowchart showing an example of the processing of a server device. [Figure 7] It is a diagram showing an example of the configuration of a tabular file. [Figure 8] It is a diagram showing an example of a screen including a list of header candidates. [Figure 9] It is a diagram showing an example of an integrated table displayed in a preview area. [Figure 10] It is a diagram showing an example of changing the order of header candidates. [Figure 11] It is a diagram for explaining an example when there is a heading in a table parser. [Figure 12] It is an explanatory diagram showing an example of a list of header candidates and an integrated table when the division unit is "sheet". [Figure 13] It is a diagram showing another example of an integrated table displayed when the division unit is "sheet". [Figure 14] It is an explanatory diagram showing an example of a list of header candidates and an integrated table when the division unit is "table". [Figure 15] It is a diagram showing an example of the configuration of a tabular file. [Figure 16] It is an explanatory diagram showing an example of a list of header candidates and an integrated table when the division unit is "file". [Figure 17] It is a diagram for explaining a cell completion function. [Figure 18] It is a diagram for explaining a cell completion function. [Figure 19] It is an explanatory diagram showing an example of a list of header candidates and an integrated table when the division unit is "sheet". [Figure 20] It is an explanatory diagram showing an example of a list of header candidates and an integrated table when the division unit is "table". [Figure 21] It is a diagram showing an example of the configuration of a tabular file. [Figure 22] It is an explanatory diagram showing an example of a list of header candidates and an integrated table when the division unit is "file". [Figure 23] This is an explanatory diagram showing a list of header candidates and an example of an integrated table when the division unit is set to "sheet". [Figure 24] This is an explanatory diagram showing a list of header candidates and an example of an integrated table when the partitioning unit is set to "table". [Figure 25] This is an explanatory diagram illustrating an example of converting a table with index headers and column headers into a unified table. [Figure 26] This is an explanatory diagram illustrating an example of converting a table into a two-dimensional table with column names followed by values. [Figure 27] This is an explanatory diagram illustrating an example of converting a table into a two-dimensional table with row names followed by values. [Figure 28] This is an explanatory diagram illustrating an example of converting a table into a one-dimensional table with column names, row names, and values ​​in that order. [Figure 29] This is an explanatory diagram illustrating an example of converting a table into a one-dimensional table with row names, column names, and values ​​in that order. [Modes for carrying out the invention]

[0018] 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.

[0019] 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.

[0020] 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.

[0021] 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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".

[0041] 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.

[0042] 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 transformation to create semi-structured data, it becomes possible to search for and easily extract necessary information from tabular data with different layouts.

[0043] 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, but can be defined as appropriate, and rules for converting each parsing object into semi-structured data can be appropriately defined.

[0044] 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 as appropriate, or to convert to tabular data and layouts based on semi-structured data. Thus, the layout may include a table parser 95 that defines the table, a sequence parser 93 that defines the sequence, and a header parser 92 that defines the headers of the cells, table parser 95, and sequence parser 93.

[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 headers.

[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] 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.

[0056] 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)").

[0057] 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.

[0058] The Count column 8122 displays the number of times the header name of the header candidate appears in the layout-defined data extracted from the selected tabular file. The Type column 8123 primarily displays the type of layout from which the header candidate of the layout-defined data was 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. The strings "Value" and "Table" are not limited to these, and any string can be defined.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] In Figure 8, server device 1 accepts a 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 header of the table parser 95 ("(blank)" in Figure 16) via a "." (period).

[0064] 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.

[0065] 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.

[0066] 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.

[0067] The headers in the lower rows will be headers where the Type field 8123 is set to "Value" or "Table". Server device 1 will also adopt the header candidate (table header) displayed with an indent 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 for the integrated 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 table with the header on the left.

[0068] 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.

[0069] Furthermore, as shown in the integrated table in Figure 9, the server device 1 can output metadata as one of the preview headers, and output the folder path of the folder where the tabular file is saved and the file name of the tabular file ("Book") as subheaders included in the metadata header. Here, the server device 1 may also output the folder path of the folder, the file name of the tabular file, the sheet name of the sheet, and a table path that is a combination of the file name, sheet name, and table header, or a combination of these, as subheaders included in the metadata header.

[0070] Figure 10 shows an example of changing the order of header candidates. Users of terminal device 2 can change the position of each header candidate displayed in the header candidate list display area 812 by, for example, dragging and dropping using the input unit 27 such as a mouse of terminal device 2. As shown in this figure, when server device 1 receives an operation 51 to move the header candidate for the table header name "Electrical Resistivity (300K)" of the sheet name "Experimental Results 1" to a lower position below the header "Transition Point" of the same table, using the mouse or the like, server device 1 can display the header candidate for "Electrical Resistivity (300K)" below the header candidate for the header name "Transition Point".

[0071] Furthermore, when server device 1 receives an operation 52, such as using a mouse, to move the header candidate for the table with the header name "Transition Point" in the sheet name "Experimental Results 2" above the header candidate for the same table with the header name "Electrical Resistivity (300K)", it can display the header candidate for "Transition Point" above the header candidate for "Electrical Resistivity (300K)".

[0072] Furthermore, when server device 1 receives an operation 53, such as a mouse operation, to deselect the checkbox for the header name "Metadata", it deselects and displays the header candidate for the header name "Metadata" and all header candidates included in that header candidate (header names "Book" and "Folder Path").

[0073] After operations 51-53, the integrated table in the preview area 813, which is displayed by operating the preview button 815, is shown below the arrow in Figure 10. As shown in the integrated table in the preview area 813, the server device 1 displays the integrated table without including the deselected header name "metadata". The server device 1 also displays the headers included in "Experimental Result 1" and "Experimental Result 2" in the order of "Sample ID", "Transition Point", and "Electrical Resistivity (300K)", respectively, so as to match the order of the header candidates that were moved in the header candidate list display area 812.

[0074] In this way, server device 1 accepts an operation to move one header candidate from the list of candidates to a higher or lower position than other candidates, and in the preview of the integrated table, that candidate can be displayed in a column to the left or right of the other candidates, respectively. This makes it possible to create an integrated table that meets the user's requirements.

[0075] In this way, the server device 1 accepts one of the following as a partitioning unit: a sheet containing tabular data, a tabular file containing one or more sheets, or a table which is layout-defined data defined as a table within the tabular data. When a tabular file is used as the partitioning unit, it can output a preview of an integrated table in which the sheet name of the sheet is used as a header that encompasses the header candidates contained in the sheet.

[0076] Figure 11 is a diagram illustrating an example where the table parser 95 has a header. The tabular file 220 in Figure 11 has sheets 711, 222, and 223. Sheet 711 is the same as sheet 711 in Figure 7, so its explanation is omitted. Sheet 222 has a table on which the table parser 95 is placed, and the header parser 92 defines the table header "Data," thereby defining the layout-defined data 2221. Here, the contents of the table are the same as the layout-defined data 7121 in Figure 7, so its explanation is omitted.

[0077] Sheet 223 defines the layout-defined data 2231 using a table parser 95 and a header parser 92 that defines the table header "Data". Here, the contents of the table are the same as the layout-defined data 7131 in Figure 7, so the explanation is omitted. As mentioned above, the configuration is the same as the tabular file in Figure 7, except that the header parser 92, which sets the header to "Data", is connected to the table parser 95 of the tabular file 71 in Figure 7.

[0078] Below the arrow in Figure 11, the integrated table displayed in the preview area 813 is shown under the same conditions as in Figure 8, namely, when the data partitioning unit is set to "file" and all header candidate checkboxes are selected. As shown in the integrated table in Figure 11, the server device 1 displays the header name "Data," which is the higher-level header encompassing all headers in each table of sheets 222 and 223 defined by the table parser 95. Here, the server device 1 displays the two header names "Data" as lower-level headers for the respective sheet names "Experimental Results 1" and "Experimental Results 2."

[0079] As described above, server device 1 can output a preview of the integrated table with the headers of table parser 95 as higher-level headers that encompass the header candidates within table parser 95. Here, even when sequence parser 93 outputs an integrated table with each connected cell as a header, server device 1 can output a preview of the integrated table with the headers of sequence parser 93 as higher-level headers that encompass the headers within sequence parser, similar to table parser 95.

[0080] [1.2. Splitting unit: Sheet] Figure 12 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 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 "sheet", the sheet name is not appended to the header name, and header names with the same string in different sheets are treated as common header candidates across sheets.

[0081] 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 12, 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.

[0082] Furthermore, regarding the 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 sheets are used as the splitting unit, Server Device 1 can add sheets to the metadata.

[0083] Here, the target tabular file 71 has layout-defined data 7111, 7121, and 7131 in three sheets, respectively (Figure 7). As shown in the integrated table in the preview area 813 of Figure 12, since the division unit is "sheet," the server device 1 arranges the layout-defined data 7111, 7121, and 7131 placed on each sheet in order vertically. As a result, the integrated table becomes a 3-row integrated table. Note that the integrated table may also extend in the column direction by transposing the rows and columns.

[0084] 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 for each row. This indicates that the contents of the cells in each row are data extracted from different sheets in the same file.

[0085] In this way, server device 1 can output metadata as one of the preview headers, and output the folder path of the folder where the tabular file is saved, the file name of the tabular file ("Book"), and the sheet name ("Sheet") as subheaders included in the metadata header. Here, server device 1 may also output the folder path of the folder, the file name of the tabular file, the sheet name, and a table path which is a combination of the file name, sheet name, and table header or a combination thereof as subheaders included in the metadata header.

[0086] Furthermore, as described above, server device 1 arranges multiple tabular data sets having common headers ("Sample ID", "Electrical Resistivity (300K)", and "Transition Point") in a first direction (vertical in this embodiment), which is either vertical or horizontal. Server device 1 also arranges multiple tabular data sets having different headers ("Person in Charge" and "Sample Name") in a second direction (horizontal in this embodiment), which is either vertical or horizontal and different from the first direction. In the example in Figure 12, tabular data sets having different headers in each division are arranged horizontally while also moving vertically. 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.

[0087] Figure 13 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 have the same attributes based on the fact that 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, it may determine that sheet 711, "Experimental Information," has different attributes from sheets 712 and 713.

[0088] In this case, as shown in the integrated table in Figure 13, 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.

[0089] 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 13, metadata is not selected in the header candidate list display area 812, and therefore metadata is not displayed in the integrated table.

[0090] Furthermore, even when multiple tabular data sets with a common header are arranged sequentially in a first direction, either vertically or horizontally, and tabular data sets with 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 13. For example, if metadata is not selected in the header candidate list display area 812, and the option to not display metadata in the integrated table is selected, the server device 1 can output an integrated table like the one shown in Figure 13 by arranging tabular data sets with 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").

[0091] [1.3. Unit of division: Table] Figure 14 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 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. 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, and header names with the same string in different "tables" are treated as common header candidates among the layout-defined data.

[0092] 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.

[0093] In the example of the header candidate list display area 812 in Figure 14, 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.

[0094] 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.

[0095] As described above, the integrated table created by server device 1 targets the layout-defined data 7121 and 7131, which have a table parser 95. As shown in the integrated table in preview area 813 of Figure 14, the division unit is a "table," so server device 1 arranges the layout-defined data 7121 and 7131 based on this table parser 95 vertically in order 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.

[0096] 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.

[0097] The "Key" column may display the table header after the sheet name, separated by a period ("."), if the extracted table parser 95 is further connected to a header parser 92. This allows the "Key" column to be displayed as a string that identifies the table (table path). Alternatively, the "Key" column may display only the table header, without displaying the file name or sheet name. Furthermore, if the table parser 95 is connected to a header parser 92, and one or more other header parsers 92 are hierarchically connected to it, the "Key" column may display the headers of each header parser 92 in hierarchical order, separated by periods ("."), including the string itself.

[0098] In this way, server device 1 can output metadata as one of the preview headers, and output the folder path of the folder where the tabular file is saved, the file name of the tabular file ("Book"), the sheet name ("Sheet"), and the table path ("Key") which is a combination of the file name, sheet name, and table header or a combination thereof, as subheaders included in the metadata header.

[0099] Here, the server device 1 may output the folder path of a folder, the file name of a tabular file, the sheet name of a sheet, and a table path that is a combination of the file name, sheet name, and table header, or a combination of these, as subheaders included in the metadata header. In addition, if the table is used as the partitioning unit, the server device 1 may add the sheet and table path to the metadata.

[0100] As described above, server device 1 outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. From the list of header candidates, it accepts the selection of an integrated table header and outputs a preview of the integrated table based on the selected header. This allows multiple different tabular data sets associated with layouts to be viewed as an integrated table, with only the selected header being considered. Therefore, it is possible to create an integrated table that meets the user's requirements, further enhancing the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data.

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

[0102] [2. Example when there are 2 tabular files] Figure 15 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] [2.1. Splitting unit: File] Figure 16 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 16, 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 15 are selected and the division unit is set to "file". As shown in the header candidate list display area 812 of Figure 16, 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.

[0107] 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 16) 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.

[0108] 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.

[0109] As shown in the integrated table in preview area 813 of Figure 16, 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 encompassing the header candidates within the sheet, among the multi-level headers in the integrated table. Furthermore, the server device 1 adopts the string displayed after the "." (period) in the header candidate list display area 812 as a lower-level header of the said sheet name header.

[0110] 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 16 as the header of the integrated table, as a header below the header where the Type field 8123 is set to "Table". In Figure 16, 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.

[0111] As shown in the integrated table in preview area 813 of Figure 16, 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 16, 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.

[0112] Here, the layout-defined data 7232 and 7332 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.

[0113] As described above, server device 1 outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. From the list of header candidates, it accepts the selection of an integrated table header and outputs a preview of the integrated table based on the selected header. This allows multiple different tabular data sets associated with layouts to be viewed as an integrated table, with only the selected header being considered. Therefore, it is possible to create an integrated table that meets the user's requirements, further enhancing the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data.

[0114] Furthermore, the server device 1 accepts one of the following as a splitting unit: a sheet containing tabular data, a tabular file containing one or more sheets, or a table which is layout-defined data defined as a table within the tabular data. When a tabular file is used as the splitting unit, it can output a preview of an integrated table in which the sheet names of the sheets are used as headers that encompass the header candidates contained in the sheets. The integrated table may also be one in which the rows and columns are transposed and extended in the column direction.

[0115] In the metadata, Server Device 1 displays the file name in the "Book" column and the folder path where the tabular file is stored in the "Folder Path" column. In this way, Server Device 1 can output either the folder path of a folder, the file name of the tabular file, the sheet name of a sheet, or a table path that combines the file name, sheet name, and table headers, or a combination of these, as subheaders included in the metadata header.

[0116] Figures 17 and 18 are diagrams illustrating the cell completion function. Figures 17 and 18 illustrate the cell completion function based on the integrated table displayed in the preview area 813 of Figure 16. As shown in Figure 17, when the server device 1 or terminal device 2 accepts an operation such as a right-click by a user of terminal device 2 who selects one of the headers of the integrated table in the preview area 813 (for example, "contact drying time") (S21), it displays a screen 816 that provides the cell completion function (S22).

[0117] Screen 816, which provides the cell completion function, has a checkbox for "Copy value and adjust row number" which completes blank cells in the column selected by selecting a header with the value of the nearest non-blank cell above it, and a checkbox for "Perform the same operation on all Value headers" which can be selected when the above checkbox is selected. The function of "Perform the same operation on all Value headers" will be described later.

[0118] For example, server device 1 or terminal device 2 receives an instruction to start cell interpolation processing when a user of terminal device 2 selects "Copy values ​​and match row numbers" and clicks the OK button or performs other actions to initiate processing.

[0119] Upon receiving the instruction to start processing, server device 1 or terminal device 2 inputs the value of the nearest higher non-blank cell into the blank cells of the column selected by the header selection and outputs it (S23). Specifically, the value of the nearest higher non-blank cell (cell F7, "10 minutes") is input into the blank cells of the column indicated by the selected header (e.g., "contact drying time") (e.g., blank cells F8 and F9 in step S21) (cells F8 and F9, "10 minutes" in S23). Here, "higher side" means the side closer to the header of the column (or row) indicated by the selected header.

[0120] Here, a blank cell means a cell that does not contain a value, and may be defined by a tabular file, or it may be a string of length 0, etc.

[0121] In the example in Figure 17, the header indicates a column, so we chose to fill in blank cells in the column. However, this can also be applied to headers that indicate rows, in which case the blank cells in the row would be filled in. Furthermore, in the explanation of Figure 17, the server device 1 or terminal device 2 outputs screen 816, which provides the cell completion function, by performing a display operation on the integrated table in the preview area 813. However, the server device 1 or terminal device 2 may also output screen 816, which provides the cell completion function, by operating the edit link 8124 in the header candidate list display area 812. This allows the setting to fill in blank cell values ​​before checking the preview.

[0122] In this way, server device 1 or terminal device 2 can accept a header selection by displaying a list of header candidates or a preview, and perform cell completion processing by inputting the value of the next non-empty cell closest to the blank cell in the row or column specified by the selected header. Alternatively, the cell completion processing may input the value of the next non-empty cell closest to the blank cell. Alternatively, blank cells belonging to a certain data division unit may be input with another non-empty value belonging to that data division unit. Furthermore, although the cell completion processing is initiated by user operation in the above example, it may also be performed as an initial setting without waiting for user operation. Furthermore, although the cell completion processing is performed on blank cells after creating the integrated table in the above example, it may also be performed in an order in which the parts of the layout-defined data corresponding to each parser are converted into separate intermediate tables, an operation equivalent to cell completion processing is performed on each intermediate table, and then the number of rows or columns of each table is made consistent before arranging them vertically and horizontally to eliminate blank cells.

[0123] Furthermore, the server device 1 or terminal device 2 may provide a screen 816 that provides the cell completion function, which can perform value completion on cells not only for the selected header column (or row) but also for all headers (headers where the type field 8123 is "Value") based on the integrated table header parser 92. In this case, the server device 1 or terminal device 2 can receive instructions to start the cell completion process for all headers based on the integrated table header parser 92, for example, on the screen 816 in Figure 17, by the user selecting both "Copy values ​​and match the number of rows" and "Perform the same operation on all Value headers," and by clicking the OK button or other operation to start the process.

[0124] Upon receiving the instruction to start processing, server device 1 or terminal device 2 outputs an integrated table to the preview area 813, with all header columns (or rows) whose type field 8123 is "Value" filled with blank cells (Figure 18). In the integrated table in step S21 of Figure 17, columns A to H are all header columns based on the header parser 92, and each has blank cells in rows 5-6 and 8-9, respectively. Through cell completion processing for all headers based on the header parser 92, the values ​​of the nearest higher non-blank cells are entered and filled, as shown in Figure 18.

[0125] The cell completion process for all headers based on the header parser 92 can also be applied to headers that indicate rows, and this process can be started by manipulating the edit link 8124 in the header candidate list display area 812. In this way, the server device 1 can perform cell completion processing for all headers in the layout based on the header parser 92 that defines values ​​and headers for those values. This makes the values ​​within cells clearer and results in a more user-friendly integrated table.

[0126] [2.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.

[0127] Aside from the absence of sheet names and metadata, the only difference between the header candidate list display area 812 in Figure 19 and the header candidate list display area 812 in Figure 16 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 16, the sheet name was included in 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 19, 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.

[0128] The explanation of the metadata in Figure 19 is the same as that for Figure 12, so redundant explanations will be omitted.

[0129] Here, the tabular file 72 in question has layout-defined data 7211, 7221, and 7231 in three sheets, respectively (Figure 7). Similarly, the tabular file 73 has layout-defined data 7311, 7321, and 7331 in three sheets, respectively. Because the unit of division is "sheet," as shown in the integrated table in the preview area 813 of Figure 19, 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.

[0130] 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 16. 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.

[0131] As described above, server device 1 outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. From the list of header candidates, it accepts the selection of an integrated table header and outputs a preview of the integrated table based on the selected header. This allows multiple different tabular data sets associated with layouts to be viewed as an integrated table, with only the selected header being considered. Therefore, it is possible to create an integrated table that meets the user's requirements, further enhancing the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data.

[0132] [2.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.

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

[0134] The explanation of the metadata in Figure 20 is the same as the explanation in Figure 14, so redundant explanations will be omitted.

[0135] Since the division unit is "table" and the target tables are the layout-defined data 7231B and 7331B in Figure 15, 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 20. 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.

[0136] As described above, server device 1 outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. From the list of header candidates, it accepts the selection of an integrated table header and outputs a preview of the integrated table based on the selected header. This makes it possible to view multiple different tabular data sets associated with layouts as an integrated table, using only the selected header. 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.

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

[0138] [3. Example when there are 6 tabular files] Figure 21 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".

[0139] 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.

[0140] 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".

[0141] 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.

[0142] [3.1. Splitting unit: File] Figure 22 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 22, 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 22, 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.

[0143] 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 22) 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.

[0144] 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.

[0145] The explanation of the metadata in Figure 22 is the same as that for Figures 8 and 9, so redundant explanations are omitted.

[0146] As shown in the integrated table in preview area 813 of Figure 22, 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 22, since all sheet names are the same "Sheet1", the header for Sheet1 is used across all headers except metadata.

[0147] Furthermore, Server Device 1 adopts the string displayed after the "." (period) in the header candidate list display area 812 as the header for the lower row below the sheet name header. The lower row header will be a header with the type field 8123 set to "Value" or "Table". Also, 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 8 as the header for the integrated table, as a further lower row header for the header with the type field 8123 set to "Table". In Figure 9, a horizontal integrated table with the header at the top is shown, but a vertical integrated table with the header on the left side may also be used.

[0148] As shown in the integrated table in preview area 813 of Figure 22, 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 that is displayed on one row, resulting in an integrated table of 10 rows in total.

[0149] As described above, server device 1 outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. From the list of header candidates, it accepts the selection of an integrated table header and outputs a preview of the integrated table based on the selected header. This allows multiple different tabular data sets associated with layouts to be viewed as an integrated table, with only the selected header being considered. Therefore, it is possible to create an integrated table that meets the user's requirements, further enhancing the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data.

[0150] In this way, the server device 1 accepts one of the following as a partitioning unit: a sheet containing tabular data, a tabular file containing one or more sheets, or a table which is layout-defined data defined as a table within the tabular data. When a tabular file is used as the partitioning unit, it can output a preview of an integrated table in which the sheet name of the sheet is used as a header that encompasses the header candidates contained in the sheet. The integrated table may also be one in which the rows and columns have been transposed and extended in the column direction.

[0151] [3.2. Splitting unit: Sheet] Figure 23 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 23, 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.

[0152] The header candidate list display area 812 and preview area 813 in Figure 23 are the same as the header candidate list display area 812 and preview area 813 in Figure 22, 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 23 is the same as the explanation in Figure 12; therefore, redundant explanations are omitted.

[0153] 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.

[0154] As described above, server device 1 outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. From the list of header candidates, it accepts the selection of an integrated table header and outputs a preview of the integrated table based on the selected header. This allows multiple different tabular data sets associated with layouts to be viewed as an integrated table, with only the selected header being considered. Therefore, it is possible to create an integrated table that meets the user's requirements, further enhancing the convenience of processing using tabular data and layouts that define the relationships between each cell in that tabular data.

[0155] [3.3. Unit of division: Table] Figure 24 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 24, 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.

[0156] 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 24 is the same as the header candidate list display area 812 in Figure 20, and redundant explanations are omitted.

[0157] The explanation of the metadata in Figure 24 is the same as the explanation in Figure 14, so redundant explanations will be omitted.

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

[0159] 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.

[0160] Figure 25 is an explanatory diagram illustrating an example of converting a table with index headers and column headers to an integrated table. The tabular file 201 has a sheet 202 containing tabular data (top of Figure 25). The tabular file 201 can be the tabular file stored in the tabular linked data 60, which is selected in step S11 of Figure 6.

[0161] Sheet 202 of the tabular file 201 contains layout-defined data 203, 204, and 205 defined by table parser 95, with "Unopened Bottle" and "Opened Bottle" as index headers and "Be," "As," and "P" as column headers, respectively. The strings "2020," "2021," and "2022" displayed in the upper left corner cell where the index header and column header areas overlap are processed in the header candidate list display area 812 in the same way as headings for table parser 95.

[0162] When server device 1 or terminal device 2 receives a selection of a tabular file, including tabular file 201, in step S11 of Figure 6, for example, it displays a screen 210 for selecting how to convert the table (Figure 25 bottom). Screen 210 is a setting for when both column headers and index headers exist, and allows the user to select one of the following options: "Convert to a 2D table with column names followed by values", "Convert to a 2D table with row names followed by values", "Convert to a 1D table with column names, row names followed by values", and "Convert to a 1D table with row names, column names followed by values".

[0163] "Convert to a 2D table with column names followed by values" means, for example, that the column names "Be," "As," and "P" from tables 203, 204, and 205, which have predefined layouts, will be used as header candidates. "Convert to a 2D table with row names followed by values" means, for example, that the row names "Unopened Bottle" and "Opened Bottle" from tables 203, 204, and 205, which have predefined layouts, will be used as header candidates.

[0164] "Converting to a one-dimensional table in the order of column names, row names, and then values" means, for example, that the column names of each table in the layout-defined data 203, 204, and 205 are used as header candidates for the higher-level header that includes the row name headers in a multi-level header, and the row names are used as header candidates for the lower-level headers of the column name headers. "Converting to a one-dimensional table in the order of row names, column names, and then values" means, for example, that the row names of each table in the layout-defined data 203, 204, and 205 are used as header candidates for the higher-level header that includes the column name headers in a multi-level header, and the column names are used as header candidates for the lower-level headers of the row name headers.

[0165] Figure 26 is an explanatory diagram illustrating an example of converting to a two-dimensional table with column names followed by values. Figure 26 shows an example of a header candidate list and an integrated table when the partitioning unit is set to "sheet". In Figure 26, along with the header candidate list display area 812, the integrated table that is displayed when all header candidates except metadata 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.

[0166] As shown in the header candidate list display area 812 of this figure, when the server device 1 accepts the selection "Convert to a 2D table in the order of column name followed by value", it lists the headers of each table parser 95, "2020", "2021", and "2022", as header candidates that encompass the other header candidates. Next, in order to display in the order of column name followed by value, the column headers (column names) of each table parser 95, "Be", "As", and "P", are displayed with indentation so that they become header candidates that encompass the respective header candidates "2020", "2021", and "2022". Here, "Convert to a 2D table in the order of column name followed by value" means that one column of the original table is displayed as one row of the integrated table.

[0167] Furthermore, in the integrated table, in order to distinguish and display the index headers (row names) of each table parser 95, header candidates for the "index" header name are displayed in the same order (indentation) as the column headers (column names). Here, the type column 8123 for the "index" header candidate is set to "metadata," but content other than "metadata" that indicates an "index" may also be displayed. Here, the explanation of the header candidate "metadata" in Figures 26 to 29 is the same as the explanation in Figure 12, so redundant explanations are omitted.

[0168] The preview area 813 in Figure 26 shows the integrated table that is displayed when all header candidates except metadata are selected in the header candidate list display area 812. As shown in the integrated table, the division unit is "sheet," but since there is only one sheet, the server device 1 arranges the contents of each table parser 95 contained in the sheet sequentially in a horizontal direction.

[0169] The integrated table header has headers for "2020", "2021", and "2022", and headers consisting of "Be", "As", "P", and "Index" contained within each of the "2020", "2021", and "2022" headers. Server device 1 reflects the contents of the column headers "Be", "As", and "P" of each table parser 95 as the contents of the "Be", "As", and "P" headers. Server device 1 displays "Unopened Bottle" and "Opened Bottle", which are the index headers of each table parser 95, in cells with "Index" as the header name.

[0170] In this example of "converting to a 2D table with column names followed by values," the column headers of the table where Table Parser 95 is installed are kept as they are, and the index header of Table Parser 95 is displayed in a header named "Index" that displays the contents of the index header. This makes it possible to generate an integrated table while maintaining a 2D table similar to the tabular data where Table Parser 95 is installed.

[0171] Thus, when the server device 1 integrates layout-defined data, which is a table with both column headers and index headers, into an integrated table, it accepts a selection to display one column of the layout-defined data as one row of the integrated table, and based on the accepted selection, it displays a preview of the integrated table and a list of header candidates. This makes it possible to generate an integrated table that represents the contents of tabular data, which has one or more table parsers 95 with column headers and index headers, as a two-dimensional table.

[0172] Figure 27 is an explanatory diagram illustrating an example of converting to a two-dimensional table with row names followed by values. Figure 27 shows an example of a header candidate list and an integrated table when the partitioning unit is set to "sheet". In Figure 27, along with the header candidate list display area 812, the integrated table that is displayed when all header candidates except metadata 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.

[0173] As shown in the header candidate list display area 812 of this figure, when the server device 1 accepts the selection "Convert to a 2D table in the order of row name followed by value", it lists the headers of each table parser 95, "2020", "2021", and "2022", as header candidates that encompass the other header candidates. Next, in order to display in the order of row name followed by value, the index headers (row names) of each table parser 95, "Unopened Bottle" and "Opened Bottle", are displayed with indentation so that they become header candidates that are encompassed by the header candidates "2020", "2021", and "2022", respectively. Here, "Convert to a 2D table in the order of row name followed by value" means that one row of the original table is displayed as one row of the integrated table.

[0174] Furthermore, in the integrated table, to show the differences in column headers (column names) for each table parser 95, header candidates for the "index" header name are displayed in the same order (indentation) as "unopened bottles" and "opened bottles" (index headers (row names)). Here, the type column 8123 for the "index" header candidate is set to "metadata," but it is also acceptable to display content other than "metadata" that indicates an "index."

[0175] The preview area 813 in Figure 27 shows the integrated table that is displayed when all header candidates except metadata are selected in the header candidate list display area 812. As shown in the integrated table, the division unit is "sheet," but since there is only one sheet, the server device 1 arranges the contents of each table parser 95 contained in the sheet sequentially in a horizontal direction.

[0176] The integrated table header has "2020", "2021", and "2022" headers, as well as "Unopened Bottles", "Opened Bottles", and "Index" headers, which are contained within the respective "2020", "2021", and "2022" headers. Server device 1 reflects the contents of the "Unopened Bottles" and "Opened Bottles" index headers of each table parser 95 as the contents of the "Unopened Bottles" and "Opened Bottles" headers, respectively. Server device 1 displays the column headers "Be", "As", and "P" of each table parser 95 in cells with "Index" as the header name.

[0177] In this example of "converting to a 2D table with row names followed by values," the column headers of the table where Table Parser 95 is installed are placed as they are, and the index header of Table Parser 95 is displayed in a header named "Index" that displays the contents of the index header. This makes it possible to generate an integrated table by converting the tabular data where Table Parser 95 is installed into a 2D table with the columns and rows swapped and then joining them.

[0178] In this way, when the server device 1 integrates layout-defined data, which is a table with both column headers and index headers, into an integrated table, it accepts a selection to display the integrated table so that one row of the layout-defined data is represented as one row of the integrated table, and based on the accepted selection, it displays a preview of the integrated table and a list of header candidates. This makes it possible to generate an integrated table that represents the contents of tabular data, in which one or more table parsers 95 having column headers and index headers are arranged, as a two-dimensional table.

[0179] Figure 28 is an explanatory diagram illustrating an example of converting to a one-dimensional table with column names, row names, and values ​​in that order. Figure 28 shows an example of a header candidate list and an integrated table when the partitioning unit is set to "sheet". In Figure 28, along with the header candidate list display area 812, the integrated table that is displayed when all header candidates except metadata 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.

[0180] As shown in the header candidate list display area 812 of this figure, when the server device 1 accepts the selection "Convert to a one-dimensional table in the order of column name, row name, then value", it lists the headers of each table parser 95, "2020", "2021", and "2022", as header candidates that encompass the other header candidates. Next, in order to display in the order of "Column name, row name, then value", the column headers (column names) of each table parser 95, "Be", "As", and "P", are displayed with indentation so that they become header candidates that are encompassed by the header candidates "2020", "2021", and "2022", respectively. Here, "Convert to a one-dimensional table in the order of column name, row name, then value" means arranging the values ​​in the layout-defined data of the original table one-dimensionally and displaying each layout-defined data as one row.

[0181] Next, to display the row names, the index headers (row names) "Unopened Bottle" and "Opened Bottle" are displayed for each column header (column name) "Be", "As", and "P", respectively. More specifically, "Unopened Bottle" and "Opened Bottle" are connected to each column header (column name) "Be", "As", and "P" with a "." (period) to create the header names for the header candidates. For example, the header names would be "Be.Unopened Bottle", "Be.Opened Bottle", "As.Unopened Bottle", and so on.

[0182] The preview area 813 in Figure 28 shows the integrated table that is displayed when all header candidates except metadata are selected in the header candidate list display area 812. As shown in the integrated table, the division unit is "sheet," but since there is only one sheet, the server device 1 arranges the contents of each table parser 95 contained in the sheet sequentially in a horizontal direction.

[0183] The integrated table header has "2020", "2021", and "2022" headers, and "Be", "As", and "P" headers that are contained within each of the "2020", "2021", and "2022" headers. Furthermore, the integrated table header also has "Unopened Bottle" and "Opened Bottle" headers that are contained within each of the "Be", "As", and "P" headers. Server device 1 reflects the contents of each table parser 95 as the contents of the "Unopened Bottle" and "Opened Bottle" headers for each of the "Be", "As", and "P" headers.

[0184] In this example, where the data is converted to a two-dimensional table with column names, row names, and values ​​in that order, the column headers and index headers of the table where Table Parser 95 is installed are superimposed to form the header of the integrated table. This makes it possible to generate an integrated table that represents the contents of the tabular data where Table Parser 95 is installed as a one-dimensional table.

[0185] In this way, when the server device 1 integrates layout-defined data, which is a table with both column headers and index headers, into an integrated table, it accepts a selection to display the integrated table by arranging the values ​​in the layout-defined data one-dimensionally, with each layout-defined data item representing one row. Based on the accepted selection, it displays a preview of the integrated table and a list of header candidates. This makes it possible to generate an integrated table that represents the contents of tabular data, which has one or more table parsers 95 with column headers and index headers, as a one-dimensional table.

[0186] Figure 29 is an explanatory diagram illustrating an example of converting to a one-dimensional table with row names, column names, and values ​​in that order. Figure 29 shows an example of a header candidate list and an integrated table when the partitioning unit is set to "sheet". In Figure 29, along with the header candidate list display area 812, the integrated table that is displayed when all header candidates except metadata 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.

[0187] As shown in the header candidate list display area 812 of this figure, when the server device 1 accepts the selection "Convert to a one-dimensional table in the order of row name, column name, then value", it lists the headings of each table parser 95, "2020", "2021", and "2022", as header candidates that encompass the other header candidates. Next, in order to display in the order of "row name, column name, then value", the index headers (row names) of each table parser 95, "unopened bottle" and "opened bottle", are displayed with indentation so that they become header candidates that are encompassed by the header candidates "2020", "2021", and "2022", respectively. Here, "Convert to a one-dimensional table in the order of row name, column name, then value" means arranging the values ​​in the layout-defined data of the original table one-dimensionally and displaying each layout-defined data as one row.

[0188] Next, to display the row names, the column headers (column names) "Be," "As," and "P" are displayed for each index header (row name) "Unopened Bottle" and "Opened Bottle," respectively. More specifically, the column headers (column names) "Be," "As," and "P" are connected with a "." (period) for each index header (row name) "Unopened Bottle" and "Opened Bottle," respectively, to form the header names of the header candidates. For example, the header names would be "Unopened Bottle.Be," "Unopened Bottle.As," "Unopened Bottle.P," "Opened Bottle.Be," "Opened Bottle.As," "Opened Bottle.P," and so on.

[0189] The preview area 813 in Figure 29 shows the integrated table that is displayed when all header candidates except metadata are selected in the header candidate list display area 812. As shown in the integrated table, the division unit is "sheet," but since there is only one sheet, the server device 1 arranges the contents of each table parser 95 contained in the sheet sequentially in a horizontal direction.

[0190] The integrated table header has headers for "2020", "2021", and "2022", as well as headers for "Unopened Bottles" and "Opened Bottles" that are contained within the respective "2020", "2021", and "2022" headers. In addition, the "Unopened Bottles" and "Opened Bottles" headers of the integrated table have headers for "Be", "As", and "P" that are contained within the respective "Unopened Bottles" and "Opened Bottles" headers. Server device 1 reflects the "Be", "As", and "P" contents of each table parser 95 as the header contents for the "Unopened Bottles" and "Opened Bottles" headers, respectively.

[0191] In this example, where the table is converted to a two-dimensional table with column names, row names, and values ​​in that order, the column headers and index headers of the table where Table Parser 95 is installed are superimposed to form the header of the integrated table.

[0192] In this way, when the server device 1 integrates layout-defined data, which is a table with both column headers and index headers, into an integrated table, it accepts a selection to display the integrated table by arranging the values ​​in the layout-defined data one-dimensionally, with each layout-defined data item representing one row. Based on the accepted selection, it displays a preview of the integrated table and a list of header candidates. This makes it possible to generate an integrated table that represents the contents of tabular data, which has one or more table parsers 95 with column headers and index headers, as a one-dimensional table.

[0193] As described above, server device 1 outputs a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data to which a layout defining the relationships between multiple cells is applied. From the list of header candidates, it accepts the selection of an integrated table header and outputs a preview of the integrated table based on the selected header. This makes it possible to view multiple different tabular data sets associated with layouts as an integrated table, using only the selected header. 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.

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

[0195] 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.

[0196] 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.

[0197] 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.

[0198] 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.

[0199] 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.

[0200] 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]

[0201] 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. Output a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data with layouts that define the relationships between multiple cells. From the list of header candidates, the selection of the header for the integrated table is accepted. Output a preview of the integrated table based on the selected header. A program that instructs a computer to perform a process.

2. The system accepts an operation to move one of the header candidates from the aforementioned list of candidates to a higher or lower position than other candidates. In the preview of the integrated table, the first candidate is displayed in a column to the left or right of the other candidates, respectively. The program according to claim 1.

3. In the list of header candidates or the display of the preview, the selection of the header is accepted. Cell completion is performed to fill in multiple blank cells in the row or column identified by the selected header with the same values ​​from the layout-defined data. The program according to claim 1.

4. Perform the cell completion process for all or more of the headers. The program according to claim 3.

5. When integrating the layout-defined data, which is a table having both column headers and index headers, into the integrated table, the integrated table accepts one of the following options: display one column of the layout-defined data as one row of the integrated table; display one row of the layout-defined data as one row of the integrated table; or arrange the values ​​in the layout-defined data one-dimensionally and display each of the layout-defined data as one row. Based on the accepted selection, the preview of the integrated table and a list of header candidates are displayed. The program according to claim 1.

6. The system accepts one of the following as a splitting unit: a sheet containing the aforementioned tabular data, a tabular file containing one or more of the aforementioned sheets, and a table which is the layout-defined data defined as a table within the aforementioned tabular data. When the tabular file is used as the division unit, the preview of the integrated table is output, with the sheet name of the sheet being a higher-level header that includes the header candidates contained in the sheet. The program according to claim 1.

7. The metadata is output as one of the headers of the aforementioned preview. 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 the table path (a combination of the file name, the sheet name, and the table headers) are output as subheaders included in the header of the metadata. The program according to claim 6.

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

9. The layout includes a table parser that defines a table, a sequence parser that defines the sequence, and a header parser that defines the headers of the cells, the table parser, and the sequence parser. The preview of the integrated table is output, with the header of the table parser or the header of the sequence parser set as a higher-level header that includes the header candidate within the table parser or sequence parser, respectively. The program according to claim 1.

10. Output a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data with layouts that define the relationships between multiple cells. From the list of header candidates, the selection of the header for the integrated table is accepted. Output a preview of the integrated table based on the selected header. Information processing methods.

11. It includes a control unit, and the control unit is Output a list of header candidates for an integrated table, which is a combination of multiple layout-defined data sets that are tabular data with layouts that define the relationships between multiple cells. From the list of header candidates, the selection of the header for the integrated table is accepted. Output a preview of the integrated table based on the selected header. Information processing device.

Images