JP5257578B2 - Information processing program and information processing apparatus - Google Patents

Description

  The present invention relates to an information processing program and an information processing apparatus.

  When information is created and edited, or existing information is edited, many editing operations may be performed. Editing is often done by trial and error, and after proceeding with editing, if there is no problem, the editing up to that point is confirmed, and if there is a problem, it is necessary to return the editing that was performed and start over. In such a case, there is a function to return editing one step at a time or to advance the returned editing one step at a time, and this function is used to withdraw or reflect the editing processing performed in time series as desired. Editing. For example, in the apparatus described in Patent Document 1, it is possible to easily restore data up to a certain point by holding an operation history and its contents (values before update if updated). Yes.

  However, if the editing is restored and another editing process is performed, the contents of the returned editing process are lost, and if the original is better, the editing operation may have to be performed again. Further, when the editing work is performed again, the contents of the original editing work must be stored, and since the memory of the operator is relied on, the original editing result is not always obtained.

  Furthermore, many systems that can withdraw and reflect edits have a limited period of time during which the function is valid. However, the editing work is not always performed continuously, and does not necessarily end in time. For this reason, when editing is necessary, the edited content is already confirmed and cannot be withdrawn. If there is a problem with the editing content once confirmed, it cannot be restored and editing must be performed again.

  In addition, when an operator updates information, there is a case where it is not desired to disclose the progress of the update to other operators. Of course, in order to avoid conflicts in editing processing for information, there is already a system that does not disclose update contents to other operators during editing processing by a certain operator. However, in order to conceal updates over a long period of time until an arbitrary point in time, the operator performs an operation to conceal the information itself from others before publishing the update, and releases the concealment when the update is completed It is necessary to perform an operation. Otherwise, the update contents are made public, so that there is a case where inconvenient data influences another person's business.

JP 2003-058534 A

  An object of the present invention is to provide an information processing program and an information processing apparatus that can be operated by returning to any operation processing performed so far.

  According to the first aspect of the present invention, the history management means for managing the history of the operation process including the operation position information indicating the position of the operation process performed for the series of operation processes from the start of the operation, and which operation process ends. Operation position management means for managing the current operation position of the operation process indicating whether to perform the operation process in the state after the operation based on the current operation position information, and based on the history of the operation process managed by the history management means until then An operation position processing means for changing the current operation position information managed by the operation position management means in response to the designation of a change in the current operation position arbitrarily specifying a position at which the performed operation processing is completed; The number of re-operations at the current operation position when the operation process instructed at the current operation position indicated by the operation position information is controlled and the operation process is performed after the current operation position. Information operation processing means for adding operation order in retry and generating operation position information to perform operation processing; information management means for managing operation target information to be operated and information related to updates to the operation target information It is an information processing program characterized by causing a computer to function.

  In the invention described in claim 2 of the present application, in the configuration described in claim 1 of the present application, the information management means instructs the operation processing for the operation target information that is the target of the operation processing by the information operation processing means. An information processing program for rejecting an update instruction from an operator other than an operator.

  In the invention according to claim 3 of the present application, in the configuration according to claim 1 of the present application, the information management unit instructs the operation processing for the operation target information that is the target of the operation processing by the information operation processing unit. An information processing program that provides a state in which no operation is performed to an operator other than the operator.

  The invention according to claim 4 of the present application is the configuration according to any one of claims 1 to 3, wherein when the information operation processing means receives an operation completion instruction, the information management means The information processing program is characterized in that the operation processing up to the instruction is reflected in the operation target information managed in this manner, and the history management means deletes the history.

  In addition to the configuration of any one of claims 1 to 4, the invention described in claim 5 of the present application further includes the history management means for the operator who designates the change of the current operation position. An information processing program that causes the computer to function as a presentation unit that presents a history of operations performed so far, managed by the computer.

  The invention according to claim 6 of the present application is an information processing program in which the presenting means in the configuration according to claim 5 presents a figure corresponding to each operation.

  In the invention according to claim 7 of the present application, when the presenting means in the configuration according to claim 6 of the present invention performs a plurality of operations from a certain operation position, the figures corresponding to the plurality of operations are arranged in parallel. It is an information processing program characterized by presenting.

  The invention according to claim 8 of the present application is an information processing program in which the presenting means in the configuration according to claim 6 presents a figure in which some operations are combined.

  The invention according to claim 9 of the present application is a history management means for managing a history of operation processing including operation position information indicating a position of operation processing performed for a series of operation processing from the start of operation, and which operation processing ends. Operation position management means for managing the current operation position of the operation process indicating whether to perform the operation process in the state after the operation based on the current operation position information, and based on the history of the operation process managed by the history management means until then An operation position processing means for changing the current operation position information managed by the operation position management means in response to the designation of a change in the current operation position arbitrarily specifying a position at which the performed operation processing is completed; The number of re-operations at the current operation position when the operation process instructed at the current operation position indicated by the operation position information is controlled and the operation process is performed after the current operation position. Information operation processing means for adding operation order in retry and generating operation position information to perform operation processing; information management means for managing operation target information to be operated and information related to updates to the operation target information It is an information processing apparatus characterized by having.

  According to the first aspect of the present invention, the operation can be performed by returning to any operation processing performed so far.

  According to the invention described in claim 2 of the present application, it is possible to prevent updating by others on the operation target information during the operation.

  According to the invention described in claim 3 of the present application, the operation target information in the middle of the operation is concealed from others and does not affect the business of others.

  According to the fourth aspect of the present invention, until an operation completion instruction is given, the operation can be performed by returning to any of the operation processes performed so far.

  According to the invention described in claim 5 of the present application, the operator can designate the current operation position where the operation processing should proceed while understanding what operation has been performed.

  According to the invention described in claim 6 of the present application, the operator can designate the current operation position by selecting the presented graphic.

  According to the invention described in claim 7 of the present application, the operator can know in a list which operation has been performed again from which stage.

  According to the invention described in claim 8 of the present application, even when a large number of operations are performed, the entire operation performed can be easily grasped and the current operation position can be designated.

  According to the ninth aspect of the present invention, the operation can be performed by returning to any operation processing performed so far.

  FIG. 1 is a configuration diagram showing an embodiment of the present invention. In the figure, 11 is an operation position management unit, 12 is an operation history management unit, 13 is an information management unit, 14 is an update management unit, 15 is an existing information management unit, 16 is an operation processing unit, 17 is a presentation processing unit, and 18 is An operation position processing unit, 21 is a storage unit, 22 is current operation position information, 23 is operation history information, 24 is update information, 25 is exclusive information, and 26 is existing permanent information.

  The operation position management unit 11 performs management such as whether the operator is performing information operation processing. In particular, the current operation position indicating which operation is to be performed in the state after completion of the operation is stored and managed as current operation position information 22 in the storage unit 21.

  The operation history management unit 12 stores and manages the history of operation processing performed after receiving an operation start instruction as operation history information 23 in the storage unit 21. The operation history information 23 includes an operation identifier for identifying a series of operation processes from the start to the end of the operation, and position information indicating the position of the operation process performed for the series of operation processes. In addition, after receiving an operation start instruction, when the presentation processing unit 17 requests acquisition of the operation history information 23, the operation history information 23 is read from the storage unit 21 and passed to the presentation processing unit 17. Further, when the operation processing unit 16 receives an operation completion instruction, the operation history information 23 of the operation processing performed up to the instruction is deleted.

  The information management unit 13 manages the operation target information that can be the target of the operation process, and also manages the update of the operation target information by the operation process. When reading of information is requested, the update management unit 14 and the existing information management unit 15 are used, and the update management unit 14 manages the operator who performs the operation by instructing the start of the operation. In accordance with the update information 24 from the operation start to the operation position indicated by the current operation position information 22 in the update information 24, a result of performing the operation process on the existing permanent information 26 managed by the existing information management unit 15 is provided. The existing permanent information 26 managed by the existing information management unit 15 is provided to other operators. In this way, by providing the original state before the operation process to non-operating operators, the operating information is concealed from others and does not affect the operations of others. I am doing so.

  When the operation processing unit 16 receives an instruction for an update operation process, the information management unit 13 uses the update management unit 14 to change information (including registration, change, deletion, etc.) The operation target information and the content of the operation process are stored as update information 24 in the storage unit 21. It should be noted that the original operation target information that is an update target is left as it is. In addition, for the operation target information to be updated and information affected by the update, an update instruction from another person is rejected using the existing information management unit 15.

  Further, when the operation processing unit 16 receives the operation completion instruction, the information management unit 13 reflects the result of the operation processing up to the instruction in the existing permanent information 26 managed by the existing information management unit 15. .

  The update management unit 14 manages the update information 24. When an update (including registration, change, deletion, etc.) is performed by an operation process after receiving an operation start instruction, information related to the operation target information that is the update target and the contents of the update are stored as update information 24. Stored in the unit 21. At that time, the content of the original operation target information is not changed. When the update information 24 is stored, in addition to the information related to the operation target information, an operation identifier for identifying the operation and operation position information indicating the position of the operation with respect to the entire operation flow are added and stored.

  The existing information management unit 15 manages the existing permanent information 26 that is the operation target information. Even if the operation is started, the existing persistence information 26 is not changed. When an operation completion instruction is received, the result of performing the operation processing up to that time is reflected in the existing persistence information 26. Further, even when an operator who has not instructed the operation start updates the information, the updated operation target information is stored in the storage unit 21 as the existing permanent information 26. However, for the operation target information that is the target of the operation process by the operator who has instructed the start of the operation, the operator is registered as the exclusive information 25, and the operation target information that is being processed by an operator other than the operator Is not updated, an update instruction from an operator other than the registered operators is rejected.

  The operation processing unit 16 receives an operation processing instruction for information from the operator, and controls each unit according to the instructed operation processing. The operation processing instructions include operation start, update (including registration, update, deletion, etc.), operation completion, and the like.

  The presentation processing unit 17 presents various information to the operator. For example, it presents information managed by the information management unit 13, presents a history of operations performed from an operation start instruction, and the like. The presentation of the operation history is used when the operator designates the change of the current operation position. In addition, when presenting an operation history, a corresponding figure is presented for each operation performed so far. At that time, when a plurality of operations are performed from a certain operation position, figures corresponding to the plurality of operations are presented in parallel. In addition, some of the plurality of operations may be presented as a combined figure.

  The operation position processing unit 18 receives the designation of change of the current operation position performed by the operator based on the operation history managed by the operation history management unit 12, and is currently managed by the operation position management unit 11. The operation position information 22 is changed. The current operation position can be changed by arbitrarily specifying the position where the operation processing performed so far has been completed. The operation process is performed again from the current operation position.

  The storage unit 21 stores various information that needs to be stored. Here, as an example, the current operation position information 22, operation history information 23, update information 24, exclusive information 25, existing permanent information 26, and the like are stored. The current operation position information 22 is managed by the operation position management unit 11 and indicates which operation is to be performed on the operation target information after the operation is completed. The operation history information 23 is a history of operation processing performed by the operation processing unit 16 and is managed by the operation history management unit 12. The operation history information 23 includes an operation identifier for identifying each operation and position information indicating a position during a series of operation processes. The update information 24 is managed by the update management unit 14, and the contents of the operation processing performed on the operation target information by the operation processing unit 16, the operation identifier for identifying the operation, information on the operation target information, Includes all target information that is affected by target operations. The exclusive information 25 is used to exclude the update from the operator other than the operator who is performing the operation on the operation target information, and associates the operation target information with the operator. The exclusive information 25 is managed by the existing information management unit 15. The existing permanent information 26 is information that can be various operations, and is managed by the existing information management unit 15. Even when an update operation process is instructed by the operator, the information before update is managed as the existing permanent information 26.

  An example of the operation in the embodiment of the present invention will be described. FIG. 2 is a flowchart illustrating an example of an operation when an operation start instruction is performed. When the operator instructs to start the operation, it is determined in S61 whether or not the operator has already instructed to start the operation. If the operation has already been instructed, error processing is performed in S65. Alternatively, switching may be made by providing another operating environment.

  In the case of an operator who has not received an operation start instruction, the operation start instruction made this time is received. In S62, an operation identifier for identifying a series of operations to be performed in the future is generated, and current operation position information 22 with the current operation position set to 0 is generated. Further, in S63, the current operation position information 22 generated in S62 is stored in the storage unit 21. In S <b> 64, the information management unit 13 or the existing information management unit 15 generates the exclusive information 25 so that the information affected by the operation process after the operation start instruction is not updated by another person. An operator identifier or the like is held as information for this purpose.

  FIG. 3 is an explanatory diagram of an example of current operation position information generated by an operation start instruction. In this example, the current operation position information 22 includes information such as an operator identifier, a start time, an operation identifier, a current operation position, an annotation, and an expiration date. Of course, the information included in the current operation position information 22 is not limited to this example, and any other information may be included as long as it includes the operator identifier, the operation identifier, and the current operation position.

  In the example shown in FIG. 3, the case where the operator 1 and the operator 2 each instruct | indicate the operation start is shown. For operator 1, XXXXXXXXXX is generated as an operation identifier, and for operator 2, YYYYYYYYYY is generated as an operation identifier.

  FIG. 4 is a flowchart illustrating an example of an operation when an update operation is instructed. The operator instructs various operation processes on the information managed by the information management unit 13. Here, a process when an operation process for update (registration, change, deletion) is instructed is shown. The operation processing instruction is received by the operation processing unit 16, and each unit is controlled.

  First, in S <b> 71, the operation position management unit 11 determines whether or not the operator who has instructed the update operation has instructed the operation start using the current operation position information 22. If the operation start instruction has not been received from the operator, in S77, the existing information management unit 15 reads the existing permanent information 26 to be operated through the information management unit 13, and the operation processing unit 16 performs the operation process. The existing information management unit 15 updates the existing permanent information 26. Of course, if the existing permanent information 26 to be operated is the information to be operated by another operator, the update in S77 is rejected and error processing is performed.

  If it is determined in S71 that the operation start instruction has already been performed, in S72, the operation position management unit 11 determines from the current operation position information 22 the operation identifier corresponding to the operator who has issued the update operation instruction. The current operation position is extracted.

  In S73, it is determined whether or not an operation process is performed after the current operation position. If the operation process is performed after the current operation position, this indicates that the operation process is returned and the operation process is to be performed again. Therefore, in S74, operation position information is generated so that it can be seen that the operation has been redone. As an example, here, the current operation position is set to '. 'And a number are added to indicate the number of re-operations. 'And a number are added to the end to indicate the order of operations in the retry and are used as operation position information. For example, if the current operation position is 2, the operation position information is 2.1.1, and if the current operation position is 3.2.1, the operation position information is 3.2.1.1.1. For example, if the current operation position is 2 and the third re-operation, 2.3.1 is used as the operation position information.

  If the operation process is not performed after the current operation position, it is assumed that the operation process is further performed. In S75, the current operation position is advanced as operation position information. As an example, 1 is added to the last number of the current operation position here. For example, if the current operation position is 2, the operation position information is 3. If the current operation position is 3.2.4, the operation position information is 3.2.5.

  In S76, it is determined whether or not the current operation position is 0. If it is 0, the existing permanent information 26 is updated in S77. If it is confirmed that the current operation position is not 0, the instructed update operation process is performed by the operation processing unit 16. Here, a case where the update operation to be instructed is any one of a registration operation, a change operation, and a delete operation is shown. Of course, other update operations may exist.

  The registration operation is an operation process for adding operation target information. The information to be added may be newly created or a copy of information stored in the storage unit 21 as the existing permanent information 26. Alternatively, information may be transferred from the outside to be operation target information. If a registration operation is instructed, after copying or transferring information as necessary, in S81, an existing information management unit is used to prevent the operation target information from being updated by other operators. 15 generates exclusive information 25 for the operation target information and stores it in the storage unit 21. In S <b> 82, the update management unit 14 generates update information 24 corresponding to the registration operation and stores it in the storage unit 21. The update information 24 includes an operation identifier indicating that the registration operation has been performed, an operation identifier, the operation position information generated in S74 or S75, and an information identifier for identifying the operation target information. Further, in S 87, the operation history management unit 12 generates operation history information 23 corresponding to the registration operation and stores it in the storage unit 21. The operation history information 23 includes an operation identifier, operation position information, an operator identifier, an operation name, an operation time, and the like.

  For example, when the operation target information is managed hierarchically, exclusive information 25 is generated not only for the operation target information but also for a higher hierarchy including the operation target information, and an update operation from another operator is excluded. May be. In such a case, the update information 24 for the upper hierarchy may be created.

  The change operation is an operation process for changing the content of the operation target information. For example, operations such as correcting the description of a document are included. When the change operation is performed in the operation processing unit 16 according to the instruction, the existing information management unit 15 generates exclusive information 25 for the operation target information that is the target of the change operation and stores it in the storage unit 21 in S83. In S <b> 84, the update management unit 14 generates update information 24 corresponding to the change operation and stores it in the storage unit 21. The update information 24 includes an operation identifier including the changed content, an operation identifier, the operation position information generated in S74 or S75, and an information identifier for identifying the operation target information. Further, in S 87, the operation history management unit 12 generates operation history information 23 corresponding to the change operation and stores it in the storage unit 21. The operation history information 23 includes an operation identifier, operation position information, an operator identifier, an operation name, an operation time, and the like. In this change operation, the operation target information before the change is not changed, the existing information management unit 15 manages the existing permanent information 26 as it is, and the update management unit 14 manages the changed part as the update information 24. .

  The delete operation is an operation process for deleting operation target information. If a deletion operation is instructed, in S85, the existing information management unit 15 generates and stores exclusive information 25 for the operation target information in order to prevent the operation target information from being updated by another operator. Stored in the unit 21. In S <b> 86, the update management unit 14 generates update information 24 corresponding to the deletion operation and stores it in the storage unit 21. The update information 24 includes an operation identifier indicating that the deletion operation has been performed, an operation identifier, the operation position information generated in S74 or S75, and an information identifier for identifying the operation target information. Further, in S 87, the operation history management unit 12 generates operation history information 23 corresponding to the deletion operation and stores it in the storage unit 21. The operation history information 23 includes an operation identifier, operation position information, an operator identifier, an operation name, an operation time, and the like.

  For example, when the operation target information is managed in a hierarchical manner, when the operation target information is deleted in a higher hierarchy including the operation target information, the exclusive information 25 is generated for the information below the deleted hierarchy, Update operation from the operator. In such a case, the update information 24 about the information of the hierarchy below the deleted hierarchy may be created. Moreover, the existing information management unit 15 may manage the operation target information to be deleted as new information.

  In the above operation example, the registration, change, and deletion operations have been described. For example, in the case of a movement operation, registration and deletion operations may be performed. Of course, it goes without saying that other various operations may be accepted.

In the description of the update operation described above, for example, in the registration operation and the delete operation, not only the operation target information but also the hierarchical information is managed, the exclusive information 25 is generated for the upper hierarchy, and is received from other operators. The update operation is not accepted. This is because an update operation for certain operation target information also affects other information. The following operations can be considered as situations that affect the situation.
-Reference-Upper layer of registration destination and deletion source-Version management information

  For example, other information may refer to the operation target information. If the operation target information is changed or deleted, information that refers to the operation target information is also affected. Therefore, it is determined whether there is information referring to the updated operation target information. If there is information, the referenced information is also treated as updated, and the existing information management unit 15 The exclusive information 25 is created, and the update history management unit 12 creates update information 24 of the information and stores it in the storage unit 21.

  The upper layers of the registration destination and the deletion source are affected because the number of information to be arranged changes. As described above, the existing information management unit 15 also creates the exclusive information 25 for the upper layer of the registration destination and the deletion source so that update operations from other operators are not accepted.

  In addition, when version management is performed, for example, a configuration may be used in which a version is updated upon completion of an operation to be described later. In such a case, it is preferable to set a new version number when the registration operation is performed so that other operators cannot use the version number. If it is necessary to exclusively control other information in the version management, exclusive information 25 may be generated for the information and stored in the storage unit 21.

  An example of the operation when the above update operation is instructed will be further described using a specific example. Here, it is assumed that the existing permanent information 26 is a file group and is hierarchically held by folders. In the following example, the file is described as a document.

FIG. 5 is an explanatory diagram of an example of the update operation performed by the operator. Here, it is assumed that the operator 1 has instructed the operation start in advance and has instructed the following operation.
(A) Register one document in the folder (b) Change the value of the user attribute A of the registered document to “A1” (c) Delete another document existing in the folder (a) (d) Return the current operation position after the operation of (c) is completed. (E) Instead of deleting (c), the value of the user attribute B of the document registered in (a) is changed to “B1”. The information identifier of the document in “100001”, (a), (b), and (e) is “100111”, and the information identifier of the document to be deleted in (c) is “100105”. It is assumed that the operation identifier given when the operator 1 gives an operation start instruction is “5000001”.

  If each of the above-described operation processes is indicated by a rectangle, the operation process shown in FIG. 5 is performed. Each rectangle is added with symbols (a) to (e) corresponding to the above operation and operation position information assigned to each operation process as will be described later.

  First, a case where an operation for registering one document in the folder (a) is instructed will be described. For example, it is assumed that one document of the existing permanent information 26 is registered in a folder as operation target information. In this case, the operation target information is handled as a new document registered in the folder.

  FIG. 6 is an explanatory diagram of an example of information stored in the storage unit 21 after the operation (a) is performed. In S72 of FIG. 4, the operation identifier “5000001” and the current operation position “0” are extracted from the current operation position information 22. Since nothing is performed before the operation (a), the current operation position is “0”.

  Since there is no operation after the current operation position, 1 is added to the current operation position in S75 to set the operation position to “1”. As shown in FIG. 6A, the current operation position of the current operation position information 22 is updated to “1”.

  Since it is a registration operation, the process advances to S81 to create exclusive information 25 so that the document to be registered and the folder in which the document is placed are not updated by another operator. As shown in FIG. 6D, the folder with the information identifier “100001” and the document with the information identifier “100111” are associated with the operator 1, and the folder and the document are not updated by an operator other than the operator 1. Like that.

  In S82, update information 24 indicating that a registration operation has been performed for the folder with the information identifier “100001” and the document with the information identifier “100111” is generated. The generated update information 24 is shown in FIG. The update information shown in this example includes items of operation identifier, information identifier, operation position, operation content, other management information, user attribute A, user attribute B, and other attribute information. The other management information includes management information such as a hierarchy and a reference destination. Of course, these items are only examples, and may be selected including other items. As operation contents, “registered (self)” is attached to a registered document, and “registration (parent)” is attached to a folder in which the document is arranged.

  In S87, operation history information 23 indicating that a registration operation has been performed is generated and stored in the storage unit 21. An example of the generated operation history information 23 is shown in FIG. In this example, the operation history information 23 includes items of an operator identifier, an operation start time, an operation identifier, an operation position, and an operation instruction. Of course, these items are examples, and other items may be selected and selected.

  In this way, each piece of information is created and stored in the storage unit 21 as shown in FIG.

  Next, a case where the user attribute A changing operation in (b) is performed will be described. FIG. 7 is an explanatory diagram of an example of information stored in the storage unit 21 after the operation (b) is performed. In S72 of FIG. 4, the operation identifier “5000001” and the current operation position “1” are extracted from the current operation position information 22. Since there is no operation after the current operation position, 1 is added to the current operation position in S75 to set the operation position to “2”. The current operation position of the current operation position information 22 shown in FIG. 7A is updated to “2”.

  Since it is a change operation, the process proceeds to S83, and the exclusive information 25 is created so that the document to be changed is not updated by another operator. However, the information identifier “ Since exclusive information 25 has already been created for the document “100111”, new exclusive information 25 is not created here.

  In S84, update information 24 indicating that a change operation has been performed on the document with the information identifier “100111” is generated. The generated update information 24 is shown with an arrow in FIG. Since the user attribute A has been changed, the changed attribute “A1” is stored in the user attribute A column.

  In S87, operation history information 23 indicating that the change operation has been performed is generated and stored in the storage unit 21. An example of the generated operation history information 23 is shown with an arrow in FIG. The operation position is “2” and the operation instruction is “change”.

  In this way, each piece of information is created and stored in the storage unit 21 as shown in FIG.

  Next, a case where a deletion operation for deleting one other document, which is the operation (c), is performed will be described. FIG. 8 is an explanatory diagram of an example of information stored in the storage unit 21 after the operation (c) is performed. In S72 of FIG. 4, the operation identifier “5000001” and the current operation position “2” are extracted from the current operation position information 22. Since there is no operation after the current operation position, 1 is added to the current operation position in S75 to set the operation position to “3”. The current operation position of the current operation position information 22 shown in FIG. 8A is updated to “3”.

  Since it is a deletion operation, the process proceeds to S85, and the exclusive information 25 is created so that the document to be deleted is not updated by another operator. As shown by an arrow in FIG. 8D, the document having the information identifier “100105” is associated with the operator 1 so that the folder and the document are not updated by an operator other than the operator 1.

  In S86, update information 24 is generated indicating that a deletion operation has been performed on the document having the information identifier “100105” and the folder having the information identification “100001” in which the document is arranged. The two pieces of generated update information 24 are indicated by arrows in FIG.

  Further, in S87, operation history information 23 indicating that the deletion operation has been performed is generated and stored in the storage unit 21. An example of the generated operation history information 23 is shown with an arrow in FIG. The operation position is “3” and the operation instruction is “delete”.

  In this way, each piece of information is created and stored in the storage unit 21 as shown in FIG. Note that the document with the information identifier “100105” to be deleted is not actually deleted here.

  The next operation (d) is to return the current operation position. In addition to the operation shown in FIG. 4, the operation position processing unit 18 changes the current operation position information 22 managed by the operation position management unit 11. Is done by doing. FIG. 9 is an explanatory diagram of an example of current operation position information stored in the storage unit 21 after the operation (d) is performed. Since the operation is returned after the operation of (c) is completed, the current operation position is changed to “2”. If the current operation position in the current operation position information 22 is changed in this way, the state after completion of any operation performed so far is restored. Note that information other than the current operation position information 22 is not changed.

  Next, a case where the user attribute B changing operation of (e) is performed will be described. FIG. 10 is an explanatory diagram of an example of information stored in the storage unit 21 after the operation (e) is performed. In S72 of FIG. 4, the operation identifier “5000001” and the current operation position “2” are extracted from the current operation position information 22. In this case, since the current operation position is returned by the operation (d), there is an operation after the current operation position. The re-operation from the current operation position is the first time. Therefore, in S74, “.1” is added to the current operation position, and since this is the first operation of the re-operation, “.1” is further added to set the operation position to “2.1.1”. The current operation position of the current operation position information 22 shown in FIG. 10A is updated to “2.1.1”.

  Since it is a change operation, the process proceeds to S83, and the exclusive information 25 is created so that the document to be changed is not updated by another operator. However, the information identifier “ Since exclusive information 25 has already been created for the document “100111”, new exclusive information 25 is not created here.

  In S84, update information 24 indicating that a change operation has been performed on the document with the information identifier “100111” is generated. The generated update information 24 is shown with an arrow in FIG. Since the user attribute B has been changed, the changed attribute “B1” is stored in the user attribute B column.

  In S87, operation history information 23 indicating that the change operation has been performed is generated and stored in the storage unit 21. An example of the generated operation history information 23 is shown with an arrow in FIG. The operation position is “2.1.1” and the operation instruction is “change”.

  In this way, each piece of information is created and stored in the storage unit 21 as shown in FIG. Thus, a series of operations from (a) to (e) is performed. In this way, the operation position is stored for each update operation, and search, display, and the like can be performed using information after each update operation. In addition, by continuously recording the update operation in the storage unit 21 in this manner, even if the apparatus is stopped, these pieces of information remain continuously. Therefore, the operation processing performed by the operator is limited by stopping the apparatus. There is nothing. Furthermore, the updating of the information being updated by others is prevented, so that the information being updated does not affect others.

  When the operator performs the above-described operation, the presentation processing unit 17 provides a state after the operation processing to the operator who is performing the operation, and also presents a history of operations performed so far. Further, an original state in which no operation process is performed is provided to an operator other than the operator who is performing the operation. An example of the process for that is shown below.

  FIG. 11 is a flowchart showing an example of the operation of the presentation process to the operator. In S <b> 91, the operation position management unit 11 determines using the current operation position information 22 whether the operator presenting the operation target information is instructing to start the operation. If the operation start instruction has not been received from the operator, the information management unit 13 presents the operation in a state where no operation processing is performed in S94. For example, when referring to information, the existing information management unit 15 reads the existing permanent information 26 (operation target information) and presents it to the operator from the presentation processing unit 17.

  When it is determined in S91 that the operation start instruction has already been performed, in S92, the operation position management unit 11 extracts the operation identifier and the current operation position corresponding to the operator from the current operation position information 22. .

  In S93, it is determined whether or not the current operation position is greater than zero. If the current operation position is 0, no operation has been performed yet, so in S94, presentation is performed in a state where no operation processing is performed through the information management unit 13.

  If the current operation position is greater than 0, some operation has been performed. In S95, the operation history management unit 12 determines the order of operations from the operation start to the current operation position based on the operation history information 23 having the operation identifier extracted in S92. The order of the calculated operation is set as the operation order. For example, when re-operation is performed from the middle, the order of operations from the start of operation to the current operation position varies depending on whether the current operation position is in the middle of the first operation or the re-operation. For example, when the operations (a) to (e) are performed, if the current operation position is “3”, the operation order is “1” → “2” → “3”, but the current operation position is If “2.1.1”, the order of operation is “1” → “2” → “2.1.1”.

  In S96, the update information 24 managed by the update management unit 14 is read according to the operation order determined in S95. If the operation content is registered or changed, the operation managed by the existing information management unit 15 is not performed. Operation processing is sequentially performed on the existing permanent information 26 (operation target information). In S97, information on the deleted operation target information is extracted even when the operation content is deletion.

  In S98, the existing information management unit 15 replaces the information that has been registered or changed in the existing permanent information 26 with the information obtained in S96, and the deleted information obtained in S97. Excluded from the presentation processing unit 17 to be presented to the operator. The operator refers to or retrieves information from the presentation target.

FIG. 12 is an explanatory diagram of another specific example of current operation position information, operation history information, update information, and exclusive information in an example of an operation of presentation processing to the operator, and FIG. 13 is a diagram of information presented to the operator. It is explanatory drawing of a specific example. Here, it is assumed that the current operation position information 22, operation history information 23, update information 24, and exclusive information 25 shown in FIG. That is, in this example, the case where the following series of operation processing is performed is shown.
(F) Register the document with the information identifier “100111” in the folder with the information identifier “100001” (g) Return the current operation position after performing the processing (f) after performing some operation processing (h) Information identifier An operation process for changing the user attribute A of the document “100105” to “A2” and the user attribute B to “B2” is performed. (I) After performing some operation process, the process of (h) is performed. (J) Delete the document with the information identifier “100100”. (K) Set the user attribute A of the document with the information identifier “100105” to “A12” and the user attribute B to “B12”. The operation process to be changed is performed. Note that FIG. 12 does not show each piece of information regarding the operation process in (g) and (i).

  If the current operation position is “1.1.1.1.2”, the process proceeds to S95 in FIG. 11 to determine the operation order. In this example, the operation order is “1” → “1.1.1” → “1.1.1.1.1” → “1.1.1.1.2”. Among these, the registration and change operation processes are “1”, “1.1.1”, and “1.1.1.1.2”. The deletion operation process is “1.1.1.1.1”. Therefore, the document with the information identifier “100111” is registered as the existing permanent information 26 in the folder with the information identifier “100001”, and the user attribute A and the user attribute B of the document with the information identifier “100105” are set to “A12”, respectively. The state is changed to “B12”, and a state in which the document with the information identifier “100100” is excluded is provided to the operator. As a result, for the operator, as shown in FIG. 13A, there is a document with the information identifier “100111” and a document with the information identifier “100105” in which the user attribute A and the user attribute B are changed. Will be provided.

  It should be noted that a state in which no operation process is performed is provided to an operator other than the operator who is performing the operation process. Therefore, as shown in FIG. 13B, there is no document with the information identifier “100111” registered by the operation process, there is a document with the information identifier “100111” deleted by the operation process, and the information identifier “100105”. Is provided in a state before the user attribute A and the user attribute B are changed. In this way, the state where the operation is performed is provided to the operator performing the operation process, and the state of the original existing permanent information 26 is provided to the other operators.

  When the operation process ends and the operation process up to that point is confirmed, the operator gives an instruction to complete the operation. FIG. 14 is a flowchart illustrating an example of the operation processing operation completion. In S <b> 101, the operation position management unit 11 determines whether or not the operator who presents the operation target information is instructing to start the operation, using the current operation position information 22. If the operation start instruction has not been received from the operator, the process ends without doing anything. Alternatively, error processing may be performed.

  If it is determined in S101 that the operation start instruction has already been performed, in S102, the operation position management unit 11 extracts the operation identifier and the current operation position corresponding to the operator from the current operation position information 22. .

  In S103, it is determined whether or not the current operation position is greater than zero. If the current operation position is 0, no operation has been performed yet. In this case, the current operation position information 22 managed by the operation position management unit 11 is deleted in S104, and the process ends.

  If the current operation position is greater than 0, some operation has been performed. In S105, the operation history management unit 12 calculates an operation order that is the order of operations from the operation start to the current operation position based on the operation history information 23 having the operation identifier extracted in S102. The operation order is as described above.

  In S106, the update information 24 managed by the update management unit 14 is read according to the operation order determined in S105. If the operation content is registered or changed, the operation managed by the existing information management unit 15 is not performed. Operation processing is sequentially performed on the existing permanent information 26 (operation target information) to generate final information. In S107, information on the deleted operation target information is extracted even when the operation content is deletion.

  In S108, the existing information management unit 15 replaces the operation target information registered and changed based on the information identifier in the existing permanent information 26 with the information generated in S106. Further, the corresponding information is deleted from the existing permanent information 26 based on the information identifier of the deleted information extracted in S107.

  In S109, the update management unit 14 extracts the operation target information that is the target of the update operation process from the update information 24 stored in the storage unit 21 in the series of operation processes based on the operation identifier. In S110, the existing information management unit 15 deletes the exclusive information 25 for the operation target information extracted in S109, and accepts updates from other operators.

  Furthermore, in S111, the operation history management unit 12 deletes the operation history information 23 stored in the storage unit 21 in a series of operation processes based on the operation identifier. In S112, the update management unit 14 deletes the update information 24 stored in the storage unit 21 in a series of operation processes based on the operation identifier.

  In step S104, the operation position management unit 11 deletes the current operation position information 22 based on the operation identifier and ends the process. In this way, the final state where the operation processing has been performed is reflected in the existing permanent information 26, and the current operation position information 22, the operation history information 23, the update information 24, which have been stored in the storage unit 21 so far, The exclusive information 25 is deleted, and the operation process is terminated.

  By performing the operation process for completing the operation, the previous operation process is reflected in the existing permanent information 26. This operation completion instruction may be given when the result desired by the operator is obtained, and therefore the result desired by the operator is reflected. As a result, an operation mistake or an inappropriate operation may be easily redone and corrected, so unnecessary recovery work does not occur, and a situation in which a previous result cannot be obtained due to a work mistake in the recovery work does not occur. On the contrary, until the operation completion instruction is given, the operation processing is not reflected in the existing persistence information 26, and the operation processing up to that time is recorded in the storage unit 21. However, operation processing may be performed from any stage until the desired result is obtained.

  Further, since information that is affected by the operation process is automatically controlled so that it cannot be updated by other operators, a troublesome operation for that purpose is unnecessary. Further, since the contents of the operation processing are concealed from other operators until an operation completion is instructed, the inconvenience information does not affect the other person's business.

  FIG. 14 illustrates an example of an operation when an operation instruction for completion of an operation is performed. However, there is a case where the user wants to withdraw without reflecting the operation processing after starting the operation processing and performing the operation processing. In such a case, the operator may instruct the operation withdrawal. FIG. 15 is a flowchart illustrating an example of the operation of the operation withdrawal operation. In S <b> 121, the operation position management unit 11 determines whether or not the operator who presents the operation target information is instructing to start the operation, using the current operation position information 22. If the operation start instruction has not been received from the operator, the process ends without doing anything. Alternatively, error processing may be performed.

  When it is determined in S121 that the operation start instruction has already been performed, in S122, the operation position management unit 11 extracts the operation identifier and the current operation position corresponding to the operator from the current operation position information 22. .

  In S123, based on the extracted operation identifier, the update management unit 14 extracts the operation target information that is the target of the update operation process from the update information 24 stored in the storage unit 21 in a series of operation processes. In S124, for the operation target information extracted in S123, the existing information management unit 15 deletes the exclusive information 25 and accepts an update from another operator.

  Further, in S125, the update management unit 14 deletes the update information 24 stored in the storage unit 21 in a series of operation processes based on the operation identifier. In S126, the operation history management unit 12 deletes the operation history information 23 stored in the storage unit 21 in a series of operation processes based on the operation identifier.

  In step S127, the operation position management unit 11 deletes the current operation position information 22 based on the operation identifier and ends the process. In this way, the operation process is terminated without reflecting the operation process performed so far.

  As described above, the operation position processing unit 18 has a function of receiving the designation of changing the current operation position and changing the current operation position information to the designated operation position. In order for the operator to change the current operation position, information related to the operation processing performed so far may be presented to the operator. Information related to the operation processing is presented to the operator through the presentation processing unit 17.

  FIG. 16 is a flowchart illustrating an example of an operation of presenting information regarding operation processing. First, in S131, the operation position management unit 11 determines using the current operation position information 22 whether or not the operator who has instructed the update operation has instructed the operation start. If the operation start instruction has not been received from the operator, error processing is performed in S136, and the process ends.

  If it is determined in S131 that the operation start instruction has already been performed, in S132, the operation position management unit 11 determines from the current operation position information 22 the operation identifier corresponding to the operator who has issued the update operation instruction. To extract.

  Here, as the information related to the operation processing, it is assumed that which operation target information is updated, or operation history information is presented. If it is determined in S133 which information is to be presented, and the operation target information that has been subjected to the update operation is presented, in S134, the update management unit 14 updates the update information 24 having the operation identifier extracted in S132. Based on the above, the operation target information that is the target of the update operation is specified and presented to the operator through the presentation processing unit 17. When presenting the operation history information, in S135, the operation history management unit 12 extracts the operation history information 23 based on the operation identifier and presents it to the operator. Of course, various information other than these information may be presented to the operator.

  When presenting the operation history information 23 to the operator in S135 described above, each operation history may be presented in a tree structure that branches by re-operation using a graphic corresponding to the operation process. FIG. 17 is an explanatory diagram illustrating an example of operation processing performed until the operation history information is presented to the operator, FIG. 18 is an explanatory diagram illustrating an example of the operation history information presented to the operator in a normal state, and FIG. This is a modified example. For example, consider a case where a series of operation processes shown in FIG. 17 are performed. In this example, first, a text document “AAA” is registered, the attribute of the document is changed, the contents are further changed seven times, the attribute is changed, and version management is started as a new version. The process returns to the end of the attribute change performed after registration of the document “AAA”, changes the content of the document “ABC” having a format different from that of the document “AAA”, and starts version management for this document as a new version. This time, after the document “AAA” is registered, the attribute and content of the document “AAA” are changed, and version management is started again as a new version. Here, returning to the new version, the attribute of the document “AAA” is changed, and version management is started as a new version. The document “AAA” is returned again after registration, and the content of the document “BBB” whose format is different from that of the document “AAA” is changed. However, the content of the document “CCC” is changed after returning to the registration of the document “AAA”. Yes. Furthermore, after the document “AAA” is registered, the content of the document “DDD” is changed, the content of the document “EEE” is changed, and then the content of the document “FFF” is changed. Documents “CCC”, “DDD”, “EEE”, and “FFF” are also different in format from document “AAA”.

  In FIG. 17, each operation process is indicated by a rectangle. For each of these processes, the documents “AAA”, “ABC”, “BBB”, “CCC”, “DDD”, which are operation target information, If “EEE” and “FFF” are expressed in a graphic form, it is as shown in FIG. Here, figures are used according to the format of each document.

  Further, FIG. 19 shows an example in which each operation process, that is, each operation process of registration, attribute change, content change, and version management start is added as a figure. Since the operation history information 23 is presented in such an expression, the operator can grasp the operation processing that has been performed and specify the operation position to be returned if the operation is to be performed again.

  When such operation history information 23 is presented, there is a concern that if a similar operation is performed many times in succession, the branches of the tree structure become longer by that number of times and the listability becomes worse. The Moreover, when there are many branches in the tree structure, there is a concern that it is difficult to find a target operation process. Furthermore, when there is a branch in the tree structure due to re-operation, it is necessary to go to each operation of the subsequent branch to examine what kind of difference has occurred after that branch. is there. Furthermore, in order to confirm the details of each operation process, it is necessary to follow the update from the initial state, but it is inconvenient to check one by one from the beginning. The functions for solving these problems that are concerned are described below.

First, the problem that a tree-structured branch becomes long due to a large number of operation processes is dealt with by a simplification process that simplifies all the similar operation processes out of successive operation processes. In this simplification process, based on the operation history information 23, a series of operation processes that are continuous without branching and that meet any of the predetermined conditions are found and simplified. To express. Here, as an example, the following conditions are set.
Condition 1. Condition in which different operation processing is continuously performed for certain operation target information. A certain operation process is performed continuously on different operation target information.

  In the case of condition 1, only one figure indicating the operation target information is displayed, and a plurality of figures indicating the operation processing added to the figure are displayed. In the case of condition 2, only one figure indicating the operation process is displayed, and a plurality of figures indicating the operation target information are displayed.

  FIG. 20 is an explanatory diagram of an example of operation history information presented in a simplified form to the operator. For example, the operation history information shown in FIG. 19 is simplified as shown in FIG. In other words, since the operation process with the operation position information from “3” to “11” is a process for the document “AAA”, the graphic indicating the document “AAA” is set to one, and nine operations corresponding to each operation process are performed. A figure is added. Note that the operation target information with the operation positions “1” and “2” is also the document “AAA”. However, since the operation is performed again at these operation positions and branches in the tree structure are branched, these operations are performed. The processing is not summarized.

  Further, in FIG. 20, since the operation processing with the operation position information “2.1.1” and “2.1.2” is processing for the document “ABC”, the figure indicating the document “ABC” is made one. Two figures corresponding to each operation process are added. In addition, since the operation processing with the operation position information “1.1.2.1.1” and “1.1.2.1.2” is processing for the document “AAA”, the graphic indicating the document “AAA”. And two figures corresponding to each operation process are added.

  In addition, the operation processes with the operation position information from “1.4.1” to “1.4.3” are processes for different documents, but all of them are operation processes for changing the contents. The figure corresponding to the operation processing to be performed is made one, and three figures indicating the documents “DDD”, “EEE”, and “FFF” as the operation target information are presented side by side.

  By performing the simplification process in this way, the operation history information is simplified and presented to the operator as shown in FIG. The operator may simply look down on the operation processing performed and select a desired operation processing.

  21 and 22 are flowcharts showing an example of the operation history information simplification process. In the simplification process shown in FIG. 21, the target set that holds the operation history information to be collected, the branch set that holds the operation history information to be branched, and the operation target information are different when the operation history information is put together. A reduction type is used for work indicating whether the operation processes are grouped (“operation object”) or whether different operation object information is grouped by combining a single common operation process (“operation contents”).

  In S141, the history of the first operation process of the operation history information 23, that is, the history of the operation process whose operation position information is “1” is set as a target element. In step S142, the target element is added to the target set for work.

  In S143, it is determined whether there is a history of the next operation process and whether or not a branch has occurred. If the next operation processing history exists and there is no branch, in S144, it is determined whether or not the work reduction type is set, and if it is set, the process proceeds to S148. If it is not set, the difference from the history of the next operation processing is further examined in S145. If the operation target information is common and the operation processing is different, in S146, “operation target” is set as the work reduction type. If the operation processing is common and the operation target information is different, “operation content” is set as the work reduction type in S147. If the operation target information is different from the operation process, the process directly proceeds to S148.

  In S148, it is determined whether or not the history of the next operation process matches the content set in the reduction type. That is, when “operation object” is set as the reduction type, it is determined whether or not the history of the next operation process and the operation object information are common. When “operation content” is set as the reduction type, it is determined whether the history of the next operation process is common to the operation process.

  If it is determined in S148 that the history of the next operation process matches the content set in the reduction type, the history of the next operation process is added to the target set in S149, and the process returns to S143. By repeating this process, the history of operation processes that are not branched and have the same operation target information or the same operation process are collected into a target set.

  If the history of the next operation process does not match the content set in the reduction type in S148, that is, if the reduction type is “operation target” and the operation target information of the next operation process history is different, or When the operation process of the next operation process is different for the type “operation content”, the process proceeds to S151 without adding to the target set. If it is determined in S143 that there is a branch or if there is no history of the next operation process, the branch from the target element in S150, that is, the history of the operation process when re-operation is performed is a branch set. And go to S151.

  In S151, the operation processing history added to the target set is simplified according to the reduction type and presented to the operator. Details of this processing are shown in FIG. In S161, the reduction type setting is determined. When the reduction type is “operation content”, in S162, one graphic showing the common operation processing is included in the operation processing history included in the operation set, and in S163, the operation processing history included in the operation set. As shown, the figures indicating the respective pieces of operation target information are arranged side by side for the number of operation processing histories. When the reduction type is “operation target”, in S164, the operation processing histories included in the operation set are arranged by the number of the operation processing histories for each operation processing history, and in S165, the operation processing history is displayed. One graphic showing the operation target information common to the history of operation processing included in the set is presented. Further, when no reduction type is set, in S166, one figure indicating the operation process corresponding to the operation process history included in the operation set is set, and in S167, the operation process history included in the operation set. One figure indicating the operation target information corresponding to is presented.

  Returning to FIG. 21, in S152, the history of operation processing in the operation set is deleted, and the setting of the reduction type is canceled. In S153, it is determined whether or not there is a history of the next operation process. If there is, the process returns to S142 with the history of the next operation process as the target element in S154. In this way, the process proceeds for one branch of the tree structure.

  When the history of the next operation process does not exist in S153 and the process proceeds to the tip of one branch of the tree structure, it is determined in S155 whether or not the branch set is empty. If the branch set is not empty, a re-operation is performed from an intermediate operation process, and an unprocessed operation process history exists. Therefore, in S156, the history of the operation process last added to the branch set is taken out as a target element, and the process returns to S142 to process the tree structure branch from the target element. If it is determined in S155 that the branch set is empty, the process ends. In this way, a history of operation processing common or a history of common operation target information is collected, and a simplified and easy-to-read operation processing history is presented to the operator.

  Next, if there are many branches in the tree structure, the problem that it is difficult to find the target operation process is handled by a filtering process that specifies the refinement condition and eliminates the presentation of unnecessary branches in the tree structure. To do. In this filter processing, the operation processing history that is the starting point in the presented operation processing history is selected, and the narrowing-down conditions are specified. Each branch that branches off from the starting point is set as a lump, and the lump of branches that do not satisfy the narrowing condition is omitted.

  For example, in the tree structure of the operation process history shown in FIG. 17, when the operation process history with the operation position “1” is the starting point, the operation positions are “2” to “11” and “2.1.1”. , “2.1.2” operation processing history forms one lump. In addition, operation history of operation positions “1.1.1” to “1.1.3”, “1.1.2.1.1”, and “1.1.2.1.2” It becomes one lump. Further, the history of the operation processes with the operation positions “1.2.1” and “1.3.1” are each one set. Furthermore, the history of the operation processing with the operation position from “1.4.1” to “1.4.3” is also one lump. It is determined whether or not a narrowing condition is satisfied for each mass. In addition, when there is no mass satisfying the narrowing-down condition, the history of operation processing after the starting point is not presented.

  FIG. 23 is an explanatory diagram showing an example of a setting screen presented to the operator for specifying the filter process. For example, in the state where the operation history information is presented as shown in FIG. 20, here, the operation processing history with the operation position “1” is designated, and “Filter designation” is selected from the menu displayed at that time. In this case, the filtering process is performed. After this “filter specification” is selected, a narrowing condition is set in the “filter condition specification” frame. Here, a narrowing-down condition that “document format” is “text” is set. If the operator operates the button labeled “Filter execution”, the filter process is executed.

  FIG. 24 is an explanatory diagram of an example of operation history information that has been subjected to filter processing and presented to the operator. If the “document format” of the document “AAA” in FIG. 20 or FIG. 19 is “text” and the document formats of other documents are different, the operation position among the branches branched from the operation position “1”. The branch starting from “2” and the branch starting from the operation position “1.1.1” satisfy the narrowing condition. Accordingly, presentation of the branches starting from the operation positions “1.2.1”, “1.3.1”, and “1.4.1” is omitted, and the operation history information shown in FIG. It will be presented to the person. As for the operation processing history of the operation positions “2.1.1” and “2.1.2”, the document format of the operation target information in the operation processing history of the operation position “2” before branching is narrowed down. It will be presented because it satisfies the conditions.

  With the operation history information shown in FIG. 24A being presented to the operator, the operation processing history at the operation position “2” is designated, “Filter designation” is selected, and “Filter condition designation” is selected. As shown in FIG. 23, when the filtering process is executed by setting a narrowing condition that “document format” is “text”, the operation history information shown in FIG. 24B is presented to the operator. In this case, presentation of the branch starting from the operation position “2.1.1” is omitted. By omitting this branch, the operation processing history from the operation position “2” to “11” has no branch in the presented range. Therefore, the operation processing history of the operation position “2” by the above-described simplification processing. Is also presented together.

  In this specific example, the condition that “document format” is “text” is exemplified as a narrowing condition, but it goes without saying that the present invention is not limited to this example, and various conditions may be set.

  FIG. 25 is a flowchart illustrating an example of filtering processing for operation history information. As described above, when a history of operation processing as a starting point is specified, and further, a narrowing condition is specified and execution of filter processing is instructed, the filter processing is performed by the processing shown in FIG. 25, for example.

  First, in S171, operation history information presented to the operator is stored as presentation management information.

  In S172, one of the branches branched from the starting point (operation processing history) is selected. In S173, the subsequent operation processing history is stored as branch management information. In S174, it is determined whether or not there is an unprocessed branch with respect to the branch branched from the starting point. If there is an unprocessed branch, the process returns to S172 and the unprocessed branch is processed. As a result, the history of operation processing for each branch is stored as branch management information.

  After the operation processing history of each branch is stored in the branch management information, in S175, one of the branches branched from the starting point stored in the branch management information is selected. Then, in S176, it is determined whether or not the history of operation processing for the selected branch satisfies the narrowing-down condition. If the narrowing condition is satisfied, the process proceeds to S178 as it is. If the narrowing condition is not satisfied, the operation processing history of the branch selected in S175 is stored as deletion information in S177. In S178, it is determined whether or not there is an unprocessed branch for the branch stored in the branch management information. If there is an unprocessed branch, the process returns to S175 to perform processing for the unprocessed branch. Do. As a result, the history of branch operation processing that does not satisfy the narrow-down condition is saved as deletion information.

  In S179, the history of the operation process saved as the deletion information is deleted from the presentation management information. In S180, the presentation management information is presented to the operator. When presenting, the above simplification process may be performed. In this way, the branch of the tree structure that does not satisfy the narrowing condition is omitted, and the operation history information is presented. Therefore, the user can easily find the history of the desired operation processing.

  Next, in order to check the details of each operation process and improve the operability when following the update, an operation that presents the difference between the selected operation process result and the previous operation process result A function for content presentation processing is provided. As the operation content presentation process, the operation content related to one operation process is presented, and the operation content performed by a series of a plurality of operation processes is also presented.

  FIG. 26 is an explanatory diagram of an example of a setting screen presented to the operator for designating the operation content presentation process. For example, in the state where the operation history information is presented as shown in FIG. 24 (B), here, the graphic of the operation processing history from “2” to “11” is presented in a simplified manner. If the user designates and selects “display operation details” from the menu displayed at that time, the operation content presentation processing for the operation position “11” is performed.

  FIG. 27 is an explanatory diagram of an example of information presented to the operator by the operation content presentation process. By performing the operation content presentation process as described above, for example, the information shown in FIG. 27 is presented to the operator. In this example, the contents of the operation process at the operation position “11” are presented. Since the operation process at the operation position “11” is a process for starting version management as a new version, “start version management” is displayed as the operation content.

  Here, the operation content is presented assuming that the operation position “11” is selected. However, for example, if a graphic corresponding to the operation processing presented in a simplified manner is selected, the operation content at the corresponding operation position is presented. Is done.

  FIG. 28 is an explanatory diagram of another example of information presented to the operator through the operation content presentation process. When the portion indicated as “cumulative operation content display” in the information presented by the operation content presentation process in FIG. 27 is selected or “operation content display (cumulative)” is selected from the menu shown in FIG. In this example, after the operation process at the operation position “1” is completed, the operation content indicating how the operation process performed from the operation position “2” to “11” has been changed is presented. In the example shown in FIG. 28, in addition to the change of the attribute names “UserE1” and “UserE2” in the example shown in FIG. 27, the attribute names “UserA”, “UserB”, and “file name” are changed.

  For example, the attribute is changed by the operation process of the operation position “2” and the operation position “10”. However, the attribute changed by the operation process of the operation position “2” is further changed by the operation process of the operation position “10”. If changed, the changed value becomes effective later. Of course, in other operation processes such as content change, if the operation process is overwritten or duplicated, the result of the operation process performed later becomes valid.

  Further, in this example, the series of operation processes simplified by the simplification process is set as the range of the operation process that presents the accumulated operation contents. However, the present invention is not limited to this, and two operation processes are arbitrarily selected. Then, the operation processing performed during that time may be collected and the operation content may be presented.

  By presenting such cumulative operation content, even if the attribute value or content has been changed many times, the final result is presented, making it easier to understand what will happen in the end. .

  FIG. 29 is a flowchart illustrating an example of the operation content presentation process. Since the process of presenting the operation content in the individual operation process may refer to the update information 24 corresponding to the operation process, the process for presenting the accumulated operation content will be described here. In the following description, it is assumed that an operation process serving as a start point and an end point indicating a range in which operation contents are collected is designated.

  First, in S191, the update information 24 corresponding to the operation processing within the range to be collected is acquired and added to the cumulative information for work.

  In S192, one piece of update information added to the accumulation target information is taken out in the reverse order of the operation processing. In S193, it is determined whether or not the information identifier in the extracted update information exists in the temporary storage information for work. If not, the information identifier is added to the temporary storage information for work in S194. When it exists, it progresses to S195 as it is.

  In S195, it is determined whether or not unprocessed update information remains in the accumulation target information. If it remains, the process returns to S192 to repeat the process. If unprocessed update information does not remain in the accumulation target information, the process proceeds to S196.

  Through the repeated processing so far, the information identifier indicating the operation target information used within the range to be collected is added to the temporary storage information for work. In S196, the difference between the temporary storage information for work and the state immediately before the range to be collected is extracted and presented. As a result, the difference due to the update is extracted for each piece of operation target information used within the range to be collected. In the specific example shown in FIG. 28 described above, the operation target information is common to the document “AAA”. However, even if an operation process related to another operation target information is included in the range to be collected, Differences will also be presented.

  Next, a branch information presentation process is provided in order to examine what difference occurs before and after the branching of the tree structure due to re-operation. In this branch information presentation process, when a re-operation is performed and a tree-structure branch occurs, the operation process that is performed in common for the branch before the branch and each branch after the branch is extracted, and the extracted operation An operation process different from the process is presented as a difference. Each branch before and after the branching is a cluster as a unit in the above-described filter processing.

  The common part is managed as a set for each operation processing content and a set for each operation target information. The difference from the common part confirms whether or not the operation content and the operation target information in each operation process are included in the common part. If the operation content is not included, the operation target information is not included, or both are not included, it is extracted as difference information. The difference information uses a figure indicating the contents of the operation process and a figure indicating the operation target information, and is adjacent to a line connecting the selected operation process history and the immediately subsequent operation process history. Present.

  FIG. 30 is an explanatory diagram illustrating an example of a setting screen presented to the operator for designating the branch information presentation process. For example, in the state where the operation history information is presented as shown in FIG. 24B, the operation processing history of the operation positions “1.1.1” and “1.1.2” is simplified here. If the figure that is presented is specified and “Branch information display” is selected from the menu that is displayed at that time, the operation position “1.1.2” at which the branch occurs is set as the starting point. Branch information presentation processing for presenting the difference is performed.

  FIG. 31 is an explanatory diagram of an example of information presented to the operator by the branch information presentation process. By specifying the starting point and performing the operation content presentation process as described above, for example, the information shown in FIG. 31 is presented to the operator. In this example, the operation processing common to the two branches at the branch after the operation position “1.1.2” is that the operation content is “version management start” and the operation target information is the document “AAA”. There is. The operation process after the operation position “1.1.2.1.1” after the re-operation includes “attribute editing” which is not included in the common operation. For this reason, a graphic showing the operation processing of “attribute editing” is presented between the operation position “1.1.2” and the operation position “1.1.2.1.1”. It should be noted that since there are no branches after the operation position “1.1.3” that are not included in the common operation, nothing is presented as a difference.

  By presenting the differences between the branches that branch in this way, the difference between the branches can be expressed in a concise manner, and the operator can determine which branch to look at in detail.

  FIG. 32 is a flowchart illustrating an example of branch information presentation processing. When a history having a branch after the operation process is designated as the starting point and execution of the branch information presentation process is instructed, the process shown in FIG. 32 is performed.

  First, the contents of the operation process and the operation target information that are performed in each branched branch are extracted by the processes from S201 to S204. That is, in S201, one of the operation processes immediately after branching is set as a processing target, and in S202, operation history information 23 and update information 24 of all the operation processes connected to the processing target are acquired. In step S203, the operation contents and operation target information in each operation process are extracted from the operation history information 23 and the update information 24 of the acquired operation process and stored. As a result, for one branch, the contents of the operation process performed in the operation process in that branch and the operation target information targeted for the operation process are extracted. In S204, it is determined whether or not there is an unprocessed operation process immediately after branching. If there is an unprocessed operation process, the process returns to S201 to perform the process for the operation process.

  When there is no unprocessed operation processing immediately after branching, in S205, one or more operation target information that exists in common in each branch is found based on the operation target information extracted for each branch. To be a common operation target. In S206, based on the contents of the operation process extracted for each branch, the contents of one or more operation processes existing in common in each branch are found and set as the common operation contents.

  In S207 to S211, the difference in each branch is extracted. That is, in S207, one of the operation processes immediately after branching is set as a processing target, and in S208, the operation history information 23 and update information 24 of all the operation processes connected to the processing target are acquired. In step S209, the operation target information of each operation process is found that is not included in the common operation target. In S210, the operation contents of each operation process that are not included in the common operation contents are found. These are the differences between the operation target information and the operation content in the processing target branch. In S211, it is determined whether or not there is an unprocessed operation process immediately after branching. If there is an unprocessed operation process, the process returns to S207 to perform the process for the operation process. By repeating this, the difference between the operation target information and the operation content in each branch is obtained.

  In S212 to S215, a difference is presented. That is, in S212, one of the operation processes immediately after branching is set as a processing target, in S213, a graphic corresponding to the difference in the operation target information is presented, and in S214, a graphic corresponding to the difference in the operation content is presented. To do. Thereby, the difference regarding the branch to be processed was presented. In S215, it is determined whether there is an unprocessed operation process immediately after branching. If there is an unprocessed operation process, the process returns to S212 to perform the process for the operation process. By repeating this, the difference in each branch is presented.

  In this way, through the simplification process, the filter process, the operation content display process, the branch information display process, or various other processes, the operation process history that is easy to see for the operator and easy to find the desired prime operation is presented. Do. For example, the operator may identify the operation process to be re-executed, specify the change of the current operation position, and redo the operation process while referring to the presented operation process history.

  FIG. 33 is an explanatory diagram of an example of a computer program, a storage medium storing the computer program, and a computer when the functions of one embodiment of the present invention are implemented by a computer program. In the figure, 31 is a program, 32 is a computer, 41 is a magneto-optical disk, 42 is an optical disk, 43 is a magnetic disk, 44 is a memory, 51 is a CPU, 52 is an internal memory, 53 is an information reading unit, 54 is a hard disk, 55 Is an interface, and 56 is a communication unit.

  A part or all of the functions described in the above-described embodiment may be realized by a program 31 that can be executed by a computer. In this case, the program 31 and data used by the program may be stored in a computer-readable storage medium. Of course, some functions may be configured by hardware, or all may be configured by hardware. The storage medium for storing the program 31 causes the information reading unit 53 provided in the hardware resource of the computer to cause a change state of energy such as magnetism, light, electricity, etc. according to the description content of the program. The description content of the program can be transmitted to the information reading unit 53 in the signal format corresponding thereto. For example, there are a magneto-optical disk 41, an optical disk 42 (including a CD and a DVD), a magnetic disk 43, a memory 44 (including an IC card and a memory card), and the like. Of course, these storage media are not limited to portable types.

  The program 31 is stored in these storage media, and the program 31 is read from the computer and stored in the internal memory 52 or the hard disk 54, for example, by mounting these storage media on the information reading unit 53 or the interface 55 of the computer 32. And what is necessary is just to implement | achieve a part or all of the function demonstrated as one Embodiment of this invention by executing the program 31 by CPU51. Alternatively, the program 31 is transferred to the computer 32 via a network or the like, and the computer 32 receives the program 31 by the communication unit 56 and stores it in the internal memory 52 or the hard disk 54, and the CPU 31 executes the program 31. May be. Alternatively, it may be realized by mounting a memory such as a ROM in which the program 31 is written in advance.

  In addition, various devices may be connected to the computer 32 via the interface 55. Of course, it goes without saying that it may be integrated with a program for realizing other functions.

  For example, the configuration shown in FIG. 1 can be realized by a plurality of computers connected by a network. For example, the storage unit 21 may be configured as one or a plurality of database servers, and the other part may be configured as a management server. The functions may be arbitrarily divided and allocated to a plurality of computers, and configured on a distributed processing system.

It is a block diagram which shows one Embodiment of this invention. It is a flowchart which shows an example of operation | movement when operation start instruction | indication is performed. It is explanatory drawing of an example of the present operation position information produced | generated by the instruction | indication of operation start. It is a flowchart which shows an example of operation | movement when update operation is instruct | indicated. It is explanatory drawing of an example of the update operation which the operator performed. It is explanatory drawing of an example of the information stored in the memory | storage part 21 after performing operation (a). It is explanatory drawing of an example of the information stored in the memory | storage part 21 after performing operation (b). It is explanatory drawing of an example of the information stored in the memory | storage part 21 after performing operation (c). It is explanatory drawing of an example of the present operation position information stored in the memory | storage part 21 after performing operation (d). It is explanatory drawing of an example of the information stored in the memory | storage part 21 after performing operation (e). It is a flowchart which shows an example of operation | movement of the presentation process to an operator. It is explanatory drawing of another specific example of the present operation position information in the example of operation | movement of a presentation process to an operator, operation history information, update information, and exclusive information. It is explanatory drawing of the specific example of the information shown to an operator. It is a flowchart which shows an example of operation | movement of the operation process of operation completion. It is a flowchart which shows an example of operation | movement of the operation process of operation withdrawal. It is a flowchart which shows an example of the operation | movement which presents the information regarding an operation process. It is explanatory drawing of an example of the operation process performed until operation history information is shown to an operator. It is explanatory drawing of an example of the operation history information shown to the operator in the normal state. It is explanatory drawing of the modification of the operation history information shown to the operator in the normal state. It is explanatory drawing of an example of the operation history information which simplified and showed the figure to the operator. It is a flowchart which shows an example of the simplification process of operation history information. It is a flowchart which shows the partial detailed process in an example of the simplification process of operation history information. It is explanatory drawing of an example of the setting screen shown to an operator in order to designate a filter process. It is explanatory drawing of an example of the operation history information which gave the operator the filter process. It is a flowchart which shows an example of the filter process with respect to operation history information. It is explanatory drawing of an example of the setting screen shown to an operator in order to designate operation content presentation processing. It is explanatory drawing of an example of the information shown to the operator by operation content presentation processing. It is explanatory drawing of another example of the information shown to the operator by operation content presentation processing. It is a flowchart which shows an example of operation content presentation processing. It is explanatory drawing of an example of the setting screen shown to an operator in order to designate a branch information presentation process. It is explanatory drawing of an example of the information shown to the operator by branch information presentation processing. It is a flowchart which shows an example of a branch information presentation process. FIG. 2 is an explanatory diagram of an example of a computer program, a storage medium storing the computer program, and a computer when the function of the embodiment of the present invention is realized by a computer program.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 11 ... Operation position management part, 12 ... Operation history management part, 13 ... Information management part, 14 ... Update management part, 15 ... Existing information management part, 16 ... Operation processing part, 17 ... Presentation processing part, 18 ... Operation position process , 21 ... Storage unit, 22 ... Current operation position information, 23 ... Operation history information, 24 ... Update information, 25 ... Exclusive information, 26 ... Existing permanent information, 31 ... Program, 32 ... Computer, 41 ... Magneto-optical disk 42 ... Optical disk 43 ... Magnetic disk 44 ... Memory 51 ... CPU 52 ... Internal memory 53 ... Information reading unit 54 ... Hard disk 55 ... Interface 56 ... Communication unit

Claims (9)

  History management means for managing the history of operation processing including operation position information indicating the position of the operation processing performed for a series of operation processing from the start of operation, and which operation processing is to be performed in the state after the operation processing is completed The operation position management means for managing the current operation position of the operation processing indicating current operation position information, and the position where the operation processing performed so far has been completed based on the history of the operation processing managed by the history management means The operation position processing means for changing the current operation position information managed by the operation position management means in response to the designation of the change of the current operation position specified arbitrarily, and the current operation position indicated by the current operation position information If the operation process is performed after the current operation position, the number of re-operations and the order of operations in the retry are displayed in the current operation position. In addition, the computer functions as an information operation processing unit that generates operation position information and performs an operation process, and an information management unit that manages operation target information that is an operation target and information related to updates to the operation target information. A characteristic information processing program.   The information management means rejects an update instruction from an operator other than the operator who has instructed the operation process with respect to the operation target information that is an object of the operation process by the information operation processing means. 1. An information processing program according to 1.   The information management means provides a state in which an operation other than the operator who has instructed the operation processing is not performed on the operation target information that is the target of the operation processing by the information operation processing means. The information processing program according to claim 1.   When receiving the operation completion instruction, the information operation processing means reflects the operation processing up to the instruction to the operation target information managed by the information management means, and The information processing program according to any one of claims 1 to 3, wherein the history is deleted.   Furthermore, the computer is caused to function as a presentation unit that presents a history of operations performed so far, which is managed by the history management unit, to an operator who designates a change in the current operation position. The information processing program according to any one of claims 1 to 4.   The information processing program according to claim 5, wherein the presenting unit presents a graphic corresponding to each operation.   The information processing program according to claim 6, wherein the presenting unit presents a figure corresponding to the plurality of operations in parallel when a plurality of operations are performed from a certain operation position.   The information processing program according to claim 6, wherein the presenting unit presents a graphic in which some of a plurality of operations are collected.   History management means for managing the history of operation processing including operation position information indicating the position of the operation processing performed for a series of operation processing from the start of operation, and which operation processing is to be performed in the state after the operation processing is completed The operation position management means for managing the current operation position of the operation processing indicating current operation position information, and the position where the operation processing performed so far has been completed based on the history of the operation processing managed by the history management means The operation position processing means for changing the current operation position information managed by the operation position management means in response to the designation of the change of the current operation position specified arbitrarily, and the current operation position indicated by the current operation position information If the operation process is performed after the current operation position, the number of re-operations and the order of operations in the retry are displayed in the current operation position. And information operation processing means for generating operation position information to perform operation processing, and information management means for managing operation target information to be operated and information related to updates to the operation target information. Information processing device.

Images