Program, information processing method and information processing device

Abstract

To provide a program etc. capable of applying the layout of a template file to tabular data. [Solution] A program according to one aspect accepts template settings for a template file that applies a layout that defines the relationships between each element of tabular data to tabular data, and causes a computer to execute a process of applying the layout of the template file set in the template to new tabular data.

Description

[Technical Field]

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

[0002] In recent years, there have been technologies for editing or converting tabular data. For example, Patent Document 1 discloses a device that converts spreadsheet-format data (tabular data) having a predefined format into semi-structured data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2017-146923 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention of Patent Document 1 has a problem in that the layout of a template file cannot be applied to tabular data.

[0005] One aspect of the present invention is to provide a program or the like that can apply the layout of a template file to tabular data. [Means for solving the problem]

[0006] A program according to one aspect receives template settings for a template file that applies a layout that defines the relationships between elements of tabular data to tabular data, and causes a computer to execute a process of applying the layout of the template file set in the template to new tabular data. [Effects of the Invention]

[0007] In one aspect, it is possible to apply the layout of a template file to tabular data. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram illustrating an overview of a template system. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of a server. [Figure 3] FIG. 2 is a block diagram illustrating an example of the configuration of a user terminal. [Figure 4] FIG. 10 is an explanatory diagram illustrating an example of a layout editing screen. [Figure 5] FIG. 10 is an explanatory diagram illustrating a process of applying the layout of a template file to new tabular data. [Figure 6] 10 is a flowchart showing a processing procedure when accepting template settings. [Figure 7] 10 is a flowchart showing a processing procedure when applying a layout to a single table-format data. [Figure 8] 10 is a flowchart showing a processing procedure when applying a layout to a plurality of table-format data. [Figure 9] FIG. 10 is an explanatory diagram illustrating a process of applying the layout of a template file to new tabular data in Modification 1. [Figure 10] FIG. 10 is a block diagram showing an example of the configuration of a server in the second embodiment. [Figure 11] FIG. 10 is an explanatory diagram illustrating an example of a record layout of an access authority DB. [Figure 12] 10A and 10B are explanatory diagrams illustrating a process of applying the layout of a template file for which access rights are set to new tabular data. [Figure 13] 10 is a flowchart showing a processing procedure for applying a layout to tabular data in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] The present invention will be described in detail below with reference to the drawings showing embodiments thereof.

[0010] (Embodiment 1) The first embodiment relates to a form in which the layout of a template file set in a template is applied to tabular data. Fig. 1 is an explanatory diagram showing an overview of a template system. The system of this embodiment includes an information processing device 1 and an information processing terminal 2, and each device transmits and receives information via a network N such as the Internet.

[0011] The information processing device 1 is an information processing device that processes, stores, transmits, and receives various types of information. The information processing device 1 is, for example, a server device, a personal computer, or a general-purpose tablet PC (personal computer). In this embodiment, the information processing device 1 is assumed to be a server device, and will be referred to as server 1 below for simplicity.

[0012] The information processing terminal 2 is a user terminal device that receives the designation of a folder storing a template file and transmits (uploads) a data file to which the layout of the template file is to be applied. The information processing terminal 2 is an information processing device such as a personal computer terminal, a tablet, a smartphone, a mobile phone, or a wearable device such as a smart watch. For simplicity, the information processing terminal 2 will be referred to as the user terminal 2 below.

[0013] In this embodiment, the server 1 and the user terminal 2 are described as separate physical devices, but this is not limiting. For example, it is possible to use a single information processing device that has both server and user terminal functions.

[0014] Setting the layout of tabular data is important for efficiently managing and recording tabular data, including data from additional experiments or data from past research themes (problems). Tabular data will be discussed later. When creating a data file containing tabular data (for example, an experimental plan or experimental report), the user (creator) must set and adjust the layout for each file. This requires time and effort to manually set the layout each time.

[0015] To solve this problem, in this embodiment, by using a template file in which a layout is set, the layout set in the template file can be automatically applied to new tabular data.

[0016] The server 1 according to this embodiment accepts template settings for a template file that applies a layout that defines the relationships between elements of tabular data to tabular data. The server 1 applies the layout of the template file set in the template to new tabular data.

[0017] 2 is a block diagram showing an example of the configuration of the server 1. The server 1 includes a control unit 11, a storage unit 12, a communication unit 13, a reading unit 14, and a large-capacity storage unit 15. Each component is connected by a bus B.

[0018] The control unit 11 includes an arithmetic processing device such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field Programmable Gate Array), a DSP (Digital Signal Processor), or a quantum processor. The control unit 11 reads and executes a control program 1P (program product) stored in the storage unit 12, thereby performing various information processing and control processing related to the server 1.

[0019] It should be noted that the control program 1P can be deployed to run on a single computer, or on multiple computers located at one site, or distributed across multiple sites and interconnected by a communications network.

[0020] 2, the control unit 11 is described as a single processor, but it may be a multi-processor. The control unit 11 may execute various information processes or control processes by the same processor within the server 1, or may execute various processes by different processors within the server 1.

[0021] The storage unit 12 includes memory elements such as RAM (Random Access Memory) and ROM (Read Only Memory), and stores the control program 1P or data required for the control unit 11 to execute processing. The storage unit 12 also temporarily stores data required for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing communication-related processing, and transmits and receives information to and from the user terminal 2, etc. via the network N.

[0022] The reading unit 14 reads a portable storage medium 1a including a CD (Compact Disc)-ROM or a DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 14 and store it in the mass storage unit 15. Alternatively, the control unit 11 may download the control program 1P from another computer via a network N or the like and store it in the mass storage unit 15. Furthermore, the control unit 11 may read the control program 1P from the semiconductor memory 1b.

[0023] The mass storage unit 15 includes a recording medium such as an HDD (Hard disk drive) or an SSD (Solid State Drive). The mass storage unit 15 includes a plurality of folders 151. Each folder 151 stores a template file 152 set as a template, a data file 153 related to a research theme or project, and the like.

[0024] In this embodiment, the storage unit 12 and the large-capacity storage unit 15 may be configured as an integrated storage device. Furthermore, the large-capacity storage unit 15 may be configured by a plurality of storage devices. Furthermore, the large-capacity storage unit 15 may be an external storage device connected to the server 1.

[0025] The server 1 may execute various information processing and control processing on a single computer, or may execute the processing in a distributed manner on multiple computers. The server 1 may also be realized by multiple virtual machines provided in a single server, or may be realized by using a cloud server.

[0026] 3 is a block diagram showing an example of the configuration of the user terminal 2. The user terminal 2 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, and a display unit 25.

[0027] The control unit 21 includes a processing unit such as a CPU or an MPU, and performs various information processing and control processing related to the user terminal 2 by reading and executing a control program 2P (program product) stored in the storage unit 22.

[0028] 3, the control unit 21 is described as a single processor, but it may be a multi-processor. The control unit 21 may execute various information processing or control processes by the same processor within the user terminal 2, or may execute various information processing or control processes by different processors within the user terminal 2.

[0029] The storage unit 22 includes memory elements such as RAM or ROM, and stores the control program 2P or data required for the control unit 21 to execute processing. The storage unit 22 also temporarily stores data required for the control unit 21 to execute arithmetic processing.

[0030] The communication unit 23 is a communication module for performing communication-related processing, and transmits and receives information to and from the server 1, etc. via the network N. The input unit 24 may be a keyboard, a mouse, or a touch panel integrated with the display unit 25. The display unit 25 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to instructions from the control unit 21.

[0031] 4 is an explanatory diagram showing an example of a layout editing screen. Through this screen, a template file 152 can be generated based on the layout arranged in the data file 153.

[0032] The screen has an operation button area 210 and a layout editing area 220. The operation button area 210 has a save button 211, an undo button 212, a redo button 213, a key-value button 214, a multiple cell button 215, a table button 216, an order button 217, an output button 218, and a template setting button 219. Each button executes the function it provides when operated (for example, clicked with a mouse) by a user (a user of the user terminal 2).

[0033] The Save button 211 provides a function to store (save) as a layout file the type, position, size, orientation, etc. of one or more perspective objects (described later) placed in the layout editing area 220. The Undo button 212 provides a function to cancel the most recent operation performed in the layout editing area 220. The Redo button 213 provides a function to redo the operation that was most recently canceled by the Undo button 212. The Key-Value button 214, Multiple cell button 215, Table button 216, Order button 217, Output button 218, and Template setting button 219 will be explained together with the explanation of the layout editing area 220 below.

[0034] The layout editing area 220 displays tabular data included in the data file (tabular file) 153 and also displays a layout on the tabular data. The tabular data is stored in the data file 153, which is created by spreadsheet software such as Excel (registered trademark).

[0035] Tabular data is composed of columns and rows, and data elements (or components) are located at the intersections of the rows and columns and are called cells. A cell is 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 4, for example, the value of cell B3 is stored as the string "Laboratory equipment" and the value of cell D3 is stored as the string "Tammann tube."

[0036] The layout is depicted mainly with bold lines and arrows in FIG. 4. In this embodiment, the elements that make up the layout are called parse objects. In this embodiment, the parse object has a cell parser 91, a header connector 92, a sequence connector 93, and a table parser 95. However, it may have parse objects other than these. It is also possible not to include any or all of these parse objects. The cell parser 91 identifies one cell. In FIG. 4, for example, the cell parser 91 is placed in cell B3, cell D3, cell B6, cell D6, cell F6, cell C16, cell C18, and cell C20.

[0037] A header connector 92 is an arrow extending from a cell parser 91 that specifies a cell indicating a header to a cell parser 91 or table parser 95 that contains the content of the header. A header connector 92 connects two cell parsers 91, or connects a cell parser 91 and a table parser 95. In Figure 4, the header connector 92 is represented by an arrow with a triangular tip that extends from cell B3 to cell D3, for example. The header connector 92 may also indicate an inclusion relationship.

[0038] The Key-Value button 214 is a button that provides the arrangement of the heading connectors 92 together with the previous and next cell parsers 91. When the user terminal 2 receives a click (touch) operation on the Key-Value button 214, it transitions to a heading connection mode in which heading connections can be executed by the heading connectors 92 as a parsing operation. The heading connection mode is a mode for performing a parsing operation that specifies element relationships defined as pairs of keys and values.

[0039] For example, the user can click on the Key-Value button 214, and then click on cells B3 and D3 in sequence to place a cell parser 91 in cells B3 and D3, and then place a header connector 92 connecting cell B3 to cell D3.

[0040] Also, when placing the table parser 95 at the end of the header connector 92, place the table parser 95 first, select the Key-Value button 214, click on the cell that will become the header, and then select the table parser 95, thereby placing the header connector 92 with the table parser 95 at its end.

[0041] Furthermore, the header connector 92 may connect three or more cell parsers 91 in series. In Fig. 4, for example, the header connector 92 extends from cell B6 to cell D6, and further extends from cell D6 to cell F6. The final header connector 92 can be connected to a table parser 95. As with the header connector 92 connecting two cell parsers 91, even when three or more cell parsers 91 are connected in series, the header connector 92 can represent a header, an inclusion relationship, or the like.

[0042] The Multiple cell button 215 is a button that provides an arrangement of multiple heading connectors 92 together with the cell parser 91 connected by the multiple heading connectors 92. When the user terminal 2 receives a click operation on the Multiple cell button 215, it transitions to a continuous heading connection mode in which continuous heading connection can be performed as a parsing operation. The continuous heading connection mode is a mode for performing a parsing operation that specifies an element relationship defined as multiple pairs that are connected consecutively.

[0043] For example, the user operates the Multiple cell button 215 by clicking, and then sequentially clicks on cells B6, D6, and F6. This places a cell parser 91 in cells B6, D6, and F6, and further places a header connector 92 that connects cell B6 to cell D6 and also connects cell D6 to cell F6.

[0044] In this case, the end of cell specification may be indicated by clicking the last cell and then again clicking the Multiple cell button 215. Also, when placing a table parser 95 at the end of the last header connector 92, first place the table parser 95, select the Multiple cell button 215, click multiple cells to be headers, and then finally select the table parser 95, thereby placing a header connector 92 with the table parser 95 at its end.

[0045] The table parser 95 is a parse object that specifies a table whose data content is structured by rows and columns. The table parser 95 is composed of a table area 951 that indicates the entire table, an item area 953 that has multiple items, and a value area 952 that corresponds to each item.

[0046] 4, table area 951 of table parser 95 is represented by a rectangle with cell B9 and cell D13 as the diagonal vertices, and value area 952 is represented by a rectangle with cell C10 to cell D13 as the diagonal vertices. Table area 951 and value area 952 are distinguished from each other by black triangles at the top left and bottom right of value area 952.

[0047] Item area 953 includes either a first item area including multiple items arranged in a first direction (e.g., row direction) or a second item area including multiple items arranged in a second direction (e.g., column direction), or both. As shown in the figure, the first item area includes "Mole Ratio," "Number of Grams," "Stock," and "Order Source" in cells B10 to B13. The second item area includes "Ti" in cell C9 and "Mn" in cell D9.

[0048] The Table button 216 is a button that provides the arrangement of the table parser 95. When the user terminal 2 receives a click operation on the Table button 216, it transitions to a table parse mode in which the table parser 95 can be executed as a parse operation. The table parse mode is a mode for performing a parse operation in which the user specifies a table area 951 of the table parser 95 and a value area 952 included in the table area 951.

[0049] For example, the user operates the Table button 216 by clicking it, and then specifies the table area 951, which is the area showing the entire table (for example, by dragging from cell B9 to cell D13).Then, the user specifies the value area 952, which shows the data portion (for example, by dragging from cell C10 to cell D13), thereby placing the table parser 95.

[0050] The order connectors 93 are parse objects that connect cell parsers 91 together, and represent the order in the direction indicated by the arrow. In Fig. 4, for example, the order connectors 93 are shown as arrows extending from cell C16 to cell C18 and from cell C18 to cell C20 for the cell parsers 91 arranged in cell C16, cell C18, and cell C20. In order to distinguish the order connectors 93 from the header connectors 92, in this embodiment, each of the order connectors 93 has a V-shaped arrow at the end.

[0051] The Order button 217 is a button for sequentially connecting multiple cell parsers 91 with multiple order connectors 93. When the user terminal 2 receives a click operation on the Order button 217, it transitions to an order connection mode in which order connection can be executed as a parse operation. The order connection mode is a mode for performing a parse operation that specifies an element relationship defined as multiple cell parsers 91 connected by order connectors 93 in a predetermined order.

[0052] For example, the user operates the Order button 217 by clicking or the like, and then sequentially clicks on cells C16, C18, and C20. This places a cell parser 91 in cells C16, C18, and C20, and further places an order connector 93 that connects cell C16 to cell C18 and also connects cell C18 to cell C20.

[0053] These parse objects are included in a layout corresponding to the tabular data, and are stored (saved) as a layout file in the mass storage unit 15 of the server 1 by an operation such as clicking the save button 211. The layout file may also be stored in the storage unit 22 of the user terminal 2.

[0054] The layout file may store the layout by converting each parse object arranged in the tabular data into a character string, etc. The layout includes at least one piece of information, such as first information obtained by a parse operation in the heading connection mode, second information obtained by a parse operation in the consecutive heading connection mode, third information obtained by a parse operation in the table parse mode, and fourth information obtained by a parse operation in the sequential connection mode.

[0055] The first information includes the position of the cell parser 91 corresponding to the key, and the position of the cell parser 91 or table parser 95 corresponding to the value. The position of the cell parser 91 is the row and column number of the cell parser 91. The position of the table parser 95 is, for example, the positions of the top left cell and bottom right cell of the table area 951 of the table parser 95, and the positions of the top left cell and bottom right cell of the value area 952 of the table parser 95.

[0056] The second information includes the position of each cell parser 91 connected by the header connector 92, and information about the order in which each cell parser 91 is connected. The third information includes the positions of the start and end cells of the table area 951 of the table parser 95, and the positions of the start and end cells of the value area 952 included in the table area 951.

[0057] The fourth information includes information about the position of each cell parser 91 connected in order by the order connector 93, and the order in which each cell parser 91 is connected in order.

[0058] For example, a header connector 92 extending from cell B3 to cell D3 can be written in a predetermined syntax such as "Header: B3: D3" to store the layout in a layout file.

[0059] The output button 218 is a button for converting tabular data into semi-structured data based on the above-mentioned parse objects. Semi-structured data is data whose data structure is defined to some extent among unstructured data whose data structure is not clearly defined. In this embodiment, the semi-structured data may be, for example, text data written in JSON (JavaScript Object Notation).

[0060] For example, a header connector 92 extending from a cell parser 91 in cell B3 to a cell parser 91 in cell D3 can be written in JSON format as follows: {"key": "Laboratory equipment", "value": [{"key": "Tammann tube"}]} By converting the data into semi-structured data in this way, necessary information can be easily extracted by searching for it among tabular data with different layouts. By generating semi-structured data from tabular data, the generated semi-structured data can be stored centrally.

[0061] Furthermore, rules for converting parse objects other than the header connector 92 into semi-structured data can be defined as appropriate. The rules for converting into semi-structured data do not have to be rules for converting into JSON format, but may be rules for converting into XML format or other rules for converting into semi-structured data. Parse objects are not limited to the cell parser 91, header connector 92, order connector 93, and table parser 95, and can be defined as appropriate, and rules for converting each parse object into semi-structured data can be defined as appropriate.

[0062] The template setting button 219 is a button for setting a data file 153, in which a layout that defines the relationships between elements of tabular data is arranged, as the template file 152. The data file 153 is a tabular file that has one or more spreadsheets created with spreadsheet software such as Excel. When the user terminal 2 receives a click operation of the template setting button 219, it acquires the layout arranged for the data file 153 by parsing the cell parser 91, table parser 95, header connector 92, and order connector 93.

[0063] The user terminal 2 accepts the designation of a target folder 151 in the mass storage unit 15 of the server 1 for storing a template file 152. Specifically, the server 1 transmits multiple folders 151 in the mass storage unit 15 to the user terminal 2. The user terminal 2 receives the multiple folders 151 transmitted from the server 1 and displays them on the screen. The user terminal 2 accepts the user's designation of a target folder 151 from the multiple folders 151.

[0064] The user terminal 2 transmits the acquired layout, data file 153, and folder information of the accepted target folder 151 (path, name, etc. of the folder 151) to the server 1. The server 1 receives the layout, data file 153, and folder information transmitted from the user terminal 2.

[0065] Based on the received folder information, the server 1 identifies the corresponding target folder 151. The server 1 stores the received data file 153 as a template file 152 in the identified folder 151 together with the received layout.

[0066] The template file 152 includes a layout and tabular data included in the data file 153. The layout includes at least one piece of information, such as first information obtained by a parse operation in the heading connection mode, second information obtained by a parse operation in the consecutive heading connection mode, third information obtained by a parse operation in the table parse mode, and fourth information obtained by a parse operation in the order connection mode.

[0067] In the present embodiment, an example has been described in which the layout and the data file 153 are stored as the template file 152, but the present invention is not limited to this. The template file 152 may store only the layout. In this case, the server 1 generates the template file 152 in a predetermined file format based on the received layout. The file format may be, for example, CSV (Comma-Separated Values), XML (eXtensible Markup Language), JSON (JavaScript Object Notation), HTML (HyperText Markup Language), or a text file.

[0068] The file name of the template file 152 can be named based on the file name of the data file 153. For example, if the file name of the data file 153 is "Experiment Record.xlsx," the file name of the template file 152 can be "Experiment Record.xxx" or "Experiment Record_Template.xxx." By using a consistent naming convention in this way, the management of the template file 152 and the data file 153 becomes more efficient, and the correspondence between the files can be quickly identified based on the file names.

[0069] FIG. 5 is an explanatory diagram illustrating the process of applying the layout of a template file to new tabular data. 5A is an explanatory diagram illustrating a process of applying a layout to a single piece of tabular data. As shown in the figure, a data file 153 including new tabular data (to which the layout is to be applied) is stored in the storage unit (local folder) 22 of the user terminal 2.

[0070] The user terminal 2 acquires a data file 153 from the storage unit 22. The user terminal 2 accepts the designation of a folder 151 in which a template file 152 to be applied to new tabular data is stored. The folder 151 exists in the mass storage unit 15 of the server 1. The user terminal 2 transmits (uploads) the acquired data file 153 and folder information of the designated folder 151 to the server 1.

[0071] The server 1 receives the data file 153 and folder information transmitted from the user terminal 2. The server 1 identifies the corresponding folder 151 based on the received folder information. The server 1 acquires list information of the template files 152 in the identified folder 151. The list information includes the name of each template file 152, etc.

[0072] The server 1 generates an application confirmation screen 12a. The application confirmation screen 12a includes a template file selection field 12b, a batch application check box 12c, an apply ("Yes") button 12d, a not apply (No) button 12e, and a cancel button 12f.

[0073] The template file selection field 12b is a field for accepting the selection of a target template file 152 from multiple template files 152. The batch application checkbox 12c is a checkbox for accepting an operation setting for whether or not to perform the same operation (such as "apply" or "do not apply") on all data files 153 (items) when multiple data files 153 are included. The batch application checkbox 12c will be described in FIG. 5B.

[0074] The apply button 12d is a button for applying the layout of the template file 152 to new tabular data. The not apply button 12e is a button for not applying the layout of the template file 152 to new tabular data. The cancel button 12f is a button for ending the application process.

[0075] The server 1 sets the list information of the acquired template files 152 in the template file selection field 12b. If the list information contains a single template file 152, only the file name of that template file 152 is set in the template file selection field 12b. Alternatively, if the list information contains multiple template files 152, the file names of all the template files 152 are set in the template file selection field 12b.

[0076] The list information includes, for example, "Experiment Record 1.XXX," "Experiment Record 2.XXX," and "Experiment Record 3.XXX." The server 1 transmits an application confirmation screen 12a on which the list information of the template file 152 is set to the user terminal 2. The user terminal 2 receives and displays the application confirmation screen 12a transmitted from the server 1.

[0077] When the user terminal 2 receives a selection operation in the template file selection field 12b, it acquires the file name (for example, "Experiment Record 1.xxx") of the selected template file 152. The user terminal 2 transmits the acquired file name of the template file 152 to the server 1. The server 1 acquires the target template file 152 according to the file name transmitted from the user terminal 2.

[0078] The server 1 reads out a layout from the acquired template file 152. The read out layout includes at least one piece of information, such as first information obtained by a parse operation in the heading connection mode, second information obtained by a parse operation in the consecutive heading connection mode, third information obtained by a parse operation in the table parse mode, and fourth information obtained by a parse operation in the order connection mode. The server 1 applies the read out layout to the data file 153 transmitted from the user terminal 2.

[0079] Specifically, the server 1 sets the same position and value in the data file 153 based on the position of the cell parser 91, the value of the cell parser 91, the position of the table parser 95, the position of each cell parser 91 connected with consecutive headers, the position of each table parser 95 connected with consecutive headers, or the connection order of each sequentially connected cell parser 91 or each table parser 95, etc., specified in the template file 152.

[0080] The server 1 transmits the data file 153 to which the layout has been applied to the user terminal 2. The user terminal 2 receives the data file 153 to which the layout has been applied transmitted from the server 1. The user terminal 2 displays the received data file 153 to which the layout has been applied on the screen.

[0081] FIG. 5B is an explanatory diagram illustrating a process of collectively applying a layout to a plurality of table-format data.

[0082] As shown in the figure, a plurality of data files 153 including tabular data (layout application targets) are stored in the storage unit 22 of the user terminal 2. These plurality of data files 153 store tabular data of research themes in the same field, and are data files to which the same layout can be applied. In other words, the layout defined in the template file 152 is a format that can be commonly applied to the plurality of data files 153 to which the layout is applied.

[0083] Although an example of three data files 153 has been described in FIG. 5B, the number of data files 153 is not limited to this, and there is no particular limit to the number of data files 153.

[0084] The user terminal 2 acquires a plurality of data files 153 from the storage unit 22. The user terminal 2 accepts the designation of a folder 151 in which a template file 152 to be applied to a plurality of new tabular data is stored. The folder 151 exists in the mass storage unit 15 of the server 1. The user terminal 2 transmits the acquired plurality of data files 153 and folder information of the designated folder 151 to the server 1.

[0085] The server 1 generates and transmits the application confirmation screen 12a based on the data file 153 and folder information transmitted from the user terminal 2. The user terminal 2 receives and displays the application confirmation screen 12a transmitted from the server 1.

[0086] When the user terminal 2 receives a setting operation of the batch application check box 12c, it acquires the received batch application information. The batch application information is information indicating whether or not to apply the layout to all data files 153 at once (for example, "apply" or "not to be applied").

[0087] The user terminal 2 transmits the file name of the template file 152 selected in the template file selection field 12b and batch application information to the server 1. The server 1 reads out the target template file 152 in accordance with the file name transmitted from the user terminal 2, and thereby acquires the layout stored in the template file 152.

[0088] The server 1 determines, in accordance with the received batch application information, whether or not to batch apply the layout to all of the data files 153. If the server 1 determines that the layout has not been batch applied to all of the data files 153, it selects one data file 153 from the multiple data files 153.

[0089] The server 1 applies a layout to the tabular data included in the selected data file 153. The server 1 transmits the data file 153 with the layout applied to the user terminal 2. The user terminal 2 receives the data file 153 with the layout applied transmitted from the server 1. The user terminal 2 displays the received data file 153 with the layout applied on the screen.

[0090] If there is a data file 153 to which a layout has not been applied, the server 1 transmits the application confirmation screen 12a again to the user terminal 2. By repeatedly executing the layout application process described above, it is possible to apply the layout to the tabular data included in all of the data files 153.

[0091] Alternatively, if the server 1 determines to collectively apply the layout to all data files 153, the server 1 applies the layout to the tabular data included in each data file 153. The server 1 transmits each data file 153 to which the layout has been applied to the user terminal 2. The user terminal 2 receives each data file 153 after the layout has been applied, transmitted from the server 1. The user terminal 2 displays each data file 153 after the received layout has been applied on the screen.

[0092] 6 is a flowchart showing the processing steps for accepting template settings. The control unit 21 of the user terminal 2 acquires from the storage unit 22 a data file 153 (e.g., an Excel file) in which a layout that defines the relationships between elements of tabular data is arranged (step S201). The control unit 21 accepts, via the input unit 24, a setting request for setting a layout in the template (e.g., a click on the template setting button 219 in FIG. 4) (step S202).

[0093] The control unit 21 acquires a layout arranged by a parsing operation on the cell parser 91, the table parser 95, the header connector 92, and the sequential connector 93 for the data file 153 (step S203). The layout includes at least one piece of information, such as first information obtained by a parsing operation in the header connection mode, second information obtained by a parsing operation in the consecutive header connection mode, third information obtained by a parsing operation in the table parse mode, and fourth information obtained by a parse operation in the sequential connection mode.

[0094] The control unit 21 receives, via the input unit 24, a designation of the target folder 151 in the mass storage unit 15 of the server 1 for storing the template file 152 (step S204). The control unit 21 transmits the acquired layout, the data file 153, and the folder information of the received target folder 151 to the server 1 via the communication unit 13 (step S205).

[0095] The control unit 11 of the server 1 receives the layout, data file 153, and folder information transmitted from the user terminal 2 via the communication unit 13 (step S101). The control unit 11 identifies the corresponding target folder 151 based on the received folder information (step S102). The control unit 11 stores the received data file 153 together with the received layout as a template file 152 in the identified folder 151 (step S103). The control unit 11 then terminates the process.

[0096] 7 is a flowchart showing the processing procedure when applying a layout to a single piece of tabular data. The control unit 21 of the user terminal 2 acquires a data file 153 including new tabular data (to which the layout is to be applied) from the storage unit 22 (step S211). The control unit 21 may also accept, via the input unit 24, the creation of the data file 153 by the user.

[0097] The control unit 21 receives, via the input unit 24, a designation of the folder 151 in which the template file 152 to be applied to the new tabular data is stored (step S212). The folder 151 exists in the mass storage unit 15 of the server 1. The control unit 21 transmits the acquired data file 153 and folder information of the designated folder 151 to the server 1 via the communication unit 23 (step S213).

[0098] The control unit 11 of the server 1 receives the data file 153 and folder information transmitted from the user terminal 2 via the communication unit 13 (step S111). The control unit 11 identifies the corresponding folder 151 based on the received folder information (step S112). The control unit 11 acquires list information of the template files 152 in the identified folder 151 (step S113). The list information includes a list of the template files 152 included in the folder 151, the names of each template file 152, etc.

[0099] The control unit 11 generates the application confirmation screen 12a (step S114). The control unit 11 sets the list information of the acquired template file 152 in the template file selection field 12b of the application confirmation screen 12a (step S115). The control unit 11 transmits the application confirmation screen 12a, in which the list information of the template file 152 has been set, to the user terminal 2 via the communication unit 13 (step S116).

[0100] The control unit 21 of the user terminal 2 receives the application confirmation screen 12a transmitted from the server 1 via the communication unit 23 (step S214). The control unit 21 displays the received application confirmation screen 12a on the display unit 25 (step S215). The control unit 21 accepts, via the input unit 24, a selection of a template file 152 to which a layout is to be applied from among the multiple template files 152 (step S216). Note that if there is a single template file 152, the control unit 21 may automatically select that template file 152.

[0101] The control unit 21 transmits the file name of the acquired template file 152 to the server 1 via the communication unit 13 (step S217). The control unit 11 of the server 1 receives the file name transmitted from the user terminal 2 via the communication unit 13 (step S117). The control unit 11 reads out a layout from the corresponding template file 152 according to the received file name (step S118).

[0102] The control unit 11 applies the read layout to the received data file 153 (step S119). The control unit 11 transmits the data file 153 after the layout has been applied to the user terminal 2 via the communication unit 13 (step S120).

[0103] The control unit 21 of the user terminal 2 receives the layout-applied data file 153 transmitted from the server 1 via the communication unit 23 (step S218). The control unit 21 displays the received layout-applied data file 153 on the display unit 25 (step S219). The control unit 21 ends the process.

[0104] 8 is a flowchart showing the processing procedure for applying a layout to multiple table-format data. Note that the same reference numerals are used to designate the same contents as those in FIG. 7, and the description thereof will be omitted.

[0105] The control unit 21 of the user terminal 2 acquires a plurality of data files 153 including tabular data (layout application target) from the storage unit 22 (step S221). The control unit 21 may also accept, via the input unit 24, the creation of a plurality of data files 153 by the user. The control unit 21 executes the process of step S212. The control unit 21 transmits the acquired plurality of data files 153 and folder information of the specified folder 151 to the server 1 via the communication unit 23 (step S222).

[0106] The control unit 11 of the server 1 receives the multiple data files 153 and folder information transmitted from the user terminal 2 via the communication unit 13 (step S121). The control unit 11 executes the processes of steps S112 to S116. The control unit 21 of the user terminal 2 executes the processes of steps S214 to S216.

[0107] The control unit 21 receives batch application information indicating whether or not to apply the layout to all data files 153 at once via the input unit 24 (step S223). For example, the control unit 21 may acquire the batch application information through the batch application check box 12c on the application confirmation screen 12a.

[0108] The user terminal 2 transmits the file name of the accepted template file 152 and the batch application information to the server 1 via the communication unit 23 (step S224). The control unit 11 of the server 1 receives the file name of the template file 152 and the batch application information transmitted from the user terminal 2 via the communication unit 13 (step S122). The control unit 11 reads out a layout from the corresponding template file 152 according to the file name of the received template file 152 (step S123).

[0109] The control unit 11 determines, based on the received batch application information, whether or not to batch apply the layout to all data files 153 (step S124). If the control unit 11 determines that the layout has not been batch applied to all data files 153 (NO in step S124), the process returns to step S116.

[0110] When the control unit 11 determines that the layout should be applied to all data files 153 at once (YES in step S124), the control unit 11 applies the layout to the tabular data included in each data file 153 (step S125). The control unit 11 transmits each data file 153 after the layout has been applied to the user terminal 2 via the communication unit 13 (step S126).

[0111] The control unit 21 of the user terminal 2 receives each data file 153 after the layout has been applied, transmitted from the server 1, via the communication unit 23 (step S225). The control unit 21 displays each data file 153 after the received layout has been applied on the display unit 25 (step S226). The control unit 21 then ends the process.

[0112] According to this embodiment, it is possible to accept template settings for the template file 152 in which a layout is applied to tabular data.

[0113] According to this embodiment, it is possible to apply the layout of the template file 152 set in the template to new tabular data.

[0114] According to this embodiment, it is possible to collectively apply the layout of the template file 152 set in the template to a plurality of tabular data.

[0115] According to this embodiment, it is possible to apply the layout of the template file 152 selected by the user to new tabular data.

[0116] <Variation 1> When template files 152 are stored in folder 151 and in the upper folder of folder 151, a process of applying the layout of template file 152 to new tabular data will be described.

[0117] 9 is an explanatory diagram illustrating the process of applying the layout of a template file to new tabular data in Modification 1. Note that the same reference numerals are used to designate the same contents as those in FIG. 5, and the description thereof will be omitted.

[0118] The user terminal 2 acquires a data file 153 including new tabular data (layout application target) from the storage unit 22. The user terminal 2 accepts designation of a folder (folder 151 and upper folder 151A of folder 151) in which a template file 152 to be applied to the new tabular data is stored. The folder exists in the mass storage unit 15 of the server 1.

[0119] Specifically, the user terminal 2 acquires the folder 151 in which the template file 152 is stored and the upper folder 151A of the folder 151 from the mass storage unit 15 of the server 1. The user terminal 2 displays the acquired folder 151 and upper folder 151A on the folder selection screen 13a. The user terminal 2 accepts the user's designation of the folder 151 or the upper folder 151A.

[0120] The template files 152 stored in folder 151 and upper folder 151A are different. For example, upper folder 151A is a folder that stores common experiment records, and folder 151 is a folder that stores experiment records by category. In this case, as an example, upper folder 151A may store "Common Experiment Record.XXX" and folder 151 may store "Single Crystal Sample Preparation.XXX".

[0121] The user terminal 2 transmits the acquired data file 153 and the folder information of the specified folder to the server 1. The folder information includes the path and name of the folder 151 or the upper folder 151A.

[0122] The server 1 receives the data file 153 and folder information transmitted from the user terminal 2. Based on the received folder information, the server 1 identifies the relevant folder (folder 151 or the parent folder 151A of the folder 151). The server 1 acquires list information of the template files 152 in the identified folder. Thereafter, the server 1 sets the acquired list information of the template files 152 in the template file selection field 12b on the application confirmation screen 12a.

[0123] The server 1 transmits an application confirmation screen 12a, in which list information of the template files 152 is set, to the user terminal 2. The server 1 accepts, via the user terminal 2, a selection of a template file 152 to which layout application is to be applied from among the multiple template files 152. The server 1 applies the layout of the accepted template file 152 to the received data file 153, similar to the processing in the first embodiment.

[0124] The flowchart of the process of applying the layout of the template file 152 stored in the folder 151 or in the upper folder 151A of the folder 151 to the data file 153 is the same as that shown in FIG. 7, and therefore the description thereof will be omitted.

[0125] As with the batch application process in embodiment 1, the layout of the template file 152 stored in the folder 151 or in the parent folder 151A of the folder 151 can be applied to tabular data contained in multiple data files 153 in a batch.

[0126] According to this embodiment, it is possible to apply the layout of the template file 152 in the folder 151 or the layout of the template file 152 in the upper folder 151A of the folder 151 to new tabular data.

[0127] (Embodiment 2) The second embodiment relates to a form in which the layout of a template file in which access rights are set in association with user identification information is applied to new tabular data. Note that a description of the content that overlaps with the first embodiment will be omitted.

[0128] Fig. 10 is a block diagram showing an example of the configuration of the server 1 in embodiment 2. Note that the same reference numerals are used to designate the same parts as in Fig. 2, and the description thereof will be omitted. The mass storage unit 15 includes an access authority DB 154. The access authority DB 154 stores user identification information, access authority for accessing the template file 152, and the like.

[0129] The user's identification information is information used to uniquely identify and recognize the user, and includes, for example, a user ID, a user name, an email address, a telephone number, or biometric information (for example, a fingerprint, face authentication, or iris authentication), etc. Note that, in this embodiment, an example will be described in which the user's identification information is a user ID, but the present invention can be similarly applied to other types of identification information.

[0130] Access rights are set in advance in association with user IDs in the template file 152. When applying the layout of the template file 152 to new tabular data, the server 1 acquires the access rights set in the template file 152 based on the user ID. The access rights will be described later.

[0131] Based on the acquired access authority, the server 1 determines whether or not the layout of the template file 152 can be applied to the new tabular data. If the server 1 determines that the layout of the template file 152 is applicable, the server 1 applies the layout of the template file 152 to the new tabular data.

[0132] 11 is an explanatory diagram showing an example of a record layout of the access permission DB 154. The access permission DB 154 includes a user ID column, a folder column, a template file name column, and an access permission column. The user ID column stores a unique user ID to identify each user.

[0133] The folder column stores the name of the folder 151 (for example, "Theme 1"). A folder 151 is set for each research theme or project. A single or multiple template files 152 are stored in the folder 151. The template file name column stores the file name of the template file 152. For example, the file name of the template file 152 is "Experiment 11.XXX".

[0134] The access authority column stores access authority set in the template file 152 in association with a user ID. The access authority column includes a reference column, a layout application column, a parse column, an edit column, and a management column. The reference column stores authority for a user to view the template file 152. The layout application column stores authority for a user to apply the layout of the template file 152 to new tabular data.

[0135] The parse column stores the authority for a user to arrange or change the layout of the template file 152. The edit column stores the authority for a user to edit the tabular data in the template file 152. The manage column stores the authority for managing the template file 152. The manage authority is the authority to set access rights such as referencing the template file 152, applying the layout, parsing, or editing.

[0136] Furthermore, the reference column, layout application column, parse column, edit column, and management column may each store "◯" if the user has the authority, and "X" if the user does not have the authority.

[0137] 11 illustrates examples of access rights such as "reference," "apply layout," "parse," "edit," and "manage," but the access rights are not limited to these. For example, the access rights may include "create" or "delete," etc.

[0138] The storage format of each DB described above is an example, and other storage formats may be used as long as the relationships between the data are maintained.

[0139] 12 is an explanatory diagram illustrating the process of applying the layout of a template file 152 for which access rights are set to new tabular data. A plurality of template files 152 are stored (contained) in a folder 151. As shown in the figure, "Experiment 11.XXX" and "Experiment 12.XXX" are stored in [Theme 1], and "Experiment 13.XXX" and "Experiment 14.XXX" are stored in [Theme 2].

[0140] When applying the layout of the template file 152 to new tabular data, the user terminal 2 acquires a user ID from the storage unit 22. The user terminal 2 transmits a data file 153 including the new tabular data and folder information of the specified target folder 151 to the server 1 in association with the acquired user ID. The server 1 receives the user ID, data file 153, and folder information transmitted from the user terminal 2.

[0141] The server 1 acquires list information of the template files 152 in the target folder 151 in accordance with the received folder information. The list information includes a list of the template files 152 included in the target folder 151, and the file names of each template file 152. The file name of the template file 152 is, for example, "Experiment 11.XXX."

[0142] Based on the file name of each template file 152, the server 1 acquires from the access permission DB 154 the access permission for each template file 152 for which the access permission is set in association with the user ID.

[0143] As shown in the figure, the user has access rights to "Experiment 11.XXX" in "Theme 1" with "Reference" and "Apply Layout" permissions, and to "Experiment 12.XXX" with "Reference" permissions only. The user has access rights to "Experiment 13.XXX" and "Experiment 14.XXX" in "Theme 2" with "Reference" permissions only.

[0144] The server 1 identifies a template file 152 in the folder 151 to which a layout can be applied, based on the access authority set in each template file 152 in association with the user ID. Specifically, the server 1 determines whether the layout of each template file 152 can be applied to new tabular data, based on the access authority set in each template file 152. If the server 1 determines that the layout of the template file 152 is applicable, it identifies the template file 152 in the folder 151 as a template file 152 to which a layout can be applied.

[0145] As shown in the figure, since the user has access rights to "Apply Layout" for "Experiment 11.XXX" in "Theme 1," "Experiment 11.XXX" within "Theme 1" is identified as a template file 152 to which layout can be applied within "Theme 1."

[0146] If there are multiple template files 152 to which the layout can be applied, the server 1 may accept, via the user terminal 2, a selection of a template file 152 by the user from the multiple identified template files 152.

[0147] If the template file 152 to which the layout can be applied does not exist, the server 1 may transmit to the user terminal 2 a message indicating that the template file 152 to which the layout can be applied does not exist.

[0148] The server 1 applies to the new tabular data the layout of the identified template file 152. Note that the layout application process is the same as in the first embodiment, and therefore a description thereof will be omitted.

[0149] 13 is a flowchart showing the processing procedure when applying a layout to tabular data in embodiment 2. Note that the same reference numerals are used to designate the same contents as those in FIG. 7, and the description thereof will be omitted.

[0150] The control unit 21 of the user terminal 2 acquires a user ID from the storage unit 22 (step S241). The control unit 21 executes the processes of steps S211 to S212. The control unit 21 transmits the data file 153 including the new tabular data and folder information (e.g., folder name) of the specified folder 151 to the server 1 via the communication unit 23, in association with the acquired user ID (step S242).

[0151] The control unit 11 of the server 1 receives the user ID, data file 153, and folder information transmitted from the user terminal 2 via the communication unit 13 (step S141). The control unit 11 executes the processes of steps S112 to S113. Based on the file names of each template file 152 obtained by the process of step S113, the control unit 11 acquires the access authority for each template file 152, for which access authority is set in association with the user ID, from the access authority DB 154 of the mass storage unit 15 (step S142).

[0152] The control unit 11 identifies template files 152 in the folder 151 to which the layout can be applied, based on the access authority set for each acquired template file 152 (step S143). The control unit 11 executes the processes of steps S118 to S120. The user terminal 2 executes the processes of steps S218 to S219.

[0153] As in the batch application process in the first embodiment, when a template file 152 to which a layout can be applied is identified in the folder 151, the layout of the template file 152 can be applied to multiple tabular data.

[0154] According to this embodiment, it is possible to apply the layout of a template file in which access rights are set in association with user identification information to new tabular data.

[0155] The embodiments disclosed herein are to be considered in all respects as illustrative and not restrictive. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.

[0156] 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 and all combinations, regardless of the reference format. Furthermore, the claims use a format in which a claim references two or more other claims (multiple claim format), but this is not limited to this. A multiple claim (multi-multi claim) that references at least one other multiple claim may also be used. [Explanation of symbols]

[0157] 1. Information processing device (server) 11 Control section 12 Storage section 13 Communications Department 14 Reading unit 15 Mass storage 151 folders 152 template files 153 Data Files 154 Access Permission DB 1a Portable storage media 1b semiconductor memory 1P control program 2. Information processing terminal (user terminal) 21 Control section 22 Storage section (local folder) 23 Communications Department 24 Input section 25 Display section 2P control program B Bus N Network

Claims

1. accepting template settings for a template file that applies a layout that defines relationships between elements of the tabular data to the tabular data; Apply the template file layout set in the template to new table format data A program that causes a computer to perform a process.

2. The template file set as a template is stored in the folder, Accepting a designation of the folder for new tabular data; Apply the layout of the template file in the specified folder to the new tabular data. The program according to claim 1.

3. Apply the layout of the template file set in the template to multiple table format data at once The program according to claim 1 or 2.

4. A template file set as a template is stored in each of the folder and the parent folder of the folder, Accept the designation of the folder, Accepts the selection of the layout of the template file in the specified folder or the layout of the template file in the parent folder of the folder, Applying the layout of the selected template file to the new tabular data The program according to claim 1.

5. The template file has access rights set in association with user identification information, Obtaining user identification information and new tabular data; The layout of the template file in which the access authority is set in association with the acquired user identification information is applied to the new tabular data. The program according to claim 1 or 2.

6. Accepts the selection of the target template file from multiple template files, Apply the layout of the selected template file to new tabular data The program according to claim 1 or 2.

7. accepting template settings for a template file that applies a layout that defines relationships between elements of the tabular data to the tabular data; Apply the template file layout set in the template to new table format data Information processing methods.

8. An information processing device including a control unit, The control unit accepting template settings for a template file that applies a layout that defines relationships between elements of the tabular data to the tabular data; Apply the template file layout set in the template to new table format data Information processing device.

Images