Control method of a data management system

Abstract

The present application aims to provide a data management system in which data possessed by a client device is collected to a server, a method of freely editing metadata extracted from data on the client device side, and a technique of transmitting data, metadata, and extraction rules of the metadata to the server side. A control method of the data management system of the present application has the following steps: an extraction rule describing a criterion for extracting metadata from data is edited by a client terminal that accesses a server that manages the data (see FIG. 1).

Description

Technical Field

[0001] This invention relates to a data management system. Background Technology

[0002] Systems that connect analytical devices, measuring devices, etc., to a network and collect data from these devices to a server are known. For example, Patent Document 1 describes a system that "manages analytical devices by database-izing measurement data, analytical condition data, etc., obtained through analysis. In such data management analytical systems, the most common type is the so-called stand-alone structure, but recently, it has been possible to share data obtained from the same or different types of analytical devices on a network using a network such as a LAN (Local Area Network)" (see paragraph 0002).

[0003] Existing technical documents

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent Application Publication No. 2005-156473 Summary of the Invention

[0006] The problem that the invention aims to solve

[0007] In prior art, such as Patent Document 1, when the server collects data from various analysis devices (clients) connected to the network, it is necessary to configure on the server side what kind of data to collect. Therefore, before using the system, it is necessary to configure based on the format of the data to be sent to the server. Furthermore, even if the user of the analysis device wants to change or add data to be sent to the server during system use, it is necessary to wait for configuration changes based on program changes or other modifications on the server side.

[0008] The present invention was made in view of the above-mentioned problems, and its object is to provide a technology that allows the client device to freely edit a method for extracting metadata from the data in a data management system that collects data from a client device into a server, and sends the data, metadata, and metadata extraction rules to the server.

[0009] Methods for solving problems

[0010] The control method of the data management system of the present invention includes the following steps: by accessing the client terminal of the server that manages the data, the extraction rules for the basis of extracting metadata from the data are edited and recorded.

[0011] Invention Effects

[0012] According to the control method of the data management system of the present invention, when data from a client device is collected into the data management system of a server, the method for extracting metadata from the data can be freely edited on the client device side, and the data, metadata, and metadata extraction rules are sent to the server side. Issues, structures, effects, etc., other than those described above, will be clarified through the following description of embodiments. Attached Figure Description

[0013] Figure 1 This is an overall structural diagram of the data management system 1000 in Implementation Method 1.

[0014] Figure 2 This is a conceptual diagram representing the process of extracting metadata from data.

[0015] Figure 3 This is a sequence diagram illustrating the steps for starting to utilize the data management system 1000.

[0016] Figure 4 This is a sequence diagram illustrating the steps of adding and modifying the extraction unit 211 and the extraction rule 212.

[0017] Figure 5 This is a flowchart illustrating the actions of the collection terminal 21.

[0018] Figure 6 This is a sequence diagram illustrating the processing of data on the search data management server 11.

[0019] Figure 7 This is a sequence diagram illustrating the processing of the results obtained by the application server 12 from the analysis data.

[0020] Figure 8 This is a structural diagram of the data management system 1000 in Implementation Method 2.

[0021] Figure 9 This is an example of a portal website page for downloading extraction section 211 and extraction rules 212.

[0022] Figure 10 This is a timing diagram illustrating the steps of the download extraction unit 211 and the extraction rule 212.

[0023] Figure 11 This is a structural diagram of the data management system 1000 in implementation method 4. Detailed Implementation

[0024] <Implementation Method 1>

[0025] <Overall Structure>

[0026] Figure 1This is an overall structural diagram of the data management system 1000 according to Embodiment 1 of the present invention. The data management system 1000 generally includes a server 1, a client-side terminal 2, a communication network 3, and a device 4. The communication network 3 is connected to the server 1 and the client-side terminal 2. Figure 1 In this design, one each of the data management server 11, application server 12, collection terminal 21, operation terminal 22, and device 4 is set up, but in reality, the number of these units is arbitrary.

[0027] <Component Description>

[0028] Server 1 includes a data management server 11 and an application server 12. The data management server 11 has a communication unit 110, a processing unit 111, and a storage unit 112. The application server 12 includes a communication unit 120, a processing unit 121, and a storage unit 122.

[0029] The client-side terminal 2 includes a collection terminal 21 and a work terminal 22. The collection terminal 21 has a communication unit 210, an extraction unit 211, an extraction rule 212, a collection unit 213, and a collection rule 214. The work terminal 22 has a communication unit 220, a processing unit 221, an input unit 222, and a display unit 223.

[0030] The data management server 11 consists of a server computer and is equipped with database management software, data processing software, and software that provides a portal website for users of the data management system 1000. The data management server 11 manages data (data collected from device 4) through the aforementioned software. Furthermore, it enables the data managed by the data management server 11 to collaborate with the application server 12, which acts as an external server.

[0031] Application server 12 consists of a server computer, which has database management software and data analysis software installed. Application server 12 uses the aforementioned software to perform data analysis and parsing.

[0032] The collection terminal 21 is a computer equipped with data collection software and data extraction software. Collection rules 214 define, for example, the categories of data to be collected. The collection unit 213 collects data from the device 4 according to the collection rules 214. Extraction rules 212 define the rules for extracting metadata from the data collected by the collection unit 213. The extraction unit 211 extracts metadata according to the extraction rules 212. The collection terminal 21 obtains the data and metadata through the software and transmits them to the data management server 11 via the communication network 3. In the collection terminal 21, the user can arbitrarily set the frequency of data collection.

[0033] The work terminal 22 is a computer with software installed for data processing.

[0034] Device 4 is a device for obtaining data from a sample, such as an analytical device or a measuring device.

[0035] User 5 is an individual who effectively utilizes the data management system 1000, such as an end user of device 4. User 5 can access the portal provided by the data management server 11 via collection terminal 21 and operating terminal 22. On the portal, user 5 can view the data managed by device 4.

[0036] <Explanation of Extraction Section 211 and Extraction Rule 212>

[0037] Figure 2 This is a conceptual diagram illustrating the process of extracting metadata from data. Information related to the data acquired by device 4, i.e., information that supplements or explains the data, is defined as metadata. For example, in the case of image data of a person, metadata is data describing the physical or facial features of that person. Metadata can also be any other data representing the attributes of the data.

[0038] like Figure 2 As shown, metadata is typically represented in a key-value format based on groups of names and values. As its format, it can use JSON (JavaScript Object Notation) or XML (eXtensible Markup Language).

[0039] The extraction unit 211 may be a plugin or an external subroutine with a predetermined API (Application Program Interface), or there may be multiple such subroutines. This API is common to all extraction units 211 and is configured to allow external modules to call the extraction unit 211 via this API. The extraction rule 212 is, for example, an attribute file that records the data category and the corresponding extraction unit 211 (a software module that performs the processing of extracting metadata from data of that data category). By referring to the extraction rule 212, the extraction unit 211 corresponding to the data category can be specified, and their operation settings can be changed.

[0040] In the data management system 1000, by enabling users on the client-side terminal to manage the extraction unit 211 and extraction rules 212, which were previously managed by the administrator of the data management system 1000, the metadata extracted from the data can be defined as arbitrary content at any time by the user.

[0041] <Service Utilization>

[0042] Figure 3This is a sequence diagram illustrating the steps for starting to utilize the data management system 1000. For ease of explanation, steps that were previously necessary but are no longer required in the data management system 1000 are also listed in the dashed boxes.

[0043] like Figure 3 As shown, previously, before using the data management system 1000, user 5 needed to create an extraction unit 211 for extracting metadata, and the administrator of the data management system 1000 needed to configure the extraction unit 211 on the server 1 side and define the extraction rules 212 (pre-set). In contrast, in embodiment 1, the user can create the extraction unit 211 and define the extraction rules 212 at any time, so the data management system 1000 can be used immediately without pre-setting.

[0044] <Additions and modifications to extraction section 211 and extraction rules 212>

[0045] Figure 4 This is a sequence diagram illustrating the steps of adding and modifying the extraction unit 211 and the extraction rule 212. For ease of explanation, procedures that were previously necessary but are no longer required in the data management system 1000 are also recorded in the dashed boxes.

[0046] like Figure 4 As shown, previously, when adding or changing metadata extracted from data, user 5 needed to create an extraction unit 211 and entrust the administrator of the data management system 1000 to reconfigure the extraction unit 211 and add or change the extraction rules 212. In contrast, in implementation method 1, user 5 can add or change the extraction unit 211 and extraction rules 212 at any time.

[0047] The data management server 11 discloses an interface (e.g., a Web API capable of issuing upload requests via HTTP) for uploading data collected from the device 4 and metadata extracted from that data from the client terminal 2 to the data management server 11. The client terminal 2 can upload data and metadata to the data management server 11 via this interface. The following steps S360-S370 can be implemented using this interface.

[0048] <Data Collection and Management Process>

[0049] Figure 5 This is a flowchart illustrating the actions of the data collection terminal 21. This flowchart, for example, is implemented at predetermined time intervals. The following description... Figure 5 Each step.

[0050] S310~S330: The collection terminal 21 communicates with the device 4, such as... Figure 5As shown, it is confirmed whether data matching collection rule 214 exists on device 4 (S310). If matching data exists, the data is collected according to collection rule 214 (S320). If no matching data exists, exception handling is performed and the flowchart ends (S330).

[0051] S340 and S370: The collection terminal 21 checks whether there is data that matches extraction rule 212 in the data collected in S320 (S340). If there is no matching data, the collected data itself is sent to the data management server 11 (S370). The data management server 11 stores the data in the storage unit 112.

[0052] S350~S360: If data that matches extraction rule 212 exists, the collection terminal 21 uses the extraction unit 211 specified by extraction rule 212 to extract metadata from the data (S350). The collection terminal 21 sends the collected data, the extracted metadata, and the correspondence information indicating the correspondence between the data and the metadata to the data management server 11 (S360).

[0053] The data management server 11, which receives data, metadata, and corresponding relationship information through the above process, stores the data and metadata in the storage unit 112, and stores the corresponding relationship information in the storage unit 112, thereby associating the data with the metadata.

[0054] <Searching the collected files>

[0055] Figure 6 This is a sequence diagram illustrating the processing of data on the data management server 11. User 5, in order to search for desired data (data collected from device 4) on the data management server 11, specifies search criteria such as keywords. The data management server 11 searches for the specified data by querying metadata using the search criteria. The following explains... Figure 6 Each step.

[0056] When user 5 inputs user information (user ID and other authentication information) into the work terminal 22, the work terminal 22 sends the input user information to the data management server 11. Upon receiving the user information, the data management server 11 returns data corresponding to the user information (data that the user has viewing permissions for). The work terminal 22 then displays a portal website based on this data.

[0057] User 5 enters keywords as search criteria on the portal website. The operating terminal 22 sends the entered keywords to the data management server 11. The data management server 11 searches for metadata matching the entered keywords and returns the associated data to the operating terminal 22. The correspondence between data and metadata can be determined based on the correspondence information in S360. The operating terminal 22 displays the search results on the portal website. This search result may be, for example, a list of data associated with metadata that meets the conditions specified by the entered keywords.

[0058] <Utilization of Analysis Results in Application Servers>

[0059] Figure 7 This is a sequence diagram illustrating the processing of data obtained from the analysis of application server 12. This sequence diagram uses, for example, [the following text is incomplete and likely refers to a different sequence diagram]. Figure 6 The portal website described in the document is used for implementation. User 5 instructs application server 12 to perform analysis. Application server 12, following this instruction, analyzes and processes the data collected from device 4. The following description... Figure 7 Each step.

[0060] When user 5 instructs on the user portal to launch an analysis application for analyzing data and metadata, job terminal 22 sends an analysis application launch command to data management server 11. Data management server 11 then communicates with application server 12 to launch the analysis application.

[0061] Application server 12 sends data from user 5 managed by the analytics application to job terminal 22. Job terminal 22 displays the analytics application's website. Application server 12 can, for example, configure the website to display a user interface that shows only a list of data that user 5 has access to.

[0062] User 5 on the application website, for example through [contact information] Figure 6 Follow the same steps to search for the desired data.

[0063] User 5 issues an analysis command via the website of the analysis application. Job terminal 22 sends the analysis command to application server 12. Application server 12 retrieves the required data from data management server 11 based on the analysis command and performs analysis. Application server 12 sends the analysis results to job terminal 22. Job terminal 22 displays the analysis results. Examples of analysis commands and the analysis processing based on them will be described later.

[0064] User 5 indicates that the data to be analyzed may not be data stored on the data management server 11. In this case, for example, the analysis application can send the data input to the job terminal 22 to the collection terminal 21, the extraction unit 211 of the collection terminal 21 can extract metadata, and the analysis application can send this metadata as a search query to the data management server 11. In this case, for example, the data management server 11 sends the data in the storage unit 112 that meets the conditions of the received metadata to the job terminal 22.

[0065] <Example 1: Summary>

[0066] In the data management system 1000 of Embodiment 1, user 5 can specify the metadata to be used when searching data collected from device 4 by editing extraction rules 212, according to user 5's wishes. Thus, user 5 can include desired data in search results, for example, when searching data held by data management server 11.

[0067] <Implementation Method 2>

[0068] Figure 8 This is a structural diagram of the data management system 1000 according to Embodiment 2 of the present invention. In Embodiment 1, a structural example was described in which one each of the data management server 11, application server 12, collection terminal 21, operation terminal 22, and device 4 is provided, but the number of these devices is arbitrary. In Embodiment 2, there are multiple servers 1, client-side terminals 2, devices 4, and users 5.

[0069] Each server 1 includes one or more data management servers 11 and one or more application servers 12. Each client-side terminal 2 includes one or more collection terminals 21 and one or more operation terminals 22. Each client-side terminal 2 is connected to one or more devices 4 and one or more users 5. Figure 8 In the structural example shown, the data management system 1000 can also perform the same operations as in implementation method 1.

[0070] <Implementation Method 3>

[0071] In Embodiment 1, an example was described where user 5 creates extraction unit 211 and extraction rules 212 and configures them on collection terminal 21. Extraction unit 211 and extraction rules 212 can be pre-configured on, for example, server 1 and can be downloaded to collection terminal 21. In Embodiment 3 of the present invention, a structural example is described. The structure other than downloading extraction unit 211 and extraction rules 212 is the same as in Embodiments 1-2.

[0072] Figure 9This is an example of a portal page for downloading extraction section 211 and extraction rules 212. This portal website can, for example, be provided on data management server 11. User 5 accesses the portal website using collection terminal 21. Data management server 11 sends data to collection terminal 21 such as... Figure 9 The page shown (download interface).

[0073] This page is configured to allow users to select any one of one extraction units 211 (extraction modules) according to the data categories managed by the data management server 11. Users select the extraction unit 211 that performs metadata extraction processing based on the data category. Each extraction unit 211 is pre-configured on the data management server 11, and the data management server 11 displays a list of extraction units 211 maintained on this page. When the download icon (downward arrow) next to the name of an extraction unit 211 is clicked, the collection terminal 21 downloads and saves that extraction unit 211 from the data management server 11.

[0074] After user 5 makes their selection, they click the download icon next to "Setting Extraction Rules" at the top of the page. The collection terminal 21 then notifies the data management server 11 of the correspondence between the data category selected by the user on the page and the extraction unit 211. The data management server 11 generates an extraction rule 212 describing this correspondence and sends it to the collection terminal 21. The collection terminal 21 stores the extraction rule 212.

[0075] Figure 10 This is a sequence diagram illustrating the steps of downloading and extracting unit 211 and extracting rule 212. User 5 accesses the portal website via collection terminal 21, selects the extraction unit 211 provided by data management server 11 according to data category, and changes the definition of extraction rule 212. The selected extraction unit 211 and the defined extraction rule 212 can be downloaded to collection terminal 21.

[0076] <Implementation Method 4>

[0077] In Embodiment 1, an example was described where user 5 creates extraction unit 211 and extraction rule 212 and configures them on collection terminal 21. Extraction unit 211 and extraction rule 212 can also be configured on server 1 (e.g., data management server 11), and user 5 can modify extraction unit 211 and extraction rule 212 on server 1. In Embodiment 4 of the present invention, a structural example is described.

[0078] Figure 11This is a structural diagram of the data management system 1000 according to Embodiment 4. The extraction unit 211 and extraction rules 212 are configured on the data management server 11. The data management server 11 exposes interfaces for modifying the extraction unit 211 and extraction rules 212. User 5 issues a request to the data management server 11 to modify the extraction unit 211 and extraction rules 212 via a client-side terminal 2 (e.g., a collection terminal 21). The data management server 11 modifies them according to the request.

[0079] The interface for modifying the extraction unit 211 is configured, for example, to upload a new extraction unit 211 from the client-side terminal 2 to the data management server 11. Similarly, the interface for modifying the extraction rule 212 is configured to upload a new extraction rule 212. Alternatively, it can be configured to allow editing of the extraction rule 212 on the data management server 11 from the client-side terminal 2.

[0080] The interface for editing extraction rule 212 is configured to define the correspondence between data categories and extraction units 211 that extract metadata based on those data categories. For example, with... Figure 9 Similarly, it can be configured with a screen interface (editing interface) that allows selection of the extraction unit 211 corresponding to each data category from preset options. Other arbitrary editing methods can also be used. The client-side terminal 2 sends the extraction rules edited on the editing interface to the data management server 11, and the data management server 11 stores them as extraction rules 212.

[0081] Data management server 11 extracts metadata from the data using extraction unit 211 according to the rules defined in extraction rule 212. Other structures are the same as in implementation method 1.

[0082] In embodiment 4, the extraction unit 211 and the extraction rule 212 are configured on the data management server 11, which is useful in that multiple client-side terminals 2 can share their functions.

[0083] <Regarding variations of the present invention>

[0084] This invention is not limited to the embodiments described above, but includes various modifications. For example, the embodiments described above are those that have been explained in detail for ease of understanding of this disclosure, and are not necessarily limited to having all the structures described. Furthermore, a portion of the structure of one embodiment can be replaced with the structure of another embodiment, and it is also possible to add structures of other embodiments to the structure of one embodiment. Additionally, regarding a portion of the structure of each embodiment, other structures can be added, deleted, or replaced.

[0085] In the above implementation, as an example, when device 4 is a webcam, the data managed by data management server 11 is the image data captured by device 4, and the metadata is the facial and body feature data of the person captured in the image data. The analysis application implemented by application server 12 determines the person based on the facial and body feature data in the image data. Figure 7 The analysis command in the image is a request to determine the person within the image selected by user 5.

[0086] In the above implementation, as an example, when the device 4 is an electron microscope, the data managed by the data management server 11 is the sample image, the metadata is the height difference of the sample surface, and the analysis application creates a 3D model of the sample based on the height difference of the sample surface.

[0087] In the above implementation, as an example, when device 4 is an analysis device, the data managed by data management server 11 is text describing analysis results and conditions, the metadata is the value of the analysis result extracted from the text with arbitrary keywords, and the analysis application groups the analysis results, conditions, and the value of the analysis result.

[0088] In the above embodiments, the functional units such as the extraction unit 211, the collection unit 213, and the processing units provided by the server 1 and the client-side terminal 2 can be constructed by hardware such as circuit devices that implement these functions, or by software that implements these functions being executed by a computing device such as a CPU (Central Processing Unit).

[0089] Symbol Explanation

[0090] 1000: Data Management System

[0091] 11: Data Management Server

[0092] 12: Application Server

[0093] 21: Collection Terminal

[0094] 211: Extraction Department

[0095] 212: Extraction Rules

[0096] 213: Collection Department

[0097] 214: Collection Rules.

Claims

1. A control method for a data management system, wherein the data management system manages data held by a server collection device, characterized in that, The method comprises the following steps: Obtain extraction rules, which describe a benchmark for extracting metadata representing attributes of the data from the data; The extraction rules are edited by the client terminal accessing the server; Extract the metadata from the data according to the edited extraction rules; The extracted metadata is stored on the server; as well as Using the metadata stored on the server, search for the data maintained by the server.

2. The control method according to claim 1, characterized in that, The server discloses an interface for the client terminal to access the server when receiving the metadata from the client terminal. In the step of storing the metadata on the server, the client terminal accesses the server via the interface and sends the metadata to the server via the interface. In the step of storing the metadata on the server, the server receives the metadata from the client terminal via the interface.

3. The control method according to claim 1, characterized in that, In the step of storing the metadata on the server, the client terminal sends the correspondence information indicating the correspondence between the extracted metadata and the data, along with the extracted metadata, to the server. In the step of storing the metadata on the server, the server stores the correspondence information. In the step of searching the data, the server searches the data held by the server based on the metadata and the correspondence information.

4. The control method according to claim 1, characterized in that, The control method further includes the step of the client terminal collecting the data from the device. In the step of storing the metadata on the server, the client terminal sends the data collected from the device and the metadata together to the server. In the step of storing the metadata on the server, the server stores the data and the metadata together on the server.

5. The control method according to claim 1, characterized in that, In the step of extracting the metadata from the data, the client terminal extracts the metadata from the data according to the edited extraction rules.

6. The control method according to claim 1, characterized in that, The control method also includes the step of the server analyzing the data. The client terminal sends a request to the server, instructing that the analysis be performed on the data retrieved during the data searching step. The server performs the analysis based on the request received from the client terminal and sends the results to the client terminal.

7. The control method according to claim 1, characterized in that, The server stores an extraction module that performs the processing of extracting the metadata from the data, and discloses a download interface for downloading the extraction module from the server. The client terminal downloads the extraction module from the server via the download interface. In the step of extracting the metadata from the data, the client terminal uses the extraction module to extract the metadata from the data.

8. The control method according to claim 1, characterized in that, The server exposes a download interface for downloading the extraction rules from the server. The client terminal downloads the extraction rules from the server via the download interface. In the step of extracting the metadata from the data, the client terminal uses the extraction rules to extract the metadata from the data.

9. The control method according to claim 1, characterized in that, The server maintains the extraction rules. The server exposes an editing interface for the client terminal to access the server when the client terminal edits the extraction rules. In the step of editing the extraction rules, the client terminal accesses the server via the editing interface and edits the extraction rules via the editing interface. In the step of extracting the metadata, the server extracts the metadata from the data according to the extraction rules edited via the editing interface.

10. The control method according to claim 9, characterized in that, The editing interface is configured to allow users to select preset values ​​for the extraction rules from options based on the category of the data. In the step of editing the extraction rules, the client terminal edits the extraction rules by sending the result of selecting the preset value to the server.

Images