Point management apparatus, 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 applied to a data warehouse system and the like.

Background Art

[0002] As a mechanism for aggregating a huge amount of data, a centralized data management in which only a data manager manages a data warehouse as an administrator is generally known. On the other hand, if only a specific administrator prepares and manages the database too much, it is difficult to become a database that reflects the needs of users, and it does not necessarily become a 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 a plurality of business systems. However, it is not a system for pre-data management such as enriching the information of a data catalog necessary for specifying the data to be collected and the target data.

[0004] Non-Patent Document 1 describes that a data catalog capable of searching a large number of metadata at once enables highly convenient data search for users. Non-Patent Document 2 describes that preprocessing on the integrated database side is important for searching and utilizing various data accumulated in the integrated database.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Non-Patent Documents

[0006]

Non-Patent Document 1

[0007] In a data warehouse system, it is required to be able to obtain the data required by users and to be a system managed in such a way.

[0008] In order to easily utilize a vast amount of data and create a database more suitable for users, there are limitations in the conventional centralized data management. Therefore, it is necessary to realize a decentralized data community in which users themselves participate in data management as database administrators and can autonomously collect, manage, or utilize data.

[0009] One aspect of the present invention aims to realize a point management device or the like that can promote data utilization by users and data management by database administrators in an applied data warehouse system. [Means for Solving the Problems]

[0010] To solve the above problems, a point management device according to one aspect of the present invention includes an acquisition unit that acquires management activity information indicating management activities performed by an administrator on databases included in a data warehouse having a plurality of databases, and utilization activity information indicating utilization activities performed by users on the databases; a calculation unit that calculates a first point corresponding to the management activity based on the management activity information and calculates a second point corresponding to the utilization activity based on the utilization activity information; and an assignment unit that assigns the first point corresponding to the management activity on the database to the user of the database and assigns the second point corresponding to the utilization activity on the database to the administrator of the database.

[0011] In order to solve the above problems, a point management method according to an aspect of the present invention includes an acquisition step of acquiring management activity information indicating management activities performed by an administrator on databases included in a data warehouse having a plurality of databases, and usage activity information indicating usage activities performed by users on the databases; a calculation step of calculating a first point corresponding to the management activity based on the management activity information and calculating a second point corresponding to the usage activity based on the usage activity information; and an assignment step of assigning the first point corresponding to the management activity on the database to the user of the database and assigning the second point 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 an aspect of the present invention includes 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 a first point corresponding to the management activity based on the management activity information and calculates a second point corresponding to the usage activity based on the usage activity information, and (3) assigns the first point corresponding to the management activity on the database to the user of the database and assigns the second point corresponding to the usage activity 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 this case, a control program for realizing the point management device by operating the computer as each part (software element) included in the point management device, and a computer-readable recording medium recording the same also fall within the scope of the present invention.

Advantages of the Invention

[0014] According to one aspect of the present invention, in an applied data warehouse system, it is possible to facilitate data utilization by users and data management by database administrators.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Modes for Carrying Out the Invention

[0016] 〔Embodiment 1〕 Hereinafter, an embodiment of the present invention will be described in detail. First, an overview of the 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 a plurality of databases DB that can be used by the user U of the data warehouse system 1. The data warehouse system 1 is operated and managed by the operation administrator MA. The operation administrator MA is a person who provides and operates the data warehouse system 1 and does not directly manage the database DB. Various data are stored in the database DB.

[0017] Each of the plurality of databases DB may be a database DB brought into the data warehouse system 1 by the user U of each database, and the user U who brought in the database DB may become the database administrator DA (administrator) who manages the database DB. The data stored in the data warehouse system 1 is managed by distributed autonomous organization (DAO: Decentralised Autonomous Organization) type data management. The database administrator DA is a person who manages the data in the database and information related to the data. In the data warehouse system 1, the formation of a distributed autonomous organization is supported by point management.

[0018] The user U of the data warehouse system 1 uses the server 20 to search for the database DB in which the data to be used is stored, and submits a data usage application to the database administrator DA who manages the database DB via the server 20. When the data usage application is approved by an approver such as the database administrator DA, the user U can use the data.

[0019] The user U checks whether the desired data exists in the data warehouse 10 by searching for 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 exists in the data warehouse 10, the user U submits a usage application to the database administrator DA of the database DB in which the data is stored via the server 20. Until the data usage application is approved by the database administrator DA and the user U can use the data, 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, the metadata 60 of the data stored in the database DB includes information related to the usage activities of the user U with respect to the database DB and the management activities by the database administrator DA of the database. Details will be described later.

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

[0022] In the data warehouse system 1, the database administrator DA can recruit a supporter S who will support the management of the database DB that the administrator manages from the users U of the data warehouse system 1, and can select the user U who applies for the recruitment as the supporter S. The supporter S is an expert who has knowledge about the data stored in the database DB and supports the database administrator DA regarding the management of the database DB. For example, the supporter S supports the database administrator DA regarding editing such as supplementing and adding the metadata 60 of the data stored in the database DB. The supporter S may support a plurality of databases DB.

[0023] (Configuration of Data Warehouse System 1) Next, the details of the configuration of the data warehouse system 1 will be described. FIG. 2 is a block diagram showing the main configuration 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 possessed by a plurality of database administrators DA or users U. The information terminal 11 can communicate with the server 20. The database administrator DA manages the database DB he / she manages using the information terminal 11. For example, the database administrator DA edits the data definition information 61 of the data stored in the database DB using the information terminal 11. The user U applies for the use of the data stored in the database DB and reports the use results of the data described later via the information terminal 11.

[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 inputs to the server 20, and a display unit 22 for displaying various types of information.

[0026] As shown in FIG. 2, the control unit 30 includes a service reception 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 reception 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 the details of the activity reception unit 31. As shown in FIG. 3, the activity reception unit 31 includes a search reception unit 31A, a data usage application reception unit 31B, a data usage approval reception unit 31C, a data usage result report reception unit 31D, a database request reception unit 31E, a database request approval reception unit 31F, a tagging reception unit 31G, a comment reception unit 31H, a reaction reception unit 31I, a quality report reception unit 31J, an improvement notification reception unit 31K, and an annotation editing reception unit 31L.

[0028] The search reception unit 31A receives a search regarding the data stored in the data warehouse 10 from the user U. As described above, the user U identifies the 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 the 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 the data definition information 61.

[0029] The data usage application reception unit 31B receives a data usage application from the user U. When the data usage application reception unit 31B receives a data usage application, it notifies the database administrator DA of the database DB in which the data is stored that there is a usage application.

[0030] The data usage approval reception unit 31C receives approval for data usage from the database administrator DA. When the data usage approval reception unit 31C receives approval for data usage, it notifies the user U that the approval has been granted. Thereby, the user U can 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 on how the user U used the data. Specifically, the data usage result report includes information such as the purpose of data usage, the results obtained using the data, and what other data was used.

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

[0033] The database request approval receiving unit 31F receives approval from the user U for a database request requested by another user U. The user U approves the database request using points.

[0034] The tagging receiving 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 a reaction from the user U to the database DB or a reaction to a comment on the database DB stored as metadata 60. The above reactions include positive reactions such as "like" and "heart", and negative reactions such as "sad".

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

[0038] The improvement contact reception unit 31K receives improvement contacts for the database DB from the database administrator DA.

[0039] The annotation editing reception unit 31L receives the editing of the annotations for 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 the data definition information 61 of each data stored in the database DB from the data warehouse 10 and stores it in the storage unit 50 as metadata 60.

[0041] Also, the metadata collection unit 32 collects information related 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 reception unit 31A receives a search from the user U for data stored in the data warehouse 10, the metadata collection unit 32 stores the log of the search (hereinafter referred to as the 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. Thereby, another user U can perform a search efficiently.

[0043] In addition, when the metadata collection unit 32 receives a data use application from the user U by the data use application reception unit 31B, it stores the data use application information 63 (for example, the ID of the applying user U, the application date and time, the data to be used, the case name, the purpose of use, the method of use, the start date of use, the end date of use, the co - user ID, the data storage location, comments, etc.) described for the said use application in the storage unit 50 as metadata 60. When the data use approval reception unit 31C receives approval for data use from the database administrator DA, it stores the approval result of the said use application in the storage unit 50 as metadata 60. The approval result includes rejection when data that does not match the said purpose is selected. Since the data use application information 63 is stored as metadata 60, when another user U conducts a search, the data use application information 63 can be referred to. Thereby, it is possible to accurately determine whether the data that another user U wants to use is appropriate or not.

[0044] In addition, when the metadata collection unit 32 receives a data use result report 64 from the user U by the data use result report reception unit 31D, it stores the data use result report 64 (for example, the ID of the reporting user U, the report summary, the report details, the achievements, the issues, the supplementary data, the data use environment, the source code storage location, the temporary storage data deletion confirmation flag, the compliance with the usage agreement confirmation flag, other reporting destinations, future plans, comments, etc.) in the storage unit 50 as metadata 60. Since the data use result report 64 is stored as metadata 60, when another user U conducts a search, the data use result report 64 can be referred to. Thereby, it is possible to accurately determine whether the data that another user U wants to use is appropriate or not.

[0045] In addition, when the metadata collection unit 32 receives a database request 65 from the user U by the database request reception unit 31E, it stores the content of the database request 65 in the storage unit 50 as metadata 60. Since the database request 65 is stored as metadata 60, the database administrator DA can grasp the data desired by the user U.

[0046] In addition, for each of the databases DB, the metadata collection unit 32 collects the number of approvals for the database requests accepted by the database request approval reception unit 31F (hereinafter referred to as the database request approval number 66), and stores it in the storage unit 50 as metadata 60. By storing the database request approval number 66 as the metadata 60, the database administrator DA can grasp the data desired by the user U.

[0047] In addition, when the tagging reception unit 31G accepts tagging of the database DB from the user U or the database administrator DA, the metadata collection unit 32 stores the tag 67 in the storage unit 50 as the metadata 60. By storing the tag 67 as the metadata 60, when another user U performs a search, the tag 67 can be referred to. Thereby, another user U can perform a search efficiently.

[0048] In addition, when the comment reception unit 31H accepts a comment 68 on the database DB from the user U or the database administrator DA, the metadata collection unit 32 stores the comment 68 in the storage unit 50 as the metadata 60. By storing the comment 68 as the metadata 60, when another user U performs a search, the comment 68 can be referred to. Thereby, another user U can perform a search efficiently. Also, communication between the user U and the database administrator DA can be performed via the comment 68 of the metadata 60.

[0049] In addition, the metadata collection unit 32 collects reactions (hereinafter referred to as reaction 69) of the user U to the database DB or comments received by the reaction reception unit 31I, and stores them in the storage unit 50 as metadata 60. By storing the reaction 69 as the metadata 60, it is possible to grasp the degree of understanding of the user U with respect to the data and / or the evaluation of the usability of the data. In addition, it is possible to grasp the management activities to be performed by the database administrator DA and the evaluation of the response comments.

[0050] In addition, when the quality report reception unit 31J receives a quality report of the data used by the user U from the user U, the metadata collection unit 32 stores the data quality evaluation 70 described in the quality report in the storage unit 50 as the metadata 60. By storing the data quality evaluation 70 as the metadata 60, when another user U performs a search, the data quality evaluation 70 can be referred to. As a result, another user U can use the data after grasping the quality. In addition, the database administrator DA can grasp the data for which the quality should be improved.

[0051] In addition, when the improvement notification reception unit 31K receives an improvement notification of the database DB from the database administrator DA, the metadata collection unit 32 stores the improvement progress 71 in the storage unit 50 as the metadata 60. By storing the improvement progress 71 as the metadata 60, when another user U performs a search, the improvement progress 71 can be referred to. As a result, another user U can identify higher-quality data.

[0052] In addition, when the annotation editing reception unit 31L receives an edit of the annotation of the database DB from the database administrator DA, the metadata collection unit 32 stores the edited annotation 72 in the storage unit 50 as the metadata 60. By storing the annotation 72 as the metadata 60, when another user U performs a search, the annotation 72 can be referred to. As a result, another user U can perform a search efficiently.

[0053] The management activity support unit 33 supports the 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 manager appointment support unit 33A supports the appointment of the database administrator DA of the database DB. Specifically, when a new database DB is brought into the data warehouse 10 and when the database administrator DA of the existing database DB is absent, the manager appointment support unit 33A recruits the database administrator DA of the database DB from the user U. When there is an application from the user U for the recruitment, the manager appointment support unit 33A appoints the user U as the database administrator DA. The manager appointment support unit 33A stores the information of the user U appointed as the database administrator DA in the storage unit 50 as the administrator information 51. When the user U is appointed as the database administrator DA, a predetermined point is given to the user U.

[0055] The supporter appointment support unit 33B supports the appointment of the supporter S of the database DB. For example, when there is a request from the database administrator DA for a certain user U to be appointed as the supporter S, the supporter appointment support unit 33B requests the user U to be appointed as the supporter S. The database administrator DA requests the appointment as the supporter S using points. When the user U agrees to the request, the supporter appointment support unit 33B appoints the user U as the supporter S. The supporter appointment support unit 33B stores the information of the user U appointed as the supporter S in the storage unit 50 as the supporter information 52. Also, when the supporter appointment support unit 33B receives a notice from the user U that the user U wants to become the supporter S of the database DB spontaneously, the supporter appointment support unit 33B appoints the user U as the supporter S and stores the information of the user U appointed as the supporter S in the storage unit 50 as the supporter information 52. When the user U is appointed as the supporter S, a predetermined point is given to the user U.

[0056] The usage activity information collection unit 34 collects, for each database DB, usage activity information 53 indicating the usage activities received by the usage reception unit 31 from the user U, in other words, the usage activities performed by the user U on the database DB. The usage activity information collection unit 34 may collect, for each data, usage activity information 53 indicating the usage activities performed by the user U on 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 by the usage activity information collection unit 34 in the storage unit 50. As shown in FIG. 5, the usage activity information collection unit 34 may store in the storage unit 50, as the usage activity information 53, a table associating the date on which 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 the usage activity ID indicating the type of the usage activity. Further, the usage activity information collection unit 34 may store in the storage unit 50, as the usage activity information 53, the table ID of each table.

[0057] The management activity information collection unit 35 collects management activity information 54 indicating the management activities received by the activity reception 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 collection unit 35 may collect, for each data, management activity information 54 indicating the management activities performed by the user U on the data. The management activity information collection 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 by the management activity information collection unit 35 in the storage unit 50. As shown in FIG. 6, the management activity information collection unit 35 may store in the storage unit 50, as the management activity information 54, a table associating the date on which 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 the management activity ID indicating the type of the management activity. Further, the management activity information collection unit 35 may store in the storage unit 50, as the management activity information 54, the table ID of each table.

[0058] The point management unit 40 manages the points given 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 transaction 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 corresponding to the management activities performed by the database administrator DA based on the management activity information 54 acquired by the acquisition unit 41 (hereinafter referred to as the first points), and points corresponding to the usage activities performed by the user U based on the usage activity information 53 acquired by the acquisition unit 41 (hereinafter referred to as the second points). 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 totals the numerical values of the data management activity items (hereinafter sometimes referred to as evaluation values) for each database DB based on the management activity information 54 and the metadata 60. Then, based on the totaled numerical values of the data management activity items, a data management index is calculated for each database DB.

[0062] In the present embodiment, the data management activity items include, but are not limited to, the following 10 items (A1) to (A10). Items (A1) to (A9) are quantitative evaluation items for evaluating direct management activities on the database DB. Item (A10) is a qualitative evaluation item for evaluating the quality of data management activities. (A1) Login frequency to the server 20 (A2) Number of annotation updates (A3) Completeness of information about the database (registration ratio of each item) (A4) Number of payment points at the time of requesting a supporter to take office (A5) Number of requests for supporters to take office (A6) Number of approvals for comments in the database (A7) Number of replies to comments (A8) Number of applicants for the recruitment of database administrators (A9) Number of approvals for the database (A10) Centrality index.

[0063] The centrality index is an index indicating the centrality of the target database in the databases used simultaneously. The centrality of a database is the importance in the mutual relationship of each database DB when the user U obtains data from a plurality of databases DB. The centrality index can be calculated by network analysis. In the present embodiment, the data management index calculation unit 42A calculates the centrality index as follows.

[0064] First, the data management index calculation unit 42A sets the number of databases DB provided in the data warehouse 10 as n, and creates an adjacency matrix that is a square matrix of n rows and n columns. Each component (i, j) of the adjacency matrix is the weight of the edge of the network, and is a value indicating the strength of the connection between database i and database j. In the present embodiment, each component (i, j) is a value obtained by aggregating and normalizing the following items K to N. When the numerical value of each item is 0, there is no mutual relationship between database i and database j, and the component (i, j) becomes 0. Item K: The number of times database i and database j were used simultaneously during a predetermined period Item L: The number of users U who have used database i and database j during a predetermined period (within the predetermined period, database i and database j do not have to be used simultaneously) 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, as the centrality index of each database DB, the return value returned by the PageRank (registered trademark) function using the adjacent matrix as an argument. As described above, the centrality index calculated in this way becomes larger as it is connected to more databases DB. In other words, the larger the value, the more it is located at the center of the network. Also, since the centrality index of a database DB connected to an important database DB becomes larger, it is determined that the database DB is more important.

[0065] The data management index calculation unit 42A may calculate the data management index for each predetermined period. In the present embodiment, the data management index calculation unit 42A calculates, as the data management index, the total value of the numerical values obtained by multiplying the numerical values of the aggregated data management activity items by the weighting coefficient 55 preset for each item. Thereby, an appropriate data management index can be calculated according to the degree of the management activities 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 (that is, the numerical values of the data management activity items) for evaluating each of the plurality of types of management activities and the importance of each of the plurality of types of management activities. Specifically, the data management index calculation unit 42A may calculate, as the data management index, the total value of the numerical values obtained by multiplying the corrected numerical values of the aggregated data management activity items by the weighting coefficient 55 preset for each item. In this case, the data management index calculation unit 42A calculates, as the data management index, the total value of the numerical values obtained by multiplying the numerical values of the data management activity items (for example, the values corrected by Z-score normalization) corrected so as to relatively evaluate the variation in the numerical values of the data management activity items among the data management activity items by the weighting coefficient 55 calculated based on the importance of each of the plurality of 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 of each data management activity item of (A1) to (A10) for a predetermined period by scaling (a process of unifying the numerical scales). Here, for example, since the number of times of logging in to the server 20 is large, the numerical value of item (A1) increases, while since the number of times of requesting the appointment of a supporter is small, the numerical value of item (A3) decreases. For this reason, the influence of the data management activity item with a large number of operations becomes large, and each data management activity item cannot be treated equally. On the other hand, by correcting by scaling, when there are variations in the aggregated values of each data management activity item, each data management activity item can be treated relatively equally. Also, the scaling method may be standardized using Z-score normalization. In that case, even when there are extreme outliers in the above aggregated values, instead of excluding the outliers, numerical values with an influence degree closer to the actual situation can be obtained. Next, the data management index calculation unit 42A calculates, as the data management index, the total value of the numerical values obtained by multiplying the aggregated values of each data management activity item of (A1) to (A10) corrected by scaling for a predetermined period by the weighting coefficient 55 calculated based on the importance of each of the plurality of types of management activities. For example, the weighting coefficient 55 may be a numerical value calculated by the following (Equation 1). X n-i / ΣX n-i ···(Equation 1) X in (Equation 1) is a preset weighting coefficient. n in (Equation 1) is the number of items of data management activity items (10 in this embodiment). i in (Equation 1) is the preset ranking of the importance of the data management activity items, which is a preset value. Therefore, (Equation 1) is an equation for calculating the weighting coefficient 55 to be multiplied by the aggregated value of the data management activity item whose importance ranking is the i-th for a predetermined period. By using the weighting coefficient 55 calculated by (Equation 1), the data management index can be calculated taking into account the importance of each of the plurality of types of management activities. In this embodiment, the data management index calculation unit 42A is provided in the server 20, but the data management index may be calculated by an external device other than the server 20.

[0068] The first point calculation unit 42B calculates the first points to be given 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 by the database administrator DA for the database DB for which the usage activity was performed. The usage activities subject to point assignment are, for example, data usage applications, reports on data usage results, and the like. 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 of 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 totals the numerical values of the data usage activity items (hereinafter sometimes referred to as evaluation values) for each database DB, and calculates the data usage index for each database DB based on the totaled numerical values of the data usage activity items.

[0070] In the present embodiment, the data usage activity items include, but are not limited to, the following ten items (B1) to (B10). Items (B1) to (B9) are quantitative evaluation items for evaluating direct usage activities for 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 result reports (B3) Number of members in the data usage result report (B4) Number of payment points at the time of database request (B5) Number of points when approving a database request (B6) Number of comments on the database (B7) Number of users who commented on the database (B8) Number of reactions to a database or database comment (B9) Number of times searched (B10) Centrality index.

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

[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 total value of the numerical values of the aggregated data usage activity items multiplied by the weighting coefficient 55 preset for each item as the data usage index. Thereby, an appropriate data usage index can be calculated according to 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 value (that is, the numerical value of the data usage activity item) 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. Specifically, the data usage index calculation unit 42C may calculate the total value of the numerical values obtained by multiplying the corrected numerical values of the aggregated data usage activity items by the weighting coefficient 55 preset for each item as the data usage index. In this case, the data usage index calculation unit 42C corrects the numerical values of the data usage activity items so as to relatively evaluate the variation in the numerical values of the data management activity items among the data usage activity items (for example, the values corrected by Z-score normalization), and calculates the total value of the numerical values multiplied by the weighting coefficient 55 calculated based on the importance of each of the plurality of types of usage activities as the data usage index. 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 of (B1) to (B10) for a predetermined period by scaling. By correcting through scaling, when there are variations in the aggregated values of each data usage activity item, each data usage activity item can be treated relatively equally. Also, the scaling method may be standardized using Z-score normalization. In that case, even when there are extreme outliers in the above aggregated values, instead of excluding the outliers, numerical values with an influence degree closer to the actual situation can be obtained. Next, the data usage index calculation unit 42C calculates, as the data usage index, the total value of the numerical values obtained by multiplying the aggregated values of each data usage activity item of (B1) to (B10) for a predetermined period, which have been corrected by scaling, by the weighting coefficient 55 calculated based on the importance of each of the plurality of types of usage activities. For example, the weighting coefficient 55 may be the numerical value calculated by the above (Equation 1). When calculating the data usage index, in (Equation 1), n is the number of items of data usage activity items (10 in this embodiment), i in (Equation 1) is the pre-set order of importance of the data usage activity items, and it is a pre-set value. In this case, (Equation 1) is an equation for calculating the weighting coefficient 55 to be multiplied by the aggregated value of the data usage activity item whose order of importance is the i-th for a predetermined period. By using the weighting coefficient 55 calculated by (Equation 1), the data usage index can be calculated taking into account the importance of each of the plurality of types of usage activities. In this embodiment, the data usage index calculation unit 42C is configured to be 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 the second point to be given to the database administrator DA using the data utilization index calculated by the data utilization index calculation unit 42C. The second point calculation unit 42D calculates the second point by multiplying the reference point set according to the type of management activity by the data utilization index indicating the degree of data utilization by the user U for the database DB for which the management activity was performed. The second point calculation unit 42D calculates the second point each time a management activity occurs. By calculating the second point as described above, the second point can be varied according to the degree of utilization activity.

[0076] The point trading unit 43 conducts point trading in the data warehouse system 1. The point trading unit 43 includes a granting unit 43A and a collection unit 43B.

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

[0078] When the user U and the database administrator DA conduct activities using points, the collection unit 43B collects the used points from the points held by the user U and the database administrator DA. For example, when the user U makes a database request using points, the points are collected from the points held by the user U.

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

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

[0081] FIG. 9 is a diagram showing an example of the point data 56 of the database administrator DA that the point transaction unit 43 stores in the storage unit 50. As shown in FIG. 9, the point transaction unit 43 may store in the storage unit 50, as the point data 56 of the database administrator DA, a table that associates an administrator ID, a management activity date and time, a management activity ID, a database ID, the held points, the points given to the management activity, and the used points.

[0082] FIG. 10 is a screen displayed on the information terminal 11 held by the user U and the database administrator DA, and is a screen showing the 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 held points, the number of acquired points this month, and the number of used points this month. On the screen 100, it may also show the usage activities performed as the user U and the management activities performed as the database administrator DA, as well as the transition of the points increased or decreased by the usage activities of other users U for the databases managed by the database administrator DA.

[0083] (Processing performed by the point management unit 40) Hereinafter, the flow of the processing (point management method) performed by the point management unit 40 will be described with reference to FIGS. 11 and 12. FIG. 11 is a flowchart showing an example of the flow of the processing performed by the point management unit 40.

[0084] As shown in FIG. 11, in the process performed by the point management unit 40, first, the acquisition unit 41 acquires from the storage unit 50, for each of the database DB, management activity information 54 indicating the management activities performed by the database administrator DA with respect to the database DB, and utilization activity information 53 indicating the utilization activities performed by the user U (step S1, acquisition step).

[0085] Next, the calculation unit 42 calculates a first point corresponding to the management activities performed by the database administrator DA based on the management activity information 54 acquired in step S1, and calculates a second point corresponding to the utilization activities performed by the user U based on the utilization 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 the process performed by the calculation unit 42.

[0087] As shown in FIG. 12, in the process performed by the calculation unit 42, first, the data management index calculation unit 42A calculates, for each database DB, a data management index indicating the degree of data management of the database administrator DA 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 totals 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 calculates, as the data management index, a value obtained by multiplying the numerical value of the totaled data management activity items by a preset weighting coefficient 55 for each item.

[0088] Next, the first point calculation unit 42B calculates the first point to be given to the user U using the data management index calculated in step S21 (step S22). Specifically, the first point calculation unit 42B first calculates the points corresponding to the usage activities performed by the user U for each database DB. Next, the first point calculation unit 42B calculates, for each database DB, a value obtained 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 point.

[0089] Next, the data usage index calculation unit 42C calculates, for each database DB, a data usage index indicating the degree of data usage of the user U based on the usage activity information 53 acquired in step S1 (step S23). Specifically, the data usage index calculation unit 42C first totals the data usage activity items for each database DB. Next, the data usage index calculation unit 42C calculates, as the data usage index, a value obtained by multiplying the numerical value of the totaled data usage activity items by the preset weighting coefficient 55 for each item.

[0090] Next, the second point calculation unit 42D calculates the second point to be given 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 the points corresponding to the management activities performed by the database administrator DA and the usage of the database DB managed by the database administrator DA himself / herself. Next, the second point calculation unit 42D calculates, as the second point, a value obtained by multiplying the calculated points by the data usage index of the database DB managed by the database administrator DA himself / herself. Steps S21 and S22, and steps S23 and 24 may be processed in the reverse order (i.e., in the order of S23, S24, S21, S22), or may be processed simultaneously.

[0091] Returning to FIG. 11, after the end of the calculation step S2, the granting unit 43A grants the first point calculated by the first point calculation unit 42B to the user U, and grants the second point 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 in which the user U becomes the database administrator DA and manages each database DB. In this case, since the management of each database DB is entrusted to the discretion and sense of responsibility of the database administrator DA, there has been a problem that it is difficult to continue the management of the database DB. On the other hand, in the data warehouse system 1 according to the present embodiment, since a mechanism for granting points to management activities is introduced, it is possible to give the database administrator DA the motivation to continue the management activities.

[0093] The data warehouse system 1 in this embodiment includes a data warehouse 10 having a plurality of 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 a first point corresponding to the management activity of the database administrator DA based on the management activity information 54 and calculates a second point corresponding to the usage activity of the user U based on the usage activity information 53, and an assignment unit 43A that assigns the first point to the user U of the database DB and assigns the second point corresponding to the usage activity of the user U with respect to the database DB to the database administrator DA of the database DB. According to this configuration, the points assigned to the user U and the database administrator DA change according to the management activity and the usage activity. Therefore, it is possible to improve the motivation of the database administrator DA or the user U to whom the points are assigned to manage or use the database DB. In addition, since the first point corresponding to the management activity is assigned to the user U and the second point corresponding to the usage activity is assigned to the database administrator DA, the points can be circulated. As a result, the management activity and the usage activity can be continuously promoted simultaneously.

[0094] According to the data warehouse system 1 of one aspect of the present invention, in order to assign and collect points that are beneficial to the database administrator DA and the user U, it is possible to continuously promote the autonomous database management activities and usage activities of the database administrator DA and the user U. Furthermore, by dynamically changing the points assigned to the database administrator DA and the user U, or the points collected from the database administrator DA and the user U according to each activity situation, it is possible to maintain the motivation of the management activity and the usage activity. Also, within the data warehouse 10, data in a state that is easy for the user U to use is managed, and the disclosure of information regarding the data is also enriched, so that the user U can easily identify and utilize data that matches the usage purpose.

[0095] In addition, in the data warehouse system 1, the data utilization index and the data management index are calculated using data management activity items and data utilization activity items that include a centrality index, which is an index indicating the centrality of the target database in the database used simultaneously. Therefore, the first point and the second point include the point (third point) calculated based on the centrality index. According to this configuration, for the user U and the database administrator DA, points can be assigned according to the degree of activity that reflects not only a quantitative evaluation of the direct activities with respect to the database DB but also a qualitative evaluation taking into account the importance in the interrelationship between databases DB. Thereby, for example, for a database DB that handles universal and important information such as master data but is not frequently managed, by using the centrality index as an item, higher data utilization index and data management index can be calculated. Therefore, points reflecting the actual situation of the management activities of the database administrator DA and the utilization activities of the user U can be assigned to the user U and the database administrator DA.

[0096] The data warehouse system 1 is operated by distributed autonomous organization-based data management. Therefore, in order to promote data utilization, it is necessary to give a certain degree of discretion to the user U, while strict restrictions on data access permission and handling are required. To address this issue, in the data warehouse system 1, the utilization activities of the user U are shared with other users U as metadata 60. As a result, the utilization activities of the user U are made transparent, and data governance can be strengthened.

[0097] The data warehouse system 1 in this embodiment includes a data warehouse 10 having a plurality of databases DB, and a control unit 30 that receives a search for metadata 60 of the plurality of databases DB from a user U. The metadata 60 includes information related to the user U's usage activities with respect to the database DB and the management activities by the database administrator DA of the database. According to the above configuration, when the user U searches for the metadata 60, the user U can refer to the information related to the usage activities and the information related to the management activities, so that the user U can identify and easily utilize the data that matches the usage purpose.

[0098] 〔Example of realization by software〕 The functions of the server 20 (hereinafter referred to as "device") can be realized by a program for causing a computer to function as the device, and by a program for causing a computer to function as each control block of the device (especially each part included in the control unit 30).

[0099] In this case, the above device includes a computer having at least one control device (for example, a processor) and at least one storage device (for example, a memory) as hardware for executing the above program. By executing the above program by this control device and storage device, each function described in the above embodiments is realized.

[0100] The above program may be recorded on one or more computer-readable recording media instead of being temporary. The recording medium may or may not be provided in the above device. In the latter case, the above program may be supplied to the above device via any wired or wireless transmission medium.

[0101] Part or all of the functions of the above control blocks can also be realized by a logic circuit. For example, an integrated circuit in which a logic circuit functioning as each of the above control blocks is formed is also included in the scope of the present invention. In addition to this, for example, it is also possible to realize the functions of the above control blocks by a quantum computer.

[0102] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope indicated in 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〕 The 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 databases included in a data warehouse having a plurality of databases, and usage activity information indicating usage activities performed by users on the databases, a calculation unit that calculates a first point corresponding to the management activity based on the management activity information and calculates a second point corresponding to the usage activity based on the usage activity information, and an assignment unit that assigns the first point corresponding to the management activity on the database to the user of the database and assigns the second point corresponding to the usage activity on the database to the administrator of the database.

[0104] The point management device according to Aspect 2 of the present disclosure, in the above Aspect 1, the calculation unit may be configured to calculate a data management index indicating the degree of data management by the administrator from the management activity information of the database and calculate the first point based on the data management index for each of the usage activities on the database.

[0105] The point management device according to Aspect 3 of the present disclosure, in the above Aspect 2, the calculation unit may be configured to calculate the data management index based on evaluation values obtained by evaluating each of a plurality of types of the management activities and the importance of each of the plurality of types of the management activities.

[0106] In the aspect 4 of the present disclosure, in the above aspect 2 or 3, the calculation unit may be configured to calculate the data management index based on a value obtained by correcting an evaluation value obtained by evaluating each of the plurality of types of management activities by Z-score normalization and the importance of each of the plurality of types of management activities.

[0107] In the aspect 5 of the present disclosure, in any one of the above aspects 1 to 4, the calculation unit may be configured to calculate a data utilization index indicating the degree of data utilization of the user from the utilization activity information of the database, and calculate the second point based on the data utilization index for each of the management activities for the database.

[0108] In the aspect 6 of the present disclosure, in the above aspect 5, the calculation unit may be configured to calculate the data utilization index based on an evaluation value obtained by evaluating each of the plurality of types of utilization activities and the importance of each of the plurality of types of utilization activities.

[0109] In the aspect 7 of the present disclosure, in the above aspect 5 or 6, the calculation unit may be configured to calculate the data utilization index based on a value obtained by correcting an evaluation value obtained by evaluating each of the plurality of types of utilization activities by Z-score normalization and the importance of each of the plurality of types of utilization activities.

[0110] In the aspect 8 of the present disclosure, in any one of the above aspects 1 to 7, the metadata of the data stored in the database may be configured to include information related to the utilization activity and the management activity.

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

[0112] The 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 databases included in a data warehouse having a plurality of databases, and usage activity information indicating usage activities performed by users on the databases, a calculation step of calculating a first point corresponding to the management activity based on the management activity information and calculating a second point corresponding to the usage activity based on the usage activity information, and an assignment step of assigning the first point corresponding to the management activity on the database to the user of the database and assigning the second point corresponding to the usage activity on the database to the administrator of the database.

[0113] The point management method according to aspect 11 of the present disclosure is a program for causing a computer to function as the point management device according to aspect 1 above, and is a program for causing a computer to function as the acquisition unit, the calculation unit, and the assignment unit.

[0114] The data warehouse system according to aspect 12 of the present disclosure includes 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 a first point corresponding to the management activity based on the management activity information and calculates a second point corresponding to the usage activity based on the usage activity information, and (3) assigns the first point corresponding to the management activity on the database to the user of the database and assigns the second point corresponding to the usage activity on the database to the administrator of the database.

Description of Reference Numerals

[0115] 1 Data warehouse system 10 Data warehouse 40 Point management unit (point management device) 41 Acquisition unit 42 Calculation unit 43A Attachment unit 60 Metadata

Claims

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

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

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

4. The calculation unit calculates the data management index based on a value obtained by correcting an evaluation value obtained by evaluating each of a plurality of types of the management activities by Z-score normalization and the importance of each of the plurality of types of the management activities. The point management device according to claim 2.

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

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

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

8. The metadata of the data stored in the database includes information related to the usage activity and the management activity. The point 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 the centrality of the database in the plurality of databases. The point management device according to claim 1.

10. An acquisition step of acquiring management activity information indicating a management activity performed by an administrator on a database included in a data warehouse having a plurality of databases, and usage activity information indicating a usage activity performed by a user on the database; A calculation step of calculating a first point corresponding to the management activity based on the management activity information, and calculating a second point corresponding to the usage activity based on the usage activity information; An assignment step of assigning the first point corresponding to the management activity on the database to the user of the database, and assigning the second point corresponding to the usage activity on the database to the administrator of the database. A point management method including:

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

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

Images