JP2008262554A - Information processing apparatus, information processing method, information processing program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image processing apparatus which easily enters a state where a user can perform a required operation. <P>SOLUTION: A personal computer 100 is provided with a database part 160 including: a user list table 162 for preserving a list of users, a task list table 161 for preserving a list of tasks associated with an image; and an operation history table 163 for preserving an operation history where the task is associated with the operation. A task information management server 300 includes an information management database part 340 with task information preserved therein. When the user performs an operation with respect to a file, a processing part 110 predicts an operation with high probability for the operation by the user, based on the task associated with the file, and presents the predicted operation to an information display part 151. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an information processing apparatus, an information processing method, an information processing program, and a computer-readable recording medium in which the information processing program is described. The present invention relates to an information processing apparatus, an information processing method, an information processing program, and a computer-readable recording medium describing the information processing program.

For electronic files (files) saved on the hard disk of a personal computer, which is an information processing device, various processes and operations such as file printing, sending as e-mail attachments, editing and compression with editors, etc. It can be carried out.
However, while the number of types of operations and operations that can be performed by the information processing device increases in this way, the number of device operations such as mouse button presses required to reach the operation area where the target operation can be performed increases. The complexity of selection is increasing.
In order to facilitate the above-described operation, for example, a method of presenting a frequently used function or presenting an operation performed immediately before has been proposed.
As another method, Patent Document 1 proposes a method for predicting and displaying an operation in a computer. The method described in Patent Document 1 predicts and presents the next operation to be performed based on the time series transition of the application, the operation target, and the operation command. In other words, in this method, the burden of function selection is reduced by presenting operations frequently used by the user in the past or presenting a screen for the administrator to the administrator.
Further, Patent Document 2 proposes a method of presenting an operation based on the usage situation of the user. The method disclosed in Patent Document 2 acquires the current “situation” such as location, time, weather conditions, user work contents, user psychological state, connected device type and state, and stores it in the past history. By comparing with, an operation suitable for the situation is presented.
JP-A-10-27089 JP 2004-206549 A

However, in the method described in Patent Document 1, there is a possibility that the burden on selecting a function that is not frequently used remains the same or increases. That is, since functions that are not frequently used are often unfamiliar with the operation, it is not preferable that the function cannot be supported because it is a part that requires a reduction in function selection. In addition, it is effective when operations are performed continuously in time series, but cannot be performed when a certain operation is performed alone.
In addition, the method of Patent Document 2 is effective when the operation to be presented is determined depending on the situation, and is effective when the operation depends on the “situation”, but in a workflow for a specific purpose such as a routine operation in the business. For operations that are less dependent on the situation, such as operations, the optimum operation is not always presented by this method. Therefore, in presenting an operation based on the history, information related to the purpose that the user intends to achieve by the operation is required.
The present device was invented in view of such circumstances, and has a high possibility of selecting a function to be presented, and is intended to enable a user to easily reach even a complicated operation. And

In the information processing apparatus, the information processing apparatus includes a user authentication unit that determines a current user, a task list storage unit that stores a list of tasks, a task acquisition unit that acquires tasks related to the user, a task, An information processing apparatus comprising: a file information storage unit that stores a relationship with a file; and an information storage management unit that stores the file in the file information storage unit in association with a task related to the file.
According to a second aspect of the present invention, in the information processing apparatus according to the first aspect, the task information acquired by the task acquisition unit includes at least one of a schedule, ToDo information, a project name, and a user group. It is characterized by.
The invention of claim 3 includes a file information storage unit for storing the association between a task and a file, an operation history storage unit for storing the task and an operation as a history associated with each other, a user authentication unit for determining a current user, An operation candidate presenting unit that selects and presents an operation related to a task based on the file when the file is operated.
According to a fourth aspect of the present invention, in the information processing apparatus according to the third aspect, the task information acquired by the task acquisition unit includes at least one of a schedule, ToDo information, a project name, and a user group. It is characterized by.

According to a fifth aspect of the present invention, in the information processing apparatus according to the third aspect, the operation candidate presenting unit includes a relationship between task information and file information held by the file information storage unit, and possession of the operation history storage unit. The operation of the file is presented by referring to the relationship between the task information and the operation to be performed.
According to a sixth aspect of the present invention, in the information processing apparatus according to the third aspect, the operation history storage unit stores task information and date / time information in association with each other, and the operation candidate presentation unit is a history stored in the operation history storage unit. The closeness between the date and time and the current date and time is used as the order of presentation of operations.
According to a seventh aspect of the present invention, in the information processing apparatus according to the third aspect, the operation history storage unit stores task information and a user in association with each other, and the operation candidate presenting unit is a history stored in the operation history storage unit. Whether the current user and the current user match or not is distinguished in the presentation of the operation.
The invention of claim 8 is an information processing method for storing a file in association with a task related to the file, a user authentication step for determining a current user, a task acquisition step for acquiring a task related to the user, An information processing method comprising: a task list storing step for storing a task list; and a file information storing step for storing a relationship between a task and a file.

The invention of claim 9 is the information processing method according to claim 8, wherein the task information acquired by the task acquisition step includes at least one of a schedule, ToDo information, a project name, and a user group. Features.
The invention of claim 10 includes a user authentication step for determining the current user, a file information storage step for storing the association between the task and the file, and an operation history storage for storing the task and the operation as a history associated with each other. And an operation candidate presenting step of selecting and presenting an operation related to a task based on the file when the file is operated.
The invention according to claim 11 is the information processing method according to claim 10, wherein the task information acquired by the task acquisition step includes at least one of a schedule, ToDo information, a project name, and a user group. Features.
The invention according to claim 12 is the information processing method according to claim 10, wherein the operation candidate presentation step includes the association between the task information held by the file information storage step and the file information, and the task information held by the operation history storage step And the relation between the operation and the operation, and the operation for the file is presented.

According to a thirteenth aspect of the present invention, in the information processing method according to the tenth aspect, the operation history storing step stores task information and date / time information in association with each other, and the operation candidate presenting step is a history record stored in the operation history storing step. The closeness between the date and the current date is used as the order of presentation of operations.
According to a fourteenth aspect of the present invention, in the information processing method according to the tenth aspect, the operation history storing step stores task information and a user in association with each other, and the operation candidate presenting step is a history record stored in the operation history storing step. Whether or not the user and the current user match is distinguished in the presentation of the operation.
A fifteenth aspect of the invention is an information processing program for causing a computer to execute the steps of the information processing method according to any one of the eighth to fourteenth aspects.
A sixteenth aspect of the invention is a computer-readable recording medium that describes an information processing program for causing a computer to execute the information processing method according to any one of the eighth to fourteenth aspects.

  According to the present invention, when an operation is performed on a file, an operation expected to be performed in advance is estimated and presented, so that the target operation can be reached without performing a complicated menu operation. In addition, the estimation is performed based on information related to the task associated with the file. Since the task is information in accordance with the business, an operation more suitable for the business is presented.

Embodiments of an information processing apparatus according to the present invention will be described below with reference to the drawings. First, a first embodiment will be described with reference to FIGS. FIG. 1 is a block diagram illustrating an information processing apparatus system according to an embodiment, FIG. 2 is a block diagram illustrating an electrical configuration of the information processing apparatus body, and FIG. 3 is a block diagram illustrating a functional configuration of the information processing apparatus body. . The information processing apparatus according to this example is applied to a personal computer or an embedded computer.
The information processing apparatus according to this example constitutes an information processing apparatus system as shown in FIG. That is, in this example, in the information processing apparatus system 10, the personal computer 100 that is a plurality of information processing apparatus bodies forming the task operation control unit is connected to the task information management server 300 forming the task database unit on the network 20. . The task information of each personal computer 100 is centrally managed by the task information management server 300.
In this example, when an operation is performed on a file stored in the system, the operation associated with the task information is called by selecting the file associated with the task information.

As a typical example of this processing, the user performs processing on a file in the personal computer 100. In this example, when this processing is performed, an operation associated with task information associated with the file is performed. The user can easily reach the target operation by selecting a desired task from the list.
As shown in FIG. 2, the personal computer 100 includes a CPU 1001, a memory 1002, a display screen 1004 as a display device via a display adapter 1003, a serial port 1005, a keyboard 1006, and a pointing device 1007 such as a mouse. A storage device 1008 and a bus 1009 for interconnecting them. In addition, many devices such as an audio interface 1010 and a network interface 1011 can be connected to the bus 1009.

For example, the personal computer 100 uses a network service 30 such as file transfer such as e-mail and FTP and WWW through the network interface 1011, and uses a printer, scanner, FAX via the bus 1009, serial port 1005, and network interface 1011. An external input / output device 40 such as the above can be used.
The personal computer 100 forms the following functional units by executing a program in the electrical configuration as described above. The personal computer 100 includes a processing unit 110 that performs overall control and task operation control of the personal computer 100, a network interface 120, a man-machine interface unit 150, a database unit 160, and a memory 170.
In this example, task management is performed by the personal computer 100. Therefore, the processing unit 110 is a task that acquires task information possessed by a user from the task information management server 300 via the central processing unit 111 including the CPU 1001, a user authentication unit 112 that specifies a user ID, and the network interface 120. An acquisition unit 113, an operation candidate presentation unit 114 that presents an operation based on the acquired task information, a history management unit 115 that stores the executed operation in a storage device together with related task information, and a task related to the file An information storage table management unit 116 that associates and stores the file information in the file information storage table 164 is provided.
The network interface 120 connects the personal computer 100 to the task information management server 300 via the network 20 to exchange data. The man-machine interface unit 150 includes an information display unit 151 such as a display for displaying information to a user, a button for a user to execute a command to the device, an operation command unit 152 such as a touch panel, and a user performed by an operation command unit An input acquisition unit 153 that senses the input of.
The database unit 160 includes a task list table 161 that stores task information held by the user, a user list table 162 that stores users who use the personal computer 100, an operation history table 163 that stores information related to executed operations, and individual task information And a file information storage table 164 for storing the association between each task information and the file.
In such an information processing apparatus system 10, the personal computer 100 acquires task information from the task information management server 300 connected via the network 20.

Next, the task information management server will be described. FIG. 3 is a block diagram showing the configuration of the task information management server. The task information management server 300 includes a user authentication unit 310, a task resource information management unit 320, a related user determination unit 330, an information management database unit 340, a communication unit 350, and an application cooperation unit 360.
The user authentication unit 310 authenticates a user who accesses the task information management server 300. The task resource information management unit 320 manages task resource information and task resource related document information. The related user determining unit 330 determines a user related to the task resource. The information management database unit 340 stores task management information. In this example, the user database 341 which is a user storage unit, the task database 342, the schedule database 343, the user group database 344, the ToDo database 345, the device database, the location A database 347 and a task resource related document database 348 are provided. The communication unit 350 is connected to the network 20 and exchanges data with a plurality of information processing apparatuses.
In this example, “task” is a resource related to a user's work or work. In this embodiment, “task” targets a user group, a schedule, ToDo information, and a project. In the present embodiment, “information related to a task” refers to information related to a task including additional information related to the location, device, user, date and time. The “task” and “information about the task” are collectively referred to as task information.
For example, when a user group is handled as a task, the location to which the user group belongs, the devices that belong to the group, the people that make up the group, the period for which the group is to be used, etc. are the “information about the task”.

When a schedule is handled as a task, the location where the schedule is performed, the device used to perform the schedule, the person who executes the schedule, the date and time when the schedule is performed, and the like are “information about the task”.
In addition, when handling ToDo information as a task, the location where the ToDo is performed, the device used to perform the ToDo, the person who performs the ToDo, the period during which the ToDo is performed, and the like become “information about the task”.
Furthermore, when a project is handled as a task, “location concerning the task” includes a place where the project is performed, a person who configures the project, a device used in the project, a period during which the project is performed, and the like.
Returning to the description of the personal computer 100, each table stored in the storage device of the database unit 160 will be described.
First, the task list table 161 will be described. FIG. 5 is a schematic diagram showing an outline of information stored in the task list table. The task list table 161 is a table for storing task information, and one task is stored in each row. That is, the first column stores a task ID that is a symbol unique to the task information.
The second column stores information related to the date and time related to the task. The information regarding the related date and time is, for example, the date and start time when the schedule or project occurs. The date and time represents a certain point in time, and may represent a certain period.
The third column stores information about the user related to the task. The information regarding the related user is, for example, the ID of a user who participates in a schedule or project.
The fourth column stores information related to the location related to the task. The information on the related place is, for example, the name of the place where the schedule or project is performed.
The fifth column stores the contents of the task. The content of the task is, for example, a group name in the case of a user group or the name of each included member, a name of an event that occurs in the case of a schedule, and a name of work to be executed in the case of a ToDo list.

Next, the user list table 162 will be described. FIG. 6 is a schematic diagram showing an outline of information stored in the user list table.
The user list table 162 is a table that associates a user name with a symbol unique to the user. The first column stores a user ID that is a symbol unique to the user, and the second column stores a user name that is the name of the user.
Next, the operation history table 163 will be described. FIG. 7 is a schematic diagram showing an outline of information stored in the operation history table.
The operation history table 163 is a table that stores information related to the operation history of the information processing apparatus.
The contents of the operation are stored in the first column. The content of the operation includes a function and a setting content for executing the function.
The second column stores date information on the operation.
The third column stores the user ID of the user who performed the operation. The user ID corresponds to the user ID in the first column of the user list table 162 (see FIG. 5).
The fourth column stores task IDs of tasks related to the operation. The task ID corresponds to the task ID in the first column of the task list table 161 (see FIG. 4).

Next, the file information storage table 164 will be described. FIG. 8 is a schematic diagram showing an outline of information stored in the file information storage table.
The file information storage table 164 is a table for storing information related to scanned images held in the system.
The first column stores a document ID that is a symbol unique to the scanned image.
The second column stores document names that are names designated by the user for the scanned image.
The third column stores a user ID that is a symbol unique to the user who saved the scanned image. The user ID corresponds to the user ID in the first column of the user list table 162 (see FIG. 5).
The fourth column stores a task ID that is a symbol unique to the task information associated with the scanned image by the user.
The fifth column stores the date and time when the scanned image was saved.

Next, the operation of the information processing apparatus according to this example will be described. First, the flow of processing when saving a file will be described. FIG. 9 is a flowchart showing the flow of file storage in the information processing apparatus. This process is applied, for example, when a user edits a document and saves it as a file.
When saving a document as a file, first, the user authentication unit 112 acquires a user ID (ST1). Next, the task acquisition unit 113 acquires the task ID of the task specified by the user with reference to the task list table 161 (ST2). For tasks that do not exist in the task list table 161, the task ID and task contents are newly stored in the last row of the task list table 161, and information about the date, place, and user is obtained for those that have been obtained.
When the user saves the document, a pointer to the saved file is obtained as the file ID (ST3). The information storage table management unit 116 stores the document ID, the document name, the user ID, and the task ID, which are the file IDs obtained in the above steps, in the file information storage table. That is, the information storage table management unit 116 displays the document ID and the document name for the file, the user ID of the user who stored the file, the task ID of the task associated with the file, and the date and time when the file was saved. All are associated and stored in the file information storage table (ST4). Specifically, a new row is created in the last row of the file information storage table, and the acquired document ID, document name, user ID, task ID, and date and time when the file was saved are each created. , First column, second column, third column, fourth column, and fifth column.

Next, the flow during file operations will be described. FIG. 10 is a flowchart showing the flow of processing when an operation is performed on a file.
First, when the user requests the operation to be presented by the input device, the input acquisition unit senses this and acquires the document ID of the file (ST11).
The request for the operation is, for example, in application software for browsing / searching data, information, etc. (for example, Explorer of Basic Software Windows (registered trademark)), right-clicking a file icon to display a context menu, and from there This is done by selecting a menu requesting the presentation of an operation or by dragging and dropping an icon of a file to be manipulated onto an icon representing the presentation of the operation on the desktop. In addition, a request for presentation of an operation can be automatically made when the mouse cursor is moved to a file icon. When an operation presentation is requested for a document that does not exist in the file information storage table, the document ID is not acquired.

When an operation presentation request is made, the operation candidate presentation unit 114 refers to the file information storage table based on the document ID obtained in the previous step, acquires the task ID associated with the document ID, and acquires the task ID. Operation candidates are displayed on the information display unit 151 based on the task ID (ST12).
At this time, a file information storage table 164 (see FIG. 8) is prepared, the document ID of the selected file is obtained, and the task ID is compared with the document ID in the first column and the task ID in the fourth column of the file information storage table. Get an ID. In the previous step, when a presentation of an operation is requested for a document that does not exist in the file information storage table and the document ID is not acquired, a similar document in the file information storage table is searched as follows, and its task ID is set. get.
In searching for similar documents, for example, a document with a similar document name is selected from the document names stored in the second column of the file information storage table. Documents with similar document names include, for example, documents with a large number of matching character strings included in two document names, documents with matching user IDs stored in the third column of the file information storage table, and matching documents. When there are a plurality of documents, the document with the closest registration date and time stored in the fifth column of the file information storage table can be selected.
Next, the input acquisition unit 153 acquires the operation selected by the user (ST13). The operation selected by the user may be an operation other than that presented by the operation candidate presenting unit.
Then, the requested operation is executed, and the history management unit 115 updates the operation history table 163 (ST14). Thereby, a series of operations is completed.

Next, the operation of the task acquisition unit 113 will be described. FIG. 11 is a flowchart showing a process flow of the task acquisition unit.
The task acquisition unit 113 refers to the system clock managed by the operating system of the information processing apparatus, and acquires the date and time at that time (ST21). Next, the information management database unit 340 of the task information management server 300 is accessed, and a predetermined number (for example, five) of tasks closer to the date after that date is acquired together with the corresponding date and stored in the memory ( ST22). The number of items to be acquired is determined by the number that can be displayed on the screen at one time. The acquired acquisition task table 420 is shown in FIG. Next, the personal computer 100 displays the acquired task on the information display unit 151 (ST23), and acquires the task specified by the user from the input acquisition unit 153 (ST24).
Here, a procedure for acquiring task information from the task information management server 300 will be described. In order to acquire task information, a user ID, date and time information, and a necessary task type are transmitted from the information processing apparatus to the communication unit 350 of the task information management server 300 via the network 20 by HTTP. The communication unit 350 of the task information management server 300 acquires task information determined by the acquired user ID, date, and task type from the information management database unit 340.
At this time, the task information management server 300 performs the following operation. First, with reference to the acquisition task table 420 (see FIG. 12) held in the task information management server 300, items to be acquired are determined (first step).
Next, based on the obtained date / time information, the date / time range of the task to be acquired is determined. (Second step). The range of task date and time to be acquired is determined, for example, one month before and after the obtained date and time.
Further, the database section of the task information management server is accessed, and the items determined in the first step are extracted from the range determined in the second step and the data corresponding to the obtained user ID.
Then, the communication unit 350 returns the acquired list to the information processing apparatus again in HTTP in the XML format. This list is received by the network interface 120 of the information processing apparatus. Thereby, the list transmission from the task information management server 300 to the information processing apparatus ends.

Based on the acquired task table 420 obtained by this processing, the operation candidate presenting unit 114 displays a selection screen on the information display unit 151. FIG. 13 is a schematic diagram showing a task acquisition selection screen. The user designates a task to be acquired from the task designation screen 430. The task is designated by pressing the designation buttons 431 to 435 for each task. Reference numeral 436 indicates a cancel button. Then, the personal computer 100 acquires the designated task and displays the following setting screen on the information display unit 151 depending on the type of the acquired task. 14 to 23 are schematic diagrams illustrating screens displayed on the information display unit 151.
When the task type is “schedule”, a schedule designation screen 440 shown in FIG. 14 is displayed on the information display unit 151. After the acquired date and time, the schedule information is presented in a predetermined number in the closest order. The number of schedule information to be presented is determined by the size of the screen.
The schedule information includes “date and time when the schedule is performed”, “schedule name”, “person (user) related to the schedule”, and “location related to the schedule”. However, the “date and time when the schedule is performed” may indicate a certain point or a range.
The schedule can be specified by pressing the schedule specification buttons 441 to 445, and displayed by pressing the “previous schedule” button 446 and the “next schedule” button 447. It is possible to display a schedule before the current date and time or a schedule after the displayed date and time. Further, a detail button 448 for executing detailed display for each schedule and a “return” button 449 for returning the display to the previous stage are arranged.

When the detail button 448 is pressed, a detail screen 450 shown in FIG. 15 is displayed. On the detail screen 450, there are arranged a display 451 for displaying details of the schedule and a “return” button 452 for returning the display screen to the schedule designation screen 440.
When the task type is “ToDo”, a ToDo designation screen 460 is displayed on the information display unit 151 as shown in FIG. After the acquired date and time, a predetermined number of ToDo information items are presented in the closest order. The number of ToDo information to be presented is determined by the size of the screen.
The ToDo information includes “date and time related to ToDo information”, “name of ToDo information”, “person related to ToDo information”, and “location related to ToDo information”. The “date and time related to ToDo information” may indicate a certain point or a range.
ToDo can be specified by pressing the selection buttons 461 to 465 of each ToDo, and from the displayed date and time by pressing buttons such as “Previous ToDo” button 466 and “Subsequent ToDo” 467. Previous ToDo information or ToDo information after the displayed date and time can be displayed. Further, on the ToDo designation screen 460, a detail button 468 for executing detailed display for each ToDo and a “return” button 469 for returning the display to the previous stage are arranged.
When the detail button 468 is pressed, a detail screen 470 shown in FIG. 17 is displayed. The detailed screen 470 includes a display 471 for displaying detailed contents of ToDo and a “return” button 472 for returning the display screen to the ToDo designation screen 460.

When the task type is “project”, a project designation screen 480 is displayed on the information display section 151 as shown in FIG. After the date and time of acquisition, a predetermined number of project information is presented in order of closeness. The number of project information to be presented is determined by the size of the screen.
The project information includes “date and time related to project information”, “name of project information”, “person related to project information”, and “location related to project information”. The “date and time related to project information” may indicate a certain point or a range.
In addition to selecting a project by pressing the selection buttons 481 to 485 of each project, pressing a button such as “Previous Project” button 486 or “Subsequent Project” 487 allows the date and time displayed to be displayed. Previous project information or project information after the displayed date and time can be displayed. Further, a detail button 488 for executing detailed display for each project and a “return” button 489 for returning the display to the previous stage are arranged on the project designation screen 480.
When the detail button 488 is pressed, a detail screen 490 shown in FIG. 19 is displayed. The detailed screen 490 includes a display 491 for displaying the detailed contents of the project and a “return” button 492 for returning the display screen to the project designation screen 480.

When the task type is “user group”, a user group designation screen 510 is displayed on the information display unit 151 as shown in FIG. After the acquired date and time, a predetermined number of user group information is presented in the closest order. The number of user group information to be presented is determined by the size of the screen.
The user group information includes “date and time related to user group information”, “name of user group information”, “person related to user group information”, and “location related to user group information”. The “date and time related to user group information” may indicate a point or a range.
The user group can be specified by pressing the selection buttons 511 to 515 of each user group, and the date and time displayed by pressing the “forward” button 516 and the “back” 517 button. Previous user group information or user group information after the displayed date and time can be displayed. The user group designation screen 510 further includes a detail button 518 for executing detailed display for each user group and a “return” button 519 for returning the display to the previous stage.

When the detail button 518 is pressed, a detail screen 520 shown in FIG. 21 is displayed. On the detail screen 520, a detailed display 521 of the user group and a “return” button 522 for returning the display screen to the user group designation screen 510 are arranged.
In addition, as shown in FIG. 22, the task selection screen 530 can be displayed on the information display unit 151 without distinguishing between task types. The information displayed at this time includes task types other than those described above.
A task can be specified by pressing the selection buttons 531 to 535 of each task, and displayed by pressing a “previous task” button 536 and a “next task” button 537. Tasks before the current date and time or tasks after the displayed date and time can be displayed. Further, on the task selection screen 530, a detail button 538 for executing detailed display for each task and a “return” button 539 for returning the display to the previous stage are arranged.
When the detail button 518 is pressed, a detail screen 520 shown in FIG. 21 is displayed. On the detail screen 520, a detailed display 521 of the user group and a “return” button 522 for returning the display screen to the user group designation screen 510 are arranged.
The user designates one of them from the operation command unit 152, and the input obtaining unit 153 obtains information on the task name and the corresponding task (ST24). For example, it is checked whether a combination of the task name and information related to the task exists in the task list table, and if it exists in the task list table, the corresponding task ID is acquired. If the task list table does not exist, the task name and additional information are stored in the last row of the task list table, and a task ID that does not exist in the task list table is acquired as a new task ID. Store in a row.

This process will be described below. First, i = 1 is set as an initial value (ST25). It is determined whether the i-th row and fifth column of the task list table 161 matches the name of the selected task (ST26). If they match, the i-th row and second to fourth columns of the task list table 161 are It is determined whether the information related to the selected task matches the information related to the date, time, person, and place (ST27). If they match, the i-th row and first column of the task list table are acquired as the selected task ID (ST28).
On the other hand, if no task exists in the task list table 161, it is determined whether i matches the number of rows in the task list table (ST30). If not, 1 is added to i (ST29) in step ST26. Process. If i matches the number of rows in the task list table, the name of the selected task is stored in the fifth column of the last row of the task list table 161 (ST31), and then the date and time that is information relating to the selected task, The information about the person and the location is stored in the last 2nd to 4th columns of the task list table, respectively, and any symbol that does not exist in all the 1st columns is set as the task ID of the selected task (ST33). ), The task ID of the selected task is stored in the last row and first column of the task list table 161 (ST34). By this processing, the task name and additional information are stored in the last row of the task list table 161, and a task ID that does not exist in the task list table 161 is acquired as a new task ID and stored in the last row of the task list table 161. be able to.
In addition, the following is mentioned as conditions for determining whether or not the task to be acquired matches another task in the task list table.
Match / mismatch of the combination of task name and additional information / match / mismatch of related person and date / time information / match / mismatch of related location and date / time information Next, a specific example of processing of the user authentication unit 112 will be described. In this example, the ID of the user who operates this system is acquired. Specifically, the login ID used when logging in to the operation system of the computer is acquired. That is, at the time of user authentication, a list of users who are assumed to use the device is displayed on the information display unit 151, and when the user presses one of them, the user name specified by the user by the input acquisition unit 153 is displayed. Authenticate by password and request password input if necessary.

Next, operation candidate presentation processing will be described. FIG. 24 is a flowchart showing the flow of operation candidate presentation processing.
Here, for all operations associated with the same task ID as the acquired task ID among the operations in the operation history storage table, the magnitude of the possibility of being selected this time is calculated, and the operations are returned in descending order of possibility. Process.
First, “i = 1, j = 1” is set as an initial setting (ST31). Then, the acquired task ID is compared with the task ID stored in the operation history table i-th row and fourth column (ST32), and if they match, the following operation is performed.
The operation stored in the operation history table in the i-th row and the first column is defined as an operation candidate A (j). (ST33). Here, in addition to the matching of the task ID, it may be added as a condition that the user ID acquired by the user authentication unit matches the user ID stored in the operation history table i-th row and third column.
Next, the selection probability P (j) of A (j) is calculated (ST34). As a calculation method of P (j), P (j) can be an arbitrary constant. In this example, first, the current date and time are compared with the date and time in the operation history table i-th row and second column, exp (−difference in date and time).
If the selection probability has already been calculated for the same operation, P (j) is added. Specifically, if there is k such that A (j) = A (k) for all k of k = 1, 2,..., J−1 (ST35), P (k) = P (k). + P (j) (ST36), otherwise j = j + 1 (ST37). Then, i = i + 1 is set (ST39), and step ST33 to step ST37 are repeated until i = the number of rows in the operation history table.
Then, the operation selection screen 550 is displayed on the information display unit 151 with the number of A (j) determined to be presented as the operation candidates in the descending order of P (j) (ST40).

FIG. 25 is a schematic diagram showing an example of the operation selection screen. In this example, on the operation selection screen 550, from the top, a “print: two-sided copy” button 551, an “email transmission” button 552, a “print: ten-sided” button 553, and “print: A “double-sided, aggregated” button 554 and a “FAX transmission” button 555 are displayed. The user selects a desired process from these and presses the button.
When such processing is performed, the history management unit 115 performs the following processing. The history management unit 115 performs two types of processing, “history addition” and “history update”. If there is a prescribed number of rows in the operation history table, the “history update” processing is performed. Performs “add history” processing.
FIG. 26 is a flowchart showing history addition processing of the history management unit. When adding a history, the history management unit 115 acquires the operation content actually operated by the user, the date and time information at the time of the operation, the user ID, and the selected task ID (ST41). Next, the operation contents, the date and time information at the time of operation, the user ID, and the selected task ID are stored in the first, second, third, and fourth columns of the last row of the operation history table, respectively (ST42). .

FIG. 27 is a flowchart showing the history update process of the history management unit. When the history is updated, the history management unit 115 acquires the operation content actually operated by the user, the date and time information at the time of the operation, the user ID, and the selected task ID (ST51). Next, the operation contents, the date and time information at the time of operation, the user ID, and the selected task ID are stored in the first, second, third, and fourth columns of the last row of the operation history table (ST52). Then, the first row of the history update table is deleted and the process is terminated (ST53). This completes a series of file operations in the information processing apparatus.
As described above, according to the information processing apparatus according to the present embodiment, when performing an operation on a file, an operation expected to be performed in advance is estimated and presented to the user. The target operation can be reached without menu operation. The estimation is performed based on information related to the “task” associated with the image. Since the “task” is information close to the purpose of the business, an operation more suitable for the business is presented.

Next, an example of an information processing apparatus according to another embodiment will be described. FIG. 28 is a block diagram showing a system in which an information processing apparatus according to another example is arranged, and FIG. 29 is a block diagram showing the information processing apparatus. In this example, two personal computers 700, the task information management server 300, and the database management server 600 are connected via a network 810 to form an information processing apparatus system 800.
As shown in FIG. 28, the personal computer 700 has a configuration in which the database unit 160 of the personal computer 100 described above is arranged and managed in the database management server 600. That is, the personal computer 700 includes a processing unit 110, a network interface 120, an interface unit 150, and a memory 170, similar to the personal computer 100. In addition, the same code | symbol is attached | subjected to the component same as the said 1st example.
Further, the configuration of the task information management server 300 is the same as the above-described example. The database management server 600 includes a network interface 610 and a database unit 620. 620 includes a task list table 621, a user list table 622, an operation history table 623, an image information storage table 624, and an image storage unit 625. For this reason, in this example, the database management in which each storage device for storing the image acquired by the image acquisition unit 130, the task information held by the user, the information related to the executed operation, and the relationship between the individual task information and the operation is on the network 810. Each storage table held in the server 600 is referred / added / updated via the network interface 610.
In the information processing apparatus system 800 according to this example, similarly to the first example, when an operation on a file is performed, an operation expected to be performed in advance is estimated and presented to the user. The target operation can be reached without menu operation. The estimation is performed based on information related to the “task” associated with the file. Since the “task” is information close to the purpose of the business, an operation more suitable for the business is presented.
In this example, the file, task information, and operation history are stored in the database management server, and the file saved from each personal computer and the task information and operation history related to the file are shared and callable by each personal computer. Therefore, the same operation can be realized from any personal computer.

It is a block diagram which shows the computer system with which example embodiment is applied. It is a block diagram which shows the computer system with which example embodiment is applied. It is a block diagram which shows the structure of a computer system. It is a block diagram which shows the system configuration | structure of a task information management server. It is a schematic diagram which shows the example of the storage content of a task list table. It is a schematic diagram which shows the example of a storage content of a user list table. It is a schematic diagram which shows the example of the storage content of the operation history table. It is a schematic diagram which shows the example of the storage content of a file information storage table. It is a flowchart which shows the flow of file preservation | save. It is a flowchart which shows the flow at the time of operating with respect to a file. It is a flowchart which shows the flow of a process of a task acquisition part. It is a schematic diagram which shows the example of storage content of the acquisition task table hold | maintained in a task information management server. It is a schematic diagram which shows the selection screen of task acquisition. It is a schematic diagram which shows the screen displayed on an image display part, when a task is a schedule. It is a schematic diagram which shows the screen which displayed the detailed content of the schedule. It is a schematic diagram which shows the screen displayed on an image display part, when a task is ToDo. It is a schematic diagram which shows the screen which displayed the detailed content of ToDo. It is a schematic diagram which shows the screen displayed on an image display part, when a task is a project. It is a schematic diagram which shows the screen which displayed the detailed content of the project. It is a schematic diagram which shows the screen displayed on an image display part, when a task is a user group. It is a schematic diagram which shows the screen which displayed the detailed content of the user group. It is a schematic diagram which shows the screen displayed on an image display part when not dividing into tasks. It is a schematic diagram which shows the screen which displayed the detailed content of the task. It is a flowchart which shows the process of an operation candidate presentation part. It is a schematic diagram which shows the example of a screen display of presentation operation selection. It is a flowchart which shows the process of "history addition". It is a flowchart which shows the process of "history update". It is a block diagram which shows the system by which the information processing apparatus which concerns on other embodiment is arrange | positioned. It is a block diagram which shows the structure of information processing apparatus.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Information processing apparatus system, 100 Personal computer, 110 Processing part, 111 Central processing part, 112 User authentication part, 113 Task acquisition part, 114 Operation candidate presentation part, 115 History management part, 116 Information storage table management part, 120 Network interface , 130 Image acquisition unit, 140 Image formation unit, 150 Interface unit, 151 Information display unit, 152 Operation command unit, 153 Input acquisition unit, 160 Database unit, 161 Task list table, 162 User list table, 163 Operation history table, 164 File information storage table, 170 memory, 300 task information management server

Claims (16)

A user authentication unit for determining the current user;
A task list storage unit for storing a list of tasks;
A task acquisition unit that acquires tasks related to the user;
A file information storage unit for storing the association between the task and the file;
An information storage management unit that stores a file in the file information storage unit in association with a task related to the file.   The information processing apparatus according to claim 1, wherein the task information acquired by the task acquisition unit includes at least one of a schedule, ToDo information, a project name, and a user group. A file information storage unit for storing the association between the task and the file;
An operation history storage unit for storing the task and the operation as a history associated with each other;
A user authentication unit for determining the current user;
An information processing apparatus comprising: an operation candidate presenting unit that selects and presents an operation related to a task based on the file when the file is operated.   The information processing apparatus according to claim 3, wherein the task information acquired by the task acquisition unit includes at least one of a schedule, ToDo information, a project name, and a user group.   The operation candidate presentation unit refers to the relationship between the task information and file information held by the file information storage unit, and the relationship between the task information and operation held by the operation history storage unit, and presents an operation on the file. The information processing apparatus according to claim 3. The operation history storage unit stores task information and date / time information in association with each other,
The information processing apparatus according to claim 3, wherein the operation candidate presenting unit sets an operation presentation order based on a history date and time in the operation history storage unit and a proximity of the current date and time. The operation history storage unit stores task information and a user in association with each other,
The information processing apparatus according to claim 3, wherein the operation candidate presenting unit distinguishes whether or not a history user in the operation history storage unit matches a current user in presenting an operation. A user authentication step to determine the current user;
A task acquisition step for acquiring a task related to the user;
A task list storage step for storing a list of tasks;
And a file information storage step for storing the association between the task and the file. The task information acquired by the task acquisition step is
Schedule, ToDo information, project name, and user group,
The information processing method according to claim 8, comprising at least one of the following. A user authentication step to determine the current user;
A file information storage step for storing an association between the task and the file;
An operation history storing step for storing the task and the operation as a history associated with each other;
An operation candidate presenting step of selecting and presenting an operation related to a task based on the file when the file is operated. The task information acquired by the task acquisition step is
Schedule, ToDo information, project name, and user group,
The information processing method according to claim 10, comprising at least one of the following. The operation candidate presentation step
The operation for the file is presented by referring to the relationship between the task information and the file information held by the file information storage step and the relationship between the task information and the operation held by the operation history storage step. The information processing method described. The operation history storing step stores task information and date / time information in association with each other,
The information processing method according to claim 10, wherein the operation candidate presenting step uses the closeness between the date and time of the history in the operation history storing step and the current date and time as an operation presentation order. The operation history storing step stores task information and a user in association with each other,
The information processing method according to claim 10, wherein the operation candidate presenting step distinguishes whether or not a history user in the operation history storing step matches a current user in presenting an operation.   The information processing program for making a computer perform each step of the information processing method as described in any one of Claims 8 thru | or 14.   A computer-readable recording medium on which an information processing program for causing a computer to execute the information processing method according to any one of claims 8 to 14 is described.

Images