WO2023121505A1

WO2023121505A1 - System and method for managing the collaborative editing of digital objects

Info

Publication number: WO2023121505A1
Application number: PCT/RU2021/000632
Authority: WO
Inventors: Алексей Владимирович СИТНИКОВ
Original assignee: Общество С Ограниченной Ответственностью "Кейс Студио"
Priority date: 2021-12-24
Filing date: 2021-12-30
Publication date: 2023-06-29

Abstract

The invention relates to the field of computer technology for managing the collaborative editing of digital objects. The technical result consists in providing more secure management of the collaborative editing of digital objects and minimizing human involvement. This technical result is achieved in that the collaborative editing environment is configured so that each user is able to send to a server a request for transfer of the rights to edit a digital object contained in the collaborative editing environment; reject, during a set period of time, a request for transfer of the rights to edit a digital object contained in the collaborative editing environment to another user; transfer, during a set period of time, the rights to edit a digital object contained in the collaborative editing environment to another user; edit at least one digital object, provided that the rights to edit the given digital object have been granted to the user by the server.

Description

SYSTEM AND METHOD FOR MANAGING JOINT EDITING OF DIGITAL OBJECTS

Technical field

[0001] The present invention relates to systems and methods for managing collaborative editing of digital objects, allowing multiple users to efficiently edit digital objects simultaneously while maintaining the security of digital objects.

State of the art

[0002] Software systems are composed of a plurality of interconnected digital objects. For the correct operation of systems as a whole, a coordinated change of several objects or parts of one object is required, while the development of large automated systems requires the joint work of several developers. Simultaneous editing of the same digital object by multiple developers may result in conflicts or incompatible changes.

[0003] The standard way to solve this problem is to be able to obtain exclusive access to the object. Initially, all objects are free, and before editing begins, one of the developers must gain access to editing the digital object, having received an exclusive lock. After some time, a developer who has obtained an exclusive lock on a digital object can release it. At the same time, while a digital object is in its exclusive lock, it can both make changes and leave the object unchanged. During the period of time when an object is under an exclusive lock, other developers cannot make changes to the digital object.

[0004] The disadvantage of this approach is that the developer can hold the object longer than necessary, making it difficult or impossible for other developers to work. This problem is often solved by introducing privileged users into the system who are able to unlock the normal user. However, this complicates the process by requiring the continued involvement of such a privileged user.

[0005] An invention is known according to patent US10817572B2 (publ. 10/27/2020; IPC: G06F 13/00; G06F 16/93; G06Q 10/10), which describes systems and methods that provide a client-server architecture capable of supporting multiple asynchronous and synchronized actions of joint work in the so-called place collaboration. Activities include: chatting, viewing and/or editing one or more data files, and sharing one or more applications, data files and/or displays. The described client-server architecture supports seamless navigation between the supported asynchronous and synchronous activities in the collaboration space. In addition, the client-server architecture supports data persistence so that data files associated with a collaboration space can be stored for later access. The main disadvantage of this solution is that it does not provide for the possibility of sending a request for the transfer of rights/access to edit a digital object. Another difference is that in order to create a collaborative environment/space, you must send a request to the server.

[0006] Also known is the solution described in the application US20140280347A1 (publ. 18.09.2014; IPC: G06F 17/30). The application describes a method for controlling access to and use of digital files stored in a file storage united in a network with several servers. The method includes the following steps: requesting a server to access and use a file stored in a file storage, sending a request containing an identifier (ID) of the file to another server; each of the other servers accepting the request checks the internal block list to see if it contains a file identifier. If it is specified, the server returns an error message to the requesting server, but if not specified, it returns a success message; and the requesting server determines from all returned messages whether an error message exists. If it exists, it does not access or use the file, and sends repeated requests after a predetermined time interval. But if it doesn't exist, it accesses the file and uses it, and sends a notification message to all other servers when the file is finished. The first disadvantage of this solution is that it provides for sending a request to the server containing a request for access to edit a digital object, but it does not provide for the possibility of intercepting access for editing. The second disadvantage is that the decision to transfer access to editing a digital object is made exclusively by the server. The third disadvantage of this solution is that the system includes many servers. To implement the system described in this application, only one server is needed, which significantly reduces the required computing power and the cost of the system. It also mentions the ability to save files server, but does not describe the frequency of storage or the possibility of intermediate storage.

[0007] Another similar solution is the invention according to the patent AU2011320745B2 (publ. 11/27/2014; IPC: G06F 9/44; G06F 15/16; G06F 17/21), which describes an online document service provided by application servers for editing users. Documents are stored in component-based structures in the application server's local memory to provide granularity for co-authoring and conflict resolution. Component-level locking is used to minimize conflicts associated with simultaneous editing of users, as well as to indicate the presence of other users. Component-based design changes are persisted to capture component changes and keep document save actions in sync. When changes are saved by one or more clients on the server, they can be saved to the current version of the server document, even if that document is different from the version used to create the current view on the client device. The first disadvantage of this solution is that it provides for sending a request to the server containing a request for access to edit a digital object, but it does not provide for the possibility of intercepting access for editing. The second disadvantage is that the decision to transfer access to editing a digital object is made exclusively by the server. The analogue also mentions the possibility of saving files by the server, but does not describe the frequency of saving or the possibility of intermediate saving.

[0008] Also among similar solutions is an invention according to patent US7249314B2 (publ. 24.07.2007; IPC: G06F 15/00). This source discloses a system and methods for simultaneous editing of a document by two or more users. The document is divided into several sections. Each section is stored in a separate data container, which is part of the document tree. The master copy of the document tree is available to the server, which transfers all or part of the document tree to two or more clients, each of which is controlled by a user. Clients can independently lock different sections, allowing users to edit different sections at the same time. When a user finishes editing a section, the modified section is stored on the main server and broadcast to other users. The document tree is headed by an independently lockable and editable parent container that is used to store summary information and other information such as default formatting and other information covering the entire document. The first disadvantage of this solution is that it provides for sending a request to the server containing a request for access to edit a digital object, but it does not provide for the possibility of intercepting access for editing. The second drawback is that the decision to transfer access to editing a digital object is made exclusively by the server. Also in the analogue there is no periodic saving of the document in / files and the possibility of intermediate saving.

[0009] Another similar solution is the invention according to the patent US8429753B2 (publ. 23.04.2013; IPC: G06F 21/00). It describes implementation options related to systems and methods for controlling access to document files on a document server. One example of the system includes document files stored on the document server, at least one of the document files referring to the file lock, and a document access processing module. An exemplary document access processing module includes a file sharing processing module that determines the co-editing status of a client computer software application requesting access to a document file, and a file lock processing module that stores one or more file locks and manages setting, and resetting file locks. An example document access processing module uses the software application's co-edit status and file/document lock status to determine whether the software application is allowed to have write access to the file/document. The first disadvantage of this solution is that it provides for sending a request to the server containing a request for access to edit a digital object, but it does not provide for the possibility of intercepting access for editing. The second drawback is that the decision to transfer access to editing a digital object is made exclusively by the server. Also, in the analogue there is no periodic saving of documents / files and the possibility of intermediate saving.

The essence of the invention

[00010] The objective of the claimed invention is to create and develop a system and method for effectively and safely managing the collaborative editing of digital objects with minimization of human participation, to optimize the process of creating digital objects.

[00011] The specified problem is solved thanks to such a technical result as ensuring the effectiveness of managing the joint editing of digital objects, as well as ensuring the security of digital objects in the co-editing mode, minimizing the degree of human intervention. The specified objective is achieved including, but not limited to, thanks to: a. limiting the response time to the request of the second user to transfer the rights to edit the digital object; b. periodic formation of backup copies of a digital object in the process of its editing; c. transferring the rights to edit a digital object to the second user who requested this right, in case the response time to the request expires; d. transfer of editing rights using the server.

[00012] More fully, the technical result is achieved by the described method for managing the co-editing of digital objects, including the steps: sending the first user a request to the server to obtain rights to edit the digital object contained in the co-editing environment; granting by the server to the first user the rights to edit the digital object; sending the second user a request to transfer rights to edit the digital object; waiting by the server for the first user's response to the second user's request for a certain time. In this case, the first user within a certain time has the opportunity to answer one of the following options: transfer the rights to edit the digital object to the second user; reject a request to transfer rights to edit a digital object to a second user; do not respond to the request to transfer rights to edit the digital object to the second user. Moreover, if the first user transferred the rights to edit the digital object to the second user or did not respond to the request, with the help of the server: they revoke the rights to edit the digital object from the first user and grant the rights to edit the digital object to the second user.

[00013] At the same time, the step at which the first user sends a request to the server to obtain the rights to edit the digital object contained in the co-editing environment, and the step of granting the server the rights to edit the digital object to the first user are necessary to include the first user in the co-editing environment , and also to ensure that the first user has a direct opportunity to edit this digital object. The stage of sending a request by the second user to transfer rights to edit a digital object is necessary so that in the editing environment the second user has the ability to intercept editing rights digital object from the first user, if the first user is not currently editing the digital object. The step of waiting for the server to respond from the first user to the second user's request for a certain amount of time is, in turn, necessary to enable the first user to respond to the second user's request. The fact that the first user has the ability to transfer rights to edit the digital object for a certain time is necessary for the first user to voluntarily transfer his rights to edit the digital object to the second user. The fact that the first user has the ability to reject a request to transfer rights to edit a digital object to a second user within a certain time is necessary so that the first user can reject the transfer of rights if the first user is currently editing this digital object. The fact that the first user has the option not to respond to a request to transfer rights to edit the digital object to the second user is necessary to determine whether the first user is currently editing the digital object or not. The fact that, if the first user transferred the rights to edit the digital object to the second one or did not respond to the request, the server can revoke the rights from the first user and grant the rights to the second user, it is necessary to directly transfer the rights to edit the digital object from the first user second user. In general, blocking the user of exclusive rights to edit a digital object is necessary to prevent incompatible changes from being made to the digital object, that is, to ensure the security of the digital object.

[00014] At the stage of sending the second user a request to transfer rights to edit the digital object, the request may be sent directly to the first user. This may be necessary so that the first user can make their own decision about transferring editing rights. Alternatively, a request may be sent to the server. This may be necessary if the server decides entirely on the transfer of editing rights. It is also possible to send a request to both the first user and the server.

[00015] Before the step of granting the right to edit the digital object to the second user, the edited digital object can be stored using the update module. In another embodiment, they can produce periodic saving digital objects using the update module. This can increase the security of data contained in digital objects.

[00016] The step of waiting for the response of the first user to the request of the second user can be performed within 1-15 minutes. This time is optimal for many tasks. In this case, periodic storage can be performed with a period of less waiting time. This will avoid loss of digital object data.

[00017] In the step of revoking the rights to edit the digital object from the first user, a notification may be sent to the first user that the rights to edit the digital object have been revoked by the server. This may inform the user that he no longer has rights to edit this digital object.

[00018] After the step of revoking the rights to edit the digital object from the first user, the server may first exclude the first user from the collaborative editing environment of the digital object and add it to the viewing environment. This may be necessary so that the first user, even after losing the rights to edit a digital object, can observe the editing process.

[00019] After saving at least one digital object, at least one digital object can be displayed using the viewing environment without being able to edit it. This may be necessary so that the first user, even after losing the rights to edit a digital object, can see significant changes made to a digital object during its editing.

[00020] Also, in the process of editing a digital object, a copy of the visual display of at least one digital object can be created using the server, the created copy can be transferred to the co-editing environment, and the resulting copy can be displayed using the co-editing environment. Such an option may allow the first user to observe the entire editing process of the digital object.

[00021] Also, the technical result is achieved by a digital object co-editing control system configured for simultaneous operation of at least two users. The system includes a server including memory and a processor. The memory then includes at least one collaborative editing environment that includes at least one digital object. The processor, in turn, is configured to grant editing rights to the digital object contained in the collaborative editing environment; waiting for the first user's response to the second user's request to transfer rights to edit digital object for a certain time; and revoking the rights to edit the digital object contained in the co-editing environment. The co-editing environment is configured in such a way that each user is able to: send a request to the editing rights server for the digital object contained in the co-editing environment; rejecting a request to transfer rights to another user to edit the digital object contained in the collaborative editing environment for a specified time; transferring rights to another user to edit the digital object contained in the collaborative editing environment for a certain time; and editing at least one digital object, provided that the user has been granted rights to edit this digital object using the server.

[00022] At the same time, the server is needed to store the co-editing environment and its digital objects using memory, as well as to organize the process of transferring rights using the processor. Granting by the server to the first user the rights to edit the digital object is necessary to include the first user in the collaborative editing environment, as well as to ensure that the first user has the direct ability to edit this digital object. Waiting by the server for the first user's response to the second user's request for a certain time, in turn, is necessary in order to enable the first user to respond to the second user's request. And the combination of the possibility of granting and revoking rights by the server is necessary for the direct transfer of rights to edit a digital object from the first user to the second user. The ability of the user to send a request to transfer the rights to edit a digital object to the server is necessary so that in the editing environment the user has the ability to intercept the rights to edit the digital object from another user if the other user is not currently editing the digital object. The fact that the user has the ability to decline a request to transfer rights to edit a digital object to another user for a certain time is necessary so that the user can refuse the transfer of rights if the user is currently editing this digital object. The fact that the user has the ability to transfer rights to edit a digital object for a certain time is necessary for the user to voluntarily transfer his rights to editing a digital object to another user. The ability for users to edit a digital object is necessary for direct editing of a digital object, the editing rights of which are assigned to this user.

[00023] The fact that the server includes an update module connected to the memory may be necessary for intermediate savings of changes during editing of a digital object. In this case, the update module can be configured to save the edited digital objects. Moreover, the storage may be a periodic storage. Periodic storage may be performed with a period less than the time to wait for the first user's response to the second user's request.

[00024] The fact that the server is configured in such a way that the first user's response time to the second user's request can be 1-15 minutes may be necessary for specific system tasks.

[00025] The server may also be configured to send notifications to users that the rights to edit a digital object have been revoked. This may inform the user that he no longer has rights to edit this digital object.

[00026] The server may include a viewing environment associated with the co-editing environment, and the server may be configured to exclude users from the co-editing environment of the digital object and add users to the viewing environment. This may be necessary so that the first user, even after losing the rights to edit a digital object, can observe the editing process.

[00027] The viewing environment can be configured to display at least one digital object from the collaborative editing environment without being able to edit it, and only display the digital objects with saved changes. This may also be necessary so that the first user, even after losing the rights to edit a digital object, can observe the process of editing it. At the same time, such an embodiment of displaying edited digital objects may allow displaying only significant changes made to the digital object.

[00028] The viewing environment may be configured to display the digital objects with all changes made to the digital objects. Such an option may allow the first user to observe the entire editing process of the digital object.

Description of drawings

[00029] In FIG. 1 is a flowchart illustrating a digital object co-editing control method according to the present invention.

[00030] In FIG. 2 is a flowchart illustrating a method for controlling co-editing of digital objects with additional steps according to the present invention.

[00031] In FIG. 3 is a schematic view of a digital object co-editing control system according to the present invention.

[00032] In FIG. 4 is a schematic view of the digital object co-editing control system of the present invention with additional elements.

Detailed description

[00033] In the following detailed description of the invention, numerous implementation details are provided to provide a clear understanding of the present invention. However, it will be obvious to one skilled in the art how the present invention can be used, both with and without these implementation details. In other cases, well-known methods, procedures and components are not described in detail so as not to obscure the features of the present invention.

[00034] In addition, from the foregoing, it is clear that the invention is not limited to the above implementation. Numerous possible modifications, alterations, variations, and substitutions that retain the spirit and form of the present invention will be apparent to those skilled in the art.

[00035] The present digital object co-editing control system and method can be applied to various co-editing environments that are capable of exclusive locking of a digital object to a user. Exclusive locks protect digital objects from incompatible updates/changes. They can only be owned by one user at a time. Any user requesting an exclusive lock must wait for the digital object to be released and rights to it transferred. editing if another user currently owns an exclusive lock on the requested digital object.

[00036] In FIG. 1 is a flowchart illustrating a digital object co-editing control method according to the present invention. First, the first user sends a request to the server to obtain rights to edit the digital object. If the digital object is free, then the server grants the first user the rights to edit the digital object. Immediately or after some time, the second user sends a request to transfer the rights to edit the digital object, the editing rights of which currently belong to the first user. From the moment the request is sent, the server waits for the first user's response to the second user's request for a certain time. At the same time, if the first user managed to respond to the request within a certain time and refused to transfer the rights to edit the digital object to the second user, then the rights to edit the digital object are not granted to the second user. Otherwise, namely, if the first user did not have time to respond to the request of the second user or managed to transfer editing rights to the second user, then using the server, first user revokes the rights to edit the digital object from the first user, and then grants editing rights digital object to the second user.

[00037] The first and second users are people interacting with the digital objects of the collaborative editing environment through the user's client. A client is a hardware or software component of a computing system that sends requests to a server. The client program communicates with the server using a specific protocol. It can request some data from the server, manipulate data directly on the server, launch new processes on the server, and so on. The client program can provide the data received from the server to the user or use it in some other way, depending on the purpose of the program. A digital object is an object consisting of a structured sequence of bytes that has a name, a unique identifier, and attributes that describe its properties. In the context of the present invention, a digital object refers to any document, file, spreadsheet or any of their components placed in a digital environment.

[00038] The specific time during which the first user is expected to respond to the second user's request may be different, depending on

AND specific application of the method. However, when implementing the method, it must be predetermined and specified. It is set specifically to limit the response time of the first user. If the user does not respond to the request within this specified time, the server interprets this as the fact that the first user is not currently editing the digital object, the editing rights of which belong to him. In this regard, the rights to edit this digital object can be transferred to the second user who requested the transfer of rights.

[00039] In FIG. 2 is a flowchart illustrating a method for controlling co-editing of digital objects with additional steps according to the present invention. The steps depicted therein and described below can be used in the digital object co-editing control method, in addition to the steps described above, individually, collectively, and in any combination.

[00040] In particular, after the first user has been granted the rights to edit the digital object, the first user can edit the digital object. At the same time, in the process of work, they can save a digital object.

[00041] Saving can be done in several ways. Firstly, the user can save the changes made in the process of editing a digital object independently and at any stage of editing. Secondly, it is possible to provide for the periodic saving of changes made to the digital object. In this case, if a periodic saving of a digital object is provided, then it is preferable that the period for saving changes be less than the time the server waits for the first user's response to the second user's request. If the period is greater than or equal to the waiting time, then there is a risk of losing data about the changes that were made by the first user to the digital object if it is transferred to the second user. For example, if the timeout is 3 minutes and the retention period is 5 minutes, then it is possible that the first user made changes to the digital object 1 minute ago. After this one minute, the second user sent a request to transfer the rights to edit the digital object, and the first user did not respond to this request within 3 minutes. Then the rights to edit the digital object will be transferred to the second user, and in the transferred digital object there will be no changes made to it 4 minutes ago, because the storage period is 5 minutes. For To prevent such data loss, a third way of saving a digital object can be used - namely, saving the changes made by the first user before directly transferring the rights to edit this digital object to the second user. That is, even if the changes made were not saved through periodic saving, they will in any case be saved before the transfer of rights. All three of these storage methods can be used individually, in combination, or in any combination.

[00042] The second user may send a request to transfer editing rights to the first user with these rights, the server, or the first user and the server at the same time. In the case of sending only to the first user, the transfer of editing rights may not be carried out at all, due to the fact that the first user may not be connected to the server at the time the request was sent by the second user, and since. If the request was not sent to the server, then the server cannot grant the rights to edit the digital object to the second user. In other cases, even if the first user is not connected to the server and cannot respond to the request, the server can revoke edit rights from the first user and grant edit rights to the second user.

[00043] The time the server waits for the response of the first user to the request of the second user can be set in the range of 1-15 minutes, depending on the specific objectives of the method. If you set the time less than a minute, the user may not have enough time to respond to the request he received, because he will need to, for example, switch from editing to reading the text of the request, read it, understand what digital object is being requested and respond to the request. If the waiting time is more than 15 minutes, then this will significantly delay the user experience, because when submitting an edit request, the second user can expect to receive editing rights to the digital object as soon as possible in order to start editing it sooner. In this regard, a waiting time of 1-15 minutes is the optimal waiting time. At the same time, if the function of periodically saving a digital object is added, the saving period should be set to less than 1-15 minutes or it should be possible to save the changes made by the first user before directly transferring the rights to edit this digital object to the second user.

[00044] In the event that the rights to edit a digital object are revoked from the first user, immediately after the rights are revoked, they can additionally send notification to the first user that the rights to edit a particular digital object have been revoked.

[00045] If the first user was granted rights to edit only one digital object, then after they are revoked, the first user may also be excluded from the collaborative editing environment of digital objects. In this case, if a viewing environment is provided, then the first user can be added to the viewing environment to enable him to observe the editing of the digital object.

[00046] After saving at least one digital object, at least one digital object can be displayed using the viewing environment without being able to edit it. That is, after each save of the changes made to the digital object, a visual copy is created using the server and the created copy is transferred to the viewing environment. Using the viewing environment, in turn, display the resulting copy. Thus, saving a digital object is a trigger event for displaying the digital object in the viewing environment. In this case, the first user has the opportunity to observe the introduction of significant saved changes to the digital object while in the viewing environment.

[00047] In another embodiment, in the process of editing a digital object, a copy of the visual display of at least one digital object can be created using a server, the created copy can be transferred to a co-editing environment, and the resulting copy can be displayed using the co-editing environment. Such an option may allow the first user to observe the entire editing process of the digital object. It differs from the previously described method in that it does not have a trigger event. All changes are rendered in the viewing environment continuously and/or at certain intervals. In this case, it is preferable to set a certain periodicity up to 1 minute. Thus, the first user has the opportunity to observe the current state of the digital object in real time while in the viewing environment.

[00048] A method for controlling co-editing of digital objects while including all the additional steps shown in FIG. 2 is carried out as follows. First, the first user sends a request to the server to obtain rights to edit the digital object. If the digital object is free, then the server grants the first user the rights to edit the digital object. After granting rights to edit a digital object to the first user, the first user can editing a digital object. At the same time, during the editing process, the first user can independently save the changes made to the digital object at any stage of editing. In parallel, the changes made to the digital object are periodically saved. Immediately or after some time, the second user sends a request to the first user and/or server to transfer the rights to edit the digital object, the editing rights of which currently belong to the first user. From the moment the request is sent, the server waits for the first user's response to the second user's request for a certain time. At the same time, if the first user managed to respond to the request within a certain time and refused to transfer the rights to edit the digital object to the second user, then the rights to edit the digital object are not granted to the second user. Otherwise, namely, if the first user did not have time to respond to the request of the second user or managed to transfer the editing rights to the second user, then using the server, they first save the changes made to the digital object by the first user, and then revoke the editing rights digital object from the first user. Thereafter, a notification is sent to the first user that the rights to edit the digital object have been revoked, and the first user is excluded from the co-editing environment. After the exclusion, the first user can be added to the browsing environment. Further, the rights to edit the digital object are granted to the second user. In this case, the server waits for a response for 1-15 minutes, and periodic saving of changes in the digital object is performed with a period of less than 1-15 minutes. At the same time, in the course of editing a digital object after saving, continuously and/or with a certain frequency, a copy of the visual display of at least one digital object is created and the created copy is transferred to the viewing environment using the server. After that, the resulting copy is displayed using the viewing environment.

[00049] It is also possible that after the second user sends a request to transfer rights to edit a digital object, the server checks whether the connection of the first user with the server is established. Those. whether the first user with editing rights for this digital object is connected to the co-editing environment. If this connection is not established, then the server, without waiting for the first user's response, revokes the rights to edit the digital object from the first user and grants rights to edit the digital object to the second user.

[00050] In FIG. 3 is a schematic view of a digital object co-editing control system according to the present invention. The digital object co-editing management system is configured for simultaneous operation of at least two users 1, 2 and includes a server 3. Server 3, in turn, includes a memory 6 and a processor 7. The memory 6 of the server 3 includes at least one co-editing environment 5 , including at least one digital object 4. The processor 7 is configured to: grant editing rights to the digital object 4 contained in the collaborative editing environment 5; waiting for the response of the first user 1 to the request of the second user 2 to transfer the rights to edit the digital object 4 within a certain time, as well as to revoke the rights to edit the digital object 4 contained in the co-editing environment 5. The co-editing environment 5 is configured in such a way that each user 1, 2 had the ability to: send a request to the server 3 to transfer the rights to edit the digital object 4; rejecting a request to transfer rights to another user 1, 2 to edit a digital object 4 for a certain time; transferring rights to another user 1, 2 to edit the digital object 4 for a certain time; as well as editing at least one digital object 4, provided that the user 1, 2, using the server 3, was granted the rights to edit this digital object 4.

[00051] The co-editing environment 5, in a particular case, may be an integrated development environment (hereinafter - IDS) (English Integrated development environment - IDE), also called a single development environment (ECR). IRS is a set of software tools used by programmers to develop software (SW). The IDE may include a text editor, a translator (compiler and/or interpreter), build automation tools, a debugger, etc. In some cases, the IDE may also contain tools for integration with version control systems and various tools to simplify the construction of a graphical user interface. Many modern development environments also include a class browser, an object inspector, and a class hierarchy diagram for use in object-oriented software development. IDEs are usually designed for multiple programming languages such as IntelliJ IDEA, NetBeans, Eclipse, Qt Creator, Geany, Embarcadero RAD Studio, Code::Blocks, Xcode, or Microsoft Visual Studio, but there is also an IDE for one specific programming language - such as Visual Basic, Delphi, Dev-C ++. In this case, as a digital object 4 may mean, for example, a part of the code (some lines of code) or one of the files included in the total code.

[00052] A special case of the IDE is a visual development environment that includes the ability to visually edit the program interface. In this case, a widget, a form, a control element, etc. can be considered as a digital object 4.

[00053] Variants may also be provided in which a co-editing environment is a set of software tools used by users to edit files, tables, and/or documents. In the case of tables, user 1, 2 can be assigned the rights to edit a specific column, row, cell, sheet, entire table, etc. In this case, the column, row, cell, sheet, and the entire table are digital objects 4. For a document, digital object 4 can be a term, a paragraph, a page, or the entire document.

[00054] Thus, for various types of digital files, the digital object 4 is some strictly defined part of it or the entire digital file.

[00055] The first 1 and second 2 users are people interacting with the digital objects 4 of the collaborative editing environment 5 via the user's client. A client is a hardware or software component of a computing system that sends requests to a server. The client program communicates with the server 3 using a specific protocol. It can request any data from server 3, manipulate data directly on server 3, launch new processes on server 3, etc. The client program can provide data received from server 3 to user 1, 2 or use it in some other way, in depending on the purpose of the program.

[00056] The co-editing control system shown in FIG. 3 works as follows. When the first user 1 sends a request to server 3 to obtain rights to edit digital object 4, if digital object 4 is free, then using server 3, the first user 1 is granted rights to edit this digital object 4. When the second user 2 sends a request to transfer rights to edit a digital object 4, the editing rights of which currently belong to the first user 1, the server 3 waits for the response of the first user 1 to the request of the second user 2 for a certain amount of time. In this case, if the first user 1 managed to respond to the request within a certain time and refused to transfer the rights to edit the digital object 4 to the second user 2, then the server 3 does not grant the rights to edit the digital object 4 to the second user 2. Otherwise, namely, if the first user 1 did not have time to respond to the request of the second user 2 or managed to transfer the editing rights to the second user 2, then with the help of the server 3, the rights to edit the digital object 4 are first revoked from the first user 1, and then grant the rights to edit the digital object 4 to the second user 2. In this case, the digital object 4 is stored in the collaborative editing environment 5 included in the memory 6 of the server 3, and all actions performed by the server 3 are carried out using the processor 7 of the server 3.

[00057] In FIG. 4 is a schematic view of a digital object co-editing control system with additional elements according to the present invention. The items depicted therein and described below can be used in the digital object co-editing management system, in addition to the items described above, individually, collectively, and in any combination.

[00058] In particular, the server 3 may include an update module 8 connected to the memory 6. The update module 8 is designed to update the data of the collaborative editing environment 5 stored in the memory 6. In particular, the update module 8 may be configured to save changes to digital objects 4 contributed by users 1, 2.

[00059] The update module 8 can be configured to save changes in several ways. Firstly, the user 1, 2 can save the changes made during the editing process of the digital object 4 by means of the updater 8 independently and at any stage of editing. Secondly, it is possible to provide for the periodic saving of changes made to the digital object 4 by the update module 8. In this case, if the digital object 4 is periodically saved, it is preferable that the period for saving the changes is less than the time the server 3 waits for the first response. user 1 to the request of the second user 2. If the period is greater than or equal to the waiting time, then there is a risk of losing data about the changes that were made by the first user 1 to the digital object 4 if it is transferred to the second user 2, as described earlier . To prevent such data loss a third way of saving the digital object 4 can be used, namely saving the changes made by the first user 1 by the update module 8 before directly transferring the rights to edit this digital object 4 to the second user 2. All these three methods of saving can be used by the update module 8 as separately, or in total or any combination.

[00060] The processor 7 may be configured such that the time the server 3 waits for a response from the first user 1 to a request from the second user 2 may be set in the range of 1-15 minutes, depending on the specific tasks of the system. If you set the time less than a minute, user 1 may not have enough time to respond to the request he received, because he will need to, for example, switch from editing to reading the text of the request, read it, understand which digital object 4 is being requested and respond to the request. If the waiting time is more than 15 minutes, then this will significantly delay the work process for users 1, 2, because when submitting an edit request, the second user 2 can expect to receive the rights to edit the digital object 4 as soon as possible in order to start editing it sooner. In this regard, a waiting time of 1-15 minutes is the optimal waiting time. In this case, if the function of periodically saving the digital object 4 by the update module 8 is added, the saving period should be set to less than 1-15 minutes or it should be possible to save the changes made by the first user 1 before directly transferring the rights to edit this digital object 4 to the second user 2.

[00061] The processor 7 of the server 3 may further be configured to send notifications to the users 1, 2 that the rights to edit the digital object 4 have been revoked. This may allow the user 1, 2 to be informed of the loss of rights to edit a particular digital object 4. The processor 7 may send a notification through the interface of the collaborative editing environment 5, in the browser during active use, or as an email notification. In this case, the notification may include at least the name and/or some identifier of the digital object 4, the rights to edit which have been revoked. The notification may also include the identifier of the user 1, 2 to whom the rights to edit the digital object 4 were transferred and/or the current status of the digital object 4.

[00062] Also, the server 3 may further include a viewing environment 9 associated with the collaborative editing environment 5. The viewing environment 9 is intended to display changes to the digital object 4, part of the digital objects 4 or all digital objects 4 included in the co-editing environment 5. The viewing environment 9 can be implemented in several ways. Firstly, the viewing environment 9 can only display the digital objects 4 as they are currently stored in the memory 6. That is, if the updater 8 periodically stores the digital objects 4 times per minute, then the display of the digital objects 4 in the viewer 9 will change every minute at the moment the update module 8 saves the changes. object 4 will be implemented with each change made to digital object 4 in co-editing environment 5. Viewing environment 9 will be a “mirror” of co-editing environment 5, which does not provide the functionality of co-editing environment 5, but only displays digital objects 4 in their current condition.

[00063] When the viewing environment 9 is included in the digital object co-editing management system, the processor 7 of the server 3 can be further configured to exclude users 1, 2 from the co-editing environment 5 of the digital object 4, as well as add users 1, 2 to the viewing environment 9 This may be necessary in order to allow user 1, 2 to monitor the progress of editing digital object 4, and also to allow user 1, 2 to know when another user 1, 2 has stopped editing digital object 4. Also this may allow identification of currently unedited digital objects 4. [00064] The digital object co-editing control system when all additional elements shown in FIG. 4 works as follows. When the first user 1 sends a request to the server 3 to obtain the rights to edit the digital object 4, if the digital object 4 is free, then using the server 3, the first user 1 is granted the rights to edit this digital object 4. After the server 3 grants the rights to the first user 1 to editing the digital object 4, the first user can edit the digital object 4 and save changes during editing using the update module 8. In parallel, the update module 8 also periodically stores the digital object 4 in the memory 6. When the second user 2 sends a transfer request for editing a digital object 4, the editing rights of which currently belong to the first user 1, the server 3 waits for the response of the first user 1 to the request of the second user 2 for a certain time (1-15 minutes). In this case, if the first user 1 managed to respond to the request within a certain time and refused to transfer the rights to edit the digital object 4 to the second user 2, then the server 3 does not grant the rights to edit the digital object 4 to the second user 2. Otherwise, namely, if the first user 1 did not have time to respond to the request of the second user 2 or managed to transfer the editing rights to the second user 2, then with the help of the server 3, the rights to edit the digital object 4 are first revoked from the first user 1, and then grant the rights to edit the digital object 4 to the second user 2. After that, the server 3 sends a notification to the first user 1 that the rights to edit the digital object 4 have been revoked, and excludes the first user 1 from the co-editing environment 5. After the exclusion the first user 1 can be added to the viewing environment 9. After that, the current state of the digital object 4 is stored in memory 6 using the update module 8. Further, using the server 3, the rights to edit the digital object 4 are granted to the second user 2. Waiting for a response by the server 3 while are carried out for 1-15 minutes, and periodic saving of changes in the digital object 4 is carried out with a period of less than 1-15 minutes. In parallel, in the course of editing the digital object 4 after saving, continuously and / or with a certain periodicity, a copy of the visual display of at least one digital object 4 is created and the created copy is transferred to the viewing environment 9 using the server 3. After that, the resulting copy is displayed using the viewing environment 9. In this case, the digital object 4 is stored in the collaborative editing environment 5 included in the memory 6 of the server 3, and all actions performed by the server 3 are carried out using the processor 7 of the server 3.

[00065] The present application materials provide a preferred disclosure of the implementation of the claimed technical solution, which should not be used as limiting other, private embodiments of its implementation that do not go beyond the requested scope of legal protection and are obvious to specialists in the relevant field of technology.

Claims

Claim

1. A method for managing collaborative editing of digital objects, including the following steps:

• sending by the first user of a request to the server to obtain the rights to edit the digital object contained in the collaborative editing environment;

• granting by the server to the first user the rights to edit the digital object contained in the collaborative editing environment;

• a second user submitting a request to transfer rights to edit a digital object contained in a co-editing environment;

• waiting by the server for the first user's response to the second user's request for a certain time; at the same time, the first user within a certain time has the opportunity to answer one of the following options:

• transfer the rights to edit the digital object to the second user;

• reject a request to transfer rights to edit a digital object to a second user;

• do not respond to the request to transfer the rights to edit the digital object to the second user, and if the first user transferred the rights to edit the digital object to the second or did not respond to the request, using the server:

• revoke the rights to edit the digital object from the first user;

• grant rights to edit the digital object to the second user.

2. The method of managing joint editing of digital objects according to claim 1, characterized in that the second user's request to transfer rights to edit the digital object is sent directly to the first user and/or server.

3. The method of managing the joint editing of digital objects according to claim 1, characterized in that before the step of granting the right to edit the digital object to the second user, the edited digital object is saved using the update module.

4. The method of managing the joint editing of digital objects according to claim 1, characterized in that the stage of waiting for the response of the first user to the request of the second user is performed within 1-15 minutes.

22

5. The method of managing the joint editing of digital objects according to claim 1, characterized in that the digital objects are periodically saved using the update module.

6. The method of managing the joint editing of digital objects according to claim 5, characterized in that the digital objects are periodically saved with a period less than the waiting time for the first user's response to the second user's request.

7. The method for managing the joint editing of digital objects according to claim 1, characterized in that at the stage of revoking the rights to edit the digital object from the first user, a notification is sent to the first user that the rights to edit the digital object have been revoked using the server.

8. The method of managing the joint editing of digital objects according to claim 1, characterized in that after the stage of revoking the right to edit the object from the first user using the server:

• exclude the first user from the digital object co-editing environment;

• add the first user to the browsing environment.

9. The method for controlling co-editing of digital objects according to claim 8, characterized in that after saving at least one digital object, at least one digital object is displayed using the viewing environment without being able to edit it.

10. The method of managing the joint editing of digital objects according to claim 8, characterized in that in the process of editing a digital object by the second user:

• create a copy of the visual display of at least one digital object using the server;

• transfer the created copy to the viewing environment using the server;

• display the resulting copy using the viewing environment.

I. A digital object co-editing management system configured for at least two simultaneous users and including:

• a server that includes at least: a memory that includes at least one co-editing environment that includes at least one digital object; and o processor configured for: granting rights to edit a digital object contained in a co-editing environment; waiting for the response of the first user to the request of the second user to transfer the rights to edit the digital object within a certain time; and revoke rights to edit the digital object contained in the co-editing environment, with the co-editing environment configured in such a way that each user has the ability to:

• sending a request to the server to transfer rights to edit the digital object contained in the collaborative editing environment;

• Rejecting a request to transfer rights to another user to edit a digital object contained in a co-editing environment for a certain amount of time;

• transferring rights to another user to edit a digital object contained in a collaborative editing environment for a specified period of time;

• editing at least one digital object, provided that the user has been granted rights to edit this digital object using the server.

12. The control system for joint editing of digital objects according to claim. And, characterized in that the server includes an update module connected to the memory.

13. The digital object co-editing control system according to claim 12, characterized in that the update module is configured to save the edited digital objects.

14. Control system for collaborative editing of digital objects according to claim 1, characterized in that the server is configured in such a way that the waiting time for the first user's response to the second user's request is 1-15 minutes.

15. The digital object co-editing control system of claim 12, wherein the updater is configured to periodically save the digital objects.

16. The control system for collaborative editing of digital objects according to claim 15, characterized in that the update module periodically saves digital objects with a period less than the waiting time for the first user's response to the second user's request.

17. The digital object co-editing management system according to claim 1, characterized in that the server is configured to send notifications to users that the rights to edit the digital object have been revoked.

18. The control system for joint editing of digital objects according to claim. And, characterized in that the server includes a viewing environment associated with the collaborative editing environment, and the server is configured to:

• exclusion of users from the environment of collaborative editing of a digital object;

• adding users to the browsing environment.

19. The digital object co-editing control system according to claim 18, characterized in that the viewing environment is configured to display at least one digital object from the co-editing environment without allowing its editing, and the digital objects are displayed only with saved changes.

20. The control system for co-editing digital objects according to claim 18, characterized in that the viewing environment is configured to display at least one digital object from the co-editing environment without allowing its editing, and the digital objects are displayed with all the changes made to the digital objects .

25