Point management device, point management method, program, and data warehouse system

Abstract

To facilitate the use of data by users and data management by database administrators, in a data warehouse system to which a system is applied.SOLUTION: A point management unit (40) includes: an acquisition unit (41) which acquires management activity information indicating management activities performed by an administrator on a database included in a data warehouse having a plurality of databases, and use activity information indicating use activities performed by a user on the database; a calculation unit (42) which calculates first points according to the management activities on the basis of the management activity information, and calculates second points according to the use activities on the basis of the use activity information; and an offering unit (43A) which offers the first points according to the management activities on the database to the user of the database, and offers the second points according to the use activities on the database to the administrator of the database.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a point management device that is applied to a data warehouse system. [Background technology]

[0002] Centralized data management, in which only a data manager manages the data warehouse, is a commonly known system for aggregating large amounts of data. However, if only a specific administrator prepares and manages the database too much, it is difficult for the database to reflect the needs of users, and it may not necessarily be the database that users want to use.

[0003] For example, Patent Document 1 discloses a system that presents preparation methods according to various purposes and uses when using data collected from multiple business systems. However, this system does not address advance data management, such as enriching the information in the data catalog required to identify data that should be collected or target data.

[0004] Non-Patent Document 1 describes that a data catalog that can search a large amount of metadata all at once enables highly convenient data searches for users. Non-Patent Document 2 describes that preprocessing on the integrated database side is important in order to search and utilize the diverse data stored in the integrated database. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2019-185582 [Non-patent literature]

[0006] [Non-Patent Document 1] Shinsuke Ito et al., ESTRELA November 2019 (No. 308) 8-14 [Non-patent document 2] Yuuki Wakuta et al., AI and Data Science Papers Vol. 1 (2020) J1 No. 25-34 Summary of the Invention [Problem to be solved by the invention]

[0007] A data warehouse system is required to be a system that allows users to obtain the data they need and is managed in such a way.

[0008] Traditional centralized data management has its limitations in making it easier to utilize vast amounts of data and creating a database that is more suitable for users. Therefore, it is necessary to realize a decentralized data community in which users themselves can participate in data management as database administrators and autonomously collect, manage, and use data.

[0009] One aspect of the present invention aims to realize a points management device or the like that can promote data usage by users and data management by database administrators in a data warehouse system to which it is applied. [Means for solving the problem]

[0010] In order to solve the above problems, a point management device according to one embodiment of the present invention comprises an acquisition unit that acquires management activity information indicating management activities performed by an administrator on a database included in a data warehouse having multiple databases, and usage activity information indicating usage activities performed by users on the database, a calculation unit that calculates first points corresponding to the management activity based on the management activity information and calculates second points corresponding to the usage activity based on the usage activity information, and an assignment unit that assigns the first points corresponding to the management activity on the database to the user of the database and assigns the second points corresponding to the usage activity on the database to the administrator of the database.

[0011] In order to solve the above problem, a point management method according to one embodiment of the present invention includes an acquisition step of acquiring management activity information indicating management activities performed by an administrator on a database included in a data warehouse having multiple databases, and usage activity information indicating usage activities performed by users on the database; a calculation step of calculating first points corresponding to the management activity based on the management activity information and calculating second points corresponding to the usage activity based on the usage activity information; and an assignment step of assigning the first points corresponding to the management activity on the database to the user of the database, and assigning the second points corresponding to the usage activity on the database to the administrator of the database.

[0012] In order to solve the above problems, a data warehouse system according to one embodiment of the present invention comprises a data warehouse having multiple databases, and a point management device that (1) acquires management activity information indicating management activities performed by an administrator on databases included in the data warehouse and usage activity information indicating usage activities performed by users on the databases, (2) calculates first points corresponding to the management activities based on the management activity information, and calculates second points corresponding to the usage activities based on the usage activity information, and (3) grants the first points corresponding to the management activities on the database to the user of the database, and grants the second points corresponding to the usage activities on the database to the administrator of the database.

[0013] The point management device according to each aspect of the present invention may be realized by a computer, in which case the control program for the point management device that realizes the point management device on a computer by causing the computer to operate as each part (software element) of the point management device, and the computer-readable recording medium on which it is recorded, also fall within the scope of the present invention. [Effects of the Invention]

[0014] According to one aspect of the present invention, in a data warehouse system to which the present invention is applied, data utilization by users and data management by database administrators can be promoted. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a conceptual diagram showing an overview of a data warehouse system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing the configuration of a main part of the data warehouse system. [Figure 3] FIG. 10 is a block diagram showing details of an activity reception unit. [Figure 4] FIG. 10 is a diagram showing data stored as metadata. [Figure 5] 10 is a diagram showing an example of usage activity information that a usage activity information acquisition unit stores in a storage unit. FIG. [Figure 6] 10 is a diagram illustrating an example of management activity information that a management activity information acquisition unit stores in a storage unit. FIG. [Figure 7] FIG. 2 is a block diagram showing the configuration of a points management unit. [Figure 8] FIG. 10 is a diagram showing an example of user point data stored in a storage unit by a point trading unit. [Figure 9] FIG. 10 is a diagram showing an example of point data of a database administrator that the point trading unit stores in the storage unit. [Figure 10] This is a screen displayed on an information terminal carried by a user and a database administrator, and shows point information relating to the user and the database administrator. [Figure 11] 10 is a flowchart showing an example of the flow of processing performed by a point management unit. [Figure 12] 10 is a flowchart illustrating an example of a flow of processing performed by a calculation unit. DETAILED DESCRIPTION OF THE INVENTION

[0016] [Embodiment 1] An embodiment of the present invention will be described in detail below. First, an overview of a data warehouse system 1 in this embodiment will be described. FIG. 1 is a conceptual diagram showing an overview of the data warehouse system 1 in this embodiment. As shown in FIG. 1, the data warehouse system 1 has multiple databases DB that can be used by users U of the data warehouse system 1. The operation of the data warehouse system 1 is managed by an operations manager MA. The operations manager MA provides and manages the data warehouse system 1, but does not directly manage the databases DB. Various data are stored in the databases DB.

[0017] Each of the multiple databases DB may be a database DB brought into the data warehouse system 1 by a user U of the respective database, and the user U who brought the database DB may become a database administrator DA (administrator) who manages the database DB. The data stored in the data warehouse system 1 is managed by a decentralized autonomous organization (DAO) type of data management. A database administrator DA is a person who manages the data in the database and information related to the data. The data warehouse system 1 supports the formation of a decentralized autonomous organization through point management.

[0018] A user U of the data warehouse system 1 uses the server 20 to search for the database DB in which the data he or she wants to use is stored, and submits a data use request to the database administrator DA who manages the database DB via the server 20. Once the data use request is approved by an approver such as the database administrator DA, the user U becomes able to use the data.

[0019] A user U checks whether desired data is in the data warehouse 10 by searching the metadata 60 of the data stored in the data warehouse 10. The metadata 60 is stored in the server 20. If the desired data is found in the data warehouse 10, the user U submits a usage request to the database administrator DA of the database DB in which the data is stored via the server 20. Until the data usage request is approved by the database administrator DA and the data becomes available for use, the user U can only check the metadata 60 and cannot check the data stored in the database DB.

[0020] In the data warehouse system 1, metadata 60 of the data stored in the database DB includes information on the usage activity of the user U for the database DB and the management activity of the database DB by the database administrator DA. Details will be described later.

[0021] The metadata 60 includes data definition information stored as metadata in a general database DB. In addition to the data definition information, the metadata 60 also includes information created based on the activities of the database administrator DA or the user U. Details of this information will be described later.

[0022] In the data warehouse system 1, the database administrator DA can recruit supporters S from users U of the data warehouse system 1 to support the management of the database DB that the database administrator DA manages, and users U who apply in response to the recruitment can be selected as supporters S. The supporters S are experts who have knowledge of the data stored in the database DB, and support the database administrator DA in managing the database DB. For example, the supporters S support the database administrator DA in editing, such as supplementing and adding, the metadata 60 of the data stored in the database DB. The supporters S may support multiple databases DB.

[0023] (Data Warehouse System 1 Configuration) Next, we will explain the details of the configuration of the data warehouse system 1. Fig. 2 is a block diagram showing the configuration of the main parts of the data warehouse system 1. As shown in Fig. 2, the data warehouse system 1 includes a data warehouse 10 having a plurality of databases DB, a plurality of information terminals 11, and a server 20.

[0024] The information terminal 11 is an information terminal owned by a plurality of database administrators DA or users U. The information terminal 11 is capable of communicating with the server 20. The database administrator DA uses the information terminal 11 to manage the database DB that he or she manages. For example, the database administrator DA uses the information terminal 11 to edit data definition information 61 of the data stored in the database DB. The user U uses the information terminal 11 to apply for use of the data stored in the database DB and to report the results of data use, which will be described later.

[0025] The server 20 manages the data warehouse system 1. The server 20 includes a control unit 30, a storage unit 50, an input unit 21 that receives input to the server 20, and a display unit 22 that displays various types of information.

[0026] As shown in Figure 2, the control unit 30 includes an activity receiving unit 31, a metadata collection unit 32, a management activity support unit 33, a usage activity information collection unit 34, a management activity information collection unit 35, and a point management unit 40.

[0027] The activity receiving unit 31 receives usage activities and management activities regarding the data stored in the data warehouse 10 from the user U and the database administrator DA. Fig. 3 is a block diagram showing details of the activity receiving unit 31. As shown in Fig. 3, the activity receiving unit 31 includes a search receiving unit 31A, a data use application receiving unit 31B, a data use approval receiving unit 31C, a data use result report receiving unit 31D, a database request receiving unit 31E, a database request approval receiving unit 31F, a tagging receiving unit 31G, a comment receiving unit 31H, a reaction receiving unit 31I, a quality report receiving unit 31J, an improvement contact receiving unit 31K, and an annotation editing receiving unit 31L.

[0028] The search reception unit 31A receives a search request for data stored in the data warehouse 10 from the user U. As described above, the user U identifies desired data by searching the metadata 60 of the data stored in the data warehouse 10. The metadata 60 is stored in the storage unit 50 of the server 20. FIG. 4 is a diagram showing data stored as the metadata 60. As shown in FIG. 4, the metadata 60 includes various information recorded by the database administrator DA or the user U in addition to data definition information 61.

[0029] The data use application receiving unit 31B receives a data use application from a user U. When the data use application receiving unit 31B receives a data use application, it notifies the database administrator DA of the database DB in which the data is stored that a use application has been received.

[0030] The data use approval receiving unit 31C receives approval to use data from the database administrator DA. When the data use approval receiving unit 31C receives approval to use data, it notifies the user U that approval has been granted. This allows the user U to use the data.

[0031] The data usage result report receiving unit 31D receives a data usage result report from the user U. The data usage result report includes information about how the user U used the data. Specifically, the data usage result report includes information such as the purpose of using the data, the results obtained using the data, and what other data was used.

[0032] The database request receiving unit 31E receives a database request from a user U. The database request is, for example, a request for a new database to the data warehouse 10, a request for new data to an existing database DB, etc. The user U makes a database request using points.

[0033] The database request support receiving unit 31F receives, from a user U, support for a database request made by another user U. The user U uses points to support the database request.

[0034] The tagging reception unit 31G receives tagging of the database DB from the user U and the database administrator DA.

[0035] The comment receiving unit 31H receives comments on the database DB from the user U and the database administrator DA.

[0036] The reaction receiving unit 31I receives, from the user U, reactions to the database DB or reactions to comments on the database DB stored as metadata 60. The reactions include positive reactions such as "like" or "heart" and negative reactions such as "sad."

[0037] The quality report receiving unit 31J receives from the user U a report on the quality of the data used.

[0038] The improvement notification receiving unit 31K receives a notification of an improvement to the database DB from the database administrator DA.

[0039] The annotation edit receiving unit 31L receives an edit of the annotation in the database DB from the database administrator DA.

[0040] The metadata collection unit 32 collects metadata 60 from the data warehouse 10 and the activity reception unit 31. The metadata collection unit 32 stores the collected metadata 60 in the storage unit 50. For example, the metadata collection unit 32 collects data definition information 61 for each piece of data stored in the database DB from the data warehouse 10 and stores it in the storage unit 50 as metadata 60.

[0041] Furthermore, the metadata collection unit 32 collects information relating to the activities of the user U and the database administrator DA received by the activity reception unit 31 as metadata 60.

[0042] As an example, when the search receiving unit 31A receives a search request from a user U for data stored in the data warehouse 10, the metadata collection unit 32 stores a log of the search (hereinafter referred to as a search log 62) in the storage unit 50 as metadata 60. By storing the search log 62 as metadata 60, when another user U performs a search, the control unit 30 can refer to the search log 62 and display similar search results. This allows the other user U to perform searches efficiently.

[0043] Furthermore, when the data use application receiving unit 31B receives a data use application from a user U, the metadata collection unit 32 stores data use application information 63 (e.g., the ID of the requesting user U, the application date and time, the data to be used, the project name, the purpose of use, the method of use, the start date of use, the end date of use, the joint user ID, the data storage location, and comments) entered in the use application as metadata 60 in the storage unit 50. When the data use approval receiving unit 31C receives approval for data use from the database administrator DA, the metadata collection unit 32 stores the approval result of the use application as metadata 60 in the storage unit 50. The approval result may also include a rejection if data that does not match the purpose is selected. Storing the data use application information 63 as metadata 60 allows other users U to refer to the data use application information 63 when searching. This allows for highly accurate determination of whether other users U want to use the data.

[0044] Furthermore, when the data usage result report receiving unit 31D receives a data usage result report 64 from a user U, the metadata collection unit 32 stores the data usage result report 64 (for example, the ID of the user U who made the report, report summary, report details, results, issues, supplementary data, data usage environment, source code storage location, temporary stored data deletion confirmation flag, terms of use compliance confirmation flag, other report destinations, future plans, comments, etc.) in the storage unit 50 as metadata 60. Storing the data usage result report 64 as metadata 60 allows other users U to refer to the data usage result report 64 when searching. This makes it possible to determine with high accuracy whether the other users U want to use the data.

[0045] Furthermore, when the database request receiving unit 31E receives a database request 65 from the user U, the metadata collection unit 32 stores the contents of the database request 65 as metadata 60 in the storage unit 50. Storing the database request 65 as metadata 60 enables the database administrator DA to grasp the data that the user U desires.

[0046] Furthermore, the metadata collection unit 32 collects the number of support for the database request accepted by the database request support acceptance unit 31F for each database DB (hereinafter referred to as the database request support number 66), and stores it in the storage unit 50 as metadata 60. Storing the database request support number 66 as metadata 60 enables the database administrator DA to grasp the data that the user U desires.

[0047] Furthermore, when the tagging receiving unit 31G receives tagging of the database DB from the user U or the database administrator DA, the metadata collection unit 32 stores the tag 67 as metadata 60 in the storage unit 50. By storing the tag 67 as metadata 60, other users U can refer to the tag 67 when performing a search. This allows other users U to perform searches efficiently.

[0048] Furthermore, when the comment receiving unit 31H receives a comment 68 to the database DB from the user U or the database administrator DA, the metadata collection unit 32 stores the comment 68 as metadata 60 in the storage unit 50. By storing the comment 68 as metadata 60, other users U can refer to the comment 68 when performing a search. This allows other users U to perform searches efficiently. Furthermore, communication between the user U and the database administrator DA can be carried out via the comment 68 in the metadata 60.

[0049] Furthermore, the metadata collection unit 32 collects reactions (hereinafter referred to as reactions 69) from the user U to the database DB or comments received by the reaction receiving unit 31I, and stores them as metadata 60 in the storage unit 50. Storing the reactions 69 as metadata 60 makes it possible to grasp the user U's level of understanding of the data and / or their evaluation of the ease of use of the data. It also makes it possible to grasp the management activities that the database administrator DA should perform and their evaluation of the reply comments.

[0050] Furthermore, when the quality report receiving unit 31J receives a quality report on the data used from a user U, the metadata collection unit 32 stores the data quality evaluation 70 described in the quality report as metadata 60 in the storage unit 50. Storing the data quality evaluation 70 as metadata 60 allows other users U to refer to the data quality evaluation 70 when performing a search. This allows other users U to use the data after understanding its quality. Furthermore, the database administrator DA can understand which data needs to be improved in quality.

[0051] Furthermore, when the improvement contact receiving unit 31K receives a contact for improving the database DB from the database administrator DA, the metadata collection unit 32 stores the improvement progress 71 in the storage unit 50 as metadata 60. By storing the improvement progress 71 as metadata 60, other users U can refer to the improvement progress 71 when performing a search. This allows other users U to identify data of higher quality.

[0052] Furthermore, when the annotation edit receiving unit 31L receives an edit of an annotation in the database DB from the database administrator DA, the metadata collection unit 32 stores the edited annotation 72 as metadata 60 in the storage unit 50. By storing the annotation 72 as metadata 60, other users U can refer to the annotation 72 when performing a search. This allows other users U to perform searches efficiently.

[0053] The management activity support unit 33 supports management activities of the database DB. The management activity support unit 33 includes a manager appointment support unit 33A and a supporter appointment support unit 33B.

[0054] The administrator appointment support unit 33A supports the appointment of a database administrator DA for a database DB. Specifically, when a new database DB is brought into the data warehouse 10, or when a database administrator DA for an existing database DB is unavailable, the administrator appointment support unit 33A solicits a database administrator DA for that database DB from the user U. When a user U applies in response to the solicitation, the administrator appointment support unit 33A appoints the user U as a database administrator DA. The administrator appointment support unit 33A stores information about the user U appointed as a database administrator DA as administrator information 51 in the storage unit 50. When the user U is appointed as a database administrator DA, the user U is awarded predetermined points.

[0055] The supporter appointment support unit 33B supports the appointment of a supporter S in the database DB. For example, when a database administrator DA requests a user U to take up the position of supporter S, the supporter appointment support unit 33B requests the user U to take up the position of supporter S. The database administrator DA uses points to request the user U to take up the position of supporter S. When the user U accepts the request, the supporter appointment support unit 33B assigns the user U as a supporter S. The supporter appointment support unit 33B stores information about the user U who has been appointed as a supporter S in the memory unit 50 as supporter information 52. Furthermore, when the supporter appointment support unit 33B receives a message from the user U that he or she will voluntarily become a supporter S in the database DB, the supporter appointment support unit 33B assigns the user U as a supporter S and stores information about the user U who has been appointed as a supporter S in the memory unit 50 as supporter information 52. When the user U is appointed as a supporter S, a predetermined number of points are awarded to the user U.

[0056] The usage activity information collection unit 34 collects, for each database DB, usage activity information 53 indicating the usage activity received from the user U by the activity reception unit 31, in other words, the usage activity performed by the user U with respect to the database DB. The usage activity information collection unit 34 may collect, for each data item, usage activity information 53 indicating the usage activity performed by the user U with respect to the data. The usage activity information collection unit 34 stores the collected usage activity information 53 in the storage unit 50. FIG. 5 is a diagram showing an example of the usage activity information 53 stored in the storage unit 50 by the usage activity information collection unit 34. As shown in FIG. 5, the usage activity information collection unit 34 may store, as the usage activity information 53, a table linking the date the usage activity was performed, the database ID on which the usage activity was performed, the ID of the user U who performed the usage activity, and a usage activity ID indicating the type of usage activity in the storage unit 50. Furthermore, the usage activity information collection unit 34 may store, as the usage activity information 53, the table ID of each table in the storage unit 50.

[0057] The management activity information collecting unit 35 collects management activity information 54 indicating the management activities received by the activity receiving unit 31 from the database administrator DA, in other words, the management activities performed by the database administrator DA on the database DB. The management activity information collecting unit 35 may collect, for each data item, management activity information 54 indicating the management activities performed by the user U on the data. The management activity information collecting unit 35 stores the collected management activity information 54 in the storage unit 50. FIG. 6 is a diagram showing an example of the management activity information 54 stored in the storage unit 50 by the management activity information collecting unit 35. As shown in FIG. 6, the management activity information collecting unit 35 may store, as the management activity information 54, a table linking the date the management activity was performed, the database ID on which the management activity was performed, the ID of the database administrator DA who performed the management activity, and a management activity ID indicating the type of management activity in the storage unit 50. Furthermore, the management activity information collecting unit 35 may store, as the management activity information 54, the table ID of each table in the storage unit 50.

[0058] The point management unit 40 manages points granted to the database administrator DA and the user U in the data warehouse system 1. FIG. 7 is a block diagram showing the configuration of the point management unit 40. As shown in FIG. 7, the point management unit 40 includes an acquisition unit 41, a calculation unit 42, and a point trading unit 43.

[0059] The acquisition unit 41 acquires the management activity information 54 and the usage activity information 53 from the storage unit 50 .

[0060] The calculation unit 42 calculates points (hereinafter referred to as first points) according to the management activity performed by the database administrator DA based on the management activity information 54 acquired by the acquisition unit 41, and points (hereinafter referred to as second points) according to the usage activity performed by the user U based on the usage activity information 53 acquired by the acquisition unit 41. The calculation unit 42 includes a data management index calculation unit 42A, a first point calculation unit 42B, a data usage index calculation unit 42C, and a second point calculation unit 42D.

[0061] The data management index calculation unit 42A calculates a data management index indicating the degree of data management of the database administrator DA for each database DB, based on the management activity information 54 acquired by the acquisition unit 41 and the metadata 60 stored in the storage unit 50. Specifically, the data management index calculation unit 42A aggregates the numerical values ​​(hereinafter, sometimes referred to as evaluation values) of the data management activity items for each database DB, based on the management activity information 54 and the metadata 60. Thereafter, the data management index is calculated for each database DB based on the aggregated numerical values ​​of the data management activity items.

[0062] In this embodiment, the data management activity items include, but are not limited to, the following ten items (A1) to (A10). Items (A1) to (A9) are quantitative evaluation items for evaluating direct management activities for the database DB. Item (A10) is a qualitative evaluation item for evaluating the quality of data management activities. (A1) Login frequency to server 20 (A2) Number of annotation updates (A3) Comprehensiveness of information in the database (percentage of entries for each item) (A4) Number of points to be paid when requesting a supporter appointment (A5) Number of requests for supporter appointments (A6) Number of likes for comments in the database (A7) Number of replies to comments (A8) Number of applications for database administrator positions (A9) Number of supporters for the database (A10) Centrality index.

[0063] The centrality index is an index that indicates the centrality of a target database among databases used simultaneously. When a user U acquires data from multiple databases (DB), the centrality of the database is the importance of the relationships between the databases (DB). The centrality index can be calculated by network analysis. In this embodiment, the data management index calculation unit 42A calculates the centrality index as follows.

[0064] First, the data management index calculation unit 42A creates an adjacency matrix, which is a square matrix with n rows and n columns, where n is the number of databases DB included in the data warehouse 10. Each component (i, j) of the adjacency matrix is ​​the weight of an edge in the network, and is a value indicating the strength of the connection between database i and database j. In this embodiment, each component (i, j) is a value obtained by aggregating and normalizing the following items K to N. Note that if the numerical value of each component is 0, there is no correlation between database i and database j, and component (i, j) is 0. Item K: Number of times database i and database j were used simultaneously during a given period Item L: The number of users U who have used database i and database j during a specified period (database i and database j do not have to be used at the same time within the specified period) Item M: 1 if database i and database j belong to the same category, 0 otherwise. Item N: The number of tags commonly assigned to database i and database j. Next, the data management index calculation unit 42A calculates the return value of the Pagerank (registered trademark) function using the above adjacency matrix as an argument, as the centrality index of each database DB. The centrality index calculated as above becomes larger the more databases DBs a database DB is connected to, in other words, the closer it is to the center of the network. Furthermore, the more important databases DBs a database DB is connected to, the larger its centrality index becomes, and therefore the more important the database DB is determined to be.

[0065] The data management index calculation unit 42A may calculate the data management index for each predetermined period. In this embodiment, the data management index calculation unit 42A calculates the data management index by the sum of the numerical values ​​obtained by multiplying the aggregated values ​​of the data management activity items by a weighting coefficient 55 set in advance for each item. This makes it possible to calculate an appropriate data management index depending on the degree of management activity of the database administrator DA. The weighting coefficient 55 may be stored in the storage unit 50 in advance.

[0066] The data management index calculation unit 42A may calculate the data management index based on the evaluation values ​​(i.e., the numerical values ​​of the data management activity items) obtained by evaluating each of the multiple types of management activities and the importance of each of the multiple types of management activities. Specifically, the data management index calculation unit 42A may calculate as the data management index the sum of numerical values ​​obtained by multiplying the corrected numerical values ​​of the aggregated data management activity items by a weighting coefficient 55 preset for each item. In this case, the data management index calculation unit 42A may calculate as the data management index the sum of numerical values ​​obtained by multiplying the numerical values ​​of the data management activity items corrected to relatively evaluate the variation in the numerical values ​​of the data management activity items between the data management activity items (e.g., values ​​corrected by Z-score normalization) by a weighting coefficient 55 calculated based on the importance of each of the multiple types of management activities. Specifically, the data management index may be calculated as follows.

[0067] The data management index calculation unit 42A first corrects the aggregated values ​​for each data management activity item (A1) to (A10) over a predetermined period by scaling (a process of standardizing the scale of values). For example, the number of times logging in to the server 20 is high results in a high value for item (A1), while the number of times requesting supporter appointments is low results in a low value for item (A3). This results in a large influence on data management activity items with a high number of tasks, preventing each data management activity item from being treated equally. On the other hand, by correcting using scaling, even if there is variation in the aggregated values ​​for each data management activity item, each data management activity item can be treated relatively equally. Furthermore, the scaling method may be standardized using Z-score normalization. In this case, even if there are extreme outliers in the aggregated values, a numerical value of the impact that is closer to the actual situation can be obtained without excluding the outlier. Next, the data management index calculation unit 42A calculates the data management index by multiplying the aggregated values ​​for each data management activity item (A1) to (A10) for a predetermined period corrected by scaling by a weighting coefficient 55 calculated based on the importance of each of the multiple types of management activities. For example, the weighting coefficient 55 may be a value calculated by the following (Equation 1). X n-i / ΣX n-i ...(Formula 1) In (Equation 1), X is a preset weighting coefficient. In (Equation 1), n ​​is the number of data management activity items (10 in this embodiment). In (Equation 1), i is a preset value that represents the preset importance ranking of the data management activity item. Therefore, (Equation 1) is a formula for calculating a weighting coefficient 55 by which the aggregate value for a predetermined period of the data management activity item that is ranked i in importance among the data management activity items is multiplied. By using the weighting coefficient 55 calculated by (Equation 1), it is possible to calculate a data management index that takes into account the importance of each of multiple types of management activities. Note that in this embodiment, the data management index calculation unit 42A is configured to be provided in the server 20, but the data management index may also be calculated by an external device other than the server 20.

[0068] The first point calculation unit 42B calculates first points to be awarded to the user U using the data management index calculated by the data management index calculation unit 42A. The first point calculation unit 42B may calculate the first points by multiplying a reference point set according to the type of usage activity by a data management index indicating the degree of data management of the database administrator DA for the database DB where the usage activity was performed. Usage activities for which points are awarded include, for example, applying for data use and reporting the results of data use. The first point calculation unit 42B calculates the first points each time a usage activity occurs. By calculating the first points as described above, the first points can be varied according to the degree of management activity.

[0069] The data usage index calculation unit 42C calculates a data usage index indicating the degree of data usage by the user U for each database DB based on the usage activity information 53 acquired by the acquisition unit 41. Specifically, the data usage index calculation unit 42C aggregates the numerical values ​​(hereinafter, may be referred to as evaluation values) of the data usage activity items for each database DB, and calculates a data usage index for each database DB based on the aggregated numerical values ​​of the data usage activity items.

[0070] In this embodiment, the data usage activity items include, but are not limited to, the following 10 items (B1) to (B10). Items (B1) to (B9) are quantitative evaluation items for evaluating direct usage activities of the database DB. Item (B10) is a qualitative evaluation item for evaluating the quality of data usage activities. (B1) Number of data usage applications (B2) Number of data usage results reports (B3) Number of members reporting data usage results (B4) Number of points paid at the time of database request (B5) Number of points for database requests (B6) Number of comments to the database (B7) Number of users who commented on the database (B8) Number of reactions to the database or comments on the database (B9) Number of searches (B10) Centrality index.

[0071] The above "number of times searched" is the number of times that when user U performs a search, the search conditions match with data stored in the database DB and user U queries the data definition information 61 of the data.

[0072] The data usage index calculation unit 42C may calculate the data usage index for each predetermined period. Specifically, the data usage index calculation unit 42C calculates the data usage index by the sum of the numerical values ​​obtained by multiplying the aggregated numerical values ​​of the data usage activity items by a weighting coefficient 55 set in advance for each item. This makes it possible to calculate an appropriate data usage index depending on the type of usage activity of the user U. The weighting coefficient 55 may be stored in the storage unit 50 in advance.

[0073] The data usage index calculation unit 42C may calculate the data usage index based on the evaluation values ​​(i.e., the numerical values ​​of the data usage activity items) obtained by evaluating each of the multiple types of usage activities and the importance of each of the multiple types of usage activities. Specifically, the data usage index calculation unit 42C may calculate, as the data usage index, the sum of numerical values ​​obtained by multiplying the corrected numerical values ​​of the aggregated data usage activity items by a weighting coefficient 55 preset for each item. In this case, the data usage index calculation unit 42C may calculate, as the data usage index, the sum of numerical values ​​obtained by multiplying the numerical values ​​of the data usage activity items corrected so as to relatively evaluate the variation in the numerical values ​​of the data management activity items between the data usage activity items (e.g., values ​​corrected by Z-score normalization) by a weighting coefficient 55 calculated based on the importance of each of the multiple types of usage activities. Specifically, the data usage index calculation unit 42C may calculate the data usage index as follows.

[0074] The data usage index calculation unit 42C first corrects the aggregated values ​​of each data usage activity item (B1) to (B10) for a predetermined period by scaling. By correcting by scaling, when there is variation in the aggregated values ​​of each data usage activity item, each data usage activity item can be treated relatively equally. Furthermore, the scaling method may be standardized using Z-score normalization. In this case, even if there is an extreme outlier in the aggregated values, it is possible to obtain a numerical value of the impact degree that is closer to the actual situation, rather than excluding the outlier. Next, the data usage index calculation unit 42C calculates, as the data usage index, the sum of numerical values ​​obtained by multiplying the aggregated values ​​for a predetermined period of each of the data usage activity items (B1) to (B10) corrected by scaling by a weighting coefficient 55 calculated based on the importance of each of the multiple types of usage activities. For example, the weighting coefficient 55 may be a numerical value calculated using the above (Equation 1). When calculating the data usage index, n in (Equation 1) is the number of data usage activity items (10 in this embodiment), and i in (Equation 1) is a predetermined value that represents the importance ranking of the data usage activity item. In this case, (Equation 1) is a formula for calculating the weighting coefficient 55 to be multiplied by the aggregated value for a predetermined period of the data usage activity item that has the i-th importance ranking among the data usage activity items. By using the weighting coefficient 55 calculated using (Equation 1), it is possible to calculate the data usage index taking into account the importance of each of the multiple types of usage activities. In this embodiment, the data usage index calculation unit 42C is provided in the server 20, but the data usage index may be calculated by an external device other than the server 20.

[0075] The second point calculation unit 42D calculates second points to be awarded to the database administrator DA using the data usage index calculated by the data usage index calculation unit 42C. The second point calculation unit 42D calculates second points by multiplying a base point set according to the type of management activity by a data usage index that indicates the degree of data usage by user U for the database DB where the management activity was performed. The second point calculation unit 42D calculates second points each time a management activity occurs. By calculating the second points as described above, it is possible to vary the second points according to the degree of usage activity.

[0076] The point trading unit 43 carries out point trading in the data warehouse system 1. The point trading unit 43 includes an adding unit 43A and a collecting unit 43B.

[0077] The granting unit 43A grants the first points calculated by the first point calculation unit 42B to the user U, and grants the second points calculated by the second point calculation unit 42D to the database administrator DA.

[0078] When the user U and the database administrator DA use points to perform an activity, the collection unit 43B collects the points used from the points held by the user U and the database administrator DA. For example, when the user U uses points to make a database request, the collection unit 43B collects the points from the points held by the user U.

[0079] When the granting unit 43A grants points and when the collecting unit 43B collects points, the point trading unit 43 stores information on the increase or decrease in points as point data 56 in the storage unit 50.

[0080] 8 is a diagram showing an example of point data 56 of user U that the point trading unit 43 stores in the storage unit 50. As shown in FIG. 8, the point trading unit 43 may store in the storage unit 50 as point data 56 of user U a table linking the user ID, usage activity date and time, usage activity ID, owned points, points awarded for usage activities in each database DB, and used points.

[0081] 9 is a diagram showing an example of point data 56 of a database administrator DA that the point trading unit 43 stores in the memory unit 50. As shown in FIG. 9, the point trading unit 43 may store in the memory unit 50 as point data 56 of the database administrator DA a table linking the administrator ID, management activity date and time, management activity ID, database ID, owned points, points granted for management activities, and used points.

[0082] 10 is a screen displayed on the information terminal 11 possessed by the user U and the database administrator DA, showing point information related to the user U and the database administrator DA. As shown in Fig. 10, the information terminal 11 may display a screen 100 showing the number of points held, the number of points earned this month, and the number of points used this month. The screen 100 may also show the trend in points increased or decreased due to usage activities performed as the user U and management activities performed as the database administrator DA, as well as usage activities of other users U on the database managed by the database administrator DA.

[0083] (Processing performed by the point management unit 40) The flow of the process (point management method) performed by the point management unit 40 will be described below with reference to Fig. 11 and Fig. 12. Fig. 11 is a flowchart showing an example of the flow of the process performed by the point management unit 40.

[0084] As shown in Figure 11, in the processing performed by the point management unit 40, the acquisition unit 41 first acquires, from the memory unit 50, management activity information 54 indicating the management activities performed by the database administrator DA on the database DB, and usage activity information 53 indicating the usage activities performed by the user U on each of the database DB (step S1, acquisition step).

[0085] Next, the calculation unit 42 calculates first points according to the management activities performed by the database administrator DA based on the management activity information 54 acquired in step S1, and calculates second points according to the usage activities performed by the user U based on the usage activity information 53 (step S2, calculation step).

[0086] Details of step S2 will be described with reference to Fig. 12. Fig. 12 is a flowchart showing an example of the flow of processing performed by the calculation unit 42.

[0087] 12, in the process performed by the calculation unit 42, first, the data management index calculation unit 42A calculates a data management index indicating the degree of data management of the database administrator DA for each database DB based on the management activity information 54 and the metadata 60 stored in the storage unit 50 (step S21). Specifically, the data management index calculation unit 42A tallies up the data management activity items for each database DB based on the management activity information 54 and the metadata 60. Next, the data management index calculation unit 42A multiplies the numerical values ​​of the tallied data management activity items by a weighting coefficient 55 that is preset for each item, and calculates the numerical value as the data management index.

[0088] Next, the first point calculation unit 42B calculates the first points to be awarded to the user U using the data management index calculated in step S21 (step S22). Specifically, the first point calculation unit 42B first calculates points according to the usage activity performed by the user U for each database DB. Next, for each database DB, the first point calculation unit 42B calculates a value by multiplying the calculated points by the data management index of the database DB for which the usage activity was performed, and calculates the sum of the calculated points as the first points.

[0089] Next, the data usage index calculation unit 42C calculates a data usage index indicating the degree of data usage by the user U for each database DB based on the usage activity information 53 acquired in step S1 (step S23). Specifically, the data usage index calculation unit 42C first aggregates the data usage activity items for each database DB. Next, the data usage index calculation unit 42C multiplies the numerical values ​​of the aggregated data usage activity items by a weighting coefficient 55 set in advance for each item to calculate the data usage index.

[0090] Next, the second point calculation unit 42D calculates second points to be awarded to the database administrator DA using the data usage index calculated in step S23 (step S24). Specifically, the second point calculation unit 42D first calculates points according to the management activities performed by the database administrator DA and the usage of the database DB managed by the database administrator DA himself. Next, the second point calculation unit 42D calculates the second points by multiplying the calculated points by the data usage index of the database DB managed by the database administrator DA himself. Steps S21 and S22 and steps S23 and S24 may be processed in the reverse order (i.e., S23, S24, S21, S22) or may be processed simultaneously.

[0091] Returning to Figure 11, after the calculation step S2 is completed, the granting unit 43A grants the first points calculated by the first point calculation unit 42B to the user U, and grants the second points calculated by the second point calculation unit 42D to the database administrator DA (S3, granting step).

[0092] As described above, the data warehouse system 1 is operated by a distributed, autonomous-organization type of data management system in which the user U serves as the database administrator DA and manages each database DB. In this case, the management of each database DB is left to the discretion and sense of responsibility of the database administrator DA, which makes it difficult to continue managing the database DB. In response to this, the data warehouse system 1 of this embodiment introduces a system that awards points for management activities, which motivates the database administrator DA to continue their management activities.

[0093] The data warehouse system 1 of this embodiment includes a data warehouse 10 having multiple databases (DB) and a point management unit 40 as a point management device. The point management unit 40 includes an acquisition unit 41 that acquires management activity information 54 and usage activity information 53; a calculation unit 42 that calculates first points corresponding to the management activity of a database administrator DA based on the management activity information 54 and calculates second points corresponding to the usage activity of a user U based on the usage activity information 53; and an assignment unit 43A that assigns the first points to the user U of the database DB and assigns second points corresponding to the user U's usage activity of the database DB to the database administrator DA of the database DB. With this configuration, the points assigned to the user U and the database administrator DA vary depending on the management activity and usage activity. This can improve the motivation of the database administrator DA or user U to manage or use the database DB. Furthermore, because the first points corresponding to the management activity are assigned to the user U and the second points corresponding to the usage activity are assigned to the database administrator DA, points can be circulated. As a result, management activity and usage activity can be continuously promoted simultaneously.

[0094] According to the data warehouse system 1 of one embodiment of the present invention, points that benefit the database administrator DA and the user U are awarded and collected, thereby continuously promoting the autonomous database management activities and usage activities of the database administrator DA and the user U. Furthermore, by dynamically changing the points awarded to the database administrator DA and the user U or the points collected from the database administrator DA and the user U according to the status of each activity, motivation for management activities and usage activities can be maintained. Furthermore, data that is easy for the user U to use is managed within the data warehouse 10, and information about that data is also disclosed extensively, making it easier for the user U to identify and utilize data that matches their purpose of use.

[0095] Furthermore, in the data warehouse system 1, the data usage index and data management index are calculated using data management activity items and data usage activity items, including a centrality index, which is an index indicating the centrality of the target database among the simultaneously used databases. Therefore, the first and second points include points (third points) calculated based on the centrality index. This configuration allows points to be awarded to the user U and the database administrator DA based on the degree of activity, reflecting not only a quantitative evaluation of their direct activities on the database DB, but also a qualitative evaluation that takes into account the importance of the interrelationships between the databases. As a result, for example, even for databases DB that handle universal and important information, such as master data, but are not frequently managed, higher data usage indexes and data management indexes can be calculated by using the centrality index as an item. Therefore, points reflecting the actual management activities of the database administrator DA and the actual usage activities of the user U can be awarded to the user U and the database administrator DA.

[0096] The data warehouse system 1 is operated using a distributed, autonomously organized data management system. Therefore, while it is necessary to give users U a certain degree of discretion in order to promote data usage, it is also necessary to impose strict restrictions on access permissions and handling of data. To address this issue, the data warehouse system 1 shares user U's usage activity with other users U as metadata 60. This makes user U's usage activity more transparent and strengthens data governance.

[0097] The data warehouse system 1 in this embodiment includes a data warehouse 10 having multiple databases (DB), and a control unit 30 that accepts searches for metadata 60 of the multiple databases (DB) from a user U. The metadata 60 includes information related to the user U's usage activities for the databases (DB) and the management activities of the database administrator (DA) for the databases. With the above configuration, when the user U searches the metadata 60, the user U can refer to information related to usage activities and information related to management activities, making it easier for the user U to identify and utilize data that matches their purpose of use.

[0098] [Software implementation example] The functions of the server 20 (hereinafter referred to as the "device") can be realized by a program that causes a computer to function as the device, and a program that causes a computer to function as each control block of the device (particularly each part included in the control unit 30).

[0099] In this case, the device includes a computer having at least one control device (e.g., a processor) and at least one storage device (e.g., a memory) as hardware for executing the program. The control device and storage device execute the program, thereby realizing the functions described in each of the above embodiments.

[0100] The program may be non-transitory and may be recorded on one or more computer-readable recording media. The recording media may or may not be included in the device. In the latter case, the program may be supplied to the device via any wired or wireless transmission medium.

[0101] Some or all of the functions of the control blocks can be realized by logic circuits. For example, an integrated circuit in which a logic circuit that functions as each of the control blocks is formed is also included in the scope of the present invention. In addition, the functions of the control blocks can also be realized by, for example, a quantum computer.

[0102] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.

[0103] 〔summary〕 A point management device according to aspect 1 of the present disclosure includes an acquisition unit that acquires management activity information indicating management activities performed by an administrator on a database included in a data warehouse having multiple databases, and usage activity information indicating usage activities performed by a user on the database; a calculation unit that calculates first points corresponding to the management activity based on the management activity information, and calculates second points corresponding to the usage activity based on the usage activity information; and an assignment unit that assigns the first points corresponding to the management activity on the database to the user of the database, and assigns the second points corresponding to the usage activity on the database to the administrator of the database.

[0104] A point management device according to aspect 2 of the present disclosure may be configured such that, in aspect 1 above, the calculation unit calculates a data management index indicating the degree of data management of the administrator from the management activity information of the database, and calculates the first points based on the data management index for each usage activity of the database.

[0105] A point management device according to aspect 3 of the present disclosure may be configured such that, in aspect 2 above, the calculation unit calculates the data management index based on evaluation values ​​obtained by evaluating each of the multiple types of management activities and the importance of each of the multiple types of management activities.

[0106] A point management device according to aspect 4 of the present disclosure may be configured such that, in aspect 2 or 3 above, the calculation unit calculates the data management index based on the evaluation values ​​obtained by evaluating each of the multiple types of management activities, corrected by Z-score normalization, and the importance of each of the multiple types of management activities.

[0107] A point management device according to aspect 5 of the present disclosure may be configured such that, in any of aspects 1 to 4 above, the calculation unit calculates a data usage index indicating the degree of data usage of the user from the usage activity information of the database, and calculates the second points based on the data usage index for each management activity on the database.

[0108] A point management device according to aspect 6 of the present disclosure may be configured such that, in aspect 5 above, the calculation unit calculates the data usage index based on evaluation values ​​obtained by evaluating each of the multiple types of usage activities and the importance of each of the multiple types of usage activities.

[0109] The point management device according to aspect 7 of the present disclosure may be configured such that, in aspect 5 or 6 above, the calculation unit calculates the data usage index based on the evaluation values ​​obtained by evaluating each of the multiple types of usage activities, corrected by Z-score normalization, and the importance of each of the multiple types of usage activities.

[0110] A point management device according to aspect 8 of the present disclosure may be configured such that, in any of aspects 1 to 7 above, the metadata of the data stored in the database includes information relating to the usage activity and the management activity.

[0111] A point management device according to aspect 9 of the present disclosure may be configured such that, in any of aspects 1 to 8 above, the first points and the second points include third points calculated based on a centrality index indicating the centrality of the database in the plurality of databases.

[0112] A point management method according to aspect 10 of the present disclosure includes an acquisition step of acquiring management activity information indicating management activities performed by an administrator on a database included in a data warehouse having multiple databases, and usage activity information indicating usage activities performed by users on the database; a calculation step of calculating first points corresponding to the management activity based on the management activity information and calculating second points corresponding to the usage activity based on the usage activity information; and an assignment step of assigning the first points corresponding to the management activity on the database to the user of the database and assigning the second points corresponding to the usage activity on the database to the administrator of the database.

[0113] According to the eleventh aspect of the present disclosure program is a program for causing a computer to function as the point management device of the above-mentioned aspect 1, and is a program for causing a computer to function as the acquisition unit, the calculation unit, and the granting unit.

[0114] A data warehouse system according to aspect 12 of the present disclosure comprises a data warehouse having a plurality of databases; and a point management device that (1) acquires management activity information indicating management activities performed by an administrator on databases included in the data warehouse and usage activity information indicating usage activities performed by users on the databases, (2) calculates first points corresponding to the management activities based on the management activity information, and calculates second points corresponding to the usage activities based on the usage activity information, and (3) assigns the first points corresponding to the management activities on the database to the user of the database, and assigns the second points corresponding to the usage activities on the database to the administrator of the database. [Explanation of symbols]

[0115] 1. Data Warehouse System 10. Data Warehouse 40 Point management unit (point management device) 41 Acquisition Department 42 Calculation section 43A Granting Division 60 Metadata

Claims

1. an acquisition unit that acquires management activity information indicating management activities performed by an administrator on a database included in a data warehouse having a plurality of databases, and usage activity information indicating usage activities performed by users on the database; a calculation unit that calculates first points corresponding to the management activity based on the management activity information and calculates second points corresponding to the usage activity based on the usage activity information; A point management device comprising: an awarding unit that awards the first points to the user of the database in accordance with the management activity for the database, and awards the second points to the administrator of the database in accordance with the usage activity for the database.

2. the calculation unit calculates a data management index indicating a degree of data management of the administrator from the management activity information of the database, and calculates the first points based on the data management index for each of the use activities of the database. The points management device according to claim 1 .

3. the calculation unit calculates the data management index based on evaluation values ​​obtained by evaluating each of the plurality of types of management activities and the importance of each of the plurality of types of management activities. The points management device according to claim 2 .

4. The calculation unit calculates an evaluation value obtained by evaluating each of the plurality of types of management activities as a Z-score. The points management device according to claim 2 , wherein the data management index is calculated based on a value corrected by normalization and the importance of each of the plurality of types of management activities.

5. the calculation unit calculates a data usage index indicating a degree of data usage by the user from the usage activity information of the database, and calculates the second points based on the data usage index for each management activity on the database. The points management device according to claim 1 .

6. the calculation unit calculates the data usage index based on evaluation values ​​obtained by evaluating each of the plurality of types of usage activities and the importance of each of the plurality of types of usage activities. The points management device according to claim 5.

7. The calculation unit calculates an evaluation value obtained by evaluating each of the plurality of types of usage activities as a Z-score. The points management device according to claim 5 , wherein the data usage index is calculated based on a value corrected by normalization and the importance of each of the plurality of types of usage activities.

8. metadata of the data stored in the database includes information related to the usage activity and the management activity; The points management device according to claim 1 .

9. the first point and the second point include a third point calculated based on a centrality index indicating centrality of a database in the plurality of databases; The points management device according to claim 1 .

10. A points management method executed by a computer, comprising: an acquisition step in which the computer acquires management activity information indicating management activities performed by an administrator on a database included in a data warehouse having a plurality of databases, and usage activity information indicating usage activities performed by users on the database; a calculation step in which the computer calculates first points corresponding to the management activity based on the management activity information and calculates second points corresponding to the usage activity based on the usage activity information; A point management method including an awarding step in which the computer awards the first points to the user of the database in accordance with the management activity for the database, and awards the second points to the administrator of the database in accordance with the usage activity for the database.

11. A program for causing a computer to function as the points management device according to claim 1, the program causing a computer to function as the acquisition unit, the calculation unit, and the granting unit.

12. a data warehouse having multiple databases; (1) acquiring management activity information indicating management activities performed by an administrator on a database included in the data warehouse and usage activity information indicating usage activities performed by users on the database; (2) calculating first points corresponding to the management activity based on the management activity information, and calculating second points corresponding to the usage activity based on the usage activity information; (3) a point management device that grants the first points to the user of the database according to the management activity on the database and grants the second points to the administrator of the database according to the use activity on the database; A data warehouse system comprising:

Images