JP2013171495A - Data management device, data management method and data management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily provide a data transition.SOLUTION: A data management device comprises: a memory section; a storage section; and a retrieval section. The memory section stores attribute information about a predetermined thing and an expiration date indicating a date that the attribute information corresponds to an attribute of the thing in association with each other. The storage section updates an expiration date indicating that a present time is within the expiration date among expiration dates stored in the memory section to a date that the latest attribute information corresponding to the expiration date does not correspond to the attribute of the thing when receiving an update request for updating the attribute information, and stores a new attribute information included in the update request and an expiration date indicating that the new attribute information corresponds to the attribute of the thing at the present time in the memory section. The retrieval section retrieves attribute information included in a retrieval request from the memory section when receiving the retrieval request of the attribute information.

Description

  Embodiments described herein relate generally to a data management device, a data management method, and a data management program.

  Conventionally, in an information system, a large amount of data is often managed by a data storage device or the like. For example, in an information system in a company, a huge amount of data is managed as a shared asset. In such a data storage device, the latest data is held, and the data change history is often held as a log (for example, a transaction log). For this reason, the user can acquire past data by referring to the data change log.

  Here, an example of a technique related to the enormous data and change log described above will be described. As described above, an enormous amount of data exists in a company, but such enormous data is accumulated in different information systems or in different formats for each organization. In recent years, techniques for effectively utilizing such a large amount of data are known. For example, EAI (Enterprise Application Integration) that links data by linking information systems within a company, knowledge management for sharing knowledge within a company, and basic information that is commonly held in many databases ( For example, technologies such as MDM (Master Data Management) for integrating and utilizing master data, such as information on products, customers, accounting, and employees, are known. In addition, in DWH (Data WareHouse), analysis including temporal changes using not only current data but also past data is becoming possible.

  In the above example, the MDM basically holds only the latest data as master data, and omits management of past data, thereby reducing data and reducing data access processing. In addition, in the MDM, since a change log of master data is often retained, past data can be referred to.

MDM One MI, “ASTERIA MDM One MI Function List”, [online], [Search February 1, 2012], Internet <http://www.infoteria.com/jp/asteriamdmone/product/mi_function.php>

  However, with the conventional data management method, it is difficult to easily provide data transition. For example, it is assumed that the above-described master data holds data regarding employee IDs and affiliated organizations, and the user views changes in affiliated organizations of specific employees. At this time, when data management is performed by the above-described conventional method, it is considered that the user can browse the transition of the organization to which the user belongs by analyzing the transaction log itself in which the transition of the data is stored. It is done. However, with this method, a large amount of transaction logs are analyzed, which increases the time and effort for the user. It is also considered that the user can browse past data by rolling back using a transaction log. However, such a technique requires rolling back to the master data state at a plurality of past points in time, so that it is not realistic as a work for browsing data transition. For this reason, it is difficult to provide the user with specific data transitions by the conventional data management method.

  The technology disclosed in the present application has been made in view of the above, and an object thereof is to provide a data management device, a data management method, and a data management program capable of easily providing data transition.

  The data management apparatus according to the embodiment updates attribute information related to a predetermined thing, a storage unit that associates and stores an expiration date indicating a time limit corresponding to the attribute of the thing, and the attribute information. When an update request is received, an expiration date indicating that the current time is within the expiration date among the expiration dates stored in the storage unit, and the latest attribute information corresponding to the expiration date is the Update to a date that no longer corresponds to an attribute, and store in the storage unit new attribute information included in the update request and an expiration date indicating that the new attribute information currently corresponds to the attribute of the thing And a search unit that searches the storage unit for attribute information included in the search request when a search request for the attribute information is received.

  The data management device, the data management method, and the data management program according to the embodiment have an effect that data transition can be easily provided.

FIG. 1 is a diagram illustrating a configuration example of a data management apparatus according to the first embodiment. FIG. 2 is a diagram illustrating an example of a master data table according to the first embodiment. FIG. 3 is a flowchart illustrating the storage processing procedure performed by the data management apparatus according to the first embodiment. FIG. 4 is a flowchart illustrating a search processing procedure performed by the data management apparatus according to the first embodiment. FIG. 5 is a diagram illustrating an example of data included in the data management apparatus according to the reference example. FIG. 6 is a flowchart illustrating a search processing procedure performed by the data management apparatus according to the reference example. FIG. 7 is a diagram illustrating a configuration example of the data management apparatus according to the second embodiment. FIG. 8 is a diagram illustrating an example of an employee ID table according to the second embodiment. FIG. 9 is a diagram illustrating an example of the organization history table according to the second embodiment. FIG. 10 is a diagram illustrating an example of the extension history table according to the second embodiment. FIG. 11 is a flowchart illustrating a storage processing procedure performed by the data management apparatus according to the second embodiment. FIG. 12 is a flowchart illustrating a search processing procedure performed by the data management apparatus according to the second embodiment. FIG. 13 is a diagram illustrating an example of an attribute management table according to the second embodiment. FIG. 14 is a diagram illustrating a computer that executes a data management program.

  Hereinafter, embodiments of a data management device, a data management method, and a data management program according to the present application will be described in detail with reference to the drawings. The data management apparatus, data management method, and data management program according to the present application are not limited to the embodiment.

[Configuration of Data Management Device According to Embodiment 1]
First, the data management apparatus according to the first embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a configuration example of the data management apparatus 100 according to the first embodiment. In the first embodiment, it is assumed that the data management apparatus 100 illustrated in FIG. 1 stores master data that is basic information (for example, information about products, customers, accounts, employees, and the like).

  As illustrated in FIG. 1, the data management apparatus 100 according to the first embodiment includes an IF (interface) unit 110, a storage unit 120, a reception unit 131, a storage unit 132, and a search unit 133.

  The IF unit 110 transmits and receives data to and from devices other than the data management device 100. For example, the IF unit 110 is realized by an electronic circuit that performs communication control, a NIC (Network Interface Card), or the like.

  The storage unit 120 is a storage device that stores various data, and is realized by, for example, a hard disk, an optical disk, or a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory (Flash Memory).

  The storage unit 120 according to the first embodiment includes a master data table 121 as illustrated in FIG. The master data table 121 stores attribute information related to a predetermined thing and an expiration date indicating a period during which the attribute information corresponds to the attribute of the thing.

  Here, FIG. 2 shows an example of the master data table 121 according to the first embodiment. The master data table 121 illustrated in FIG. 2 stores each piece of attribute information related to an employee that is a specific thing. Specifically, as shown in FIG. 2, the master data table 121 includes items such as “ID”, “employee ID”, “organization name”, “extension”, “room number”, “startDate”, and “endDate”. Have “Employee ID”, “Organization name”, “Extension”, and “Room number” correspond to employee attribute information.

  “ID” indicates identification information for identifying a record stored in the master data table 121. That is, “ID” corresponds to a primary key in the master data table 121.

  “Employee ID” indicates identification information for identifying an employee. Such “employee ID” is assigned to each employee in the company. “Organization name” indicates the name of the organization or department to which the employee belongs. “Extension” indicates an extension telephone number assigned to the employee. The “room number” indicates identification information for identifying a building or a room where the employee performs his / her duties, for example, a room where the employee's work desk is placed.

  “StartDate” indicates the first date when each piece of attribute information in the record including the startDate corresponds to the employee attribute, or the date when the record including the startDate is stored in the master data table 121. “EndDate” is the last date when each attribute information in the record including the endDate corresponds to the employee attribute, or the date when the new record next to the record including the endDate is stored in the master data table 121. Indicates the previous day. In addition, as in the example shown in FIG. 2, when each attribute information in the record still corresponds to the employee attribute, the information is not stored in “endDate”, or the attribute also corresponds to the attribute at present. Is stored (for example, a date “3000-1-1” or the like on which the data management apparatus 100 is assumed not to be operated). In the following embodiments, description will be made using an example in which information is not stored in “endDate” when each piece of attribute information still corresponds to an employee attribute.

  That is, each attribute information (employee ID, organization name, extension, room number) stored in the master data table 121 is attributed to the employee attribute between the date indicated by “startDate” and the date indicated by “endDate”. Indicates that this is the case. In other words, “startDate” and “endDate” indicate a time limit during which each piece of attribute information in the record is valid as employee attribute information.

  For example, the record identified by the ID “000001” shown in FIG. 2 indicates that the employee with the employee ID “1122” is from October 1, 2009 (“startDate”) to March 31, 2010 (“endDate”). In FIG. 5, the extension number “1111” belongs to the organization (department) with the organization name “G11”, and the job is performed in the room indicated by the room number “1-1001”.

  Further, for example, the record identified by the ID “000003” shown in FIG. 2 indicates that the employee with the employee ID “1122” has the organization name “G13” since December 1, 2011 (“startDate”). It indicates that it belongs to an organization (department), is assigned an extension number “3333”, and is performing duties in the room indicated by the room number “1-1001”.

  As described above, the master data table 121 according to the first embodiment stores the attribute information of each employee, and manages the history of each attribute information according to the expiration date (“startDate” and “endDate”).

  The master data table 121 according to the first embodiment stores at least identification information for identifying a specific thing (hereinafter referred to as “specific information”) when storing attribute information indicating the attribute of the specific thing. Remember). For example, the master data table 121 illustrated in FIG. 2 stores “employee ID”, “organization name”, “extension”, and “room number” as attributes of a specific thing “employee”. In the case of this example, the master data table 121 stores specific information “employee ID” for identifying an employee as a specific thing.

  2 illustrates an example in which the master data table 121 stores “ID”. In the following embodiment, an example in which the master data table 121 stores “ID” will be described. However, when the primary key is unnecessary, the master data table 121 does not need to store “ID”.

  Returning to the description of FIG. 1, the accepting unit 131 accepts an update request for updating the master data table 121 via the IF unit 110. For example, the reception unit 131 receives update data together with an update request from another device that requests an update of the master data table 121.

  Here, update data received by the receiving unit 131 according to the first embodiment will be described. It is assumed that the update data in the first embodiment includes all attribute information stored in the master data table 121. For example, in the case of the example shown in FIG. 2, the master data table 121 includes employee ID, organization name, extension, and room number even if it is update data for updating only the organization name. The update data in the first embodiment may include a plurality of records that are combinations of such employee IDs, organization names, extensions, and room numbers.

  In addition, the update data according to the first embodiment may include a date for validating the attribute information to be updated (hereinafter, sometimes referred to as “valid date”). The “valid date” indicates the first date when the attribute information to be updated corresponds to the attribute of the specific thing. In other words, the “effective date” indicates the date when the change of the organization, extension, and room number is issued to the employee. For example, in the example shown in FIG. 2, it is assumed that the employee with the employee ID “2233” belongs to the organization with the organization name “G13” with “January 1, 2012”. At this time, the update data for updating the organization name of the employee ID “2233” to “G13” includes the first date that the employee belongs to the new organization in addition to the employee ID “2233” and the organization name “G13”. “January 1, 2012 (as data, 2012-1-1, 20120101, etc.)” may be included. The transmission source of the update data includes the effective date in the update data, so that the update date of the attribute information is displayed in the master data table 121 without sending the update data to the data management apparatus 100 on the date when the attribute information is changed. You can register.

  In the above example, the data management apparatus 100 receives the update data from another apparatus. However, the data management apparatus 100 may accept the update data by being directly operated by the user. For example, the data management apparatus 100 may include an input unit (keyboard, mouse, etc.) and a display unit (liquid crystal display device, etc.) not shown, and update data may be input by the user via the input unit. In such a case, the accepting unit 131 accepts update data input via the input unit.

  The storage unit 132 stores the update data received by the receiving unit 131 in the master data table 121. Specifically, when the update request is received, the storage unit 132 applies the expiration date (startDate, endDate) corresponding to the attribute information of the newest employee among the attribute information stored in the master data table 121. Update the expiration date to indicate that the new attribute information is no longer an employee attribute. Further, the storage unit 132 stores new attribute information included in the update request and an expiration date indicating that the new attribute information currently corresponds to the employee attribute in the master data table 121.

  More specifically, the storage unit 132 determines whether or not the same information as the specific information included in the update data is stored in the master data table 121 when the update data is received by the reception unit 131. To do. In other words, the storage unit 132 determines whether a record to be updated exists in the master data table 121. For example, in the example of the master data table 121 shown in FIG. 2, attribute information related to the employee is stored, so that the update data includes at least the employee ID. In the case of this example, when the specific information “employee ID” included in the update data is stored in the master data table 121, the storage unit 132 determines that there is a record to be updated. On the other hand, if the specific information “employee ID” included in the update data is not stored in the master data table 121, the storage unit 132 determines that there is no record to be updated.

  When there is no record to be updated, the storage unit 132 stores each attribute information included in the update data in the master data table 121 as a new record. At this time, the storage unit 132 stores the effective date in “startDate” when the update data includes the effective date, and stores the current date in “startDate” when the update data does not include the effective date. Store. In addition, the storage unit 132 does not store information in “endDate”.

  On the other hand, when there is a record to be updated, the storage unit 132 specifies a record in which information is not stored in “endDate” among the records to be updated as the latest record. Then, the storage unit 132 determines whether or not each attribute information stored in the latest record is the same as each attribute information included in the update data. At this time, if the update data and the latest record are the same, the storage unit 132 does not perform a storage process using the update data.

  On the other hand, when the update data and the latest record are not the same, the storage unit 132 stores the date obtained by subtracting “1 day (24 hours)” from the valid date included in the update data in “endDate” of the latest record. At this time, when the update data does not include the valid date, the storage unit 132 stores the date obtained by subtracting “1 day (24 hours)” from the current date in “endDate” of the latest record. In addition, the storage unit 132 stores the update data received by the receiving unit 131 in the master data table 121 as a new record. At this time, the storage unit 132 stores the effective date or the current date in “startDate” and does not store the information in “endDate”, as in the above example.

  The storage processing by the storage unit 132 will be described using the example shown in FIG. Here, it is assumed that only the record with ID “000001” is stored in the master data table 121. In this state, the reception unit 131 receives update data including the employee ID “1122”, the organization name “G12”, the extension “1111”, the room number “1-1001”, and the effective date “2010-4-1”. Shall be. In such a case, the storage unit 132 determines whether or not the employee ID “1122” included in the update data is stored in the master data table 121. In this example, since the employee ID “1122” is stored in the master data table 121, the storage unit 132 determines that there is a record to be updated. In such a case, the storage unit 132 identifies a record whose “endDate” is NULL among the records that match the employee ID “1122” (the record whose employee ID is “1122”) as the latest record. In this example, the storage unit 132 identifies the record having the ID “000001” as the latest record.

  Then, the storage unit 132 adds a date “2010-3-31” obtained by subtracting one day from the effective date “2010-4-1” included in the update data to the “endDate” of the record whose ID is “000001”. Store. Further, the storage unit 132 stores the employee ID “1122”, the organization name “G12”, the extension “1111”, and the room number “1-1001” included in the update data in the master data table 121 as new records. At this time, the storage unit 132 stores the effective date “2010-4-1” in “startDate” of the new record and does not store information in “endDate”. In this way, the storage unit 132 newly stores a record such as the example indicated by the ID “000002” in FIG. 2 in the master data table 121.

  The storage unit 132 assigns a number that is not stored in the master data table 121 to the ID of the new record. For example, the storage unit 132 sets a value obtained by incrementing “1” to the maximum value of the ID stored in the master data table 121 as the ID of the new record.

  Further, after the above example, the reception unit 131 causes the reception unit 131 to update data including the employee ID “1122”, the organization name “G13”, the extension “3333”, the room number “1-1001”, and the effective date “2011-12-1”. Is accepted. In this case, the storage unit 132 stores “2011-11-30” in “endDate” of the record whose ID is “000002”, and the ID is “000003”, as in the example illustrated in FIG. Store records.

  Also, update data including an employee ID “2233”, an organization name “G12”, an extension “2222”, a room number “1-1001”, and an effective date “2011-4-1” is received by the reception unit 131. And In this case, since the employee ID “2233” is not stored in the master data table 121, the storage unit 132 stores the record having the ID “000004” in the master data table 121 as in the example illustrated in FIG. 2. Store new.

  When the search unit 133 receives a search request via the IF unit 110, the search unit 133 searches various data from the master data table 121 according to the search request. For example, the search unit 133 receives a search request including specific information and the name (column name) of attribute information to be searched. In this case, the search unit 133 searches the master data table 121 for “search target attribute information” and “startDate” using the specific information included in the search request as a key. Then, the search unit 133 sorts the attribute information of the search results in descending order of startDate. Furthermore, when the same attribute information is continuously present in the sorted attribute information, the search unit 133 deletes other attribute information other than the last attribute information from the consecutive attribute information. And the search part 133 produces | generates the search result list | wrist with which attribute information and startDate after sorting and duplication information deletion were described, and notifies the produced | generated search result list | wrist to the transmission origin of a search request.

  The search process by the search unit 133 will be described using the example shown in FIG. For example, it is assumed that the search unit 133 receives a search request including the employee ID “1122” and the name “extension” of the attribute information to be searched. In this case, the search unit 133 searches the master data table 121 using the employee ID “1122” as a key, thereby acquiring “extension” and “startDate”. In this example, the search unit 133 includes the combination of the extension “1111” and the startDate “2009-10-1”, the combination of the extension “1111” and the startDate “2010-4-1”, and the extension “3333” and the startDate. The combination of “2011-12-1” is acquired. Then, the search unit 133 sorts the extensions into “3333”, “1111”, and “1111” by sorting in descending order of the startDate. Furthermore, since the extension “1111” exists continuously, the search unit 133 deletes the leading “1111” from the two extensions. Then, the search unit 133 notifies the search request source of the search result list described in the order of the extension “3333” and the startDate “2011-12-1”, the extension “1111”, and the startDate “2009-10-1”. To do. As a result, the user who refers to the search result list can check the transition of the extension number assigned to the employee whose employee ID is “1122”.

  In the above description, the search unit 133 has shown an example in which the search results are rearranged in descending order of the startDate. However, the search unit 133 may rearrange the search results in ascending order of startDate. Further, the search unit 133 may search for endDate instead of startDate. In such a case, the search unit 133 sorts the attribute information whose endDate is NULL as the latest attribute information. Moreover, the search part 133 may search both startDate and endDate.

  In the above example, the data management apparatus 100 receives a search request from another apparatus, but the data management apparatus 100 may accept the search request by being directly operated by a user. For example, the data management apparatus 100 may include an input unit and a display unit (not shown), and a search request may be input by a user via the input unit. In such a case, the search unit 133 performs the search process according to the search request input via the input unit.

  Moreover, the reception unit 131, the storage unit 132, and the search unit 133 illustrated in FIG. 1 are realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). Further, for example, the reception unit 131, the storage unit 132, and the search unit 133 may store a program stored in a storage device (not shown) by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like (Random Access Memory). Is implemented as a work area.

[Storage Processing Procedure by Data Management Device According to Embodiment 1]
Next, the procedure of storage processing by the data management apparatus 100 according to the first embodiment will be described with reference to FIG. FIG. 3 is a flowchart illustrating the storage processing procedure performed by the data management apparatus 100 according to the first embodiment. Hereinafter, a case where the master data table 121 stores various types of information illustrated in FIG. 2 will be described as an example. That is, the data management apparatus 100 accepts update data including an employee ID as specific information.

  As illustrated in FIG. 3, the storage unit 132 of the data management apparatus 100 performs the processing illustrated in the loop 1 by the number of rows (number of records) included in the update data when the update data is received by the reception unit 131. Repeat.

  Specifically, the storage unit 132 determines whether or not the same information as the specific information “employee ID” included in the update data in the first row exists in the master data table 121 (step S101).

  When the employee ID of the update data does not exist in the master data table 121 (No at Step S101), the storage unit 132 stores the employee ID and each attribute information (organization name, extension, room number, etc.) included in the update data. Then, startDate and endDate are stored as new records in the master data table 121 (step S102). At this time, the storage unit 132 stores the effective date in the startDate when the update data includes the effective date, and stores the current date (that is, the update date) in the startDate when the update data does not include the effective date. ). The storage unit 132 does not store information in endDate.

  On the other hand, when the employee ID of the update data exists in the master data table 121 (Yes in step S101), the storage unit 132 stores each attribute information stored in the latest record among the records that match the employee ID. It is determined whether or not all pieces of attribute information included in the update data are the same (step S103). When the same attribute information as the attribute information of the update data is stored in the latest record (Yes at Step S103), the storage unit 132 does not perform the storage process using the update data.

  On the other hand, when the update data and the latest record are not the same (No at Step S103), the storage unit 132 subtracts “one day” from the effective date included in the update data, or the current date (update date). The date obtained by subtracting “1 day” from “endDate” of the latest record is stored (step S104). Further, the storage unit 132 stores the employee ID, each attribute information (organization name, extension, room number, etc.), startDate and endDate included in the update data as new records in the master data table 121 (step S105). At this time, the storage unit 132 stores the effective date in the startDate when the update data includes an effective date, and stores the current date (update date) in the startDate when the update data does not include the effective date. Store. The storage unit 132 does not store information in endDate.

[Search Processing Procedure by Data Management Device According to Embodiment 1]
Next, a search process procedure performed by the data management apparatus 100 according to the first embodiment will be described with reference to FIG. FIG. 4 is a flowchart illustrating the search processing procedure performed by the data management apparatus 100 according to the first embodiment. Hereinafter, a case where the master data table 121 stores various types of information illustrated in FIG. 2 will be described as an example.

  As shown in FIG. 4, when receiving a search request, the search unit 133 of the data management apparatus 100 searches the master data table 121 for search target attribute information using the employee ID included in the search request as a key ( Step S201). At this time, the search unit 133 also searches for startDate.

  Then, the search unit 133 sorts the attribute information of the search results based on the startDate (Step S202). For example, the search unit 133 sorts the attribute information of the search results in order from the newest. And the search part 133 deletes other attribute information except the last attribute information among the attribute information continuous in the attribute information after a sort (step S203). Thereafter, the search unit 133 notifies the search result transmission source of the search result list.

[Effect of Example 1]
As described above, in the data management apparatus 100 according to the first embodiment, the storage unit 120 includes attribute information related to a predetermined thing, and an expiration date (corresponding to endDate) indicating a time limit when the attribute information corresponds to the attribute of the thing. Are stored in association with each other. Further, when receiving an update request for updating the attribute information, the storage unit 132 takes an expiration date indicating that the current time is within the expiration date among the expiration dates stored in the master data table 121. Update to the expiration date indicating that the latest attribute information corresponding to the expiration date no longer corresponds to the attribute of the thing. Further, the storage unit 132 stores new attribute information included in the update request and an expiration date indicating that the new attribute information currently corresponds to the attribute of the object in the master data table 121. Further, when receiving a search request for attribute information, the search unit 133 searches the master data table 121 for attribute information included in the search request.

  As described above, the data management apparatus 100 according to the first embodiment manages the change history of the attribute information together with each attribute information in the master data table 121 as the expiration date. In other words, the data management apparatus 100 does not manage the change history of each attribute information as a log, but manages it in the same master data table 121. Thereby, the data management apparatus 100 according to the first embodiment can easily search for the transition of the data stored in the master data table 121, and therefore can easily provide the transition of the data.

  Further, in the data management apparatus 100 according to the first embodiment, the storage unit 132 determines that the latest attribute is included when the new attribute information included in the update request is different from the latest attribute information stored in the master data table 121. The expiration date corresponding to the information is updated, and new attribute information is stored in the master data table 121.

  Thereby, the data management apparatus 100 according to the first embodiment can prevent the same attribute information from being stored in the master data table 121 continuously. As a result, the data management apparatus 100 can update the master data table 121 when there is a data transition even when the same update data is received in duplicate. Can be provided.

[Data management device according to reference example]
Here, in order to clarify the effect of the data management apparatus 100 according to the first embodiment, data management by the data management apparatus 900 according to the reference example will be described with reference to FIGS. 5 and 6. The data management apparatus 900 according to the reference example corresponds to an example of a data management apparatus that can be generally considered. FIG. 5 is a diagram illustrating an example of data included in the data management apparatus 900 according to the reference example. In the example illustrated in FIG. 5, the data management apparatus 900 includes a master data table 91 and a log data table 92.

  The master data table 91 holds only the latest data. That is, the master data table 91 shown in FIG. 5 stores the organization name “G13”, the extension “3333”, and the room number “1-1001” as the current attribute information of the employee with the employee ID “1122”. The organization name “G12”, extension “2222”, and room number “1-1001” are stored as the current attribute information of the employee with the employee ID “2233”. As described above, generally, the data management apparatus 900 holds only the latest master data as in the example shown in the master data table 91. The log data table 92 stores an update log of the master data table 91. In the example illustrated in FIG. 5, the log data table 92 stores an update command (such as an SQL statement) used at the time of updating the master data table 91 in the changed content.

  When the data management device 900 holds the master data table 91 and the log data table 92 described above, the user can confirm the transition of the organization to which a specific employee belongs by analyzing the log data table 92, for example. It is thought that it becomes. However, since an enormous log is stored in the log data table 92, the method for analyzing the log data table 92 increases the time and effort required for the user. In addition, it is considered that the user can confirm the transition of the organization belonging to a specific employee by browsing past data by rolling back the master data table 91 using the master data table 91. However, this method is not practical because it requires many times to roll back to the master data state at a plurality of past time points.

  It is also conceivable that the data management device 900 analyzes the log data table 92 and outputs the change of the organization to which a specific employee belongs. However, the analysis processing of the log data table 92 becomes complicated, and the load on the data management device 900 increases. This point will be described with reference to FIG. FIG. 6 is a flowchart illustrating a search processing procedure performed by the data management apparatus 900 according to the reference example. FIG. 6 shows a process that can be considered as a search process by the data management apparatus 900. Here, a case where the data management apparatus 900 searches for the transition of the organization name in the employee ID “1122” will be described as an example.

  In the example illustrated in FIG. 6, when the data management apparatus 900 receives a search request for searching for the organization name of the employee ID “1122”, the data management apparatus 900 reads the organization name “1122” of the organization ID “1122” from the master data table 91. "G13" is retrieved and stored as the latest organization name (step S11). Subsequently, the data management apparatus 900 searches the log data table 92 for changes made using the employee ID “1122” as a key (step S12). Then, the data management apparatus 900 sorts the search results in order from the newest (step S13).

  Subsequently, the data management apparatus 900 repeatedly performs the process shown in the loop 1 by the number of search results (the number of changes). Specifically, the data management apparatus 900 determines whether or not an organization name change or an organization name addition is included in the latest change content that is a search result after sorting (step S14). For example, the data management apparatus 900 determines whether or not the change content includes the character strings “update” and “organization name”, and the change content includes the character strings “insert” and “organization name”. Or not. When the change content includes an organization name change or an organization name addition (Yes at step S14), the data management apparatus 900 determines whether the organization name included in the change content is different from the latest organization name. (Step S15). If the data management device 900 is different from the latest organization name (Yes at step S15), the data management device 900 retains the organization name included in the changed content as the new latest organization name while retaining the latest organization name (step S16). ). The data management apparatus 900 repeatedly performs the processes in steps S14 to S16 in the order of the changed contents with respect to the changed contents after sorting.

  In this way, the data management apparatus 900 searches for the transition of the organization name in the employee ID “1122”. However, when the data management apparatus 900 performs the processing of FIG. 6, the processing load increases because the SQL sentence or the like is analyzed in step S14. Further, the processing procedure shown in FIG. 6 has a large number of processing steps and poor processing efficiency as compared with the search processing (see FIG. 4) by the data management apparatus 100 according to the first embodiment.

  As described above, the data management apparatus 100 according to the first embodiment can easily search for the transition of data stored in the master data table 121, and as a result, can easily provide the transition of data. it can.

  In the first embodiment, the example in which the data management apparatus 100 holds the master data table 121 illustrated in FIG. 2 has been described. However, the data management apparatus may divide and hold the master data table for each attribute information. In the second embodiment, an example in which the master data table is divided and held for each attribute information will be described.

[Configuration of Data Management Apparatus According to Second Embodiment]
First, the data management apparatus according to the second embodiment will be described with reference to FIG. FIG. 7 is a diagram illustrating a configuration example of the data management apparatus 200 according to the second embodiment. In addition, below, the detailed description is abbreviate | omitted as attaching | subjecting the same code | symbol to the site | part which has the function similar to the already shown component site | part. As illustrated in FIG. 7, the data management apparatus 200 according to the second embodiment includes a storage unit 220, a storage unit 232, and a search unit 233.

  The storage unit 220 is realized by a semiconductor memory element such as a hard disk, an optical disk, or a RAM or a flash memory, for example. The storage unit 220 according to the second embodiment stores the change history of attribute information in different history tables for each type of attribute information stored in the master data table 121 illustrated in FIG. Specifically, as illustrated in FIG. 7, the storage unit 220 includes an employee ID table 221, an organization history table 222, and an extension history table 223.

  The employee ID table 221 stores employee IDs of employees. FIG. 8 shows an example of the employee ID table 221 according to the second embodiment. As shown in FIG. 8, the employee ID table 221 has items such as “employee ID”, “startDate”, and “endDate”. These items correspond to the items shown in FIG.

  “Employee ID” corresponds to the employee ID shown in FIG. The “employee ID” corresponds to a main key in the employee ID table 221. “StartDate” indicates the first date when the employee ID in the record including the startDate corresponds to the attribute of the employee, or the date when the record including the startDate is stored in the employee ID table 221. “EndDate” is the last date when the employee ID in the record including the endDate corresponds to the attribute of the employee, or the day before the date when the new record next to the record including the endDate is stored in the employee ID table 221 Indicates. In the second embodiment, the employee ID of the employee is not changed. That is, no information is stored in “endDate” of the employee ID table 221. However, when an employee retires, “end date” or the like is stored in “endDate” of the employee ID table 221 corresponding to the employee.

  The organization history table 222 stores an organization name change history for each employee. FIG. 9 shows an example of the organization history table 222 according to the second embodiment. As illustrated in FIG. 9, the organization history table 222 includes items such as “employee ID”, “organization name”, “startDate”, and “endDate”.

  “Employee ID” corresponds to the employee ID shown in FIG. The “employee ID” corresponds to a foreign key that refers to the employee ID in the employee ID table 221. “Organization name” corresponds to the organization name shown in FIG. “StartDate” indicates the first date when the organization name in the record including the startDate corresponds to the employee attribute, or the date when the record including the startDate is stored in the organization history table 222. “EndDate” indicates the last date when the organization name in the record including the endDate corresponds to the attribute of the employee, or the day before the date stored in the new organization history table 222 next to the record including the endDate. .

  The extension history table 223 stores an extension change history for each employee. FIG. 10 shows an example of the extension history table 223 according to the second embodiment. As illustrated in FIG. 10, the extension history table 223 includes items such as “employee ID”, “extension”, “startDate”, and “endDate”.

  “Employee ID” corresponds to the employee ID shown in FIG. 8 and corresponds to an external key with the employee ID in the employee ID table 221 as a reference destination. The “extension” corresponds to the extension shown in FIG. “StartDate” indicates the first date when the extension in the record including the startDate corresponds to the employee attribute, or the date when the record including the startDate is stored in the extension history table 223. “EndDate” indicates the last date when the extension in the record including the endDate corresponds to the employee attribute, or the day before the date stored in the new extension history table 223 next to the record including the endDate.

  Although not shown in FIG. 7, the storage unit 220 according to the second embodiment stores, in addition to the above-described tables, a history table that stores a change history of such attribute information for each attribute information of each employee. Have For example, the storage unit 220 includes a “room number history table” that stores room number change history for each employee.

  Returning to the description of FIG. 7, the storage unit 232 stores the update data received by the receiving unit 131 in the employee ID table 221, the organization history table 222, the extension history table 223, and the like in the storage unit 220.

  Specifically, when update data is received by the reception unit 131, the storage unit 232 stores the same information as the specific information (employee ID in this example) included in the update data in the employee ID table 221. It is determined whether or not it has been done. When the employee ID of the update data is not stored in the employee ID table 221, the storage unit 232 stores the employee ID included in the update data as a new record in the employee ID table 221. At this time, the storage unit 232 stores the effective date in “startDate” when the update data includes the effective date, and stores the current date in “startDate” when the update data does not include the effective date. Store. In addition, the storage unit 232 stores no information in “endDate”.

  In addition, the storage unit 232 selects a history table corresponding to the type of attribute information included in the update data from the storage unit 220. Then, the storage unit 232 stores whether or not the same information as the specific information (employee ID in this example) included in the update data is stored in the selected history table (hereinafter referred to as “selection table”). Determine. When the employee ID of the update data is not stored in the selection table, the storage unit 232 stores the employee ID and attribute information included in the update data as a new record in the selection table. At this time, the storage unit 232 stores the effective date in “startDate” when the update data includes the effective date, and stores the current date in “startDate” when the update data does not include the effective date. Store. In addition, the storage unit 232 stores no information in “endDate”.

  On the other hand, when the employee ID of the update data is stored in the selection table, the storage unit 232 is the same as the employee ID included in the update data among the records stored in the selection table, and “ A record in which no information is stored in “endDate” is specified as the latest record. Then, the storage unit 232 determines whether or not the attribute information included in the update data is the same as the attribute information of the latest record. Then, when the attribute information of the update data and the attribute information of the latest record are the same, the storage unit 232 does not store the attribute information included in the update data in the selection table.

  On the other hand, if the attribute information of the update data is not the same as the attribute information of the latest record, the storage unit 232 subtracts the date obtained by subtracting “1 day (24 hours)” from the effective date included in the update data. Stored in “endDate”. At this time, if the update data does not include a valid date, the storage unit 232 stores the date obtained by subtracting “1 day (24 hours)” from the current date in “endDate” of the latest record. In addition, the storage unit 232 stores the attribute information included in the update data in the selection table as a new record. At this time, the storage unit 232 stores the effective date or the current date in “startDate” and does not store information in “endDate”, as in the above example.

  The storage processing by the storage unit 232 will be described using the examples shown in FIGS. Here, it is assumed that the employee ID table 221 is in the state shown in FIG. 8, the organization history table 222 is in the state shown in FIG. 9, and the extension history table 223 is in the state shown in FIG.

  In this state, the receiving unit 131 receives update data including the employee ID “1122”, the organization name “G14”, the extension “3333”, the room number “1-1001”, and the effective date “2012-1-1”. Shall be. In this case, the storage unit 232 does not update the employee ID table 221 because the employee ID “1122” included in the update data is stored in the employee ID table 221.

  Subsequently, since the combination of the employee ID “1122” and the organization name “G14” included in the update data is not stored in the organization history table 222, the storage unit 232 stores the employee ID stored in the organization history table 222. Among the records “1122”, the date “2011-12” obtained by subtracting one day from the effective date “2012-1-1” to the endDate of the latest record (record on the third line in FIG. 9) whose endDate is NULL. 31 "is stored. Furthermore, the storage unit 232 stores the employee ID “1122” and the organization name “G14” included in the update data in the organization history table 222 as new records. At this time, the storage unit 232 stores the effective date “2012-1-1” in “startDate” of the new record, and does not store information in “endDate”.

  Subsequently, since the combination of the employee ID “1122” and the extension “3333” included in the update data is stored in the extension history table 223, the storage unit 232 does not update the extension history table 223. In this way, the storage unit 232 updates a room number history table (not shown) using the room number “1-1001” as update data.

  When receiving a search request, the search unit 233 searches various data from the storage unit 220 according to the search request. For example, the search unit 233 receives a search request including specific information and the name (column name) of attribute information to be searched. In such a case, the search unit 233 selects a history table corresponding to the type of attribute information to be searched included in the search request from the storage unit 220, and uses the specific information included in the search request as a key, “Information” and “startDate” are searched from the history table. Then, the search unit 233 sorts the search result attribute information in descending order of the startDate, and notifies the search request transmission source of the search result list in which the sorted attribute information and the startDate are described.

  The search processing by the search unit 233 will be described using the example shown in FIG. For example, it is assumed that the search unit 233 receives a search request including the employee ID “1122” and the name “organization name” of the attribute information to be searched. In such a case, the search unit 233 selects the organization history table 222 as a search target history table. Then, the search unit 233 searches the organization history table 222 using the employee ID “1122” as a key, thereby acquiring “organization name” and “startDate”. In this example, the search unit 233 includes a combination of an organization name “G11” and a startDate “2009-10-1”, a combination of an organization name “G12” and a startDate “2010-4-1”, and an organization name “G13”. ”And the combination of startDate“ 2011-12-1 ”. Then, the search unit 233 sorts the organization names into “G13”, “G12”, and “G11” by sorting in descending order of the startDate. Then, the search unit 233 executes the organization name “G13” and the startDate “2011-12-1”, the organization name “G12” and the startDate “2010-4-1”, the organization name “G11”, and the startDate “2009-10-1”. The search result list described in the order "" is notified to the transmission source of the search request. As a result, the user who refers to the search result list can confirm the transition of the organization to which the employee whose employee ID is “1122” belongs.

  In the above description, the search unit 233 shows an example in which the search results are rearranged in the descending order of the startDate. However, the search unit 233 may rearrange the search results in ascending order of startDate. In addition, the search unit 233 may search for endDate instead of startDate. In such a case, the search unit 233 sorts the attribute information whose endDate is NULL as the latest attribute information. Further, the search unit 233 may search both the startDate and the endDate.

  Further, the storage unit 232 and the search unit 233 illustrated in FIG. 7 are realized by an integrated circuit such as an ASIC or FPGA, for example. Further, for example, the storage unit 232 and the search unit 233 are realized by a program stored in a storage device (not shown) being executed using the RAM as a work area by a CPU, an MPU, or the like.

[Storing Procedure by Data Management Device According to Second Embodiment]
Next, the procedure of storage processing by the data management apparatus 200 according to the second embodiment will be described with reference to FIG. FIG. 11 is a flowchart illustrating a storage processing procedure performed by the data management apparatus 200 according to the second embodiment. Hereinafter, a case where the storage unit 220 includes the history tables illustrated in FIGS. 8 to 10 will be described as an example.

  As illustrated in FIG. 11, when update data is received by the reception unit 131, the storage unit 232 of the data management apparatus 200 performs the processing illustrated in the loop 1 by the number of rows (number of records) included in the update data. Repeat. Specifically, the storage unit 232 repeatedly performs the process shown in the loop 2 for one record in the update data by the number of history tables stored in the storage unit 220. The storage unit 232 performs storage processing in the order of an employee ID table 221, an organization history table 222, an extension history table 223, and a room number history table (not shown).

  Processing in the loop 2 will be described. The storage unit 232 determines whether or not the history table to be updated is the employee ID table 221 (step S301). At this time, if the history table to be updated is the employee ID table 221 (Yes in step S301), the storage unit 232 stores the same information as the specific information “employee ID” included in the update data in the employee ID table 221. It is determined whether it is stored (step S302).

  If the employee ID of the update data is not stored in the employee ID table 221 (No at step S302), the storage unit 232 stores the employee ID included in the update data as a new record in the employee ID table 221. (Step S303). At this time, the storage unit 232 stores the effective date in “startDate” when the update data includes the effective date, and stores the current date in “startDate” when the update data does not include the effective date. Store. In addition, the storage unit 232 stores no information in “endDate”. Further, when the employee ID of the update data is stored in the employee ID table 221 (Yes in step S302), the storage unit 232 stores the employee ID included in the update data in the employee ID table 221 without storing the employee ID. The process returns to step S301.

  Further, when the history table to be updated is not the employee ID table 221 (No at Step S301), the storage unit 232 stores the same information as the specific information “employee ID” included in the update data in the history table to be updated. It is determined whether or not it has been performed (step S304). For example, when the history table to be updated is the organization history table 222, the storage unit 232 determines whether or not the employee ID included in the update data is stored in the organization history table 222.

  Then, when the employee ID of the update data is stored in the update target history table (Yes in step S304), the storage unit 232 extracts a record that matches the employee ID from the update target history table, Among the extracted records, the latest record whose endDate is NULL is specified. Then, the storage unit 232 determines whether or not the same attribute information as the attribute information included in the update data is stored in the latest record (step S305).

  For example, it is assumed that the history table to be updated is the organization history table 222. In such a case, the storage unit 232 identifies, from the organization history table 222, the latest record whose endDate is NULL among the records that match the employee ID included in the update data, and the organization included in the update data in the identified latest record It is determined whether the name is stored.

  When the update data attribute information is not stored in the latest record (No at Step S305), the storage unit 232 subtracts “one day” from the effective date included in the update data, or the current date. The date obtained by subtracting “1 day” from (update date) is stored in “endDate” of the latest record (step S306). Further, the storage unit 232 stores the employee ID and attribute information included in the update data, and the startDate and endDate as new records in the update target history table (step S307). At this time, the storage unit 232 stores the effective date in the startDate when the update data includes the effective date, and stores the current date (update date) in the startDate when the update data does not include the effective date. Store. The storage unit 232 does not store information in endDate.

  For example, it is assumed that the history table to be updated is the organization history table 222. In such a case, when the organization name of the update data is not stored in the latest record of the organization history table 222, the storage unit 232 displays the date obtained by subtracting “one day” from the effective date included in the update data. Stored in “endDate”. Further, the storage unit 232 stores the employee ID, organization name, startDate, and endDate included in the update data as new records in the organization history table 222.

  Further, when the attribute information of the update data is stored in the latest record (Yes at Step S305), the storage unit 232 does not store the employee ID and attribute information included in the update data in the history table to be updated. Returning to step S301.

  In addition, when the employee ID of the update data is not stored in the history table to be updated (No at Step S304), the storage unit 232 newly updates the employee ID and attribute information included in the update data, and startDate and endDate. As a new record in the history table to be updated (step S308). At this time, the storage unit 232 stores the effective date in the startDate when the update data includes the effective date, and stores the current date (update date) in the startDate when the update data does not include the effective date. Store. The storage unit 232 does not store information in endDate.

[Search Processing Procedure by Data Management Device According to Second Embodiment]
Next, a search processing procedure performed by the data management apparatus 200 according to the second embodiment will be described with reference to FIG. FIG. 12 is a flowchart illustrating a search processing procedure performed by the data management apparatus 200 according to the second embodiment. Hereinafter, a case where the storage unit 220 includes the history tables illustrated in FIGS. 8 to 10 will be described as an example.

  As shown in FIG. 12, when the search unit 233 of the data management apparatus 200 receives a search request, the search unit 233 stores a history table (organization history table 222, extension history table 223, room number history table) that stores search target attribute information. Etc.), the search target attribute information is searched using the employee ID included in the search request as a key (step S401).

  Then, the search unit 233 sorts the search result attribute information in descending order of startDate (step S402). Thereafter, the search unit 233 notifies the search request transmission source of the sorted search result list. In addition, since the same attribute information is not continuously stored in each history table in the storage unit 220, the search unit 233 does not have to perform a process of deleting the continuous attribute information.

[Effect of Example 2]
As described above, in the data management apparatus 200 according to the second embodiment, the storage unit 220 includes a history table that stores the attribute information and the expiration date in association with each attribute information type. In addition, when the storage unit 232 receives an update request, the storage unit 232 updates the expiration date of the latest attribute information stored in the history table corresponding to the new attribute information type included in the update request. Store information in history table. Further, when receiving a search request, the search unit 133 searches for attribute information from a history table corresponding to the type of attribute information included in the search request.

  As described above, the data management apparatus 200 according to the second embodiment manages the change history of the attribute information in the history table that is different for each attribute information. As a result, the data management apparatus 200 according to the second embodiment can update only the attribute information that has been updated, and thus the amount of data managed in the storage unit 220 can be reduced. Further, since the data management apparatus 200 according to the second embodiment does not store continuously overlapping attribute information in each history table, it does not require processing such as deleting continuously overlapping attribute information. As a result, the data management apparatus 200 according to the second embodiment can easily provide data transition.

  In the second embodiment, the data management apparatus 200 may manage the attribute name stored in each history table in the storage unit 220 using the attribute management table. FIG. 13 illustrates an example of the attribute management table 224 according to the second embodiment. As shown in FIG. 13, the attribute management table 224 has items such as “attribute name” and “table name”. “Attribute name” indicates the name (column name) of attribute information stored in each history table in the storage unit 220 and corresponds to the type of attribute information. The “table name” indicates the name of the history table that stores the attribute information indicated by the “attribute name”.

  That is, in the example of FIG. 13, the employee ID table 221 stores “employee ID”, the organization history table 222 stores “organization name”, and the extension history table 223 stores “extension”. .

  The storage unit 232 according to the second embodiment can select the history table to be updated by referring to the attribute management table 224. Further, the search unit 233 according to the second embodiment can select a history table to be searched by referring to the attribute management table 224. Thereby, the storage unit 232 and the search unit 233 can update the history table to be updated by referring to the attribute management table 224 even when the number of types of attribute information becomes enormous and the number of history tables becomes enormous. Can be easily selected.

  In the above example, the attribute management table 224 illustrated in FIG. 13 stores the record of the attribute name “employee ID” and the table name “employee ID table”. However, the storage unit 232 and the search unit 233 may recognize in advance in which table basic information such as “employee ID” is stored. In such a case, the attribute management table 224 may not store records of the attribute name “employee ID” and the table name “employee ID table”.

  The data management apparatus described above may be implemented in various different forms other than the above embodiment. Therefore, in a third embodiment, another embodiment of the data management apparatus will be described.

[Managed data]
In the above embodiment, the example in which the data management apparatus 100 or 200 manages master data has been shown. However, the data management apparatus 100 or 200 according to the embodiment can be applied to managing any data other than the master data.

[data structure]
In the above embodiment, the data management apparatus 100 or 200 manages data including specific information (“employee ID” in the above embodiment). However, the data management apparatus 100 or 200 according to the above embodiment can also be applied when managing data that does not include specific information. For example, the data management apparatus 100 according to the first embodiment may have as many master data tables as the number of employee IDs. In this case, the data management apparatus 100 has a master data table that does not include an employee ID. In such a case, the storage unit 132 of the data management apparatus 100 selects the master data table to be updated based on the employee ID included in the update data. Then, the storage unit 132 determines whether or not the attribute information in the latest record of the selected master data table matches the attribute information included in the update data. If they match, the storage process is not performed. If they do not match, the attribute information included in the update data is stored in the master data table. Similarly, the data management apparatus 200 according to the second embodiment may have as many history tables as the number of employee IDs. In this case, the data management apparatus 200 has a history table that does not include an employee ID.

[Update data]
Moreover, in the said Example, the example in which all the attribute information was contained in update data was shown. However, the update data may include only characteristic information (“employee ID” in the above embodiment) and attribute information to be updated. For example, the update data for updating the organization name includes the employee ID, the updated organization name, and the effective date, and may not include the extension and the room number. In the case of this example, the storage unit 132 of the data management apparatus 100 according to the first embodiment stores the combination of the employee ID and the organization name included in the update data when stored in the latest record of the master data table 121. Do not process. On the other hand, when such a combination is not stored in the latest record, the storage unit 132 updates the endDate of the latest record and stores the attribute information included in the update data in the master data table 121 as a new record. At this time, for the attribute information not included in the update data, the storage unit 132 copies the attribute information in the latest record to a new record.

[System configuration]
In addition, among the processes described in the above embodiment, all or a part of the processes described as being automatically performed can be manually performed, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedures, specific names, and information including various data and parameters shown in the document and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in FIGS. 2, 8 to 10, and 13 is an example and can be arbitrarily changed. For example, the master data table 121 shown in FIG. 2 may store information such as employee names, addresses, mobile phone numbers, and job titles. In addition, the master data table 121 illustrated in FIG. 2 may store master data related to products, customers, accounting, and the like instead of master data related to employees.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the reception unit 131 and the storage unit 132 illustrated in FIG. 1 may be integrated. Similarly, the reception unit 131 and the storage unit 232 illustrated in FIG. 7 may be integrated.

[program]
In addition, it is possible to create a program in which the processing executed by the data management apparatus 100 or 200 described in the above embodiment is described in a language that can be executed by a computer. For example, a data management program in which processing executed by the data management apparatus 100 or 200 is described in a language that can be executed by a computer can be created. In this case, when the computer executes the data management program, the same effect as in the above embodiment can be obtained. Further, by recording the data management program on a computer-readable recording medium, and reading and executing the data management program recorded on the recording medium by the computer, the same processing as in the above-described embodiment may be realized. Good. An example of a computer that executes a data management program that implements the same function as that of the data management apparatus 100 shown in FIG. 1 will be described below.

  FIG. 14 is a diagram illustrating a computer 1000 that executes a data management program. As illustrated in FIG. 14, the computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012 as illustrated in FIG. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1031 as illustrated in FIG. The disk drive interface 1040 is connected to the disk drive 1041 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive. The serial port interface 1050 is connected to, for example, a mouse 1051 and a keyboard 1052 as illustrated in FIG. The video adapter 1060 is connected to a display 1061, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 14, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the data management program is stored in, for example, the hard disk drive 1031 as a program module in which a command to be executed by the computer 1000 is described. For example, a reception procedure for executing information processing similar to that of the reception unit 131 illustrated in FIG. 1, a storage procedure for executing information processing similar to the storage unit 132, and a search procedure for executing information processing similar to that of the search unit 133 Is stored in the hard disk drive 1031.

  Various data held by the storage unit 120 described in the above embodiment is stored as program data, for example, in the memory 1010 or the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1031 to the RAM 1012 as necessary, and executes the reception procedure, the storage procedure, and the search procedure.

  Note that the program module 1093 and the program data 1094 related to the data management program are not limited to being stored in the hard disk drive 1031, but are stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive or the like. Also good. Alternatively, the program module 1093 and the program data 1094 related to the data management program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and the network interface 1070 is stored. Via the CPU 1020.

DESCRIPTION OF SYMBOLS 100 Data management apparatus 120 Storage part 121 Master data table 131 Reception part 132 Storage part 133 Search part 200 Data management apparatus 220 Storage part 221 Employee ID table 222 Organization history table 223 Extension history table 224 Attribute management table 232 Storage part 233 Search part

Claims (7)

A storage unit that associates and stores attribute information related to a predetermined thing and an expiration date that indicates a time limit for which the attribute information corresponds to the attribute of the thing;
When an update request for updating the attribute information is received, an expiration date indicating that the current time is within the expiration date among the expiration dates stored in the storage unit, and the latest attribute corresponding to the expiration date Updated on the date when the information no longer corresponds to the attribute of the thing, the new attribute information included in the update request, and an expiration date indicating that the new attribute information currently corresponds to the attribute of the thing; Storing in the storage unit;
A data management apparatus comprising: a search unit that searches the storage unit for attribute information included in the search request when a search request for the attribute information is received. The storage unit
When the new attribute information included in the update request is different from the latest attribute information stored in the storage unit, the expiration date corresponding to the latest attribute information is updated, and the new attribute information is updated. The data management device according to claim 1, wherein the data management device is stored in the storage unit. The storage unit
For each type of attribute information related to the thing, a history storage unit that stores the attribute information and the expiration date of the attribute information in association with each other,
The storage unit
When the update request is received, the expiration date of the latest attribute information stored in the history storage unit corresponding to the new attribute information type included in the update request is updated, and the new attribute information is updated Store it in the history storage,
The search unit
The data management apparatus according to claim 1 or 2, wherein when the search request is received, the attribute information is searched from a history storage unit corresponding to a type of attribute information included in the search request. The storage unit
As the expiration date, storing the first date when the attribute information corresponds to the attribute of the thing, and the last date when the attribute information corresponds to the attribute of the thing,
The storage unit
When receiving an update request including the new attribute information and an effective date that is the first date when the new attribute information corresponds to the attribute of the thing, the latest attribute information stored in the storage unit The last date in the corresponding effective date is updated to the date before the effective date, the new attribute information is stored in the storage unit, and the effective date is the first date in the effective date of the new attribute information. The data management device according to any one of claims 1 to 3, wherein the data management device is stored. An attribute management storage unit that stores the identification information for identifying the history storage unit that stores the type of the attribute information and the attribute information corresponding to the type in association with each other;
The storage unit
When the update request is received, the history storage unit acquires the identification information of the history storage unit corresponding to the new attribute information type included in the update request from the attribute management storage unit, and is specified by the acquired identification information Update the expiration date of the latest attribute information stored in the unit, store the new attribute information in the history storage unit,
The search unit
When the search request is accepted, identification information of the history storage unit corresponding to the type of attribute information included in the search request is acquired from the attribute management storage unit, and from the history storage unit specified by the acquired identification information The data management apparatus according to claim 1, wherein the attribute information is searched. A data management method executed by a data management device,
An accepting step of accepting an update request for updating attribute information stored in a storage unit that stores attribute information related to a predetermined thing and an expiration date indicating an expiration date corresponding to the attribute of the thing in question. When,
When the update request is accepted in the accepting step, the latest attribute information corresponding to the expiration date indicates an expiration date indicating that the current time is within the expiration date among the expiration dates stored in the storage unit. Update to a date that no longer corresponds to the attribute of the thing, the new attribute information included in the update request and an expiration date indicating that the new attribute information currently corresponds to the attribute of the thing A storage step of storing in the storage unit;
And a search step of searching the storage unit for attribute information included in the search request when a search request for the attribute information is received. Accepting procedure for accepting an update request for updating attribute information stored in a storage unit that associates and stores attribute information related to a predetermined thing and an expiration date indicating a deadline corresponding to the attribute of the thing When,
When the update request is received in the reception procedure, the latest attribute information corresponding to the expiration date indicates an expiration date indicating that the current time is within the expiration date among the expiration dates stored in the storage unit. Update to a date that no longer corresponds to the attribute of the thing, the new attribute information included in the update request and an expiration date indicating that the new attribute information currently corresponds to the attribute of the thing A storage procedure for storing in the storage unit;
A data management program that, when receiving a search request for attribute information, causes a computer to execute a search procedure for searching for attribute information included in the search request from the storage unit.

Images