JP2013218575A - Id information management system, id information management server and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically update an ID information management DB for managing ID information, and to reduce a workload in the case of preliminarily registering the update content.SOLUTION: An ID information management server 10 includes: an ID information management DB 104 for registering ID information; and a reservation information management DB 102 for registering reservation information for updating the ID information management DB 104. An ID information updating part 103 of the ID information management server 10 performs access to a reservation information management DB 102 in a predetermined timing, and determines whether or not an update scheduled date included in searched reservation information is an appointed day, and when the update scheduled date is the appointed day, updates the content of an ID information management DB 104 on the basis of the content of the reservation information. A reservation information registration part 101 registers the reservation information in the reservation information management DB 102 on the basis of upload data of a first storage format or a second storage format from a terminal device received by an upload data reception part 100.

Description

  The present invention relates to a technique for managing ID information.

  For example, in a company, ID information used for user authentication / authorization in an in-house business system or file server is centrally managed in an ID information management DB (database), and at the timing of personnel changes, organizational reorganization, etc. Generally, it is updated appropriately by human work.

  Such update work needs to be completed in as short a time as possible.For example, if there are many people to be transferred and the amount of updates is enormous, the work will be time-consuming and the work will be completed even on the day of the transfer date. There are cases where this is not the case. On the other hand, in order to avoid such a situation, if the update operation is started early, the user ID information is updated before the transfer date, which causes inconvenience in authentication and the like.

  For such a problem, for example, Patent Document 1 refers to the latest position information table in which personnel changes of each staff are written in a preset cycle, and on the day when the position of each staff changes, A system (information management system) that automatically rewrites the contents of a staff information table in which job titles are registered is disclosed.

JP 2000-10928 A

  Incidentally, the ID information management DB may include ID information of employees in a plurality of companies such as a group company. In this case, although the ID assigned to each employee is not the same even if the company is different, the data management system (item configuration of the employee information DB) of the employee information in each company is often various. For example, some companies include in their employee information the date on which the employee's current affiliation and / or position became valid, while others do not. Then, when information is uploaded to a temporary registration DB such as the latest post information table of Patent Document 1, the input item group does not match the item group of the employee information DB of the company, and the input work is easy. is not.

  The present invention has been made in view of the above problems, and automatically updates an ID information management DB that manages user ID information and can reduce the workload when pre-registering the update contents. The goal is to provide an information management system.

In order to achieve the above object, an ID information management system according to the present invention includes:
An ID information management system including an ID information management server that manages ID information for each user, and a terminal device that performs data communication with the ID information management server via a predetermined network,
The ID information management server
An ID information management database in which the ID information is registered;
A reservation information management database in which reservation information for updating the ID information management database is registered;
Access the reservation information management database at a predetermined timing, sequentially search all the registered reservation information, determine whether the scheduled update date included in the searched reservation information is the current day, If it is that day, an ID information update unit that updates the content of the ID information management database based on the content of the reservation information;
An upload data receiving unit that performs data communication with the terminal device by a predetermined communication method and receives upload data transmitted from the terminal device;
A reservation information registration unit for registering the reservation information in the reservation information management database based on the upload data received by the upload data receiving unit;
The terminal device
Depending on the user's operation, upload data of the first storage format in which one or a plurality of update schedule information including the update schedule date is stored, or one or a plurality of update schedule information not including the update schedule date is stored. Sending upload data of the second storage format in which the scheduled update date is stored in the header part to the ID information management server;
The reservation information registration unit of the ID information management server is
In the case of the upload data in the first storage format, each update schedule information stored in the upload data is registered as reservation information in the reservation information management database,
In the case of the upload data in the second storage format, the update date is extracted from the header area of the upload data, and the reservation information storing the contents of the update schedule information stored in the upload data is It is registered in the reservation information management database, and the extracted update date is stored in each of the registered reservation information.

  According to the present invention, reservation information (updated user ID information) registered in the reservation information management database is automatically updated and registered in the ID information management database on the scheduled update date. Therefore, the ID information management database can be appropriately updated without depending on human work. Thereby, for example, the ID information of the user can be normally used regardless of before and after the personnel change date. Further, in the registration of reservation information in the reservation information management database, the terminal device does not include upload data in the first storage format in which one or a plurality of update schedule information including the update schedule date is stored and the scheduled update date. Upload data in which one or more update schedule information is stored can be appropriately selected and transmitted. Therefore, it becomes easy to register reservation information in the reservation information management database.

It is a figure showing the whole ID information management system composition concerning an embodiment of the present invention. It is a block diagram which shows the structure of the ID information management server of this embodiment. It is a figure which shows the structure of ID information. It is a figure which shows the structure of reservation information. It is a figure which shows an example of the upload data of a 1st storage format. It is a figure which shows an example of the upload data of a 2nd storage format. It is a figure which shows an example of a storage format inquiry screen. It is a figure which shows an example of the update schedule information input screen corresponding to a 1st storage format. It is a figure which shows an example of the update schedule information input screen corresponding to a 2nd storage format. It is a flowchart which shows the procedure of a reservation information registration process. It is a flowchart which shows the procedure of ID information update process.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing an overall configuration of an ID information management system 1 according to the present embodiment. The ID information management system 1 includes an ID information management server 10 and a plurality of terminal devices 20. For example, the ID information management server 10 and each terminal device 20 are connected to a predetermined network 30 such as the Internet, and are configured to be able to transmit and receive data to and from each other.

  The ID information management system 1 is a system for managing ID information used for authentication / authorization (hereinafter referred to as authentication) of employees (users) of each company in a company composed of a plurality of group companies. The ID information managed here is used, for example, when a user accesses a common internal business system or file server in the company.

  The ID information management server 10 is installed in a department that manages ID information of any company (such as a group head office). The ID information management server 10 has a hardware configuration equivalent to that of a general server computer. That is, although none of the ID information management server 10 is shown in the figure, a control device comprising a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), etc., a readable / writable nonvolatile semiconductor An external storage device comprising a memory, a hard disk drive, etc., a communication interface for performing data communication with each terminal device 20 via the network 30, an input device comprising a keyboard, mouse, keypad, touch pad, touch panel, etc And a display device including a CRT, a liquid crystal monitor, and the like.

  One or a plurality of terminal devices 20 are installed for each company, and each has a hardware configuration equivalent to that of a general personal computer. Each terminal device 20 is preinstalled with application software for transmitting upload data to the ID information management server 10.

  As shown in FIG. 2, the ID information management server 10 functionally includes an upload data receiving unit 100, a reservation information registration unit 101, a reservation information management DB 102, an ID information update unit 103, and an ID information management DB 104. And comprising.

  As described above, the ID information management DB 104 is a database that manages ID information that is used when a user accesses an in-house business system or a file server. In the ID information management DB 104, ID information of all the group companies currently in office is registered. As shown in FIG. 3, the ID information includes items of ID 300, name 301, affiliation 302, post 303, valid start date 304, and valid end date 305.

  ID 300 stores an ID assigned to each user. The ID is composed of alphanumeric characters having a predetermined number of digits (for example, 7 digits), for example. Each user is assigned a different ID. The name 301 stores information indicating the name of the user. The name is composed of kanji, hiragana, katakana, or any combination thereof. In the affiliation 302, information indicating the current affiliation destination of the user (for example, “Company A, Department B, Section C”) is stored. The post 303 stores information indicating the current post of the user (for example, “section manager”). Note that a predetermined code may be stored in the affiliation 302 and the post 303.

  The effective start date 304 stores information (for example, “20080401”) indicating the date on which the current affiliation and / or post of the user becomes effective. The effective end date 305 stores information (for example, “20301031” or the like) that indicates the expiration date (year / month / day) of the user. The term of employment indicates, for example, the retirement date if the user is a regular employee, and the expiration date of the contract period if the user is a non-regular employee (dispatch etc.). In addition, even if the user is in regular employment, if the current affiliation and / or position is limited to a predetermined period, the expiration date of the period is indicated. Note that the information indicating the term of employment is not essential information in the ID information, and “NULL” may be stored in the effective end date 305.

  The reservation information management DB 102 is a database in which ID information scheduled to be registered in the ID information management DB 104 is registered as reservation information. As shown in FIG. 4, the reservation information includes items of ID 400, name 401, affiliation 402, post 403, valid start date 404, and valid end date 405. The input format of each of these items is the same as the input format of each item of ID 300, name 301, affiliation 302, post 303, valid start date 304, and valid end date 305.

  As in ID 300, ID assigned to each user is stored in ID 400. Similarly to the name 301, the name 401 stores information indicating the name of the user (a user who is scheduled to be transferred or newly registered).

  In the affiliation 402, information indicating the affiliation destination of the current or scheduled transfer of the user is stored. The job title 403 stores information indicating the job title of the user that is currently scheduled to be transferred. Note that, as in the case of the affiliation 302 and the position 303, a predetermined code may be stored in the affiliation 402 and the position 403.

  The effective start date 404 stores information (for example, “20120401” or the like) indicating the date on which the user is scheduled to change. Similarly to the valid end date 305, the valid end date 405 stores information indicating the user's tenure (year / month / day). As with the valid end date 305, “NULL” may be stored in the valid end date 405.

  The ID information update unit 103 is a functional unit realized by a CPU or the like executing a predetermined program stored in a ROM or an external storage device, and manages reservation information at a predetermined timing (for example, periodically). The DB 102 is accessed to refer to all registered reservation information. If the date indicated by the information stored in the effective start date 404 matches the date of the current day, the corresponding ID in the ID information management DB 104 is based on the contents of the reservation information. Update the information content. Then, the ID information update unit 103 deletes the reservation information from the reservation information management DB 102.

  The upload data receiving unit 100 is a functional unit that is realized by a CPU or the like executing the above-described predetermined program and in cooperation with a communication interface or the like, and performs data communication with the terminal device 20 via the network 30 by a predetermined communication method. And the data (upload data) transmitted from the terminal device 20 is received. The upload data receiving unit 100 supplies the received upload data to the reservation information registration unit 101.

  Here, the upload data transmitted from each terminal device 20 will be described in detail. In this embodiment, there are two types of storage formats for upload data. As shown in FIG. 5, the upload data in the first storage format stores one or more pieces of update schedule information in a format in accordance with the reservation information in the reservation information management DB 102. For example, CSV (Comma Separated Values) can be adopted as the file format of the upload data in the first storage format.

  In FIG. 5, for example, update schedule information is shown when “Taro Yamada” whose ID is “M000110” whose chief is the current title is transferred to the section manager with “December 1, 2011”. ing.

  On the other hand, the upload data in the second storage format stores one or a plurality (usually a plurality) of update schedule information in a format that does not conform to the reservation information in the reservation information management DB 102, as shown in FIG. As the file format of the upload data in the second storage format, for example, CSV can be adopted as in the first storage format.

  As shown in FIG. 6, the update schedule information does not include the valid start date 404 and the valid end date 405 in the reservation information of the reservation information management DB 102. However, information corresponding to the scheduled update date (scheduled change date) is stored at a predetermined location in the header area of the upload data. That is, in the upload data in the second storage format, the update scheduled date is common to all the update schedule information.

  When upload data is supplied from the upload data receiving unit 100, the reservation information registration unit 101 determines the storage format of the upload data. In this embodiment, it is assumed that information indicating whether the storage format is the first or second storage format is stored in a predetermined portion of the header area of the upload data.

  When the upload data supplied from the upload data receiving unit 100 is in the first storage format, the reservation information registration unit 101 uses each update schedule information stored in the upload data as reservation information, and the reservation information management DB 102 Register with.

  On the other hand, when the upload data supplied from the upload data receiving unit 100 is in the second storage format, the reservation information registration unit 101 extracts information indicating the scheduled update date from the header area of the upload data. Then, the reservation information storing the contents of each update schedule information stored in the upload data is additionally registered in the reservation information management DB 102, and the extracted update schedule date is shown in the effective start date 404 of the registered reservation information. Store information. Note that “NULL” is stored as the effective end date 405.

  As described above, the upload data transmitted from the terminal device 20 is reflected in the reservation information management DB 102.

  Next, a user I / F process for transmitting upload data to the ID information management server 10 executed in each terminal device 20 will be described. This user I / F processing is started when the above-described application software is activated by a control device (not shown) of the terminal device 20 by a user operation.

  First, as shown in FIG. 7, the control device of the terminal device 20 displays a screen (storage format inquiry screen 701) for inquiring of the storage format of the upload data to the user on the liquid crystal monitor or the like. .

  The user can select (specify) the storage format of the upload data by performing an operation of selecting either the radio button 702 or 703 via an input device (not shown) provided in the terminal device 20. For example, when it is desired to designate “first storage format”, the user may perform an operation of selecting the radio button 702. On the other hand, when it is desired to specify “second storage format”, the user may perform an operation of selecting the radio button 703.

  For example, in the department where the terminal device 20 is installed (for example, the B section C section of the company A), when there are few people who change in the near future, or when the date of change varies, the user The “first storage format” may be designated.

  When the user designates “first storage format” and presses the OK button 704, the control device of the terminal device 20 displays an update schedule information input screen 801 as shown in FIG. 8 on a liquid crystal monitor or the like. To do.

  The update schedule information input screen 801 is provided with an input area 802 for inputting the update schedule information in a format according to the reservation information in the reservation information management DB 102. The user can directly input text corresponding to the user who is scheduled to move to each item in the input area 802 via the input device included in the terminal device 20.

  In order to input a plurality of pieces of update schedule information, the user may press the next button 803. When the next button 803 is pressed, the control device of the terminal device 20 clears the display of each item in the input area 802 after taking the input contents of the input area 802 into the buffer. Thereby, the user can input the next update schedule information.

  When one or more update schedule information is input by the user and the OK button 804 is pressed, the control device of the terminal device 20 stores the input one or more update schedule information in the data area, Furthermore, upload data storing information indicating the first storage format at a predetermined location in the header area is generated. And the control apparatus of the terminal device 20 controls the communication interface which is not shown in figure, and transmits the produced | generated upload data to the ID information management server 10 via the network 30. FIG.

  On the other hand, for example, in the department where the terminal device 20 is installed (for example, part C of company B), there are many people who change on the same day, or in the data management system for employee information in the department, the effective start date When the effective end date is not managed (not included in the employee information DB item), the user only has to specify “second storage format”.

  When “second storage format” is designated by the user and the OK button 704 is pressed, the control device of the terminal device 20 displays an update schedule information input screen 901 as shown in FIG. 9 on a liquid crystal monitor or the like. To do.

  The update schedule information input screen 901 is provided with an input area 902 for designating a file storing the update schedule information. As a result, the user can designate a CSV file (update schedule.csv) prepared in advance and outputting the contents of the employee information DB of the relevant department. When the user presses the OK button 903, the control device of the terminal device 20 stores the contents of the designated CSV file in the data area, and further stores the second storage format at a predetermined location in the header area. Generate upload data that stores information indicating. And the control apparatus of the terminal device 20 controls the communication interface which is not shown in figure, and transmits the produced | generated upload data to the ID information management server 10 via the network 30. FIG.

  As described above, the user I / F process for transmitting the upload data to the ID information management server 10 is executed in each terminal device 20.

  Next, reservation information registration processing executed by the ID information management server 10 will be described with reference to the flowchart of FIG.

  When the upload data receiving unit 100 receives the upload data transmitted from the terminal device 20 (step S101; YES), the upload data receiving unit 100 supplies the received upload data to the reservation information registration unit 101.

  The reservation information registration unit 101 determines the storage format of the upload data (step S102). When the upload data is in the first storage format (step S102; YES), the reservation information registration unit 101 registers each update schedule information stored in the upload data in the reservation information management DB 102 as reservation information. (Step S103).

  On the other hand, when the upload data is in the second storage format (step S102; NO), the reservation information registration unit 101 extracts information indicating the scheduled update date from the header area of the upload data (step S104). ). The reservation information registration unit 101 additionally registers reservation information storing the contents of each update schedule information stored in the upload data in the reservation information management DB 102 (step S105). Then, the reservation information registration unit 101 stores the extracted information indicating the scheduled update date in the effective start date 404 of the registered reservation information, and stores “NULL” in the effective end date 405 (step S106).

  Next, ID information update processing executed by the ID information management server 10 will be described with reference to the flowchart of FIG. The ID information update unit 103 accesses the reservation information management DB 102 at a predetermined timing (for example, every day at midnight) (step S201). The ID information update unit 103 sequentially searches for reservation information registered in the reservation information management DB 102, checks the date indicated by the information stored in the effective start date 404, and matches the date of the current day. It is determined whether or not to perform (step S202).

  As a result, if it matches the date of the day (step S202; YES), the ID information update unit 103 updates the content of the corresponding ID information in the ID information management DB 104 based on the content of the reservation information ( Step S203). Further, the ID information update unit 103 deletes the reservation information from the reservation information management DB 102. If there is no ID information corresponding to the ID information management DB 104, the reservation information is additionally registered in the ID information management DB 104 as new ID information.

  On the other hand, if the date does not match the date (step S202; NO), or after the process of step S203, the ID information update unit 103 determines whether or not all the reservation information has been searched (step S204). . When all the reservation information has not been searched (step S204; NO), the ID information update unit 103 searches for the next reservation information (step S205), and performs the process of step S202 again.

  On the other hand, when all the reservation information has been searched (step S204; YES), the ID information update unit 103 waits for the process until the next reference time (midnight of the next day) (step S206).

  As described above, according to the ID information management system 1 of the present embodiment, the reservation information registered in the reservation information management DB 102 is automatically updated and registered in the ID information management DB 104 on the scheduled update date. Therefore, the ID information management DB 104 can be appropriately updated without depending on human work. Thereby, for example, the ID information of the user can be normally used regardless of before and after the personnel change date.

  Furthermore, when registering reservation information in the reservation information management DB 102, the terminal device 20 can appropriately select and transmit upload data based on individual unit information input and upload data based on file designation. . Therefore, it is possible to easily register the reservation information in the reservation information management DB 102 even when the data management method of the employee information in each department is different or when there are many people who change on the same day.

  In addition, this invention is not limited to the said embodiment, Of course, the various change in the range which does not deviate from the summary of this invention is possible.

  For example, if the date indicated by the information stored in the effective start date 404 of the reservation information matches the date of the current day, the ID information update unit 103 immediately responds to the ID information management DB 104. Instead of updating the content of the ID information, it may be updated when the content of at least one of the name, affiliation, and post changes as compared with the corresponding ID information. For example, when upload data in the second storage format is selected, depending on the department, it is possible to assume that the contents of the employee information DB of the department are output to a CSV file or the like without particularly restricting the conditions. May include information that is not related to the user scheduled to be transferred. Therefore, by doing as described above, it is possible to efficiently update only the ID information of the user scheduled to be transferred.

  In addition, by applying the program executed by the ID information management server 10 of the above embodiment to an existing server computer or the like, the server computer can also function as the ID information management server according to the present invention. .

  Such a program distribution method is arbitrary, for example, a computer-readable recording medium such as a CD-ROM (Compact Disk Read-Only Memory), a DVD (Digital Versatile Disk), an MO (Magneto Optical Disk), or a memory card. It may be stored and distributed in a network, or distributed via a communication network such as the Internet.

  Various embodiments and modifications can be made to the present invention without departing from the broad spirit and scope of the present invention. Further, the above-described embodiment is for explaining the present invention, and does not limit the scope of the present invention. That is, the scope of the present invention is shown not by the embodiments but by the claims. Various modifications within the scope of the claims and within the scope of the equivalent invention are considered to be within the scope of the present invention.

1 ID Information Management System 10 ID Information Management Server 100 Upload Data Receiving Unit 101 Reservation Information Registration Unit 102 Reservation Information Management DB
103 ID information update unit 104 ID information management DB

Claims (4)

An ID information management system including an ID information management server that manages ID information for each user, and a terminal device that performs data communication with the ID information management server via a predetermined network,
The ID information management server
An ID information management database in which the ID information is registered;
A reservation information management database in which reservation information for updating the ID information management database is registered;
Access the reservation information management database at a predetermined timing, sequentially search all the registered reservation information, determine whether the scheduled update date included in the searched reservation information is the current day, If it is that day, an ID information update unit that updates the content of the ID information management database based on the content of the reservation information;
An upload data receiving unit that performs data communication with the terminal device by a predetermined communication method and receives upload data transmitted from the terminal device;
A reservation information registration unit for registering the reservation information in the reservation information management database based on the upload data received by the upload data receiving unit;
The terminal device
Depending on the user's operation, upload data of the first storage format in which one or a plurality of update schedule information including the update schedule date is stored, or one or a plurality of update schedule information not including the update schedule date is stored. Sending upload data of the second storage format in which the scheduled update date is stored in the header part to the ID information management server;
The reservation information registration unit of the ID information management server is
In the case of the upload data in the first storage format, each update schedule information stored in the upload data is registered as reservation information in the reservation information management database,
In the case of the upload data in the second storage format, the update date is extracted from the header area of the upload data, and the reservation information storing the contents of the update schedule information stored in the upload data is Register in the reservation information management database, and store the extracted scheduled update date in each registered reservation information.
An ID information management system characterized by that. The ID information update unit, when the scheduled update date included in the searched reservation information is the current day, when the ID information corresponding to the searched reservation information does not exist in the ID information management database, or the search If the contents of the reservation information and the corresponding ID information do not match under a predetermined condition, the contents of the ID information management database are updated based on the contents of the reservation information.
The ID information management system according to claim 1. An ID information management database in which ID information for each user is registered;
A reservation information management database in which reservation information for updating the ID information management database is registered;
Access the reservation information management database at a predetermined timing, sequentially search all the registered reservation information, determine whether the scheduled update date included in the searched reservation information is the current day, If it is that day, an ID information update unit that updates the content of the ID information management database based on the content of the reservation information;
An upload data receiving unit that performs data communication with a terminal device by a predetermined communication method via a predetermined network and receives upload data transmitted from the terminal device;
A reservation information registration unit for registering the reservation information in the reservation information management database based on the upload data received by the upload data receiving unit;
When the upload data transmitted from the terminal device is upload data in a first storage format in which one or a plurality of update schedule information including an update scheduled date is stored, the reservation information registration unit stores the upload data in the upload data Each update schedule information that has been stored is registered in the reservation information management database as reservation information, and one or more update schedule information that does not include the update schedule date is stored, and the update schedule date is stored in the header part. In the case of upload data in the storage format, the update date is extracted from the header area of the upload data, and reservation information storing the contents of the update schedule information stored in the upload data is stored as the reservation information. Register in the management database and store the extracted scheduled update date in each registered reservation information.
An ID information management server characterized by the above. An ID information management database in which ID information for each user is registered;
A computer comprising: a reservation information management database in which reservation information for updating the ID information management database is registered;
Access the reservation information management database at a predetermined timing, sequentially search all the registered reservation information, determine whether the scheduled update date included in the searched reservation information is the current day, If it is that day, an ID information update unit that updates the contents of the ID information management database based on the contents of the reservation information;
An upload data receiving unit that performs data communication with a terminal device by a predetermined communication method via a predetermined network and receives upload data transmitted from the terminal device;
A program that functions as a reservation information registration unit that registers the reservation information in the reservation information management database based on the upload data received by the upload data reception unit,
When the upload data transmitted from the terminal device is upload data in a first storage format in which one or a plurality of update schedule information including an update scheduled date is stored, the reservation information registration unit stores the upload data in the upload data Each update schedule information that has been stored is registered in the reservation information management database as reservation information, and one or more update schedule information that does not include the update schedule date is stored, and the update schedule date is stored in the header part. In the case of upload data in the storage format, the update date is extracted from the header area of the upload data, and reservation information storing the contents of the update schedule information stored in the upload data is stored as the reservation information. Register in the management database and store the extracted scheduled update date in each registered reservation information.
A program characterized by that.

Images