JP2006040096A - Schedule information collection device, schedule information collection method, schedule information collection processing program, etc. - Google Patents

Abstract

A schedule information collection device, a schedule information collection method, a schedule information collection processing program, and the like are provided.
A schedule information collection device for collecting schedule information managed on a plurality of different applications executed on one or a plurality of computers, the application identification information assigned to each application, and a user Association data storage means for storing association data for associating user identification information assigned to each user or each group to which the user belongs, identification information reception means for receiving user identification information designated by the user, and reference to association data Identification information specifying means for specifying application identification information associated with the received user identification information, and schedule information collecting means for collecting schedule information managed on the application to which the specified application identification information is assigned And comprising.
[Selection] Figure 4

Description

  The present invention relates to a technical field such as a schedule information management system for managing schedule information of a plurality of users.

Conventionally, various types of schedule information management systems of this type have been proposed. For example, the schedule management system disclosed in Patent Document 1 manages not only the function of a single schedule but also the schedule of individuals and groups. By adding facility management and process management functions to the functions to be performed, and by adding the function to arrange and display multiple screens on the same screen, or to restore them to their original state, Schedule functions, facility management, process management, and other functions can be managed collectively.
JP 7-282129 A

  By the way, a user may manage schedule information separately using a plurality of systems and applications. For example, in the case of an application that manages and manages the insertion of leaflets (printed advertisements) in newspapers, magazines, etc., where product advertisement information is posted, such as the leaflet insertion date, printing deadline, design deadline, etc. Schedule information is managed. On the other hand, in the case of an application that manages and manages a product sales promotion plan and the like, schedule information such as the sale (sales) period, events, and events of the product is managed.

  However, in the conventional schedule management system, when the user wants to register schedule information separately managed independently on different applications in this way, for example, in the groupware schedule function, A troublesome work such as storing the schedule information by the user and re-registering with the schedule function occurs.

  The present invention has been made in view of the above points, and even schedule information that is managed separately and independently on different applications is collected more efficiently and effectively for the user. It is an object to provide a schedule information collection device, a schedule information collection method, a schedule information collection processing program, and the like that can be presented.

  In order to solve the above-described problem, the invention described in claim 1 is a schedule information collection device that collects schedule information managed on a plurality of different applications executed on one or a plurality of computers. The association data storage means for storing the association data for associating the application identification information assigned for each application with the user identification information assigned for each user or for each group to which the user belongs, and designated by the user Identification information receiving means for receiving the user identification information, identification information specifying means for specifying application identification information associated with the received user identification information with reference to the association data, and the specified application identification information. The schedule managed on the given application Characterized in that it comprises a schedule information collecting means for collecting Lumpur information.

  The invention according to claim 2 is the schedule information collection device according to claim 1, further comprising schedule information presenting means for presenting the collected schedule information.

  According to a third aspect of the present invention, in the schedule information collecting device according to the first or second aspect, when each of the schedule information managed on the plurality of applications is collected by the schedule information collecting means The schedule information presenting means displays each collected schedule information on the same screen.

  According to a fourth aspect of the present invention, in the schedule information collecting apparatus according to any one of the first to third aspects, the schedule information collection rejection setting is set in at least any one of the plurality of applications. A collection refusal setting presence / absence determining means for determining whether an application to which the application identification information specified by the identification information specifying means is given is an application for which the collection refusal setting has been made, When it is determined that the application has been set to reject collection, the schedule information collecting unit does not collect the schedule information managed on the application.

  According to a fifth aspect of the present invention, in the schedule information collecting device according to any one of the first to fourth aspects, the personal schedule information for collecting the individual personal schedule information corresponding to the received user identification information Collecting means, and the schedule information presenting means displays the schedule information collected by the schedule information collecting means and the individual schedule information collected by the personal schedule information collecting means on the same screen. It is characterized by being displayed.

  The invention according to claim 6 is a schedule information collection method for collecting schedule information managed on a plurality of different applications executed on one or a plurality of computers, and is provided for each of the applications. Storing association data associating the application identification information with the user identification information assigned to each user or each group to which the user belongs, receiving the user identification information designated by the user, and the association Identifying application identification information associated with the received user identification information with reference to data, and collecting the schedule information managed on the application to which the identified application identification information is assigned And.

  According to a seventh aspect of the present invention, a computer is caused to function as the schedule information collecting device according to any one of the first to fifth aspects.

  The invention according to claim 8 is characterized in that the schedule information collection processing program according to claim 7 is recorded so as to be readable by a computer.

  According to the present invention, schedule information that is managed separately and independently on different applications can be collected more efficiently without performing troublesome work such as newly re-registering in the personal schedule function, for example. Can be effectively presented to the user.

  Hereinafter, the best embodiment of the present invention will be described in detail with reference to the drawings. The embodiment described below is an embodiment when the present invention is applied to a schedule information management system.

  First, the configuration of a schedule information management system according to an embodiment of the present invention will be described with reference to FIG.

  FIG. 1 is a diagram illustrating an example of a hardware configuration of the schedule information management system according to the present embodiment.

  As shown in FIG. 1, the schedule information management system S includes a schedule information collection server 1 as a schedule information collection device, a plurality of application servers (systems) 2a to 2c, and a plurality of terminals 3a to 3c. They are connected to each other via, for example, a LAN (Local Area Network) 4.

  In the present embodiment, the schedule information means information representing a schedule of some business, work, event, event or the like scheduled to be performed in the future.

  Each of the application servers 2a to 2c includes, for example, a server computer. On each of the application servers 2a to 2c, different predetermined applications (application programs) are executed, and schedule information is managed on each application (each application Are managed independently).

  For example, in the application server 2a, an application that manages and manages the insertion of a leaflet (advertisement printed matter) in which product advertisement information is posted into a newspaper, magazine, or the like is executed. Schedule information such as the date of insertion, the deadline for printing, the deadline for design, etc. is managed. On the other hand, the application server 2b executes an application that manages and manages a product sales promotion plan and the like, thereby managing schedule information such as the sale period, event, and event of the product on the application. Is done. Further, such schedule information is managed for each user or for each group to which the user belongs in each application.

  In the following description, an application executed on the application server 2a is referred to as "application A", an application executed on the application server 2b is referred to as "application B", and an application executed on the application server 2c is referred to as "application It shall be referred to as “C”. Each application A to C is given a unique application code as application identification information. For example, an application code assigned to application A is referred to as “AAA”, an application code assigned to application B is referred to as “BBB”, and an application code assigned to application C is referred to as “CCC”.

  The terminals 3a to 3c are made up of personal computers, for example, and are used by each user.

  In the following description, a user who uses the terminal 3a is referred to as “user X”, a group to which the user X belongs is referred to as “group X”, and a user who uses the terminal 3b is referred to as “user Y”. The group to which the user Y belongs is called “group Y”, the user who uses the terminal 3c is called “user Z”, and the group to which the user Z belongs is called “group Z”. . Each of the users X to Z (or groups X to Z) is given a unique user code (or group code) as user identification information. For example, a user code (or group code) assigned to the user X (or group X) is referred to as “XXX”, and a user code (or group code) assigned to the user Y (or group Y) is referred to as “YYY”. The user code (or group code) assigned to the user Z (or group Z) is referred to as “ZZZ”.

  Each user or each group is given permission to use any one of the plurality of applications according to, for example, business contents of the user or each group.

  Each application server 2a to 2c receives a request from a terminal (any of 3a to 3c) used by a user who is permitted to use the application or a user belonging to a group (for example, an input provided to the terminal by the user) The schedule information is presented to the terminals 3a to 3c, or the schedule information from the terminals 3a to 3c is displayed in accordance with a part (for example, an instruction input by operating a mouse or a keyboard). Registration (memory storage) is performed in association with the user code (or group code).

  2A is a diagram illustrating an example of schedule information and the like managed on the application A, and FIG. 2B is a diagram illustrating an example of schedule information and the like managed on the application B. is there. Note that such schedule information and the like are stored and saved in a storage unit (for example, a hard disk or the like) provided in the application server.

  In the example of FIGS. 2A and 2B, user code (or group code), schedule information (date, schedule content), collection rejection setting, and the like are associated with each other. For example, the row of the reference numeral 51 shown in FIG. 2A shows the schedule information of the user X of the user code “XXX”. Note that the schedule information and the like are managed on the application C in a format as shown in FIG.

  Thus, the schedule information managed on the application A is collected in the schedule information collection / presentation process described later by the schedule information collection server 1. Here, the schedule information with the collection rejection setting “1” shown in FIG. 2 means that the schedule information is the collection rejection setting, and the schedule information is included in the schedule information collection / presentation process. Not collected. Such collection refusal setting is performed by the user X from the user terminal 3a, for example.

  In addition, user codes (group codes) of authorized users (or groups) are stored and stored in the storage units of the application servers 2a to 2c, and the application servers 2a to 2c are connected to the terminals ( The user code (or group code) is acquired from any one of 3a to 3c), and the use of the application is permitted by determining whether or not the user code (or group code) is stored in the storage unit. It is determined whether or not the terminal is a connected terminal. The user code (or group code) may be input by the user of the terminals 3a to 3c operating the input unit, or the user code is stored in the storage unit provided in the terminals 3a to 3c in advance. (Or a group code) may be stored and stored and transmitted when the terminals 3a to 3c access the application servers 2a to 2c.

  Next, as shown in FIG. 1, the schedule information collection server 1 is composed mainly of a CPU, and includes an arithmetic processing unit 11 having a RAM, a ROM, and the like, and a storage unit (for example, a hard disk) that stores various data and programs 12 and a server computer including a communication unit 13 that performs communication control between the application servers 2a to 2c and the terminals 3a to 3c. Then, when the CPU executes a schedule information collection processing program stored in, for example, the ROM or the storage unit 12, the arithmetic processing unit 11 includes an identification information receiving unit, an identification information specifying unit, a schedule information collecting unit, It functions as a schedule information presenting means, a collection rejection setting presence / absence judging means, and a personal schedule information collecting means. A detailed description of each of these means will be described later. Note that the schedule information collection processing program may be stored and stored in a predetermined server connected to the Internet, downloaded from the server and stored in the storage unit 12, for example, a CD-ROM or the like. It may be configured to be recorded on a recording medium, read by a drive, and stored in the storage unit 12.

  Further, the storage unit 12 stores and saves association data associating the application code with the user code (or group code) as association data storage means. This association data is data for associating which application use permission is given to the user or the group.

  FIG. 3 is a diagram illustrating an example of association data. In the example of FIG. 3, the application codes “AAA” and “BBB” are associated with the user code “XXX”, that is, the use permission of the applications A and B is given to the user X. Show.

  Next, the operation of the schedule information management system S will be described with reference to FIG.

  FIG. 4 is a flowchart showing schedule information collection / presentation processing executed in the arithmetic processing unit 11 of the schedule information collection server 1. The schedule information collection / presentation process is performed by executing the schedule information collection program by the CPU.

  For example, when the user X operates the input unit of the terminal 3a and specifies (inputs, etc.) the schedule information presentation instruction together with his own user code (or group code to which he belongs) “XXX”, the user (or his / her own) belongs Group code) “XXX” and a schedule information presentation instruction request are transmitted from the terminal 3 a to the schedule information collection server 1 via the LAN 4. In response to this, the arithmetic processing unit 11 of the schedule information collection server 1 starts the schedule information collection / presentation process as the identification information receiving means, and the user code designated by the user X (or the group code to which the user belongs) “XXX” is accepted (step S1).

  Next, the calculation processing unit 11 of the schedule information collecting server 1 reads the association data stored and stored in the storage unit 12 as identification information specifying means, refers to this, and receives the received user code (or self belongs) Group code) It is determined whether or not there is an application code associated with “XXX” (step S2). If there is an application code (step S2: Y), the application code is specified (step S3). On the other hand, when there is no application code (step S2: N), the process proceeds to step S7.

  Here, in the example of FIG. 3, since the application codes “AAA” and “BBB” are associated with the user code “XXX”, the application codes “AAA” and “BBB” are specified. .

  Next, the arithmetic processing unit 11 of the schedule information collection server 1 serves as an application server 2a on which the application A to which the identified application code “AAA” is assigned is executed as a collection rejection setting presence / absence determination unit. It is determined whether or not A is an application for which the collection rejection setting has been made by inquiring via the LAN 4 (step S4). When it is determined that the application A is not the application for which the collection rejection setting is made (step S4: N), the arithmetic processing unit 11 of the schedule information collection server 1 uses the identified application as the schedule information collection unit. Schedule information managed on the application A to which the code “AAA” is assigned is collected from the application server 2a (step S5). On the other hand, if it is determined that the application A is an application for which the collection rejection setting has been made (step S4: Y), the arithmetic processing unit 11 of the schedule information collection server 1 is managed on the application A. The schedule information is not collected and the process proceeds to step S6.

  In step S6, the arithmetic processing unit 11 of the schedule information collection server 1 determines whether or not the identified application code is still present. In the example of FIG. 3, since the application code “BBB” still exists, the process returns to step S4, and the same process as in steps S4 and S5 is performed for the application code “BBB”.

  In this way, when schedule information is collected for all of the identified application codes (step S6: N), the arithmetic processing unit 11 of the schedule information collection server 1 then receives the received user code “XXX ”Is determined (step S7), and if there is (step S7: Y), the schedule information of the user X is collected as a personal schedule information collection means. (Step S8), the process proceeds to Step S9, and if there is not (Step S7: N), the process proceeds to Step S9 without collecting the schedule information.

  This user X individual schedule information is registered in association with the user code (or group code) of the user X by execution of an application for managing the user individual schedule. It may be installed in 3a, or may be installed in the application server or schedule information collection server 1.

  FIG. 5 is a diagram illustrating an example of schedule information of the user X individual. In the example of FIG. 5, the user code is associated with personal schedule information (date, schedule content) and the like. It should be noted that such individual user schedule information and the like may be stored and saved in any one of the schedule information collection server 1, the application servers 2a to 2c, and the terminals 3a to 3c. Recognizes whether personal schedule information is stored or saved.

  In step S9, the arithmetic processing unit 11 of the schedule information collection server 1 presents the schedule information acquired in this way to the user X of the terminal 3a, and ends the process. For example, when each schedule information is collected from a plurality of applications, the arithmetic processing unit 11 of the schedule information collection server 1 displays the collected schedule information on a display unit (not shown) provided in the terminal 3a. ) On the same schedule information display screen. Further, when the user's personal schedule information is acquired, the schedule information managed on the application and the user's personal schedule information are displayed on the same schedule information display screen.

  FIG. 6 is a diagram illustrating an example of a plurality of schedule information displayed on the same schedule information display screen. On the schedule information display screen shown in FIG. 6, the schedule information managed on the application A, the schedule information managed on the application B, and the schedule information of the individual user X are mixed to create one It is displayed on the schedule information display screen.

  As described above, according to the above-described embodiment, schedule information that is managed separately and independently on different applications can be newly registered in the personal schedule function without performing troublesome work such as re-registration. , Can be collected more efficiently and presented to the user.

  In the above embodiment, the plurality of applications are configured to be executed by a plurality of different application servers, but the present invention is not limited to this, and a plurality of applications are executed by one application server. You may comprise.

It is a figure which shows an example of the hardware constitutions of the schedule information management system concerning this embodiment. (A) is a figure which shows an example of the schedule information etc. which are managed on application A, (B) is a figure which shows an example of the schedule information etc. which are managed on application B. It is a figure which shows an example of correlation data. It is a flowchart which shows the schedule information collection and presentation process performed in the arithmetic processing part 11 of the schedule information collection server 1. FIG. It is a figure which shows an example of a user X individual's schedule information, etc. It is a figure which shows an example of the some schedule information displayed on the same schedule information display screen.

Explanation of symbols

1 Schedule information collection server 2a to 2c Application server 3a to 3c Terminal 4 LAN
11 arithmetic processing unit 12 storage unit 13 communication unit S schedule information management system

Claims (8)

A schedule information collection device that collects schedule information managed respectively on a plurality of different applications executed on one or more computers,
Association data storage means for storing association data for associating application identification information assigned to each application and user identification information assigned to each user or each group to which the user belongs;
Identification information receiving means for receiving the user identification information designated by the user;
Identification information specifying means for specifying application identification information associated with the received user identification information with reference to the association data;
Schedule information collection means for collecting the schedule information managed on the application to which the identified application identification information is assigned;
A schedule information collecting apparatus comprising: In the schedule information collection device according to claim 1,
A schedule information collection device comprising schedule information presentation means for presenting the collected schedule information. In the schedule information collection device according to claim 1 or 2,
When each schedule information managed on the plurality of applications is collected by the schedule information collecting means, the schedule information presenting means displays the collected schedule information on the same screen. A schedule information collecting apparatus characterized by the above. In the schedule information collection device according to any one of claims 1 to 3,
In at least any one of the plurality of applications, the schedule information collection rejection setting is made,
A collection refusal setting presence / absence determining means for determining whether or not the application to which the application identification information specified by the identification information specifying means is an application for which the collection refusal setting has been made is further provided;
When it is determined that the application has been set to reject collection, the schedule information collection unit does not collect the schedule information managed on the application. In the schedule information collection device according to any one of claims 1 to 4,
Personal schedule information collecting means for collecting schedule information of the individual user corresponding to the received user identification information;
The schedule information presenting means displays the schedule information collected by the schedule information collecting means and the user personal schedule information collected by the personal schedule information collecting means on the same screen. Schedule information collection device. A schedule information collecting method for collecting schedule information managed respectively on a plurality of different applications executed on one or a plurality of computers,
Storing association data for associating application identification information assigned to each application and user identification information assigned to each user or each group to which the user belongs;
Receiving the user identification information designated by the user;
Identifying application identification information associated with the accepted user identification information with reference to the association data;
Collecting the schedule information managed on the application provided with the identified application identification information;
A schedule information collecting method comprising:   A schedule information collection processing program for causing a computer to function as the schedule information collection device according to any one of claims 1 to 5.   8. A recording medium on which the schedule information collection processing program according to claim 7 is recorded so as to be readable by a computer.

Images