JP3631828B2 - Schedule data management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a schedule data management system for managing schedule data of a large number of users with a plurality of servers connected via a network .
[0002]
[Prior art]
Conventionally, as shown in FIG. 11A, schedule management registers a user (for example, A user) in a certain server (for example, X server) and registers personal schedule data and personal information of the user (A data). As a reference) and make settings for reference.
[0003]
Further, as shown in FIG. 11B, registered users are grouped and managed, group schedule data and group information are registered, a schedule of a plurality of people is referred to, and a schedule data of a plurality of people is batched. I was trying to make settings.
[0004]
In such a schedule management system, when referring to / setting the schedule of another server, the following procedure is used.
(1) When connecting to a server where information exists and referring to it: As shown in FIG. 12A, a plurality of servers connected to a schedule where reference is made are connected simultaneously, and data is read from each server. Each was displayed and schedule data was set.
[0005]
(2) When registering information necessary for other servers to refer to information on a single server: As shown in FIG. Register as a user and switch the server to access as necessary.
[0006]
(3) When registering all information of other servers in order to refer to the information on a single server: As shown in FIG. 12 (c), the schedule managed by each server on the server being used All the same data was registered and referenced / set.
[0007]
[Problems to be solved by the invention]
In the case of (1) described above, the user must be consciously connected to the server where the schedule data to be referenced exists, and when referring to the schedules of a plurality of persons at once, it is necessary to connect to the plurality of servers. There is a problem that the connection operation is troublesome and the display of the schedule depends on the line speed to each server, which is difficult to use.
[0008]
In the case of (2) described above, access to the server that performs the reference / setting is switched as necessary, and thus there is a problem that the user's schedule cannot be referred to each other. There is a problem that it is necessary to register the same schedule and the operation is troublesome.
[0009]
In the case of (3) described above, the user's schedule data is registered in all the servers, and there is also a problem that there is a user's schedule data that is not referred to, and resources are wasted.
[0010]
In order to solve these problems, the present invention automatically transfers the schedule to a specific server by e-mail or the like and manages it in units of groups, and automatically transfers the group schedule to users belonging to the group, and reflects the result. An object is to eliminate the need for simultaneous connection to a plurality of servers without making a server aware of the schedule data to be referenced, and to eliminate the waste of resources by leaving the schedule data that is not referenced / set by others.
[0011]
[Means for Solving the Problems]
Means for solving the problem will be described with reference to FIGS.
1 and 2, the server 1 registers and manages user schedule data 3.
[0012]
The client 2 is a terminal (for example, PC, personal computer, etc.) through which the user inputs the schedule data 3.
The schedule data 3 is personal schedule data of the user and schedule data for each group.
[0013]
The schedule management means 4 manages a schedule.
The linked server group table 5 is a table in which linked servers are registered.
Next, the operation will be described.
[0014]
User schedule data 3 input by the schedule management means 4 and user schedule data 3 received from the network (LAN) are registered and managed in association with the user ID, and the group management table 7 is referred to It is registered and managed in the group to which the user belongs.
[0015]
Also, the user schedule data 3 input by the schedule management means 4 and the user schedule data 3 received from the network are registered and managed in association with the user ID, and the group to which the user belongs by referring to the group management table 7 Registered and managed, and transferred to other users' servers belonging to the group for notification, and when schedule data 3 is returned as a response, it is registered and managed in association with the user ID, and as necessary Register and manage with a group.
[0016]
Further, the schedule data of the user input by the schedule management means 4 is registered and managed in association with the user ID, and the schedule data 3 is transferred to the linked server by referring to the linked server group table 5 The server is registered and managed in association with the user ID, and is registered and managed in the group to which the user belongs.
[0017]
Therefore, the schedule data 3 to be referred to is automatically transferred to the specific server 1 by e-mail or the like and managed in units of groups, and the group schedule is automatically transferred to the users belonging to the group and the result is reflected, whereby the schedule data 3 to be referred to Without making the existing server 1 conscious, simultaneous connection to a plurality of servers 1 is unnecessary, and it is possible to eliminate wasteful use of resources by leaving the schedule data 3 that is not referenced / set by others.
[0018]
DETAILED DESCRIPTION OF THE INVENTION
Next, embodiments and operations of the present invention will be described in detail sequentially with reference to FIGS.
[0019]
FIG. 1 shows a system configuration diagram of the present invention.
In FIG. 1, a server 1 is connected to a LAN (network) and registers and manages schedule data 3 (A data, B data, etc.) from a plurality of clients 2, and comprises a schedule management means 4 and the like. It is what is done.
[0020]
The server (X) registers and manages personal schedule data 3 of A user, B user, and C user as A data, B data, and C data, respectively.
The server (Y) is a specific server, and here, the linked personal schedule data 3 of the linked servers (X) and (Z) is A data, B data, C data, 1 data, 2 It is registered and managed as data (three users do not manage in cooperation).
[0021]
The server (Z) registers and manages personal schedule data 3 of 1 user, 2 users, and 3 users as 1 data, 2 data, and 3 data, respectively.
The schedule data 3 is personal schedule data of the user and schedule data for each group.
[0022]
The schedule management means 4 registers and manages the schedule data 3 for each user (described later with reference to FIG. 3).
The linked server group table 5 sets servers and groups to be linked in association with user IDs (see FIG. 6).
[0023]
The user management file 6 registers and manages the schedule data 3 in association with the user ID (see FIG. 4).
The group management file 7 registers and manages the user ID of the member in association with the group ID (see FIG. 5).
.
[0024]
FIG. 2 shows another system configuration diagram of the present invention. This is a configuration example in which a specific server (Y) 1 manages schedule data for each group.
The α group registers and manages the schedule data 3 of the A user and the 1 user as a group.
[0025]
The β group is for registering and managing the schedule data 3 of the B user and the two users together as a group.
The γ group is for registering and managing the schedule data 3 of C users and 2 users as a group.
[0026]
Next, the operation of the configuration of FIGS. 1 and 2 will be described in detail according to the order shown in the flowchart of FIG. FIG. 3 shows a case where the user A of the X server reserves (registers) a schedule.
[0027]
FIG. 3 is a flowchart for explaining the operation of the present invention (part 1).
In FIG. 3, in S1, a user A creates a schedule and a group schedule by referring to the past history.
[0028]
S2 stores it in the schedule file of the X server. In S1 and S2, the user A in FIG. 1 creates schedule data (A data) using the client 2, and the server (X) 1 stores the data in the schedule file as A data (see FIG. 4).
[0029]
In S3, the X server searches for the A user in the cooperation server group table. This searches for the user ID “A” in the linked server group table 5 of the X server in FIG. When it exists, it progresses to S4. If it does not exist, the schedule data does not need to be transferred to another server to be linked by e-mail, and the process ends.
[0030]
In S4, since it is determined that there is a server to be linked due to the presence of S3, a transfer table in which schedule data is added to the linked server group table is created. This creates a transfer table (1) in FIG. 7 in which schedule data (A data) is added to the entry of the A user in the linked server group table 5 in FIG. 6 to be described later.
[0031]
In S5, the information in the transfer table created in S4 is converted into a mail format.
In S6, the mail is transmitted. In this case, the transfer table converted in S5 is sent to the cooperation destination server as an email.
[0032]
In step S11, the mail transmitted in step S6 is received by the cooperation destination Y server.
In S12, the Y server converts (restores) the mail information into a transfer table format.
S13 determines whether the transfer destination is a directory. This determines whether the transfer destination is the current Y server. In the case of YES, the schedule data of the transfer table is copied and registered in the management directory and managed in S14 (see FIG. 5). On the other hand, if NO, the process proceeds to S15.
[0033]
In S15, a transfer table to other members of the group is created from the linked server group table 5 and the group management file 7. For example, a transfer table (2) in FIG.
[0034]
In step S16, the transfer table information is converted into a mail format.
In S17, the mail is transmitted.
In S21, the Z server in which other members belonging to the group are present receives the mail sent in S17.
[0035]
In S22, the Z server converts the mail information into a transfer table format.
In S23, the schedule data of the transfer table is copied and registered in the management directory for management.
[0036]
As described above, the A user of the X server creates schedule data using the client (A) 2 and registers it as “A data” in association with the user ID “A” in the X server, and also refers to the linked server group table 5 Then, the mail is transferred to the cooperation destination Y server as mail, and the received Y server is registered in association with the A user and is stored as group schedule data of the group to which it belongs. When the group management table 7 is searched and it is found that there is a user of another server (Z server) belonging to the same group, here, it is transferred to the Z server as a mail addressed to one user of the Z server, and received Z The server notifies and informs one user. If the schedule data (group schedule data) received by this one user is inconvenient, the modified schedule data is created and sent to the Y server of the sender as e-mail and registered as the schedule data of one user At the same time, it is reflected in the group schedule data. As a result, the user A simply creates schedule data 3 and notifies the X server. The user A automatically registers the schedule data 3 and automatically transfers the schedule data to one user of the Z server belonging to the group. If the data is inconvenient, the corrected schedule data can be sent to the Y server of the transmission source by e-mail and reflected in the group schedule data.
[0037]
FIG. 4 shows an example of a user management file of the present invention. This user management file 6 is for registering schedule data by setting the following items shown in the figure as shown.
[0038]
\ A \ Schedule file \ A \ Schedule index file Here, the first directory "A" indicates the user ID, and the "schedule file" and "schedule index file" on the right side indicate the file names of the schedule file and the schedule index file. . The corresponding schedule ID is searched from the schedule index file, and schedule 1 (schedule data) is read at a high speed from the point pointed to from now on (the schedule index is registered in units of days).
[0039]
FIG. 5 shows an example of the group management file of the present invention. As shown in the figure, the group management file 7 is a file in which the server and user ID of the member are registered in association with the group ID (for example, “α”). Then, as shown in the lower row, the group schedule data finds the corresponding one from the file name “group schedule index file” in association with the group directory, for example “α”, and corresponds to the file name “group schedule file”. Register / read group schedule data at the location.
[0040]
FIG. 6 shows an example of a linked server group table of the present invention. As shown in the figure, this linkage server group table 5 is a table in which a linkage server ID linked to a user ID and a group ID to which the linkage server ID belongs are registered in advance. For example, as shown in the figure, for the user ID “A”, the cooperation server is “Y server”, and the group to which the user belongs is “α group”.
[0041]
FIG. 7 shows an example of a transfer table of the present invention. Here, as shown in the upper part, in accordance with the example of FIG.
A (X server) transfers the transfer table of (1) to α (Y server), and α (Y server) transfers the transfer table of (2) to 1 (Z server) (and if necessary) The transfer table created for A is transferred to A (X server)).
[0042]
The transfer table (1) is obtained by adding schedule data to the entry of the user ID “A” in FIG. In FIG. 3, the transfer table (1) is sent by the X server as a mail to the cooperation destination Y server.
[0043]
In the transfer table (2), the Y server changes the transfer destination server of the transfer table (1) to “Z server” and sends it as a mail to the Z server.
FIG. 8 is a flowchart (part 2) for explaining the operation of the present invention. This is when the cooperation server Y registers the user A (user A) of the X server.
[0044]
8, in S31, the Y server registers the user IDs “A” and “1” in the group information file of the group management file 7 as members of the group ID “α”. In response to this registration, group information (X server “A” belongs to group “α”) is sent to the X server by electronic mail. Similarly, group information (Z server “1” belongs to group “α”) is sent to the Z server by electronic mail.
[0045]
In step S32, the X server receives the fact that A is registered in the group α of the Y server by the mail transmitted in step S31.
In step S33, the information received in step S32 is registered in the cooperation server group table. Registration is performed as shown in the record in the first row of the linked server group table 5 in FIG.
[0046]
As described above, when the member user IDs “A” and “1” are registered in association with the group ID “α” on the specific Y server, the fact is automatically transmitted to each X server and Z server by mail. Then, the cooperation server and the affiliated group are automatically registered in each cooperation server table 5 in association with the user ID.
[0047]
FIG. 9 shows a flowchart (part 3) for explaining the operation of the present invention. This is a flowchart when referring to the schedule of the cooperation server Y.
In FIG. 9, S41 inputs A's user ID with X server.
[0048]
In step S42, it is determined whether or not the X server is used. This is based on the user ID A input in S41, and a use authority table (not shown) is referenced to determine whether or not the use authority exists. When it is determined that there is, the schedule data of A is referred from the file registered in the X server in S43 (see the user management file 6 in FIG. 4). Following this reference, the cooperation destination Y server is also referred to by S51 to S57. On the other hand, if it is determined in S42 that there is no, the process ends.
[0049]
In S51, the user ID of A is input on the Y server.
In S52, it is determined whether or not Y server use authority is present. This is based on the user ID A input in S51, and a use authority table (not shown) is referenced to determine whether or not the use authority exists. If it is determined that there is, the process proceeds to S53. On the other hand, in the case of none, it is terminated as unusable.
[0050]
In step S53, it is determined whether the user management file 6 is registered. If YES, the process proceeds to S54. On the other hand, in the case of NO, it is determined that the information has not been registered, so the processing is terminated as being unusable.
[0051]
In S54, a list of group IDs to which A of the Y server belongs is obtained.
In step S55, a list of group IDs is displayed.
In S56, one desired group ID (for example, α) is selected from the list on which the A user is displayed.
[0052]
S57 refers to the schedule data of the selected α group and the schedules of all registered members. These are referred to the group management table 7 of FIG. 5 described above, the schedule 1... Of the selected group “α” to which A belongs and the schedules of all registered members are extracted and transferred, and the client of the A user Display on the screen of 2 and refer to it.
[0053]
As described above, the A user receives the transfer of his / her personal schedule data from the X server with the usage authority, displays it on the screen of the client 2, and further references the group schedule data belonging to the Y server with the usage authority. The personal schedule data of all the members of the group can be received and displayed on the screen of the client 2 for reference.
[0054]
FIG. 10 is a diagram for explaining the operation of the present invention. This is a description of the manner in which schedule data is registered in the α group of the Y server from the X server described above in an easy-to-understand manner. Here, the X server, the Y server, and the Z server correspond to those in FIG. 1, and the Y server is a specific linkage server.
[0055]
(1): A schedule (10: 00 → 12: 00 schedule) is registered in A of the X server. In this state, nothing is registered in the Y server and Z server.
{Circle over (2)} The X server transfers the schedule data to the Y server as mail, registers the schedule data in association with the group α to which it belongs, and also associates the schedule data with the user ID “A” as shown in the figure. register.
[0056]
(3): In response to the schedule data being registered in the group “α” in (2), the schedule data is transferred to the Z server of the other user ID “1” belonging to the group “α”.
[0057]
{Circle over (4)} If the user 1 who has seen the schedule data of the group “α” transferred in {circle over (3)} understands, the processing ends here. On the other hand, if the user 1 of the Z server does not agree with the schedule data, it is changed to (5) in the same manner as (2).
[0058]
{Circle around (5)} The schedule data corrected by the user 1 of the Z server in step {circle around (4)} is transferred to the Y server and registered as shown in FIG. At this time, it is reflected in the group “α”, and the schedule data of the group “α” after the reflection is transferred to the user “A” of the X server, so that it is automatically performed so as to obtain an understanding. Also good.
[0059]
【The invention's effect】
As described above, according to the present invention, the schedule is automatically transferred to a specific server by e-mail or the like and managed in units of groups, and the group schedule is automatically transferred to users belonging to the group and the response result is reflected. Therefore, by registering the schedule on one server, the schedule is automatically transferred to the linked server and managed as a registration and group schedule, and automatically transferred to users belonging to the group. The response result can be reflected, the user's personal schedule and the group schedule to which the user belongs can be automatically registered, and the group schedule can be automatically notified to all the groups. As a result, there is no need to be aware of the server on which the conventional schedule data exists, the simultaneous connection to a plurality of servers is unnecessary, and it is possible to eliminate wasteful use of resources by leaving the schedule data 3 that is not referenced / set by others. Become.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram of the present invention.
FIG. 2 is another system configuration diagram of the present invention.
FIG. 3 is a flowchart (part 1) for explaining the operation of the present invention.
FIG. 4 is an example of a user management file according to the present invention.
FIG. 5 is an example of a group management file of the present invention.
FIG. 6 is an example of a linked server group table of the present invention.
FIG. 7 is an example of a transfer table according to the present invention.
FIG. 8 is a flowchart (part 2) illustrating the operation of the present invention.
FIG. 9 is a flowchart (part 3) illustrating the operation of the present invention.
FIG. 10 is an operation explanatory diagram of the present invention.
FIG. 11 is an explanatory diagram (part 1) of the prior art.
FIG. 12 is an explanatory diagram (part 2) of the prior art.
[Explanation of symbols]
1: Server 2: Client 3: Schedule data 4: Schedule management means 5: Linked server group table 6: User management file 7: Group management file

Claims (2)

In a schedule data management system for managing schedule data of a large number of users with a plurality of servers connected via a network,
A group management table for pre-registering a user who is a member in association with a group and a server to which the user belongs;
Means for registering the user's schedule data and the user's schedule data received from the network in association with the user ID and registering them in the group to which the user belongs by referring to the group management table;
Refer to the above group management table and automatically transfer it to the server of other users in the group to which the user belongs, and when the schedule data is sent back as a response, A schedule data management system characterized in that a server is provided with means for managing. In a schedule data management system for managing schedule data of a large number of users with a plurality of servers connected via a network,
A table for pre-registering servers and groups to be linked in association with user IDs;
Means for registering and managing input user schedule data in association with a user ID;
A first server provided with means for automatically transferring schedule data to a server that cooperates with reference to the table;
To the linked server that received the automatically transferred schedule data,
Means for registering and managing the received schedule data in association with the user ID;
Means for registering and managing the received schedule data in a group to which the user belongs;
And a means for registering and managing in association with the returned user ID when the schedule data is returned as a response and automatically transferred to a server of another user belonging to the group. Schedule data management system.

Images