A method for creating a shortcut for collaborative documents and related equipment

Abstract

The present invention provides a method and related equipment for creating shortcuts for collaborative documents. When a shortcut creation request is received, at least one collaborative document and each shortcut storage location of each collaborative document are determined; each collaborative document is verified. When each collaborative document passes the verification, a calling method corresponding to the number of collaborative documents is applied to create a shortcut entity for each collaborative document in each shortcut storage location corresponding to the collaborative document; for each collaborative document, operation permissions for the collaborative document are set for each user corresponding to each shortcut storage location of the collaborative document, and each shortcut entity of the collaborative document is written into a preset document table, thereby completing the creation of the collaborative document shortcut. By creating a shortcut for the collaborative document, the collaborative document can be directly accessed using the shortcut, without going through multiple jump steps, thereby improving user work efficiency.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method for creating a shortcut to a collaborative document and related equipment. Background Art

[0002] With the development of computer technology, electronic documents are widely used in life. People can save text, pictures, tables and other data through documents. The application of electronic documents makes people's lives more convenient.

[0003] To meet the needs of multiple people editing documents simultaneously, developers have developed a document that supports multiple people editing online. This type of document is called a collaborative document or online collaborative document. Currently, collaborative documents cannot create corresponding shortcuts. This means that when users open a collaborative document, they need to go through multiple steps to access it. This prevents users from quickly accessing the document, reducing their work efficiency. Summary of the Invention

[0004] In view of this, an embodiment of the present invention provides a method for creating a shortcut to a collaborative document and related equipment, which creates a shortcut for a collaborative document that can directly access the collaborative document. There is no need to go through multiple jump steps when accessing the collaborative document, thereby improving user work efficiency.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] A first aspect of the present invention discloses a method for creating a shortcut to a collaborative document, comprising:

[0007] When a shortcut creation request is received, determining at least one collaborative document and determining respective shortcut storage locations for each of the collaborative documents;

[0008] Verifying each collaborative document, and when each collaborative document passes verification, applying a calling method corresponding to the number of collaborative documents to create a shortcut entity in each shortcut storage location corresponding to each collaborative document;

[0009] For each collaborative document, the operation permissions of the collaborative document are set for each user corresponding to each shortcut storage location of the collaborative document, and each shortcut entity of the collaborative document is written into a preset document table to complete the creation of the shortcut of the collaborative document.

[0010] Optionally, in the above method, verifying each collaborative document includes:

[0011] Verify whether each collaborative document has sharing permissions;

[0012] When it is determined that each of the collaborative documents has sharing authority, determining gateway service parameters;

[0013] Verify whether the gateway service parameters are legal;

[0014] When it is determined that the gateway service parameters are legal, determining operator information based on the shortcut creation request;

[0015] Determine whether the operator corresponding to the operator information has creation authority;

[0016] When it is determined that the operator corresponding to the operator information has the creation permission, determining whether each of the shortcut storage locations has the permission to store shortcuts;

[0017] When it is determined that each of the shortcut storage locations has permission to store shortcuts, determining whether the number of collaborative documents is greater than a preset number;

[0018] When the number of collaborative documents is not greater than a preset number, it is determined that each of the collaborative documents passes verification.

[0019] Optionally, the above method uses an asynchronous call when the number of collaborative documents is greater than 1, and a synchronous call when the number of collaborative documents is equal to 1.

[0020] Optionally, the method described above, creating a shortcut entity in each shortcut storage location corresponding to each collaborative document, includes:

[0021] For each collaborative document, the document identifier of the collaborative document is determined, and a virtual file is created in each shortcut storage location corresponding to the collaborative document. The file identifier of each virtual file is bound to the document identifier of the collaborative document, and the title of each virtual file is linked to the title of the collaborative document to obtain a shortcut entity of the collaborative document in each shortcut storage location.

[0022] The above method may optionally further include:

[0023] Based on the calling method, generating a processing result corresponding to the shortcut creation request;

[0024] Based on the processing result, a document list containing information of each shortcut entity is obtained, and the document list is displayed to the user corresponding to the shortcut creation request.

[0025] The above method may optionally further include:

[0026] Get quick access request;

[0027] Determining a shortcut identifier in the shortcut access request, determining a document identifier bound to a shortcut entity corresponding to the shortcut identifier based on the document table, and determining a collaborative document to which the document identifier belongs as a target collaborative document;

[0028] determining, based on the authorization information of the target collaborative document, whether the user sending the quick access request has access rights to the target collaborative document;

[0029] When it is determined that the user who sent the quick access request has access authority to the target collaborative document, the target collaborative document is displayed to the user.

[0030] A second aspect of the present invention discloses a device for creating a shortcut to a collaborative document, comprising:

[0031] a first determining unit, configured to, upon receiving a shortcut creation request, determine at least one collaborative document and determine a storage location of each shortcut of each collaborative document;

[0032] a verification unit, configured to verify each of the collaborative documents, and when each of the collaborative documents passes the verification, apply a calling method corresponding to the number of collaborative documents to create a shortcut entity in each shortcut storage location corresponding to each collaborative document;

[0033] The setting unit is used to set the operation permissions of the collaborative document for each user corresponding to each shortcut storage location of the collaborative document, and write each shortcut entity of the collaborative document into a preset document table to complete the creation of the shortcut of the collaborative document.

[0034] In the above device, optionally, the verification unit includes:

[0035] A first verification subunit, configured to verify whether each of the collaborative documents has sharing permissions;

[0036] A first determining subunit is configured to determine gateway service parameters when it is determined that each of the collaborative documents has sharing authority;

[0037] A second verification subunit, configured to verify whether the gateway service parameters are legal;

[0038] a second determining subunit, configured to determine operator information based on the shortcut creation request when it is determined that the gateway service parameter is legal;

[0039] The first judgment subunit is used to judge whether the operator corresponding to the operator information has the creation authority;

[0040] A second judgment subunit is configured to, when it is determined that the operator corresponding to the operator information has the creation permission, judge whether each of the shortcut storage locations has the permission to store shortcuts;

[0041] a third judging subunit, configured to judge whether the number of collaborative documents is greater than a preset number when it is determined that each of the shortcut storage locations has permission to store shortcuts;

[0042] The fourth determining subunit is configured to determine whether each collaborative document has passed verification when the number of collaborative documents is not greater than a preset number.

[0043] Optionally, the above device may be configured such that when the number of collaborative documents is greater than 1, the calling mode is asynchronous calling; and when the number of collaborative documents is equal to 1, the calling mode is synchronous calling.

[0044] In the above device, optionally, the verification unit includes:

[0045] A creation subunit is configured to determine, for each collaborative document, a document identifier of the collaborative document, create a virtual file in each shortcut storage location corresponding to the collaborative document, bind the file identifier of each virtual file to the document identifier of the collaborative document, and link the title of each virtual file to the title of the collaborative document to obtain a shortcut entity of the collaborative document in each shortcut storage location.

[0046] The above device may optionally further include:

[0047] a generating unit, configured to generate a processing result corresponding to the shortcut creation request based on the calling method;

[0048] The first acquiring unit is configured to acquire a document list containing information of each of the shortcut entities based on the processing result, and present the document list to a user corresponding to the shortcut creation request.

[0049] The above device may optionally further include:

[0050] A second acquiring unit, configured to acquire a quick access request;

[0051] a second determining unit, configured to determine a shortcut identifier in the shortcut access request, determine a document identifier bound to a shortcut entity corresponding to the shortcut identifier based on the document table, and determine a collaborative document to which the document identifier belongs as a target collaborative document;

[0052] a third determining unit, configured to determine, based on the authorization information of the target collaborative document, whether the user sending the quick access request has access rights to the target collaborative document;

[0053] The display unit is configured to display the target collaborative document to the user when it is determined that the user who sends the quick access request has access authority to the target collaborative document.

[0054] A third aspect of the present invention discloses a storage medium, which includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the method for creating a shortcut to a collaborative document as described above.

[0055] A fourth aspect of the present invention discloses an electronic device comprising a memory and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by one or more processors to execute the method for creating a shortcut to a collaborative document as described above.

[0056] Compared with the prior art, the present invention has the following advantages:

[0057] The present invention provides a method and related equipment for creating shortcuts for collaborative documents. When a shortcut creation request is received, at least one collaborative document and each shortcut storage location for each collaborative document are determined. Each collaborative document is verified. When each collaborative document passes verification, a calling method corresponding to the number of collaborative documents is applied to create a shortcut entity for each collaborative document in each shortcut storage location corresponding to the collaborative document. For each collaborative document, operation permissions for the collaborative document are set for each user corresponding to each shortcut storage location of the collaborative document, and each shortcut entity of the collaborative document is written into a preset document table, thereby completing the creation of the collaborative document shortcut. By creating a shortcut for a collaborative document, a user can directly access the collaborative document using the shortcut, eliminating the need for multiple jump steps to directly access the collaborative document, thereby improving user work efficiency. Furthermore, shortcuts to collaborative documents can be created in multiple locations, thereby providing multiple access points to the collaborative document, making access to the collaborative document more convenient. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0059] Figure 1A flowchart of a method for creating a shortcut to a collaborative document provided by an embodiment of the present invention;

[0060] Figure 2 A flowchart of a method for accessing collaborative documents through shortcuts provided in an embodiment of the present invention;

[0061] Figure 3 A flow chart of a method for verifying each collaborative document provided by an embodiment of the present invention;

[0062] Figure 4 A schematic diagram illustrating a method for creating a shortcut to a collaborative document according to an embodiment of the present invention;

[0063] Figure 5 A schematic diagram of the structure of a shortcut for creating a collaborative document provided by an embodiment of the present invention;

[0064] Figure 6 A timing diagram of a method for creating a shortcut to a collaborative document provided by an embodiment of the present invention;

[0065] Figure 7 A schematic diagram of the structure of a device for creating a shortcut to a collaborative document provided by an embodiment of the present invention;

[0066] Figure 8 A schematic structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0067] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0068] In this application, the terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0069] Explanation of terms:

[0070] Private space: Your own space. Only you can use this space and operate the documents in this space.

[0071] Team space: A team space where team members can work on documents within the space.

[0072] Duplicate: A document formed after a document is copied. It is an independent document. Modifications to the document will not affect the content of the original document.

[0073] Current technologies for quick access to collaborative documents include favorites, quick access, copy creation, and document sharing. Favorites generally store important and classic documents, not for quick access. If non-important documents are also stored, there will be too many documents in the favorites, making them difficult to find and maintain. Quick access is generally used for quick access to documents and has a pinning function. It is located on the homepage of the document system. If a large number of documents are added, you need to flip through the pages to search, and there are certain restrictions on the number of documents managed. Copies can be created and stored in any authorized directory or team space, but copies are independent documents and will not change with changes to the original document. Because they exist independently, they take up a certain amount of storage space. Document sharing can be shared with specific users, groups, departments, etc., and is generally viewed in the directory where the user receives it. There are limitations on the location of access to documents. When a large number of files are received, it is more difficult to find documents that have been received in the past.

[0074] All of the above methods cannot directly access collaborative documents, and multiple steps such as searching are required to achieve collaborative document access, which easily reduces user work efficiency.

[0075] The present invention can be used in a wide variety of general-purpose or specialized computing environments or configurations. For example, personal computers, server computers, handheld or portable devices, tablet devices, multi-processor devices, and distributed computing environments including any of the above. The present invention can be implemented in a processing system, with the solution of the present invention being implemented through data exchange between the front-end, back-end, and gateway within the processing system.

[0076] Reference Figure 1 , which is a flow chart of a method for creating a shortcut to a collaborative document provided by an embodiment of the present invention, and is specifically described as follows:

[0077] S101: When a shortcut creation request is received, at least one collaborative document is determined and respective shortcut storage locations of each collaborative document are determined.

[0078] A shortcut creation request is a request generated when an operator needs to create a shortcut for a collaborative document. The shortcut creation request includes information about each collaborative document selected by the operator for which a shortcut is to be created, as well as information about the storage location selected by the operator for the shortcut to each collaborative document.

[0079] The shortcut creation request is parsed to determine at least one collaborative document for which a shortcut needs to be created and the respective shortcut storage locations of each collaborative document; the shortcut storage location is the storage location of the shortcut selected by the operator.

[0080] S102: Verify each collaborative document. When each collaborative document passes the verification, apply a calling method corresponding to the number of collaborative documents to create a shortcut entity in each shortcut storage location corresponding to each collaborative document.

[0081] Each collaborative document is verified. Only when all collaborative documents pass the verification will a shortcut entity be created for each collaborative document in each corresponding shortcut storage location. Furthermore, for each collaborative document, the shortcut entity in each shortcut storage location of the collaborative document is the access entry for the collaborative document. Therefore, there is only one location where the collaborative document is actually stored, but there are multiple entries to access the collaborative document.

[0082] It should be noted that different numbers of collaborative documents correspond to different calling methods. When the number of collaborative documents is greater than 1, the calling method is asynchronous calling; when the number of collaborative documents is equal to 1, the calling method is synchronous calling. It should be noted that asynchronous calling can generate shortcuts in batches, thereby reducing the time required to create multiple shortcuts.

[0083] A synchronous call can be understood as a synchronous request, where the required interface is returned after calling the interface once; an asynchronous call can be understood as an asynchronous request, where the interface is called twice and the required result is obtained by pulling.

[0084] Furthermore, when creating a shortcut entity for each collaborative document in each corresponding shortcut storage location, specifically, for each collaborative document, the document identifier of the collaborative document is determined, and a virtual file is created in each shortcut storage location corresponding to the collaborative document. The file identifier of each virtual file is bound to the document identifier of the collaborative document, and the title of each virtual file is linked to the title of the collaborative document, thereby obtaining a shortcut entity for the collaborative document in each shortcut storage location. It should be noted that the document identifier of a collaborative document is unique and can be understood as the source identifier of the collaborative document's content. The file identifier of a virtual file is also unique.

[0085] It should be noted that the collaborative document selected by the operator may be a shortcut document, and the file type of the collaborative document can be determined by the file type code. For example, when the file type code of the collaborative document is 5, the collaborative document is determined to be a shortcut document; illustratively, when the file type code is 1, the collaborative document can be determined to be an online document containing content that can be read and written. When the collaborative document is a shortcut document, it is necessary to determine the online document containing content that can be read and written corresponding to the collaborative document. Specifically, the identity identifier of the collaborative document can be used to determine it, and the identity identifier of the determined online document is used as the document identifier of the collaborative document. Exemplarily, collaborative document A is a shortcut access document, the identity identifier of collaborative document A is A1, and the online document containing content that can be read and written corresponding to A1 is B, and the identity identifier of online document B is B1. At this time, the document identifier of collaborative document A can be determined to be B1; preferably, when the collaborative document is an online collaborative document that supports read and write operations, the identity identifier of the online collaborative document is used as the document identifier of the collaborative document; it should be noted that the identity identifier is unique.

[0086] It should be noted that each shortcut entity of a collaborative document can be used as a shortcut document, or can be understood as a shortcut to a collaborative document. The shortcut entity can be placed in any authorized location and can appear in the file list like a normal file, which is convenient for query and classification. After clicking the shortcut, you can access the real document corresponding to the shortcut. The real document can be understood as a collaborative document that supports read and write operations.

[0087] S103: For each collaborative document, set the operation permission of the collaborative document for each user corresponding to each shortcut storage location of the collaborative document, and write each shortcut entity of the collaborative document into a preset document table to complete the creation of the collaborative document shortcut.

[0088] It should be noted that when there are multiple collaborative documents, the collaborative documents can be processed in batches using asynchronous calls, thereby shortening the processing time.

[0089] Collaborative documents can create shortcuts in private spaces, team spaces, and shortcuts. It should be noted that private spaces, team spaces, and shortcuts all contain corresponding root locations and different directory locations. When creating shortcuts for collaborative documents, operators can make choices based on actual needs.

[0090] It should be noted that different shortcut storage locations correspond to different users. For example, when the shortcut storage location is in the root location and / or different directory locations in the private space, the corresponding user is oneself, that is, the operator himself; when the shortcut storage location is in the team space, the corresponding user is the various members of the team space, and no examples will be given here.

[0091] When setting the operation authority for the collaborative document for each user, the operation authority at least includes read authority, and preferably, may also include write authority. Furthermore, after the user has the write authority, he or she may edit the content in the collaborative document.

[0092] The information of each shortcut entity of the collaborative document is written into a preset document table, which includes but is not limited to the file identifier of each shortcut entity and the document identifier bound to each shortcut entity.

[0093] It should be noted that each collaborative document shortcut entity has the functions of reading / editing, collecting, sharing, and creating copies.

[0094] After the collaborative document shortcuts are created, the collaborative document can be accessed through the collaborative document shortcuts. Each shortcut is an access entry to the collaborative document.

[0095] In the method provided by an embodiment of the present invention, upon receiving a shortcut creation request, at least one collaborative document and the respective shortcut storage locations for each collaborative document are determined; each collaborative document is verified, and when each collaborative document passes verification, a call method corresponding to the number of collaborative documents is applied to create a shortcut entity for each collaborative document in each corresponding shortcut storage location; for each collaborative document, operation permissions for the collaborative document are set for each user corresponding to each shortcut storage location of the collaborative document, and each shortcut entity of the collaborative document is written to a preset document table, thereby completing the creation of the collaborative document shortcut. By creating a shortcut for a collaborative document, a user can directly access the collaborative document using the shortcut, eliminating the need for multiple jump steps to directly access the collaborative document, thereby improving user work efficiency. Furthermore, shortcuts to collaborative documents can be created in multiple locations, thereby providing multiple access points to the collaborative document, making access to the collaborative document more convenient.

[0096] In the method provided by the embodiment of the present invention, in the process of creating shortcuts for each collaborative document, a processing result corresponding to the shortcut creation request is generated based on the calling method; based on the processing result, a document list containing information of each shortcut entity is obtained, and the document list is displayed to the user corresponding to the shortcut creation request. Furthermore, when the calling method is synchronous, the generated processing result contains a prompt message indicating that the creation is complete, and a document list containing information of each shortcut entity can be directly obtained. Furthermore, the document list can be understood as the document table described above; when the calling method is asynchronous, the processing result contains a task identifier corresponding to the shortcut creation request, and the progress query interface is called based on the task identifier to query the creation progress. When the creation progress is 100, it indicates that the creation is successful, and the document list can be obtained at this time.

[0097] The present invention can prompt the user that the shortcut of the selected collaborative document has been successfully created by displaying the acquired document list to the user, so that the user can intuitively see the information of the created shortcut, which is convenient for the user to manage the created shortcut.

[0098] In the method provided by the embodiment of the present invention, after creating shortcuts for each collaborative document, users can access the collaborative document through the shortcuts. The specific process is as follows: Figure 2 The specific instructions are as follows:

[0099] S201: Obtain a quick access request.

[0100] The quick access request may be a request generated when a user clicks any shortcut. The shortcut here may be understood as the shortcut entity mentioned above.

[0101] S202: Determine the shortcut identifier in the quick access request, determine the document identifier bound to the shortcut entity corresponding to the shortcut identifier based on the document table, and determine the collaborative document to which the document identifier belongs as the target collaborative document.

[0102] The shortcut identifier is the identity identifier of the shortcut entity clicked by the user. The document identifier bound to the identity identifier is determined in the document table. The document identifier bound to the identity identifier is the document source identifier of the shortcut entity. The document identifier is used to search for collaborative documents, and the collaborative document found is determined as the target collaborative document. Furthermore, the document identifier is the identity identification identifier of the target collaborative document.

[0103] S203. Based on the authorization information of the target collaborative document, determine whether the user sending the shortcut access request has the access rights to the target collaborative document; when it is determined that the user sending the shortcut access request has the access rights to the target collaborative document, execute S204; when it is determined that the user sending the shortcut access request does not have the access rights to the target collaborative document, execute S205.

[0104] The target collaborative document has authorization information, which includes permission information of users who can access and edit the document. Whether the user corresponding to the shortcut request has the access permission to the target collaborative document can be determined based on the authorization information.

[0105] S204: Display the target collaborative document to the user.

[0106] S205: Prompt the user that he does not have access rights.

[0107] It should be noted that after determining that the user has access rights to the target collaborative document, the target collaborative document can be loaded to be displayed to the user; after determining that the user does not have access rights to the target collaborative document, the user is prompted that he does not have access rights to the target collaborative document and cannot operate on the target collaborative document.

[0108] The method provided in the embodiment of the present invention supports different users using different shortcut entities to request access to collaborative documents. Furthermore, the content of the collaborative document will change with the editing operations of users with editing permissions. When accessing the collaborative document through a shortcut, the content of the document displayed to the user using the shortcut to access the collaborative document is the latest data.

[0109] Users can click on any shortcut entity to request access to collaborative documents. Different users can request access to collaborative documents through different shortcut entities, ensuring that different users can access collaborative documents from different locations, ensuring the collaboration of collaborative documents, and when accessing collaborative documents through shortcut entities, they can directly access collaborative documents without going through multiple steps of jumping, which can effectively improve user work efficiency.

[0110] In the process of creating a shortcut to collaborative documents using the present invention, each collaborative document needs to be verified. For a specific flow chart, please refer to Figure 3 , the specific instructions are as follows:

[0111] S301 , verify whether all collaborative documents have sharing permissions; if it is determined that all collaborative documents have sharing permissions, execute S302 ; otherwise, execute S309 .

[0112] Obtain document information of each collaborative document, which includes sharing permission information of the collaborative document. Based on the document information of each collaborative document, determine whether each collaborative document has sharing permission. If each collaborative document has sharing permission, execute S302; otherwise, execute S309.

[0113] S302: Determine gateway service parameters.

[0114] Gateway service parameters include but are not limited to gateway address, interface parameters and other information.

[0115] S303, verify whether the gateway service parameters are legal; when it is determined that the gateway service parameters are legal, execute S304; otherwise, execute S309.

[0116] You can verify whether the gateway service parameters are legal by calling the http interface of the shortcut provided by the gateway service. Further, verifying whether the gateway service parameters are legal can also be understood as the gateway service verifying the legality of the input parameters.

[0117] S304: Determine operator information based on the shortcut creation request.

[0118] Operator information includes but is not limited to user name, user ID and other information.

[0119] S305. Determine whether the operator corresponding to the operator information has the creation permission. If it is determined that the operator corresponding to the operator information has the creation permission, execute S306; otherwise, execute S309.

[0120] The shortcut service can be called through the Rpc (Remote Procedure Call) interface provided by the shortcut to verify whether the operator has the authority to create each collaborative document.

[0121] S306: Determine whether each shortcut storage location has permission to store shortcuts; if it is determined that each shortcut storage location has permission to store shortcuts, execute S307; otherwise, execute S309.

[0122] For each shortcut storage location of each collaborative document, it can be determined whether the shortcut storage location has the permission to save shortcuts based on the storage setting information of the shortcut storage location. It should be noted that the storage setting information includes information about the file types that the storage location can save; when the storage setting information does not contain information about the shortcut file type, it can be determined that the shortcut storage location does not have the permission to store shortcuts; when the storage setting information contains information about the shortcut file type, it can be determined that the shortcut storage location has the permission to store shortcuts.

[0123] S307 , determining whether the number of collaborative documents is greater than a preset number; when the number of collaborative documents is not greater than the preset number, executing S308 ; otherwise, executing S309 .

[0124] The preset number can be set according to actual needs. The preset number can also be understood as a threshold. The preset number can limit the maximum number of collaborative documents for creating shortcuts. It can be set according to the system's operating capabilities, thereby ensuring the reasonable allocation of system resources and avoiding the situation where the system crashes due to excessive numbers, so that the system can be in the optimal operating state. In addition, it can also avoid the situation where a large number of collaborative documents are maliciously selected for creation.

[0125] S308: Determine whether each collaborative document has passed verification.

[0126] S309: Feedback creation failure information to the operator corresponding to the shortcut creation request.

[0127] In the method provided by the embodiment of the present invention, by verifying each collaborative document from multiple dimensions, after each collaborative document passes the verification, the smoothness of subsequent creation of shortcuts for the collaborative document and the stability of the creation environment can be ensured.

[0128] In order to further illustrate the implementation principle of the present invention, the embodiment of the present invention also provides a principle architecture diagram, specifically referring to Figure 4 , used to further illustrate the implementation principle of the method provided by the present invention, the specific description is as follows:

[0129] To create a shortcut, you can select a single document or multiple documents. The selected document is a collaborative document. You can drag and drop or manually select a storage location. The storage locations include Private Space, Team Space, and Quick Access. These three areas each include a root location and different directories. You can place the shortcut in the root location or the desired directory. After making your selection, the shortcut is created. The frontend first checks whether the selected collaborative document has permission to create a shortcut, or whether it has permission to share. If permission is granted, the backend shortcut creation API is called. If permission is denied, an error message is generated. Upon receiving the request, the backend shortcut creation API verifies the validity of the input parameters, verifies whether the collaborative document has permission to create a shortcut, and verifies permission to store the shortcut in the target location. Once all verifications are passed, the shortcut creation begins. When creating shortcuts for collaborative enclosures, you must also determine whether the document is a single collaborative document or multiple collaborative documents. Single collaborative documents are created synchronously, using a synchronous call. After creation is complete, a success status is returned, with the TaskId field empty. If there are multiple collaborative documents, asynchronous creation is used, that is, a shortcut is created using asynchronous calls. When the processing result is returned, the TaskId in the processing result cannot be empty. After the front-end receives the returned processing result, it needs to call the background progress query interface in a cyclic manner according to the TaskId. When the progress value reaches 100, it indicates that the creation is complete.

[0130] Furthermore, the present invention also provides a schematic diagram of the structure of the shortcut to the collaborative document created, referring to Figure 5 , the specific instructions are as follows:

[0131] When creating shortcuts for collaborative documents, the operations include creating shortcuts for a single document and creating shortcuts for batches of documents. The storage locations of the created shortcuts include private space, team space, and quick access. The private space includes the root location and different directories, the team space includes the root location and different directories, and the quick access includes the root location and different directories. The created shortcuts have the functions of ordinary documents, such as reading / editing, collecting, sharing, and creating copies.

[0132] To illustrate the execution process of the present invention in detail, the embodiment of the present invention also provides a timing example diagram, referring to Figure 6 , the specific instructions are as follows:

[0133] The user creates a shortcut through the front-end, selects the location where the shortcut file will be stored, begins creation, and verifies whether the collaborative file has permission to be shared and created. If the collaborative file has permission to be shared and created, the verification passes, and the HTTP interface provided by the gateway service is called to verify the legitimacy of the input parameters. If the gateway service verifies the legitimacy of the input parameters, the verification passes, and the RPC interface provided by the shortcut is called. The shortcut service verifies whether the current person (the person applying to create the shortcut) has permission to create a shortcut for the collaborative file. The permission service can be called to verify whether the current person has permission to create a shortcut for the collaborative file. If the current person has permission to create a shortcut, the verification passes, verifies the permission for the shortcut storage location, and returns the verification result for the storage location. Verify whether the number of collaborative files exceeds the maximum threshold. If the number of collaborative files does not exceed the maximum threshold, a single document is called synchronously, and multiple documents are called asynchronously using MQ. Both synchronous and asynchronous methods execute the same shortcut creation method, asynchronously sending MQ, subscribing to MQ, and calling the interface for creating the shortcut method. The shortcut creation method generates a corresponding shortcut entity based on the incoming or selected collaborative file. If the collaborative file is a shortcut, it is necessary to query the ID of the target file corresponding to the collaborative file. The target file is the file containing the data displayed to the user. The source ID of the shortcut is the ID of the target file, the title is empty, and the file type is shortcut. After that, a transaction is started, the shortcut entities are executed to write batches to the document table, and the execution results are returned. If the target storage location is a team space, the team space members need to be queried. If the target storage location is a team space directory, the members corresponding to the team space directory need to be queried. The permission interface of the permission service is called to authorize the members of the team space or directory to read the original file. After the permission service successfully processes the file, it returns the processing result. The target storage location here is illustrated with the team space as an example, and other spaces can be implemented. If the permission service fails to process, the shortcut service will send MQ asynchronously for authorization, and complete the authorization with eventual consistency. After all the executions are completed, the processing progress value needs to be recorded in the cache and the processing result is returned to the gateway service. The gateway service returns it to the front end. The front end determines whether the TaskId in the result is empty. If it is empty, it is a synchronous operation and the user is directly prompted to complete the creation. If the TaskId is not empty, the front end needs to pass in the TaskId and call the progress query interface provided by the gateway to check the completion status. If the progress value is 100, the creation is completed and prompted to the user.

[0134] The synchronous creation and asynchronous creation in the present invention are explained. In synchronous creation, after the shortcut creation is completed, the shortcut file ID list is returned, but the TaskId is not returned. The front end cannot obtain the TaskID, that is, the TaskId is empty. In this way, the shortcut ID list can be directly obtained to query the shortcut document list. In asynchronous creation, because the creation time is relatively long, the TaskId is returned first, and the progress value is initially 0. The front end uses the TaskId to call the creation progress interface. When the progress reaches 100, the query result will include the shortcut file ID list. In this way, the shortcut ID list can be obtained to query the shortcut document list.

[0135] Furthermore, TaskId is an identifier of an opened transaction, and may also be an identifier of a process for creating a shortcut for a collaborative document selected by a user. TaskId is a 20-digit non-repeating string that serves as a key.

[0136] When the TaskId is passed in and the progress query interface provided by the gateway is called, the progress query interface uses the TaskId as the key to query the cache for progress. If it is not completed, there is only the progress value. After completion, the progress value is 100 and also contains a list of shortcut IDs.

[0137] Example of returned results:

[0138]

[0139] The present invention can batch create shortcuts for collaborative documents, thereby creating multiple access portals for collaborative documents. Collaborative documents can be directly accessed through shortcuts without the need for jump steps, providing users with a more convenient access method and improving user work efficiency.

[0140] and Figure 1 Corresponding to the method shown, an embodiment of the present invention further provides a device for creating a shortcut to a collaborative document, which can be applied in a processing system, and is used to support Figure 1 The implementation of the method shown in life, refer to Figure 7 , is a schematic diagram of the structure of the device, and the specific description is as follows:

[0141] A first determining unit 401 is configured to, upon receiving a shortcut creation request, determine at least one collaborative document and determine a storage location for each shortcut of each collaborative document;

[0142] A verification unit 402 is configured to verify each collaborative document and, when each collaborative document passes verification, create a shortcut entity for each collaborative document in each shortcut storage location corresponding to the collaborative document using a calling method corresponding to the number of collaborative documents;

[0143] The setting unit 403 is used to set the operation permissions of each collaborative document for each user corresponding to each shortcut storage location of the collaborative document, and write each shortcut entity of the collaborative document into a preset document table to complete the creation of the shortcut of the collaborative document.

[0144] In the method provided by an embodiment of the present invention, upon receiving a shortcut creation request, at least one collaborative document and the respective shortcut storage locations for each collaborative document are determined; each collaborative document is verified, and when each collaborative document passes verification, a call method corresponding to the number of collaborative documents is applied to create a shortcut entity for each collaborative document in each corresponding shortcut storage location; for each collaborative document, operation permissions for the collaborative document are set for each user corresponding to each shortcut storage location of the collaborative document, and each shortcut entity of the collaborative document is written to a preset document table, thereby completing the creation of the collaborative document shortcut. By creating a shortcut for a collaborative document, a user can directly access the collaborative document using the shortcut, eliminating the need for multiple jump steps to directly access the collaborative document, thereby improving user work efficiency. Furthermore, shortcuts to collaborative documents can be created in multiple locations, thereby providing multiple access points to the collaborative document, making access to the collaborative document more convenient.

[0145] In another embodiment provided by the present invention, the verification unit 402 of the device includes:

[0146] A first verification subunit, configured to verify whether each of the collaborative documents has sharing permissions;

[0147] A first determining subunit is configured to determine gateway service parameters when it is determined that each of the collaborative documents has sharing authority;

[0148] A second verification subunit, configured to verify whether the gateway service parameters are legal;

[0149] a second determining subunit, configured to determine operator information based on the shortcut creation request when it is determined that the gateway service parameter is legal;

[0150] The first judgment subunit is used to judge whether the operator corresponding to the operator information has the creation authority;

[0151] A second judgment subunit is configured to, when it is determined that the operator corresponding to the operator information has the creation permission, judge whether each of the shortcut storage locations has the permission to store shortcuts;

[0152] a third judging subunit, configured to judge whether the number of collaborative documents is greater than a preset number when it is determined that each of the shortcut storage locations has permission to store shortcuts;

[0153] The fourth determining subunit is configured to determine whether each collaborative document has passed verification when the number of collaborative documents is not greater than a preset number.

[0154] In another embodiment provided by the present invention, the device includes: when the number of collaborative documents is greater than 1, the calling mode is asynchronous calling; when the number of collaborative documents is equal to 1, the calling mode is synchronous calling.

[0155] In another embodiment provided by the present invention, the verification unit 402 of the device includes:

[0156] A creation subunit is configured to determine, for each collaborative document, a document identifier of the collaborative document, create a virtual file in each shortcut storage location corresponding to the collaborative document, bind the file identifier of each virtual file to the document identifier of the collaborative document, and link the title of each virtual file to the title of the collaborative document to obtain a shortcut entity of the collaborative document in each shortcut storage location.

[0157] In another embodiment provided by the present invention, the device further comprises:

[0158] a generating unit, configured to generate a processing result corresponding to the shortcut creation request based on the calling method;

[0159] The first acquiring unit is configured to acquire a document list containing information of each of the shortcut entities based on the processing result, and present the document list to a user corresponding to the shortcut creation request.

[0160] In another embodiment provided by the present invention, the device further comprises:

[0161] A second acquiring unit, configured to acquire a quick access request;

[0162] a second determining unit, configured to determine a shortcut identifier in the shortcut access request, determine a document identifier bound to a shortcut entity corresponding to the shortcut identifier based on the document table, and determine a collaborative document to which the document identifier belongs as a target collaborative document;

[0163] a third determining unit, configured to determine, based on the authorization information of the target collaborative document, whether the user sending the quick access request has access rights to the target collaborative document;

[0164] The display unit is configured to display the target collaborative document to the user when it is determined that the user who sends the quick access request has access authority to the target collaborative document.

[0165] An embodiment of the present invention further provides a storage medium, which includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the above-mentioned method for creating a shortcut to the collaborative document.

[0166] The embodiment of the present invention further provides an electronic device, the structural diagram of which is shown in FIG. Figure 8 As shown, it specifically includes a memory 601 and one or more instructions 602, wherein the one or more instructions 602 are stored in the memory 601 and are configured to be executed by one or more processors 603 to execute the one or more instructions 602 to execute the method for creating a shortcut to the above-mentioned collaborative document.

[0167] The specific implementation processes and derivative methods of the above embodiments are all within the protection scope of the present invention.

[0168] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple. For relevant parts, refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without expending creative work.

[0169] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0170] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for creating a shortcut for a collaborative document, characterized in that: include: When a shortcut creation request is received, determining at least one collaborative document and determining respective shortcut storage locations for each of the collaborative documents; Verifying each collaborative document, and when each collaborative document passes verification, applying a calling method corresponding to the number of collaborative documents to create a shortcut entity in each shortcut storage location corresponding to each collaborative document; For each collaborative document, setting operation permissions for each user corresponding to each shortcut storage location of the collaborative document, and writing each shortcut entity of the collaborative document into a preset document table, thereby completing the creation of the shortcut for the collaborative document; The verifying of each of the collaborative documents includes: verifying whether each of the collaborative documents has sharing permissions; when it is determined that each of the collaborative documents has sharing permissions, determining gateway service parameters; verifying whether the gateway service parameters are legal; when it is determined that the gateway service parameters are legal, determining operator information based on the shortcut creation request; judging whether the operator corresponding to the operator information has creation permissions; when it is determined that the operator corresponding to the operator information has creation permissions, judging whether each of the shortcut storage locations has permissions to store shortcuts; when it is determined that each of the shortcut storage locations has permissions to store shortcuts, judging whether the number of collaborative documents is greater than a preset number; when the number of collaborative documents is not greater than the preset number, judging that each of the collaborative documents has passed the verification; When the number of collaborative documents is greater than 1, the calling mode is asynchronous calling; when the number of collaborative documents is equal to 1, the calling mode is synchronous calling; The step of creating a shortcut entity for each collaborative document in each shortcut storage location corresponding to the collaborative document includes: determining a document identifier for each collaborative document, creating a virtual file in each shortcut storage location corresponding to the collaborative document, binding the file identifier of each virtual file to the document identifier of the collaborative document, and linking the title of each virtual file to the title of the collaborative document to obtain a shortcut entity for the collaborative document in each shortcut storage location.

2. The method according to claim 1, characterized in that Also includes: Based on the calling method, generating a processing result corresponding to the shortcut creation request; Based on the processing result, a document list containing information of each shortcut entity is obtained, and the document list is displayed to the user corresponding to the shortcut creation request.

3. The method according to claim 1, characterized in that Also includes: Get quick access request; Determining a shortcut identifier in the shortcut access request, determining a document identifier bound to a shortcut entity corresponding to the shortcut identifier based on the document table, and determining a collaborative document to which the document identifier belongs as a target collaborative document; determining, based on the authorization information of the target collaborative document, whether the user sending the quick access request has access rights to the target collaborative document; When it is determined that the user who sent the quick access request has access authority to the target collaborative document, the target collaborative document is displayed to the user.

4. A device for creating a shortcut to a collaborative document, characterized in that: include: a first determining unit, configured to, upon receiving a shortcut creation request, determine at least one collaborative document and determine a storage location of each shortcut of each collaborative document; a verification unit, configured to verify each of the collaborative documents, and when each of the collaborative documents passes the verification, apply a calling method corresponding to the number of collaborative documents to create a shortcut entity in each shortcut storage location corresponding to each collaborative document; a setting unit configured to set, for each collaborative document, the operation permissions of the collaborative document for each user corresponding to each shortcut storage location of the collaborative document, and write each shortcut entity of the collaborative document into a preset document table to complete the creation of the shortcut of the collaborative document; The verification unit includes: a first verification subunit, a first determination subunit, a second verification subunit, a second determination subunit, a first judgment subunit, a second judgment subunit, a third judgment subunit and a fourth determination subunit; The first verification subunit is used to verify whether each of the collaborative documents has sharing permissions; The first determining subunit is configured to determine a gateway service parameter when it is determined that each of the collaborative documents has sharing authority; The second verification subunit is used to verify whether the gateway service parameters are legal; The second determining subunit is configured to determine operator information based on the shortcut creation request when it is determined that the gateway service parameter is valid; The first judgment subunit is used to judge whether the operator corresponding to the operator information has the creation authority; The second judgment subunit is configured to judge whether each of the shortcut storage locations has permission to store shortcuts when it is determined that the operator corresponding to the operator information has permission to create shortcuts; The third judgment subunit is configured to judge whether the number of collaborative documents is greater than a preset number when it is determined that each of the shortcut storage locations has the permission to store shortcuts; The fourth determining subunit is configured to determine that each collaborative document has passed verification when the number of collaborative documents is not greater than a preset number; when the number of collaborative documents is greater than 1, the calling mode is asynchronous calling; and when the number of collaborative documents is equal to 1, the calling mode is synchronous calling; The verification unit includes: creating a subunit; The creation subunit is configured to determine, for each collaborative document, a document identifier of the collaborative document, create a virtual file in each shortcut storage location corresponding to the collaborative document, bind the file identifier of each virtual file to the document identifier of the collaborative document, and link the title of each virtual file to the title of the collaborative document to obtain a shortcut entity of the collaborative document in each shortcut storage location.

5. A storage medium, characterized in that The storage medium includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the method for creating a shortcut to a collaborative document according to any one of claims 1 to 3.

6. An electronic device, characterized in that: The system comprises a memory and one or more instructions, wherein the one or more instructions are stored in the memory and configured to execute the method for creating a shortcut to a collaborative document according to any one of claims 1 to 3 by one or more processors.

Images