JP2016048513A - List management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently manage a list at an organization.SOLUTION: A user table 200 stores user information including a department name, a user name and a mail address. A list storage 110 stores a list 300 with a department name column and a user name column. A task request section 105 acquires, on the basis of the department name and the user name, the mail address of a requested person who is requested for a task for the list 300 from the user table 200, and sends an e-mail on which a request of the task from a requester is written to the mail address as a destination. A task realization section 106 enables the requested person who received the e-mail sent by the task request section 105 to perform the task for the list 300 according to the request of the task written on the e-mail.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a list management system for managing a list in an organization.

  In an organization such as a company, there is a task of maintaining and managing a list created by a spreadsheet or the like such as Excel (registered trademark) among employees. This work is mainly done manually. For example, the administrator who manages the master of such a list sends the file storing the list to the person in charge as an email, or places the file on a file server and stores the location (path name) electronically. A method of requesting an update by e-mail notification is used.

Some e-mail software can display a list of whether or not an e-mail indicating that the task has been completed is returned when an e-mail requesting a task is sent. For example, Microsoft Outlook (registered trademark) has a function of creating and managing task requests (see, for example, Non-Patent Document 1).
Patent Document 1 and Patent Document 2 disclose a technique for automatically extracting a task request and an answer from an electronic mail.

In the database, the database administrator can set the access right of the user for each record of the table. Therefore, when the list is stored in the database table, by setting the user access right for each record in the table, it is possible to update only the records that each user is responsible for.
Patent Document 3 discloses a technique for setting a review time for each file in a file management system to ensure updating, and contacting a manager (common to all files) when review is necessary.

  The list often includes the department in charge and the name of the person in charge. When the list is a database table, a batch program is executed for each system, and the department name and the person in charge in the database are updated when personnel changes.

  In addition, companies often use groupware to manage each person's tasks. In the groupware, it is possible to set a requested task for each individual regarding a task request between employees, and to input or display a task completion status. Some groupware can input and manage the requested task when requesting a task between employees. In such groupware, each person can check the tasks requested by other employees and their completion statuses, and the tasks requested by themselves and their completion statuses in a list.

JP 2006-190177 A JP 2002-7437 A JP 2007-213171 A

“Create and manage job requests”, [online], [Search July 3, 2014], Internet <URL: http: //office.microsoft.com/en-us/outlook-help/HA001229368. aspx>

Companies have many lists, but there are various difficulties in maintaining them.
For example, when the list is created as a spreadsheet, the department name, person in charge, etc. of the list cannot be updated in a batch. When a personnel change occurs, the list must be manually updated using the character string replacement function of the spreadsheet based on the personnel change data. For this reason, it takes time and cost to change the department name in the list when personnel changes.

Further, in a company, when updating the person-in-charge list of each department, there are cases where a large number of people are instructed and requested at the same time. In such a case, there is one email for the request, but there are as many reply emails as the completion of the update, and the task completion status such as how many of the requests are not completed and who is not completed. It is difficult to grasp.
Even when using email software that can display a list of reply emails for request emails, reply emails for various requests are displayed in a mixed manner, so it is possible to grasp the completion status of each request and which matters have been completed. It is difficult to figure out if
In addition, the organizer must separately create a progress management table using a spreadsheet, etc., and manually enter the task completion status for each request destination in the progress management table based on the reply email. I don't get it.
In addition, when trying to analyze the number of days required to update a list for business improvement in a company, it is necessary to manually input data by e-mail, which requires a large amount of work.

  Furthermore, when a person in charge listed in the list retires, the manager of the list may not be aware and the person in charge may remain unupdated.

  An object of the present invention is to provide a list management system capable of efficiently managing a list in an organization.

In order to achieve the above object, the list management system of the present invention provides:
User information storage means for storing user information including user identification information for identifying a user and an email address of the user;
A list storage means for storing list data including user identification information of requestee candidates who can become requestees;
The list data input by the user identified by the user identification information included in the user information stored in the user information storage means is received, and the list data is registered in the list storage means. A list registration means;
Selected from the list data stored in the list storage means by the client who is the user identified by the user identification information included in the user information stored in the user information storage means List determination means for determining the list data as a task target;
The requestee selected by the requester from the requestee candidates indicated by the user identification information included in the list data determined as the task target by the list determination means is the user information storage. Requestee determination means for determining, when the user is identified by the user identification information included in the user information stored in the means, the requestee as a task request destination for the list data When,
Obtains the email address of the requestee determined as the request destination of the task by the requestee determination means from the user information stored in the user information storage means, and uses the acquired email address as the destination for the request A task request means for sending an e-mail in which a task request by a user is described;
The requestee who has received the e-mail sent by the task requesting unit is subject to the list data determined as the task target by the list determining unit, according to the task request described in the e-mail. A task realization means that makes it possible to execute a task;
It is characterized by providing.

Preferably, the list management system of the present invention comprises:
The list data is created by a spreadsheet.

Preferably, the list management system of the present invention comprises:
The requestee determination means can cause the requester to select a requestee to update each record for each record of the list data, and the selected requestee is the user information storage means. When the user is identified by the user identification information included in the user information stored in the table, the selected requestee is determined as a request destination for each record of the list data,
The task realization means presents, to each requested person, only the record in which each requested person is determined as a request destination by the requested person determining means, and only the presented record is presented to each requested person. Allow users to update,
It is characterized by that.

Preferably, the list management system of the present invention comprises:
A progress manager presenting means for presenting the progress of the task for the list data to the user who has input the list data registered by the list registration means;
Progress requestee presenting means for presenting to the requestee the progress of the task for the list data;
Progress requester presenting means for presenting the requester with the progress of the task for the list data;
It is characterized by comprising a progress management means including

Preferably, the list management system of the present invention comprises:
The progress management means includes prompting means for sending a reminder e-mail to a requestee who has not completed the task at a timing set by the requester.

Preferably, the list management system of the present invention comprises:
The user identification information includes a user name and a department name,
Based on the data indicating the department change and / or personnel change, the department name and / or user name of the user identification information included in the list data stored in the list storage means is updated, and the use The mail address of the user who entered the list data registered by the list registration means is acquired from the user information stored in the person information storage means, and the updated mail address is used as the destination. A department name / user name update means for sending an e-mail in which a request for a task for checking a department name and / or a user name is described;
In the requestee determination means, the requestee is selected by the requester who has received the e-mail transmitted by the department / user name update means,
The tasks that can be executed by the task realization means are: the requestee determined by the requestee determination means confirms the department name and / or user name of the user identification information included in the list data; Is to update,
It is characterized by that.

Preferably, the list management system of the present invention comprises:
The task that can be executed by the task realization means is that the requestee determined by the requestee determination means obtains a document file related to the list data that is the target of the task, and / or It is characterized by submitting a document file related to the list data.

  According to the present invention, a list can be efficiently managed in an organization.

It is a figure which shows an example of a structure of a list management server utilization system. It is a figure which shows an example of a structure of a user table. It is a figure which shows the example of a list. FIG. 3A shows an example of a product list. FIG. 3B is a diagram showing an example of a list of meeting participants. It is a figure which shows an example of a list table. It is a figure which shows an example of a task table. It is a figure which shows an example of the task table for every record. It is a figure which shows an example of a department name change table. It is a figure which shows an example of a transfer table. It is a figure which shows an example of the flow of the list registration process which registers a list in a list storage. It is a figure which shows an example of a user screen. It is a figure which shows an example of the list list in a user screen. It is a figure which shows an example of the flow of the task request process which requests the task about a list. It is a figure which shows an example of a department / person in charge designation screen. It is a figure which shows an example of a request screen. It is a figure which shows an example of the requested task list in a user screen. It is a figure which shows an example of the list which is the person in charge of a record in a user screen. It is a figure which shows an example of a task execution screen. It is a figure which shows an example of the task list requested in the user screen. It is a figure which shows an example of a request person's progress display screen. It is a figure which shows an example of a progress display screen for every record. It is a figure which shows an example of the flow of a department change / transfer process when a department change table and / or a transfer table are updated.

  Hereinafter, a list management system according to an embodiment of the present invention will be described with reference to the drawings. In all the drawings for explaining the embodiments, common constituent elements are denoted by the same reference numerals, and repeated explanation is omitted.

FIG. 1 shows an example of the configuration of a list management server utilization system.
The list management server utilization system includes a list management server 100, a plurality of user terminals 140, a system administrator terminal 150, a mail server 160, and a user authentication system 170. The list management server 100, the plurality of user terminals 140, the system administrator terminal 150, the mail server 160, and the user authentication system 170 are connected to the network 180 and can communicate with each other.
The user terminal 140 has a mail client 141 and a browser 142. The list management server 100 has the function of a Web server, and can display various screens on the browser 142 and accept operations input to the browser 142. The mail client 141 and the list management server 100 can send and receive mail via the mail server 160.
The system administrator terminal 150 has a database client 151. There is a system administrator in the list management server utilization system. The system administrator updates each DB using the database client 151.
The list management server 100 and the user terminal 140 adopt a single sign-on technology. With the single sign-on technology, the user can receive identification and authentication by the user authentication system 170 when logging into the user terminal 140 prior to use of the list management server 100. The list management server 100 acquires the result of identifying and authenticating the user from the user authentication system 170, and identifies the user.

The list management server 100 is an example of a list management system of the present invention. The list management server 100 includes a CPU (Central Processing Unit), a main memory including a RAM (Random Access Memory), a storage device including a hard disk, a list storage 110, a task DB (database). ) 120 and a department name / user name DB 130. The list storage 110, the task DB 120, and the department / user name DB 130 may be independent devices or may be stored in a storage device.
A list management program is stored in the storage device of the list management server 100, and the CPU of the list management server 100 reads the list management program from the storage device into the main memory and executes it, whereby the authentication unit 101. , List registration unit 102, list determination unit 103, requested party determination unit 104, task request unit 105, task realization unit 106, progress management unit 107, department name / person in charge name update unit The function of each part with 108 is realized.

The list storage 110 stores a list 300 that is list data. The user who has registered the list 300 in the list storage 110 is responsible for maintaining and updating the list 300. That is, the user who registered the list 300 becomes the manager. A user who uses the user terminal 140 can be both a requester who requests a task for the list 300 and a requestee who is requested for the task. There may be a case where a requester of a task that targets a certain list 300 is a requestee of a task that targets another list 300. Tasks include, for example, updating a list, distributing and submitting documents related to the list.
The task DB 120 stores a list table table 400, a task table 500, and a task table for each record 600. The list table 400 is a list of the list 300 stored in the list storage 110. The task table 500 stores requests for tasks for the list 300 stored in the list storage 110. The task table 500 stores both completed and uncompleted tasks. The per-record task table 600 stores information about tasks for each record in the list 300. The per-record task table 600 stores both completed and uncompleted tasks.
The department name / user name DB 130 stores a department name change table 700, a transfer table 800, and a user table 200. The department change table 700 stores a department change history for all the signatures appearing in the list 300 stored in the list storage 110. The department change table 700 stores both past and scheduled ones. The change table 800 stores a history of changes for all user names appearing in the list 300. The transfer table 800 stores both past and planned items. The user table 200 stores information about all users who use the list management server 100. The user table 200 can also be introduced into the user authentication system 170.

FIG. 2 shows an example of the configuration of the user table 200.
The user table 200 stores user information including, for example, a user ID (Identifier) 201, a department name 202, a user name 203, a mail address 204, and a user status 205. Each user of the list management server 100 is registered in the user table 200.
The user ID 201 is information that uniquely indicates a user. The department name 202 indicates the department to which the user belongs. A user name 203 indicates the name of the user. The department name 202 and the user name 203 are examples of user identification information according to the present invention. An e-mail address 204 indicates an e-mail address that is a destination when the user is contacted by e-mail.
The user state 205 indicates, for example, whether the user is a responsible person, a retired person, or another person. The retired person cannot use the list management server 100, and the retired person's authentication is failed. The role of the person in charge will be described with reference to FIG.

FIG. 3 shows an example of the list 300. FIG. 3A shows an example of the product list 301. FIG. 3B shows an example of the XX conference participant list 311.
The column is different for each list 300. The example of the product list 301 in FIG. 3A includes a record 306 including a product ID 302, a product name 303, a responsible department 304, a responsible person name 305, and so on (other columns). 3B includes a record 306 that includes a participant ID 312, a department 313, a participant name 314, and an attendance 315.
Here, the department name 202 and the user name 203 included in the user information are required in any list 300. However, in the different list 300, the department name 202 and the user name 203 may have different names and names. Which of the columns of each list 300 corresponds to the department name 202 and the user name 203 is specified by the administrator of each list 300 (the person who registered each list 300 in the list storage 110). To do.
For example, the department 304 in charge is the department name 202 in FIG. A responsible department 304 indicates a department that maintains the record 306. The person in charge name 305 is the user name 203. A person-in-charge name 305 indicates a person in charge (requestee) who is requested to update the record 308. The person in charge belongs to the department with the department name 304. If the person-in-charge name 305 is undefined, the person in charge of the department with the department name 304 is requested to update the record 306. That is, the user who is described as the person in charge in the user state 205 in FIG. 2 is requested to update the record 306. The example of FIG. 3A shows a case where there is one person in charge name 305 per record 306, but a plurality of person in charge names 305 can be set.
As an example of a task for the product list 301, there is a change in the product name 303, the department in charge 304, or the person in charge name 305.

As an example of a task for the XX conference participant list 311, the attendance 315 is filled in, and the conference participant (requestee) is a document file related to the XX conference participant list 311 (meeting materials and proceedings). Record), meeting participants may submit document files (review of meeting materials and minutes).
The exchange of materials between the manager of the conference participant list 311 and the conference participants is performed by attaching a document file, for example. In order to attach a document file, a folder corresponding to each list 300 (hereinafter referred to as a storage folder) is provided in the list storage 110. The file is attached through the storage folder.
As will be described later, for example, when the minutes are distributed to the conference participants, the manager of the conference participant list 311 attaches the minutes by pressing the file attachment button 1408 on the request screen 1400 in FIG. To do. At this time, the minutes are stored in the storage folder. As a person in charge (requestee), the conference participant can refer to the minutes by selecting the record 1709 on the task execution screen 1700 in FIG. 17 and pressing the attached file button 1710. Further, for example, when a conference participant submits a review of the minutes as a person in charge (requestee), the conference participant selects the record 1709 on the task execution screen 1700 of FIG. 17 and presses the file attachment button 1711. Attach a review of the minutes. At this time, the review of the minutes is stored in the storage folder. The administrator selects the record 2008 on the progress display screen 2000 for each record in FIG. 20 and presses the attached file button 2009 to refer to the review of the minutes or take it out and save it in the storage device of the user terminal 140. You can do it.

FIG. 4 shows an example of the list table 400.
There is one list table 400 for each organization such as a company that uses the list management server 100.
The list table 400 includes, for example, a list ID 401, a list name 402, an administrator name 403, a registration date and time 404, a department name range 405, a user range 406, and a relationship 407 between departments. Is done.
A list ID 401 is information that uniquely indicates the list.
A list name 402 indicates the name of the list 300 stored in the list storage 110. Note that there may be a plurality of registered lists 300 having the same name (file name). The list 300 is stored in a folder in the list storage 110 so that the list with the same file name can be registered, and the folder name + file name including the folder name is added as the list name 402 when the list name is registered. It can also be specified.
The administrator name 403 is information indicating the administrator of the list 300 (that is, the person who registered the list 300 in the list storage 110). The administrator name 403 corresponds to the user ID 201, the user name 203, or the mail address 204 in the user table 200. The administrator requests the requestee to update the list 300.
The registration date and time 404 is the date and time when the administrator registered the list 300 in the list storage 110.
The department name range 405 indicates the column name and row number in which the department name in the list 300 is specified.
A user range 406 indicates column names and row numbers in which users in the list 300 are specified.
The relationship 407 between departments has a one-to-one and one-to-n relationship, and indicates a method of updating the list 300 when the departments are divided, merged, or abolished. Here, one-to-one is a case of one department and one record. When departments are divided, it is necessary to add records and set the person in charge for the increased number of departments. When departments are merged or abolished, it is necessary to delete as many records as there are departments. One-to-n is a case where there are a plurality of records (zero or more) for each department. When a department is divided, it is necessary to distribute existing records to any department.

FIG. 5 shows an example of the task table 500.
The task table 500 includes, for example, a task number 501, a list ID 502, a list name 503, a requester name 504, a task type 505, a start date and time 506, a deadline date and time 507, a reminder date and time 508, and a subject name 509. , Request sentence 510, storage folder path 511, and status 512.
When a row is added to the task table 500, for example, when the list 300 indicated by the list name 503 is the product list 301 in FIG. When a person in charge in the product list 301 offers to change the department in charge 304 or the person in charge name 305, a new department name change is registered in the department name change table 700 for the department in charge 304 in the product list 301, and There is a case where a new change is registered in the change table 800 for the person in charge name 305 in the product list 301.
Task No. 501 is a number uniquely assigned to each task. The list ID 502 is information that uniquely indicates the list 300. A list name 503 is a name of the list 300.
The requester name 504 differs depending on the task type 505. The task type 505 includes request, offer, department name change, and transfer. When the administrator of the list 300 makes a request, it becomes a request, and when the person in charge of the record 306 offers, it becomes an offer. When the department name is changed, the department name is changed, and the person in charge changes. If it is a change.
The start date and time 506 indicates the date and time when the request is made. The time limit date and time 507 indicates the date and time when the requestee should complete the update. The reminding date and time 508 indicates the date and time that the progress management unit 107 is scheduled to prompt.
The subject 509 and the request sentence 510 are a subject and a request sentence input by the requester, as will be described later.
A storage folder path 511 indicates a path to a folder in which a document distributed to the requestee by the requester, a document submitted by the requestee, or the like is stored. As described later with reference to FIGS. 14 and 17, when the file attachment button 1408 on the request screen 1400 is pressed by the requester and when the file attachment button 1711 on the task execution screen 1700 is pressed by the requestee, the task The request unit 105 secures a storage folder in the list storage 110 and sets a path to the storage folder in a storage folder path 511.
The state 512 indicates the total number of records in each requested task and the number of records that have been updated. For example, when the total number of requested records of task No. 501 = 1 is 100 and updating of 50 records is completed, “50 out of 100 completed” is obtained.

FIG. 6 shows an example of the per-record task table 600.
The per-record task table 600 includes a task No 601, a user ID 602, a record number 603, a task status 604, an update location 605 in the record, a last update date 606, a pre-update record 607, and a post-update record 608. It consists of.
When a row is added to the task table 500, one row is added to the per-record task table 600 for the corresponding record 306 in the list 300 indicated by the list name 503 of the task table 500.
Task No. 601 is a number uniquely assigned to each task. Task No. 601 indicates the task No. 501 of the corresponding task table 500.
A user ID 602 indicates a user ID of a requestee to whom a task request is sent. The user ID 602 corresponds to the user ID 201 of the user table 200.
A record number 603 indicates the record 306 for which a task is requested.
The task state 604 indicates the progress status of the request for the record 306. For example, it is not completed before the requestee executes the task, but is completed if the task is completed. Further fine division can be made.
The update location 605, the last update date / time 606, the pre-update record 607, and the post-update record 608 are effective when the task is to update the record 306. When the task content is acquisition or submission of a document by the requestee, the update location 605 in the record is the path to the attached file that is referenced or attached, and the last update date and time 606 is the date and time of reference or attachment. The pre-update record 607 is a referenced attached file, and the post-update record 608 is an attached file.
An update location 605 in the record indicates an updated location in the record 306. There may be multiple update locations. The last update date and time 606 is the date and time of the last update by updating the task No. 601 for the record 306. If the task No 601 has not been updated yet, it is undefined. The pre-update record 607 is data of the record 306 before being updated by the requestee. The updated record 608 is data of the record 306 after being updated by the requestee. Before the requestee updates the record 306, it is undefined.

For example, if the person in charge name 305 of the plurality of records 306 in the product list 301 (list 300) is the same, the person in charge may be requested to update the plurality of records 306. In that case, even if the user ID 602 is the same, a row having a different record number 603 is added for each record 306 to be updated.
Further, there may be a plurality of update requests for the same record 306. In such a case, the requestee determination unit 104 detects and notifies the requester and the requestee. However, since the number of requested clients that can be updated is limited to one by the structure of the task table 600 for each record, it is possible to prevent the inconvenience that two people update at the same time and one update is lost. When the requestee updates the record 306 having a plurality of update requests, the last update date and time 606 for the record 306 is the same date and time in the update request task.

FIG. 7 shows an example of the department name change table 700.
The department change table 700 includes a department change No. 701, a change date 702, an old department 703, a new department 704, and a department change classification 705.
The department change number 701 is a number uniquely assigned to each line. The change date and time 702 indicates the date and time when the department name is changed. The old department name 703 indicates the department name before the change. A new department name 704 indicates the department name after the change.
The department change classification 705 indicates the type of department change, and includes change, new establishment, abolition, division, and integration. The change indicates a case where the name of one department is changed, and one line is added to the department name change table 700. The addition indicates a case where one department is added, and the old department name 703 is undefined. The abolition indicates a case where one department is abolished. One line is added to the department change table 700, and the new department 704 is undefined. The division indicates a case where one department is divided into a plurality of departments, and the number of lines corresponding to the number of departments after division is added to the department change table 700. Integration indicates a case where a plurality of departments are integrated into one department, and the number of lines corresponding to the number of departments before division is added to the department change table 700. At the start of use of the list management server 100, the department change section 705 is additionally registered.
When a line is added to the department change table 700, the department / person in charge name update unit 108 updates the user table 200 accordingly. Further, the task request unit 105 adds one line to the task table 500 for the list 300 related to the change of the department name.

FIG. 8 shows an example of the transfer table 800.
The change table 800 includes a change number 801, a change date and time 802, a transfer person name 803, a change front signature 804, a change back signature 805, and a change classification 806. One line is added to the change table 800 for each change of one user.
The change No. 801 is a number uniquely assigned to each row. The change date and time 802 indicates the date and time of change. The transferer name 803 indicates the user who is transferred. The pre-change part name 804 indicates the pre-change part name. The post-change department name 805 indicates the post-change department name.
The change classification 806 indicates the type of change, and includes registration, transfer, retirement, and the like. Registration indicates that the user starts to use the list management server 100 anew. The change indicates that the user's department name is changed. Retirement means that if the transferee name 803 is specified in the list 300 as the person-in-charge name 305 or the participant name 314, it is necessary to update, and it is necessary to update to another person by the transfer date and time 802. It indicates that the transfer table cannot be used by the transfer person after the transfer date and time 802.
When a line is added to the transfer table 800, the department name / person-in-charge update unit 108 updates the user table 200 accordingly. Further, when a row in which the change classification 806 is changed or retired is added, the task request unit 105 adds one row to the task table 500 for the list 300 related to the transferee.

Hereinafter, functions of each unit of the list management server 100 will be described.
All users of the list management server 100 are registered in the user table 200 in advance. In addition, the administrator of each list 300 creates the list 300 using a spreadsheet such as Excel (registered trademark) on the user terminal 140 in advance, or acquires the created list 300 and Save in the storage device of the terminal 140. Creation, acquisition, and storage of the list 300 are processing outside the list management server 100. The list 300 is stored in a folder secured in the storage device of the user terminal 140, for example. In the list 300, the department name and user name of the user who should maintain the record 306 are written.

FIG. 9 shows an example of a list registration process flow for registering the list 300 in the list storage 110.
[Processing of Authentication Unit 101, User Identification / Authentication Step (S901)]
The user receives identification and authentication by the user authentication system 170 before accessing the list management server 100. When the user accesses the list management server 100, the user ID 201 and the user name 203 have been identified and authenticated.
When there is an access from the user terminal 140 to the list management server 100, the authentication unit 101 inquires the user authentication system 170 about the identification / authentication status of the user and obtains a response so that the user can access the user table. The user in 200 is identified. At this time, if the user state 205 is a retired person, the user identification / authentication process is failed and the authentication unit 101 returns an error message to the user terminal 140.

[Process of List Table Registration Unit 102, List Table Registration Step (S902)]
The list registration unit 102 stores the list 300 input by the user identified by the department name 202 and the user name 203 (user identification information) included in the user information stored in the user table 200. The list 300 is received and registered in the list storage 110.
Specifically, when the authentication unit 101 identifies and authenticates the user, the list registration unit 102 displays the user screen 1000 in FIG. 10 on the browser 142 of the user terminal 140.
The user screen 1000 includes a list list 1001, a requested task list 1002, a requested task list 1003, and a list list 1004 in which the user is in charge of the record.
As shown in FIG. 11, the list table list 1001 includes a list table ID 1201, a list table name 1202, an administrator name 1203, an incomplete task 1204, a completed task 1205, and a list table output button 1206. The
The list registration unit 102 displays the list 300 stored in the folder in the storage device of the user terminal 140 on the folder screen 1207 in the browser 142. The user inputs the list 300 to the list management server 100 by dragging and dropping the icon of the list 300 in the folder screen 1207 to the area of the list list 1001 in the user screen 1000 in the browser 142 ( Send).
The list registration unit 102 receives the input list 300 and registers the list 300 in the list storage 110. Then, the list registration unit 102 adds a new row to the list table 400, adds a list ID 401, and registers the list name 402. Here, the list registration unit 102 registers the user name 203 of the user who has been previously identified and authenticated as the administrator name 403. Furthermore, a list ID 1201, a list name 1202, and an administrator name 1203 are additionally displayed in the list 1001. Here, the list registration unit 102 automatically determines the department range 405 and the user range 406 based on the column names or data of the list 300. The list registration unit 102 can use the registered contents of the department change table 700 and the transfer table 800 for this determination.
The uncompleted task 1204 and the completed task 1205 indicate the number of tasks that are not completed and completed among the tasks requested by the administrator for the list 300. The progress management unit 107 calculates the incomplete task 1204 and the completed task 1205 at a predetermined timing and displays them on the list 1001.
The list 1001 is an example of the progress manager presenting means of the present invention.

FIG. 12 shows an example of a flow of task request processing for requesting a task for the list 300.
Prior to the task request, the requester (user) receives identification of which user in the user table 200 by the authentication unit 101 (S1201). The processing of the authentication unit 101 in step S1201 is the same as that in step S901 described above.

[Process of List Table Determining Unit 103, List Table Determination Step (S1202)]
The list table determination unit 103 is a user identified by a department name 202 and a user name 203 (user identification information) included in the user information stored in the user table 200 (hereinafter referred to as a requester). Thus, the list 300 selected from the list 300 stored in the list storage 110 is determined as a task target.
For example, when the task type 505 is a request, the requester selects the list 300 that is the target of the task by selecting the row of the list 1001 displayed in the browser 142 with a mouse or the like. The list determination unit 103 determines the list 300 selected by the requester as a task target.
Further, the list 1004 displayed in the browser 142 for which the person in charge of the record is in charge will be described in detail later with reference to FIG. The table list 1004 displays a list 300 in which the user is in charge of the record. For example, if the task type 505 is an offer, the requester selects the list 300 that is the target of the task from the list 1004 that is the person in charge of the record. The list determination unit 103 determines the list 300 selected by the requester as a task target.

[Processing by Requestee Determination Unit 104, Requestee Determination Step (S1203)]
The requestee determination unit 104 includes a candidate candidate indicated by the group name 202 and the user name 203 (user identification information) included in the list 300 determined as a task target by the list determination unit 103. The requestee selected by the requester is a user identified by the department name 202 and the user name 203 (user identification information) included in the user information stored in the user table 200. Then, the requested person is determined as a task request destination for the list 300.

Specifically, when the list table 300 that is the target of the task is determined by the list table determination unit 103, the requestee determination unit 104 stores the group signature shown in FIG. 13 in the browser 142 based on the list table 300. -The person-in-charge designation screen 1300 is displayed. The department name / person-in-charge designation screen 1300 includes at least a list name 1301, a department name 1302, a department name range frame 1303, a user name 1304, a user name range frame 1305, a confirmation message 1306, and a completion button. 1307 and a cancel button 1308.
The requestee determination unit 104 displays the department name range frame 1303 and the user range frame 1304 based on the department range 405 and the user range 406 of the list table 400, and displays a confirmation message 1306 that prompts updating. The requestee determination unit 104 further confirms whether the combination of the department in charge 304 and the person in charge name 305 of each record 306 in the list 300 is in the department name 202 and the user name 203 in the user table 200. . If there is a combination that does not match, the requestee determination unit 104 displays an error message. The requestee determination unit 104 processes a case where the department name 1302 or the user name 1304 is not defined even if it is not defined. Here, when the requester is the administrator of the list 300 (that is, the user who registered the list 300 in the list storage 110), the department name or the user name of the list 300 is corrected and corrected. The match can be confirmed again using the result of the list 300. When the administrator modifies, it is possible to select from the department name 202 and the user name 203 in the user table 200.

When the completion button 1307 is pressed by the requester, the requestee determination unit 104 selects the list based on the department name 1302 in the department name range frame 1303 and the user name 1304 in the user name range frame 1305. A requestee who is a request destination of the task for the table 300 is determined.
Note that the user name is a record in the list 300, such as the person in charge name 305 in the product list 301 in FIG. 3A and the participant name 314 in the XX conference participant list 311 in FIG. It is specified for each 306. For this reason, the requestee determination unit 104 can cause the requester to select a requestee to update the record for each record 306 in the list 300 on the department name / person-in-charge designation screen 1300. The requestee is determined as a request destination for each record 306 in the list 300. Then, as will be described later, the task realization unit 106 presents only the records in which each requested person is determined as the request destination by the requested person determination unit 104 on the task execution screen 1700 of FIG. It is possible for each requestee to update only.

[Process of Task Request Unit 105, Task Request Step (S1204)]
The task request unit 105 acquires the requestee email address 204 determined by the requestee determination unit 104 from the user information registered in the user table 200, and the requester uses the acquired email address as the destination. Send an email with the task request.
Specifically, when the requestee is determined by the requestee determination unit 104, the task requesting unit 105 displays a request screen 1400 shown in FIG. 14 on the browser 142 of the user terminal 140 of the requester. The requester inputs the task contents for the list 300 on the request screen 1400.
The request screen 1400 includes a list ID 1401, a list name 1402, a requestee name 1403, a deadline date 1404, a reminder date 1405, a subject 1406, a request sentence 1407, a file attachment button 1408, and a request button 1409. And a request button 1410 and a cancel button 1411 later.
The deadline date 1404 indicates the deadline for completing the task. The reminding date and time 1405 indicates the date and time when the progress management unit 107 transmits the reminding mail. The requester inputs the expiration date 1404 and the reminder date 1405.
A subject 1406 and a request sentence 1407 are a subject and a request sentence to be transmitted to the request destination regarding the task. The requester inputs the subject 1406 and the request sentence 1407.
When the file attachment button 1408 is pressed by the requester, the task request unit 105 secures a save folder in the list storage 110 and opens a screen for saving the document file in the save folder in the browser 142. The requester can save the document file in the save folder by dragging and dropping the document file onto the screen.

When the requester sets each item on the request screen 1400 and presses the request button 1409, the task request unit 105 adds a new row to the task table 500 and registers the contents of each item. At the same time, the task request unit 105 adds a row corresponding to each record 306 of the list 300 to the record-by-record task table 600. At this time, the task request unit 105 registers the reminding date and time 508 in the event management function of the operating system. As a result, when the reminding date / time is reached, an event is notified to the list management server 100, thereby prompting the requestee who is not executing the task.
Next, the task request unit 105 searches the user table 200 and acquires the mail address 204 corresponding to each requested person. Then, the task request unit 105 creates an e-mail addressed to the e-mail address 204 acquired based on the contents registered in the task table 500, and transmits the e-mail to the requestee via the mail server 160.
Although FIG. 13 described above shows an example in which one department name frame 1303 and one user range frame 1304 are displayed on the department / person name designation screen 1300, one list 300 is shown. A plurality of department range frames 1303 and user range frames 1304 may be set. As a result, it is possible to request a task by designating only a part of the records 306 in the list 300 or only a part of many persons in charge. Further, in the present embodiment, the case where there is one person in charge name 305 and one participant 314 for each record 306 is described, but when a plurality of person in charge names 305 and participants 314 are set, the record 306 You can also choose to send only to the representatives and participants, or to all representatives and participants.

[Process of Task Realization Unit 106]
The task realization unit 106 describes the list 300 determined by the list determination unit 103 as the task target by the requestee who has received the email transmitted by the task request unit 105. The task can be executed according to the requested task.
The task realization part 106 performs a task confirmation process and a task execution process. However, prior to the execution of the task confirmation process and the task execution process, the requestee (user) receives identification of which user in the user table 200 by the authentication unit 101 (S1205). The processing of the authentication unit 101 in step S1205 is the same as that in step S901 described above.

[Task Confirmation Step (S1206)]
When the user screen 1000 is displayed on the browser 142 of the user terminal 140 used by the requestee, the task realization unit 106 sets the user ID 201 corresponding to the user name 203 of the requestee for each record task. Search is made in the table 600, and the requested task list 1003 in FIG. 15 and the list list 1004 in which the user is in charge of the record in FIG. 16 are displayed on the user screen 1000.
The task realization part 106 displays the task requested by the requestee in the requested task list 1003. In addition, the task realization unit 106 displays a list including the records in which the requested person is in charge in the list 1004 in which the task is in charge of the record. By looking at the requested task list 1003 or the list 1004 that is the person in charge of the record, the requestee can know the task requested by him.

As shown in FIG. 15, the requested task list 1003 includes a task No 1501, a requester name 1502, a list name 1503, a start date and time 1504, a deadline date and time 1505, a subject name 1506, and a request statement 1507. The number of records requested 1508, the number of records not updated 1509, and a completion status 1510 including other request destinations.
The number of requested records 1508 and the number of unupdated records 1509 indicate the number of records that the requestee is in charge of and the incomplete of the task No. 1501 for the list 300 of the list name 1503. Is the number of records.
In the requested task list 1003, when the requestee selects a row including the list name 1503 to be executed, the task realization unit 106 takes charge of the requestee from the list 300 in the list storage 110. A task execution screen 1700 shown in FIG. 17 is displayed on the browser 142 by selecting the record 306 in which the task is not completed. Note that by specifying a condition for selecting the record 306 to be displayed, it is possible to display only those for which the task has been completed on the task execution screen 1700, or display both incomplete and completed tasks.

Also, as shown in FIG. 16, the list 1004 in which the person in charge of the record is in charge is a list ID 1601, list name 1602, manager name 1603, number of records in charge 1604, incomplete task. 1605 and a completion task 1606.
Even when there is no task request for the list 300, the user, for example, what kind of responsibility he / she is in charge of when preparing a work plan, and what kind of request he / she needs to respond to in the future You may want to check. In such a case, the user refers to the list 1004 in which the user is in charge of the record. The list 1004 for which the person is in charge of the record includes a list 300 that does not include the task requested by the user (the task for which the user is a requestee). Of the list 300 in the table 400, the list 300 in which the user is the person in charge of the record is displayed.
Here, the number of records in charge 1604 indicates the number of records in which the person in charge is in charge of the list 300 displayed in each row.
An incomplete task 1605 indicates the number of tasks that have not been completed among the tasks requested by the user regarding the list 300 displayed in each row. The completed task 1606 indicates the number of tasks that have already been completed among the tasks requested by the user regarding the list 300 displayed in each row. The fact that both the incomplete task 1605 and the completed task 1606 are 0 means that no task is requested for the list 300 (i.e., the user is not a requestee).
For this reason, each requested person can grasp what person he / she is in charge by referring to the list name 1602 of the list / list 1004 in which he / she is in charge of the record. In the list 1004 that is the person in charge of the record, when the requestee selects a row including the list name 1602 that he / she wants to execute the task and selects task execution from the pull-down menu displayed at that time, for example, Similarly to the above, the task realization unit 106 selects the record 306 in which the task in charge of the requestee is incomplete from the list 300 in the list storage 110, and displays the task execution screen 1700 of FIG. . Note that by specifying a condition for selecting the record 306 to be displayed, it is possible to display only those for which the task has been completed on the task execution screen 1700, or display both incomplete and completed tasks.
Further, when requesting a task whose task type 505 is an offer, when the user (requester) selects a row including the list name 1602 to which the task is requested and selects a task offer from a pull-down menu displayed at that time, for example. The list determination unit 103 determines the list 300 selected by the user as a task target.
The requested task list 1003 and the list list 1004 in which the person is in charge of the record are examples of the progress requestee presenting means of the present invention.

[Task execution step (S1207)]
The task execution screen 1700 includes a task No. 1701, a requester name 1702, an expiration date and time 1703, the number of records in charge 1704, a request statement 1705, a list name 1706, a department name 1707, and a person in charge (user name). One or more records 1709 including 1708, an attachment file button 1710, a file attachment button 1711, a completion button 1712, a continue button 1713, and a cancel button 1714 are configured.
The task realization unit 106 displays on the task execution screen 1700 only the records determined to be updated by each requested person by the requested person determination unit 104. The requestee confirms the list name 1706 and the record 1709 of the list 300 that is the target of the task on the task execution screen 1700 and edits the record 1709. The task realization part 106 updates the record 306 of the list 300 stored in the list storage 110 according to the edit of the requestee. For example, if the person in charge has changed from “Sato XX” to “Watanabe ΔΔ”, the requested person changes the person in charge 1708 to “Watanabe ΔΔ”. Accordingly, the task realization unit 106 updates the person-in-charge name 305 of the record 306 in the list 300 to “Watanabe ΔΔ”.
The task realization unit 106 has an editing function for the list 300 created by a spreadsheet. Even when the user terminal 140 of the requestee does not have spreadsheet software, the task realization unit 106 displays the task execution screen. The list 300 created in the spreadsheet according to the input in 1700 can be updated.
The attached file button 1710 is displayed when the file attachment button 1408 is pressed by the requester on the request screen 1400 of FIG. 14 described above and a storage folder is secured in the list storage 110. When the attached file button 1710 is pressed by the requestee, the task realization unit 106 displays the file saved in the save folder by the requester on the browser 142.
When the record 1709 (that is, the record 306 in the list 300) is selected and the file attachment button 1711 is pressed by the requestee, the task realization unit 106 opens a screen for saving the document file in the save folder in the browser 142. . If the save folder is not in the list storage 110 when the file attachment button 1711 is pressed by the requestee, the task realization unit 106 reserves the save folder in the list storage 110 and stores the document in the save folder. A screen for saving the file is opened in the browser 142. The requestee can save the document file in the save folder by dragging and dropping the document file onto the screen.
When the record 1709 (that is, the record 306 of the list 300) is updated on the user terminal 140 and the completion button 1712 is pressed, the corresponding row of the task table 600 for each record is updated, and the task is completed.
Note that a check mark for selecting only some records 1709 may be provided in the task execution screen 1700 so that only some records 1709 can be updated.

[Process of Progress Management Unit 107]
The progress management unit 107 executes a progress confirmation process, a reminder process, and a task completion process.

[Progress confirmation step (S1208)]
FIG. 18 shows an example of a requested task list 1002 in the user screen 1000.
The requested task list 1002 includes a task number 1801, a list ID 1802, a list name 1803, a requestee name 1804, a task type 1805, a start date 1806, an expiration date 1807, and a reminder date 1808. , A subject 1809, a request sentence 1810, a progress 1811 per requestee, a progress 1812 per record, and a deadline button 1813. By viewing the requested task list 1002, the user can confirm the progress of the task requested by another user.
Here, the progress 1811 for each requested person indicates how many of the requested persons who have been requested for the task for the list 300 have completed the task. The progress for each record 1812 indicates how many records of the total number of records included in the list 300 are completed.
In the requested task list 1002, when the user selects a list name 1803 in a row of a task No. 1801, the progress management unit 107 displays the list 300 at that time.

Further, in the requested task list 1002, when the user selects the progress 1811 for each requested person in the row of a task No. 1801, the progress management unit 107 displays the progress display screen 1900 for each requested person shown in FIG.
The requestee progress display screen 1900 includes a list name 1901, a task number 1902, a person in charge 1903, the number of records 1904, a completion status 1905, and a deadline button 1906. By referring to the progress screen 1900 for each requested person, the requester can grasp the progress status of the requested task for each person in charge (for each requested person).

Also, in the requested task list 1002, when the user selects the progress for each record 1812 in a row of a task No. 1801, the progress management unit 107 displays the progress for each record display screen 2000 of FIG.
The record-by-record progress display screen 2000 includes a list name 2001, a task number 2002, a product ID 2003, a product name 2004, a responsible department 2005, a responsible person name 2006, a completion status 2007, an attached file button 2009, and a deadline. And a button 2010. By referring to the progress display screen 2000 for each record, the requester can grasp the progress status of the requested task for each record 2008 (that is, the record 306 of the list 300).
The attached file button 2009 is displayed when the file attachment button 1711 is pressed by the requestee on the task execution screen 1700 of FIG. 17 described above and a storage folder is secured in the list storage 110. When the requester selects the record 2008 and presses the attached file button 2009, the task realization unit 106 displays the file saved in the save folder by the requestee on the browser 142.
FIG. 20 shows a case where there is one person in charge name 2006 per record 306, but a plurality of person in charge names 2006 can be set.
The requested task list 1002, the requestee progress display screen 1900, and the record progress display screen 2000 are examples of the progress requester presenting means of the present invention.

[Reminder Step (S1209)]
When the reminder date for an incomplete task is reached, the event management function of the operating system notifies the progress management unit 107 of the event. The progress management unit 107 identifies a requestee who has not completed a task based on the notified event, the task table 500, and the task-by-record table 600. Then, the progress management unit 107 transmits a reminder e-mail to the identified requestee via the mail server 160.
Note that the prompting step of step S1209 is an example of steps executed by the prompting means of the present invention.

[Task completion step (S1210)]
When all the requestees have completed the task, or some of the requestees have not executed the task but the deadline has passed, the requester selects a task from the requested task list 1002 Then, by pressing the deadline button 1803, or by pressing the deadline button 1906 or the deadline button 2010 on the progress display screen 1900 for each requestee or the progress display screen 2000 for each record, the record update by the subsequent requestee for the task is performed. Can be prohibited.
When the deadline buttons 1803, 1906, and 2010 are pressed, the progress management unit 107 prevents the requested person from executing the task thereafter.
By pressing the deadline buttons 1803, 1906, 2010, the administrator can complete the task for the list 300.

  Further, the administrator of the list 300 can select several list names 1202 and press the list output button 1206 in the list 1001 of FIG. When a list output button 1206 is pressed, the progress management unit 107 takes out the updated list 300 from the list storage 110 and outputs (sends) it to the user terminal 140 of the administrator.

FIG. 21 shows an example of the flow of department change / transfer processing when the department change table 700 and / or the transfer table 800 are updated.
In the department change / transfer process, if there is a department change or personnel change in the organization, the department / person in charge name update unit 108 includes the user name (included in the list 300 stored in the list storage 110). The person-in-charge name 305 and the participant name 314) and the department name (the department in charge 304 and the department 313) are updated. Then, the department name / person-in-charge update unit 108 transmits an e-mail requesting confirmation of the result to the administrator of each list 300 (the user who registered the list 300 in the list storage 110) (S2101). . The subsequent processes are the same as steps S1201 to S1210 in the task request process of FIG.

[Process of Department / Responsible Person Name Update Unit 108, Department / Responsible Person Name Update Step (S2101)]
The department / user name update unit 108 is based on the data indicating the department change and / or personnel changes, and the department name and / or user name included in the list 300 stored in the list storage 110. Is updated, the mail address of the administrator who registered each list 300 is acquired from the user information stored in the user table 200, and the updated department name and / or usage is acquired using the acquired mail address as a destination. Send an e-mail with a task request to confirm the name.
Specifically, when the department name is changed or the user (person in charge or participant) is changed in the organization, the personnel department or the like creates a list of correspondence of the old and new department names and a list of the changes and receives them. The system administrator uses the database client 151 to register the correspondence list of the old and new department names and the change list as additional lines in the department name change table 700 and the change table 800.
When a line is added to the department change table 700 and the transfer table 800, the department / user name update unit 108 adds new lines to the task table 500 by the number of each list 300 in the list storage 110. To do. Then, the department / user name update unit 108, for each department in the range specified in the department range 405 of the list 300, the relation 407 with the department in the list table 400 and the department change table 700. The old department name 703 is updated to the new department name 704 according to the department name change classification 705, the record 306 is divided into two lines, the record 306 is deleted, and the department name (department 304 or department 313) is undefined. Process. Subsequently, the department name / user name update unit 108 changes the user name (the person in charge name 305 and the participant name 314) in the range specified by the user range 406 of the list table 400. In accordance with the change classification 806, the changer's department name is updated from the pre-change department signature 804 to the post-change department name 805, or undefined. When updating the user name, the department / user name update unit 108 updates the user name while confirming that the department name has already been updated using the task table 600 for each record.
The department / user name update unit 108 transmits an e-mail requesting each administrator to confirm the update result of the list 300 when the update of the list 300 due to the change or change of the department name is completed.

Steps after step S2101 are the same as steps S1201 to S1210 in the task request process of FIG.
The administrator sets the department name and user name in the requestee determination step (S1203) for the record 306 in which the department name and user name are updated to undefined in the department name / person name update step (S2101). Then, the requestee of the update of the record 306 can be determined.
This embodiment shows a case where there is one user name for each record 306, but when a plurality of user names are set and only a part of the users retires, the remaining users are notified. It may be requested to set a new user for a retired user.
If the department name and user name are all defined, the department / user name update unit 108 may directly request the user (person in charge or participant). In addition, for each list 300, it may be possible to specify whether the administrator requests or the department / user name update unit 108 directly requests.

  In the above-described embodiment, an example in which the list 300 is created with a spreadsheet has been described. However, the present invention is not limited to this, but can be applied to a list created with another system.

As described above, according to the present invention, a list can be efficiently managed in an organization.
Further, according to the present invention, it is possible to effectively perform work requests and management such as sending and reviewing conference materials, project status reports, work execution status reports, and questionnaire requests. Furthermore, for example, work such as distribution of a list of cases for each person in charge can be effectively performed.

  Although the embodiments of the present invention have been described above, various modifications and combinations necessary for design reasons and other factors are described in the inventions described in the claims and the specific embodiments described in the embodiments of the invention. It should be understood that it falls within the scope of the invention corresponding to the examples.

DESCRIPTION OF SYMBOLS 100 ... List management server 101 ... Authentication part 102 ... List registration part 103 ... List determination part 104 ... Requestee determination part 105 ... Task request part 106 ... Task realization part 107 ... Progress management , 108 ... department / person name update part, 110 ... list storage, 120 ... task DB, 130 ... department / user name DB, 140 ... user terminal, 141 ... mail client, 142 ... browser, 150 ... system administrator terminal, 151 ... database client, 160 ... mail server, 170 ... user authentication system, 180 ... network, 200 ... user table, 300 ... list table, 400 ... list table, 500 ... task table, 600 ... task table for each record, 700 ... department change table, 800 ... transfer table, 1000 ... profit Person screen, 1001 ... List list, 1002 ... Requested task list, 1003 ... Requested task list, 1004 ... List list that is in charge of the record, 1300 ... Department / person in charge Name designation screen, 1400 ... request screen, 1700 ... task execution screen, 1900 ... progress display screen for each requestee, 2000 ... progress display screen for each record

Claims (7)

User information storage means for storing user information including user identification information for identifying a user and an email address of the user;
A list storage means for storing list data including user identification information of requestee candidates who can become requestees;
The list data input by the user identified by the user identification information included in the user information stored in the user information storage means is received, and the list data is registered in the list storage means. A list registration means;
Selected from the list data stored in the list storage means by the client who is the user identified by the user identification information included in the user information stored in the user information storage means List determination means for determining the list data as a task target;
The requestee selected by the requester from the requestee candidates indicated by the user identification information included in the list data determined as the task target by the list determination means is the user information storage. Requestee determination means for determining, when the user is identified by the user identification information included in the user information stored in the means, the requestee as a task request destination for the list data When,
Obtains the email address of the requestee determined as the request destination of the task by the requestee determination means from the user information stored in the user information storage means, and uses the acquired email address as the destination for the request A task request means for sending an e-mail in which a task request by a user is described;
The requestee who has received the e-mail sent by the task requesting unit is subject to the list data determined as the task target by the list determining unit, according to the task request described in the e-mail. A task realization means that makes it possible to execute a task;
A list management system characterized by comprising:   The list management system according to claim 1, wherein the list data is created in a spreadsheet. The requestee determination means can cause the requester to select a requestee to update each record for each record of the list data, and the selected requestee is the user information storage means. When the user is identified by the user identification information included in the user information stored in the table, the selected requestee is determined as a request destination for each record of the list data,
The task realization means presents, to each requested person, only the record in which each requested person is determined as a request destination by the requested person determining means, and only the presented record is presented to each requested person. Allow users to update,
The list management system according to claim 1 or 2, characterized by the above-mentioned. A progress manager presenting means for presenting the progress of the task for the list data to the user who has input the list data registered by the list registration means;
Progress requestee presenting means for presenting to the requestee the progress of the task for the list data;
Progress requester presenting means for presenting the requester with the progress of the task for the list data;
The list management system according to claim 1, further comprising: a progress management unit including:   5. The list according to claim 4, wherein the progress management means includes prompting means for sending a reminder e-mail to a requestee who has not completed the task at a timing set by the requester. Management system. The user identification information includes a user name and a department name,
Based on the data indicating the department change and / or personnel change, the department name and / or user name of the user identification information included in the list data stored in the list storage means is updated, and the use The mail address of the user who entered the list data registered by the list registration means is acquired from the user information stored in the person information storage means, and the updated mail address is used as the destination. A department name / user name update means for sending an e-mail in which a request for a task for checking a department name and / or a user name is described;
In the requestee determination means, the requestee is selected by the requester who has received the e-mail transmitted by the department / user name update means,
The tasks that can be executed by the task realization means are: the requestee determined by the requestee determination means confirms the department name and / or user name of the user identification information included in the list data; Is to update,
The list management system according to any one of claims 1 to 5, characterized in that:   The task that can be executed by the task realization means is that the requestee determined by the requestee determination means obtains a document file related to the list data that is the target of the task, and / or 7. The list management system according to claim 1, wherein a document file related to the list data is submitted.

Images