JP3085016B2 - Method and apparatus for operating shared data model - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and an apparatus for operating a shared data model, and more particularly, to a method for storing a plurality of data and a data model representing a relationship between the data in a shared storage area, and real-time processing of the data model. When performing operations on a shared data model in a collaborative work system that performs collaborative work, personally operate the shared data model by trial and error without disturbing the work of other collaborators And a method and apparatus for operating a shared data model that enables to perform

[0002]

2. Description of the Related Art Conventionally, in a collaborative work system in which a plurality of data and a data model expressing a relation between the data are stored in a shared storage area, and the data model is collaboratively operated in real time, The method of operating the system in the case of performing the operation by using a shared data model depends on the timing of reflecting the operation result on the shared data model and the timing of incorporating the change of the shared data model into each workstation. These are classified into two types.

(A) Synchronous system An operation on a shared data model from a workstation is immediately reflected in a shared data model held in a common storage area. In addition, the change is immediately notified to each other workstation connected via the network, and the display on the workstation is changed to maintain consistency with the shared data model.

In such a synchronous system, all operations performed by the user are reflected in real time in a shared data model on a common storage area, and further reflected in a view of another collaborator. For this reason, it is difficult for each user to attempt an operation involving a change in the data model as a personal operation without affecting other collaborators.

(B) Asynchronous system This is a system that operates the shared data model locally without affecting the shared data model and the view of the co-worker. The method of implementing the system differs depending on the timing at which the operation performed on the shared data model performed locally is reflected on the shared data model.

For example, the collaborative work system described in Japanese Patent Application Laid-Open No. 2-2450, entitled "Expression of Collaborative Multi-User Activity on Shared Structured Data Objects in a Networked Workstation Environment," cooperates with one shared book. Work on shared data in a multipart publication called (SharedBook). In this SharedBook, when editing data, the user explicitly acquires a lock to obtain the right to operate the shared data, and then copies the shared data to the user's workstation. Perform the operation.

[0007] The result of the data operation can be stored or rejected in the shared data. However, during this time, the lock mechanism prevents other collaborators from accessing this data. Although this method provides a method of virtually operating data on a local workstation, it must explicitly lock before operating data, and imposes an annoying operation called locking on the user. And interfere with the work of others. In addition, since there is no concept of a data model, the virtual operation is applied only to a specific piece of data.

As a system that solves the problem of the lock mechanism, for example, a knowledge management system (Knowledge Management System) of Ellis Yoda et al.
m; KMS). In the KMS system, by introducing a mechanism called "optimistic parallel control", a plurality of users can operate the data model without locking the same data. In an asynchronous system, there is a possibility that another user may change the same data while the user is working. In such a case, in the KMS system, when the data is saved, if the data has already been changed, that fact is notified, and the change is not accepted. However, there is a mechanism in which the contents of changes made by the user are temporarily stored in a local workstation, and the contents of changes are stored for the latest data.

However, in the KMS system, the unit of the data model handled by the user is fixed to a unit called a frame. Therefore, the unit of editing / storing is also fixed to the unit of a frame. On the other hand, you cannot selectively edit / save. For this reason, when saving data, even if a change has been made immediately before by another person, the data is replaced for each frame, and it is not possible to save data utilizing the change made by another person.

(C) Mixed system The gIBIS system according to the following document [2] or the rIBIS system according to the document [3] is a mixed system of the synchronous / asynchronous type. Transitions can be made easily. Synchronous mode (rIB
IS), the editing process of data is reflected in real-time to the shared data and the view of others, whereas in the asynchronous type (gIBIS), editing of data is performed locally without affecting other people, and editing is performed. After completion, the result can be reflected in the shared data. In this example, it can be said that the virtual operation in the synchronous system is realized by the transition between the modes. However, in the gIBIS system, only the text content of specific data can be locally edited, and operations involving changes in the data model structure, such as addition, deletion, and movement of new data, cannot be performed locally. In the asynchronous mode, since the virtual operation is applied to all data, it is not possible to perform the virtual operation only on a specific part of data at a certain time.

<Prior art documents> Reference [1] Elise Yoder, Robert Akscyn, Donald McCr
acken: “Collabolation in KMS, A Shared Hypermedi
a System ", CHI'89 Proceedings, May 1989, pp. 37-42 Reference [2] Conklin J. and Begeman ML:" gIBIS:
A Hypertext Tool for Exploratory Policy Discussio
n ", ACM Transactions on Office InformationSystems,
vol.6 no.4, 1988, pp.303-331 Reference [3] Rein, GL and Ellis, CA: "rIBIS: a
real-time group hypertext system ", International J
ournal of Man-Machine Studies, vol. 34 no.3 (199
1), pp. 349-368

[0012]

As described above, the concept of virtual operation does not exist in the conventional synchronous system. Even in an asynchronous system capable of virtual operation, an operation such as a lock operation or a transition between modes must be additionally performed, thereby forcing a user to perform an additional operation. Furthermore, the target of the virtual operation is limited to a limited operation such as text editing, and an operation that changes the structure of the data model cannot be performed. Further, the operation on the data is fixed to a specific unit, and there is a problem that the user cannot freely select the data.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object of the present invention is to reduce a user's additional work in a synchronous type cooperative work system, and to reduce the number of cooperative workers. It is an object of the present invention to provide a method and apparatus for operating a shared data model that enables a trial and error operation to be performed on an arbitrary shared data model and its structure by a method that does not cause interference or interference between the models.

[0014]

In order to achieve the above object, a method of operating a shared data model according to a first feature of the present invention is to provide a data model expressing a plurality of data and a relation between the data. A method of operating a shared data model in a collaborative work system that stores in a shared storage area and performs a joint work on a data model in real time, comprising: Generate a virtual data model by temporarily transcribing a part, perform an operation on the generated virtual data model, hold the operation performed on the virtual data model as an operation sequence, and selectively operate the operation sequence. It is characterized in that it is reflected in the operation of the shared data model.

According to a second aspect of the present invention, there is provided a method for operating a shared data model, wherein a plurality of data and a data model expressing a relation between the data are stored in a shared storage area, and the data model is collaborated in real time. A method of operating a shared data model when performing an operation on a shared data model in a collaborative work system for performing work, wherein at least a part of the shared data model displayed in a view is temporarily transcribed to virtual data. Generate a model, display the generated virtual data model in another view, perform operations on the virtual data model displayed in another view, hold the operations performed on the virtual data model as an operation series, The operation sequence is selectively reflected in the data operation of the shared data model.

A shared data model operating device according to a third aspect of the present invention is a shared data model holding a data model expressing a plurality of data and a relation between the data so that the plurality of workstations can commonly access the network via a network. Storage means (14), display means (5, 6) for displaying the data model on the display screen of the workstation, and operation means (5, 1) for operating the displayed data model
9) and management means (11, 11) for reflecting the result of the operation in real time to the data model stored in the shared storage means and notifying each workstation of the change of the data model.
18), a virtual data model generating means (8) for transcribing the data model held in the shared storage means and generating a virtual data model on a workstation, and a control for displaying the generated virtual data model in a virtual view And a virtual data model operating means (10) for operating the virtual data model via the virtual view and attempting an operation on the data model without directly changing the shared data model. It is characterized by the following.

Further, a shared data model operating device according to a fourth feature of the present invention, in the shared data model operating device, holds series information of a series of operations in which the virtual data model is operated by the virtual data model operating means. Operating sequence information holding means (13).

A shared data model operating device according to a fifth aspect of the present invention is the shared data model operating device, wherein the shared data model is further converted into two different views, a real view and a virtual view. A display control means (17) for displaying simultaneously; an operation sequence information holding means (13) for holding information of an operation sequence of performing an operation on the virtual data model, using the data model displayed in the virtual view as a virtual data model; Virtual data model conversion means (12) for converting a data operation based on operation sequence information into a real operation on a shared data model, and a data management means for determining whether the shared data model can be applied to the data operation based on operation sequence information (18).

[0019]

According to a first feature of the present invention, a method for operating a shared data model stores a plurality of data and a data model expressing a relationship between the data in a shared storage area, and performs a collaborative operation on the data model in real time. When an operation is performed on a shared data model, a virtual data model is generated by temporarily transcripting at least a part of the shared data model. And
An operation is performed on the generated virtual data model, and the operation performed on the virtual data model is retained as an operation sequence, and the operation sequence is selectively reflected in the operation of the shared data model.

Thus, when an operation is performed on the shared data model, the data operation can be repeatedly attempted on the virtual data model generated from the shared data model, and the result can be confirmed in advance. Also in this case, the original shared data model is not operated as it is, and the operation on the virtual data model is held as an operation sequence. To be processed. For this reason, it is possible to perform an operation by trial and error personally on the shared data model without interfering with the work of other collaborators.

In the shared data model operation method according to the second feature of the present invention, when an operation is performed on a shared data model, the shared data model is first displayed in a view. Then, at least a part of the shared data model displayed in the view is temporarily transcribed to generate a virtual data model, and the generated virtual data model is displayed in another view. Then, an operation is performed on the virtual data model displayed in another view. Operations performed on this virtual data model are stored as an operation sequence,
The operation sequence is selectively reflected in the data operation of the shared data model.

Here, when an operation is performed on the shared data model, a virtual data model generated from the shared data model is displayed in another view while the shared data model is displayed in the view. Thus, data manipulation on the virtual data model can be attempted. For the operation on the virtual data model, data manipulation can be attempted while checking the contents of the original shared data model in a view different from the view in which the shared data model is displayed in the view. Therefore, as in the case described above, it is possible to individually perform an operation by trial and error on the shared data model without disturbing the work of another collaborator.

In the shared data model operating device according to the third aspect of the present invention, the shared storage means (14)
Has a data model that expresses a plurality of data and a relationship between the data so as to be commonly accessible from a plurality of workstations via a network, and displays the data model by the display means (5, 6). When displayed on the screen and operated on the displayed data model by the operation means (5, 19), the management means (1)
1, 18) reflect the result of the operation on the data model held in the shared storage means in real time, and notify each workstation of the change of the data model. When the virtual data model generation means (8) transcribes the data model held in the shared storage means and generates the virtual data model on the workstation, the virtual data model generated by the display control means (16) is displayed in a virtual view. The virtual data model operating means (10) operates the virtual data model via the virtual view and attempts an operation on the data model without directly changing the shared data model.

As described above, in the shared data model operating device, the operation on the shared data model is performed on the virtual data model. In the shared data model operating device according to the fourth feature of the present invention, A series information holding unit (13) holds a series of operations in which the virtual data model is operated by the virtual data model operation unit as the series information of the operation.

Thus, when an operation is performed on the shared data model, the data operation can be repeatedly attempted on the virtual data model generated from the shared data model, and the result can be confirmed in advance. Also in this case, the original shared data model is managed without being operated as it is, and the operation performed on the virtual data model is retained as an operation sequence, so that it can be arbitrarily determined later. Selectively perform data manipulation processing on the shared data model. For this reason, it is possible to perform an operation by trial and error personally on the shared data model without interfering with the work of other collaborators.

In the shared data model operating device according to a fifth aspect of the present invention, the display control means (17)
Has a shared data model, a real view and a virtual view.
Display in two different views simultaneously. The operation sequence information holding means (13) holds information on an operation sequence in which an operation is performed on the virtual data model, using the data model displayed in the virtual view as a virtual data model. When the virtual data model conversion means (12) converts the data operation based on the information of the operation sequence into an actual operation on the shared data model and makes an operation request on the shared data model, the data management means (18) uses the information on the operation sequence to execute the operation. The applicability of the shared data model to the data operation is determined, and the operation is performed on the shared data model.

As described above, when an operation is performed on the shared data model, the shared data model is simultaneously displayed in the real view and the virtual view, and the shared data model displayed in the virtual view is displayed on the virtual data. As a model, data operations can be attempted on the virtual data model. Operations on the virtual data model in the virtual view
Data manipulation can be attempted while checking the contents of the shared data model displayed in another real view. Since the data operation is held as operation sequence information, the operation on the shared data model can be selectively applied later based on the operation sequence information. As a result, as in the case described above, it is possible to individually perform an operation by trial and error on the shared data model without disturbing the work of another collaborator.

[0028]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be specifically described below with reference to the drawings. FIG. 1 is a block diagram showing a system configuration of a shared data model operating device according to one embodiment of the present invention. In FIG. 1, 1 is a first workstation, 2 is a second workstation, 3 is an nth workstation.
This is the second workshop. 4 is a file server,
5 is a user interface control unit, 6 is a bitmap display, 7 is a virtual data model management unit, 8 is a virtual data model generation unit, 9 is a virtual data model storage area, 1
0 is a virtual data model operation unit, 11 is a shared data model monitoring unit, 12 is a virtual data model conversion unit, 13
Is a virtual operation sequence storage area, 14 is a shared data model storage area, 15 is a view management section, 16 is a pew display section, 17
Is a multi-pew management unit, 18 is a data model management unit, 1
An operation input unit 9 includes a keyboard, a mouse, and the like.

Such a shared data model operating device is
Through a network, a plurality of workstations 1,
It is configured as a network system in which the file servers 4 and 3 are connected. The user interface control unit 5 visualizes the direct operation of the data model,
This is a control unit for making it possible from a graphical interface on a display screen. The user interface control unit 5 allows a user to operate a data model of a view displayed on the bitmap display 6 through a pointing device such as a mouse.

The virtual data model management unit 7 is a control unit that manages overall processing of the virtual data model. Under the control of the virtual data model management unit 7, a virtual data model generation unit 8 that performs processing on the virtual data model. , A virtual data model operation unit 10, and a virtual data model conversion unit 12. The virtual data model generation unit 8 creates a virtual data model of the instructed shared data model,
The data is stored in the virtual data model storage area 9. The virtual data model operation unit 10 manages the operation of the virtual data model operated via the view, and reflects the result in the virtual data model storage area. The shared data model monitoring unit 11 performs an interface process for sending a data operation request of the shared data model to the data model management unit 18 of the file server 4.

The virtual data model conversion unit 12 stores a virtual operation as operation sequence information, and provides a conversion processing mechanism for converting the virtual operation into a real operation based on the stored operation sequence information. That is, the virtual data model conversion unit 12 replaces the corresponding data of the shared data model in the shared data model storage area 14 with the corresponding data in the virtual data model storage area,
A process of converting operation sequence information of the third virtual operation into an actual operation on the shared data model in the shared data model storage area 14 is performed. The information on the operation sequence of the virtual operation converted into the real operation on the shared data model is sent to the data model management unit 18 of the file server 4 via the shared data model monitoring unit 11 as an intermediary. The data model management unit 18 checks whether or not the change can be applied to the original data of the shared data model in response to the operation request of the real operation on the shared data model based on the received information of the operation sequence of the virtual operation. Then, data processing is performed.

The view display unit 16 is a display control unit that generates a view for visualizing the data model and displays the data model. The multi-view management unit 17 manages a plurality of views, generates a plurality of views for one data model, and performs display control for displaying the data model by the plurality of views. The file server 4 is provided with a shared data model storage area 14 of a storage area for holding a shared data model, and a data model management unit 18 for managing the data model stored in the shared data model storage area 14 is provided. Is provided.

When a virtual operation instruction is received from the user via the operation input unit 19, the virtual data model management unit 7 activates the virtual data model generation unit 8. The virtual data model generation unit 8 transcribes (copies) the shared data model linked to the view specified by the control of the user interface control unit 5, generates a virtual data model, and generates a virtual data model storage area 9. To save.
The virtual data model is visualized by being connected to an existing view or a new virtual view generated by display control of the view display unit 16, and is displayed on the bitmap display 6 via the user interface control unit 5. .

In the virtual view generated by the view display unit 16 and its display is controlled, the operation on the displayed virtual data model is controlled by the virtual data model operation unit 10 without affecting the shared data model. The operation is performed on the virtual data model stored in the virtual data model storage area 9. The change result is reflected only in the virtual data model in the virtual data model storage area 9, and the change result is displayed in the virtual view.
In this case, the log of the operation sequence of the virtual operation that causes the change result is also stored in the virtual data model storage area 9.
Are sequentially stored in the virtual operation sequence storage area 13.

At the time of saving the virtual operation, the data model management unit 18 via the shared data model monitoring unit 11
To the shared data model.
In this case, it is determined whether or not the shared data model in the shared data model storage area 14 that is the copy source of the virtual data model is changed. If there is no change, the shared data model in the shared data model storage area 14 is changed to Replace with the data in the virtual data model storage area 9. On the other hand, when it is determined that there is a change, the virtual data model conversion unit 12 converts the operation sequence information of the virtual operation stored in the virtual operation sequence storage area 13 to the actual operation of the operation sequence for the shared data model. And makes an operation request for the shared data model to the data model management unit 18 via the shared data model monitoring unit 11. In accordance with the operation request, the data model management unit 18 checks whether the operation request can be applied to the shared data model by the actual operation of the operation sequence, and selects the real operation converted from the virtual operation to the shared data model according to the user's instruction. To run.

In this manner, in the synchronous system, a copy of the data model of the user's attention is created by the shared data model, and the content of the data and the structure of the data model with respect to the virtual data model are created as the virtual data model. , A virtual operation can be performed on the shared data model by personal trial and error.

Next, the relationship between the virtual data model and the virtual view with respect to the shared data model will be described. FIG. 2 is a diagram illustrating a relationship between a shared data model and a view in which a part of the data model is displayed. Here, the data model defines a data structure that expresses data and a relationship between the data, whereas a view is a mechanism for visualizing the data model. That is, the view defines what the data model looks like. Views and data models are clearly separated and exist independently. The data model is visualized on a bitmap display by being connected to the view, and can be operated by the user.

In the system configuration of the shared data operation device according to the present embodiment, as shown in FIG. 2, a huge shared data model 20 is stored in the shared data model storage area 18 on the file server side. Collaborate on data manipulation for shared data models. Usually, the data that a certain user wants to operate is a part of the data model, and this partial data model 21 is connected to the view 23 on the workstation 22 and displayed on the view screen. Perform the operation. here,
The data model 24 connected to the view 23 on which the user is working is referred to as a “data model of interest to the user”.

In the virtual data model operation method of the present embodiment, when a virtual operation is instructed by the user, the data model M to which the user focuses is applied to the data model M.
Is copied (copied) to generate a virtual data model M ′,
An operation is attempted on this virtual data model M '. FIG. 3 is a diagram illustrating a main part of the data structure of the original data model and the virtual data model of the shared data model. As shown in FIG. 3, the original data model 31 stored in the shared data model storage area 18 on the file server side includes a creation date and time 31a, a change date and time 31b,
Data model information 31c on the data model itself
It is composed of On the other hand, the virtual data model 32 stored in the virtual data model storage area 9 on the workstation side includes a pointer 32a to the original data model as a copy source, a creation date and time 32b, and log information 32c of an operation on the virtual data model. , And data model information 32d relating to the data model itself. The data model information 32d here is a copy of the data model information 31c in the original data model, and has the same contents when the virtual data model is generated.

In the virtual data model operation method according to the present embodiment, a virtual data model is generated, this virtual data model is displayed in a virtual view, and data operation is performed. There are two types of instruction methods. One is a method based on the FREEZE mode, and the other is a method based on the OPEN mode. FIG. 4 is a diagram for explaining a virtual operation of the virtual data model in the FREEZE mode, and FIG.
FIG. 4 is a diagram illustrating virtual operation of a virtual data model in N mode.

In the FREEZE mode (freeze view), the view on which the user is operating becomes the virtual view as it is. As shown in FIG. 4, when performing a virtual operation, a virtual data model 42 is generated on the workstation 1 side with respect to the focused data model 41 in the shared data model on the file server 4 side, Displayed at 43, a virtual operation is performed on the display data model 44. In this case, when the FREEZE command is instructed, thereafter, all operations performed on the display data model 44 via the view 43 are interpreted as operations on the virtual data model (M ') 42, and the shared data It is not reflected on the model (M) 41.

In the OPEN (open virtual view) mode, the view V, which normally operates the shared data model in real time, is not changed, and a new view V 'is generated for the virtual operation. That is, as shown in FIG. 5, in this case, as in the case described above, the virtual data is placed on the workstation 1 side with respect to the data model 41 of interest in the shared data model on the file server 4 side. Generate the model 42, display it on the view,
The virtual operation of the data model is performed. In the OPEN mode in this case, when the virtual data model (M ′) 42 is generated in order to perform the virtual operation, the virtual view (V ') 52 is generated.

For the data model 41 of interest on the file server 4 side, the view (V) 51 that normally operates in real time displays the data model 41 of interest as it is. Therefore, as a result, the view (V) for the original data model (M) 41
Two views 51 and a virtual view (V ') 52 for the virtual data model (M') 42 are displayed at the same time. The data operation in the view (V) 51 is an operation on the shared data model (M) 41 as before, and the data operation on the new virtual view (V ′) 52 is an operation on the virtual data model (M ′) 42. Interpreted as an operation.

Next, the flow of processing when an operation is performed on a shared data model will be described. FIG. 6 is a flowchart showing the flow of a data operation process in a normal synchronous system. In FIG. 6, the upper frame shows processing on the workstation side, and the lower frame shows processing on the file server side. In the case of performing processing on the shared data model, when the workstation receives an operation on the data model in step 61, this is interpreted as an operation on the shared data model, and the data management unit of the file server is operated. Notify that there is a request. For this reason, in the process of step 62, the server side is notified of a data model operation request.

When a data model operation request is notified,
In the file server 4, the data model management unit
In order to check whether or not the shared data model is in a state in which this operation can be performed, first, in step 63, it is determined whether or not the operation request can be accepted. If not, a rejection message is sent to the workstation.

If the operation request is acceptable,
In step 64, the requested operation is performed on the data model M. Then, in the next step 65, the result of the execution is notified to the workstation side of success or some failure.

As described above, in the ordinary synchronous system, the operation performed on the workstation is immediately transmitted to the server and is directly performed on the shared data model. As a result, the data content of the shared data model stored in the shared data model storage area on the server side is directly rewritten, and the result is immediately transmitted to the workstation.

In the synchronous system, the operation of the shared data model of the file server is immediately performed as described above, and the result is immediately transmitted to the workstation. On the other hand, the flow of the processing of the virtual operation performed only on the workstation will be described. FIG.
9 is a flowchart illustrating a flow of a virtual operation process performed on a shared data model. The processing of the virtual operation will be described with reference to FIG.

First, when performing a virtual operation, the user explicitly instructs the selection by selecting an appropriate item from a menu or the like.
Upon receiving the instruction of this virtual operation, the next step 7
In step 2, the data model M of interest of the user is copied to the user's workstation to generate a virtual data model M '. At this time, a pointer (link information) to the original data model M is held in the virtual data model M '.

Since the connected view of the virtual data model differs depending on the type of operation mode specified by the user, it is determined in the next step 73 whether the operation mode is the open mode. When the virtual operation is instructed by the OPEN command, in step 74, a new virtual view V 'is generated, and the virtual data model M' is connected to the generated virtual view V '. On the other hand, FR
When the virtual operation is instructed by the EEZE command, the connection of the original data model M is disconnected from the view V displaying the shared data model in step 75, and the newly generated virtual data model M 'is connected. Thereby, the virtual data model is visualized by the view in any operation mode when the virtual operation is instructed.

When the virtual data model is visualized by the view, the user can operate the virtual data model. In the next step 76, the user operates the virtual data model. Here, all operations on the data model in the view are interpreted as operations on the virtual data model M '. In step 77, the result of the operation is applied to the virtual data model M 'on the workstation, and the result of the change is written to the virtual data model storage area. Further, in the next step 78,
The operation performed on the virtual data model is stored as a log in the virtual operation sequence storage area. Then, in the next step 79, it is determined whether or not an instruction to end the operation has been received from the user, and the process returns to step 76 until the instruction to end the operation has been explicitly received from the user. The process is repeated to perform an operation on the virtual data model.

The biggest difference between the processing flow of the virtual operation here and the processing flow for the shared data model performed in real time in the normal processing described in FIG. 6 is that the operation instruction target is the virtual data model. Or a shared data model. When the operation target is interpreted as a shared data model, a data exchange between the workstation and the file server naturally occurs because the system is a synchronous system. There is no exchange of data operations between the server and the file server. later,
When the operation performed on the virtual data model is applied to the shared data model, the exchange of the data operation occurs between the workstation and the file server.

When the user gives an instruction to end the virtual operation,
In response to this, the end instruction is determined by the processing of step 79, and the process proceeds to step 80. At the end of the virtual operation, it is first determined in step 80 whether the editing operation is to be saved or rejected. If it is to be saved, operation log data is saved in step 81, Proceed to end processing. If not, the process directly proceeds to the end process from step 82.

In this processing, the view to which the virtual data model is connected differs depending on the type of the operation mode specified by the user. Therefore, in the termination processing, the operation mode is the open mode in step 82. It is determined whether or not. In the case of the virtual operation started by the OPEN command, in step 83, the view V 'and the virtual data model M' are discarded, and the process ends. In the case of the virtual operation started by the FREEZE command, in step 84, the connection of the virtual data model M 'is disconnected from the view V, the original data model M is reconnected, and the process ends. In this case as well, the virtual data model M 'is discarded, and the process ends.

Next, a description will be given of the flow of processing when an operation log of a virtual operation is stored. FIG. 8 is a flowchart showing the overall processing flow of the storage processing, and FIG. 9 is a flowchart showing the flow of the selective storage processing in the storage processing. FIG. 10 is a diagram illustrating an example of a selection instruction operation using a view displayed when performing the selective saving process.

First, reference is made to FIG. When the storing process is started, in step 85, the original data model M is obtained by following the pointer to the original data model held in the virtual data model M '. In order to determine whether or not the original data model M has been changed by another person while the user is performing the virtual operation, next, at step 86, the creation date and time (T ') of the virtual data model M' And the modification date (T) of the original data model M are compared. If the result of this determination in step 86 is that T '> T, it is determined that the creation date and time of the virtual data model is new, and that no modification operation of the original data model M has been performed by another person since the creation date and time of the virtual data model. Therefore, in step 87, the original data model M on the server side is replaced with the virtual data model M ', and a process for changing the shared data model in the shared data model storage area is performed.

On the other hand, if it is determined in step 86 that T ′ ≦ T, the modification date and time of the original data model is newer than the creation date and time of the virtual data model. Since it is determined that the operation of changing the original data model M has been performed, in the next step 88, it is presented to the user that the change request cannot be accepted as it is because the original data model has been changed by another person. And
Next, in step 89, a selective storage process is performed.
In the selective saving process, a process is performed for the user to selectively reflect the virtual operation to the operation of the shared data model by a manual operation.

If the original data model has been changed by another person, not all virtual operations can be reflected in the shared data model. Therefore, in the selective storage processing, support is provided for requesting the user to selectively perform a virtual operation on the shared data model. In such an operation, it is desirable to display two states, the latest state of the original data model M and the result of the virtual operation, and obtain a selection instruction after comparison.

For this reason, in this embodiment, as shown in FIG. 10, when a virtual data model 101 is generated and connected to a virtual view 102 and a virtual operation is performed, operation sequence information 103 of the virtual operation is displayed. Since it is held in the virtual data model 101, it is visualized as an operation log list by another view 104. Also, a view 105 of the original data model is displayed, and each operation in the operation log list of the view 104 is selectively applied to the original data model by an execution command.

Next, referring to FIG. 9, the selective storage processing will be described. In the selective storage processing, processing is performed by displaying two views, a view for the original data model and a virtual view for the virtual data model. Therefore, when the selective storage process is started, first, in step 91,
In, to determine the type of operation mode, it is determined whether the operation mode is the open mode. OPE
In the case of the virtual operation started by the N command, since the two views, the view for the original data model and the virtual view for the virtual data model, are already displayed, the operation is performed with the two views displayed. Done.

On the other hand, in the determination in step 91, if the open mode is not determined, the operation is a virtual operation started by the FREEZE command. In this case, the original view for the original data model is switched and the virtual operation is started. It is displayed as a view.
Therefore, in step 92, the original data model is displayed in another view. Thus, two views are displayed by the virtual view for the virtual data model and another view for the original data model.

Next, in step 93, the operation sequence information of the virtual operation recorded in the virtual operation sequence storage area is converted into human-readable information and displayed as an operation log list. As a result, as shown in FIG. 10, the operation log list view 104, the virtual data model virtual view 102, and the original data model view 105
One view is displayed. Each operation in the operation log list can be arbitrarily selected by the user. When an execution command is instructed in a state where an item in the operation log list is selected, next, in step 94, a log list selection instruction and an execution command are accepted, and in the next step 95, a command sequence is notified to the file server. And execute the command.

As a result, the virtual operation is interpreted as an operation on the original data model M, an operation request is notified to the file server side, and the operation is executed directly on the shared data model. Will be. And
Since the result is notified from the file server side to the workstation side, in the next step 96, the execution result of the operation on the data model is notified to the user. Next, in step 97, it is determined whether or not the data operation has been completed.
4, the process from step 94 is repeated.
If it is determined in step 97 that the data operation has been completed, a series of processing is terminated. As described above, the user can execute data operations by selectively applying each operation performed by the virtual operation displayed on the operation log list to the shared data model by manual operation.

Further, since the processing for storing the virtual operation is performed as described above, the user's labor for reflecting the virtual operation on the shared data is reduced. Since the log of the operation sequence of the virtual operation is retained and displayed in an readable state that can be confirmed by the user as an operation log list, it is possible to help remember the operation performed by the user. Then, since only a necessary part is extracted and can be selectively executed, efficient data operations can be performed on the shared data model without wasting changes by others.

[0065]

As described above, according to the present invention, when a user instructs a virtual operation on an arbitrary data model, a virtual data model is created, and all operations on the virtual view are virtual data. Because it is interpreted as an operation on the model, even in a synchronous system, the user does not disturb the collaborator and does not interfere with the collaborator, Operations can be performed. The virtual operation makes it easier for the user to directly work on the data, and can reduce the cognitive burden on the user as compared with the case where the result is predicted only in the mind and performed directly on the shared data model.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a system configuration of a shared data model operation device according to an embodiment of the present invention;

FIG. 2 is a diagram for explaining a relationship between a shared data model and a view in which a part of the data model is displayed;

FIG. 3 is a view for explaining a main part of a data structure of an original data model and a virtual data model of a shared data model;

FIG. 4 is a view for explaining virtual operation of a virtual data model in a FREEZE mode;

FIG. 5 is a view for explaining a virtual operation of a virtual data model in an OPEN mode;

FIG. 6 is a flowchart showing a flow of a data operation process in a normal synchronous system;

FIG. 7 is a flowchart illustrating a flow of a virtual operation process performed on a shared data model;

FIG. 8 is a flowchart showing the flow of the entire storage process;

FIG. 9 is a flowchart showing the flow of a selective save process in the save process;

FIG. 10 is a diagram illustrating an example of a selection instruction operation based on a view displayed when performing selective storage processing.

[Explanation of symbols]

1 ... first workstation, 2 ... second workstation, 3 ... nth workstation,
4 file server, 5 user interface control unit, 6 bitmap display, 7 virtual data model management unit, 8 virtual data model generation unit, 9 virtual data model storage area, 10 virtual data model operation unit,
11: Shared data model monitoring unit, 12: Virtual data model conversion unit, 13: Virtual operation sequence storage area, 14
... shared data model storage area, 15 ... view management unit, 1
6 ... Pew display unit, 17 ... Multi Pew management unit, 18 ...
Data model manager, 19 operation input unit, 20 shared data model, 21 partial data model, 22 workstation, 23 view, 31 original data model, 32 virtual data model, 41 data model , 42 virtual data model, 43 view, 44 display data model, 51 view, 52 virtual view.

──────────────────────────────────────────────────続 き Continued on the front page (58) Field surveyed (Int. Cl. ⁷ , DB name) G06F 13/00 G06F 3/14-3/153 H04N 7/15

Claims (5)

(57) [Claims] In a collaborative work system for storing a plurality of data and a data model expressing a relationship between the data in a shared storage area and performing a collaborative work on the data model in real time, an operation on the shared data model is performed. A method of operating a shared data model in which a virtual data model is generated by temporarily transcribing at least a part of the shared data model, performing an operation on the generated virtual data model, A method of operating a shared data model, wherein an operation performed on a shared data model is retained as an operation sequence, and the operation sequence is selectively reflected in an operation of a shared data model. 2. In a collaborative work system for storing a plurality of data and a data model expressing a relationship between the data in a shared storage area and performing a joint work on the data model in real time, an operation is performed on the shared data model. Is a method of operating a shared data model in which a virtual data model is generated by temporarily posting at least a part of the shared data model displayed in a view, and the generated virtual data model is displayed in another view Perform operations on the virtual data model displayed in another view, retain the operations performed on the virtual data model as an operation sequence, and selectively reflect the operation sequence on data operations of the shared data model A method for operating a shared data model, characterized in that: 3. A shared storage means for holding a plurality of data and a data model expressing a relation between the data so as to be commonly accessible from a plurality of workstations via a network, and displaying the data model on a display screen of the workstation. Display means, an operation means for performing an operation on the displayed data model, and a result of the operation reflected on the data model held in the shared storage means in real time, and the change of the data model is notified to each workstation. Management means; virtual data model generation means for transcribing the data model held in the shared storage means and generating a virtual data model on a workstation; and display for controlling display of the generated virtual data model in a virtual view Manipulate the virtual data model via control means and virtual views, and share A shared data model operation device, comprising: virtual data model operation means for attempting an operation on the data model without directly changing the data model. 4. The shared data model operation device according to claim 3, further comprising operation series information holding means for holding series information of a series of operations in which the virtual data model is operated by the virtual data model operation means. Characteristic shared data model operation device. 5. The shared data model operating device according to claim 3, wherein a display control means for simultaneously displaying the shared data model in two different views, a real view and a virtual view, and data displayed in the virtual view. An operation sequence information holding unit that stores information of an operation sequence that has performed an operation on the virtual data model, using the model as a virtual data model, and a virtual data model that converts a data operation based on the information of the operation sequence into a real operation on a shared data model A shared data model operation device, further comprising: a conversion unit; and a data management unit that determines whether a shared data model can be applied to a data operation based on operation sequence information.