A content management method, system, device and storage medium

Abstract

This invention relates to a content management method, system, device, and storage medium. The method includes: upon receiving a target replication instruction, obtaining the target snapshot content and content source identifier of the target replication snapshot from a public protocol area; storing the target snapshot content as a target replication document in a private workspace, and marking the content source identifier onto the target replication document; upon receiving a content editing instruction, updating the target content in the target replication document; and upon receiving a content publishing instruction, publishing the target replication document to a snapshot publishing space matching the content source identifier, obtaining a target publishing snapshot, and marking the content source identifier onto the target publishing snapshot. The technical solution of this invention can physically isolate the content editing state from the publishing state while automatically aggregating multiple versions obtained through distributed collaboration, improving the security and management efficiency of multi-version content.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a content management method, system, device and storage medium. Background Technology

[0002] As internet content creation shifts from centralized production to decentralized collaboration, users are not only consumers of content but also increasingly becoming secondary creators and revisers. Under this trend, effectively managing massive amounts of derivative versions and tracking the complete content genealogy has become a core challenge for current content management technologies.

[0003] The current mainstream content management and version control technologies mainly include: code version control systems represented by Git / GitHub, where when a user performs a fork operation on a repository, the system creates a complete copy of the repository in the user's namespace. This copy has an independent URL (Uniform Resource Locator) and storage space. If the maintainer of the derived repository wants to merge the changes back into the original repository, they need to actively initiate a merge request, which is then manually reviewed by the original repository owner to decide whether to accept the merge; online document collaboration platforms represented by Notion and Google Docs, which adopt a "real-time collaboration" model, allowing multiple users to edit the same document simultaneously; wiki systems represented by MediaWiki, which adopt a "single source" model, where all users collaboratively edit the same page; and CMS (Content Management System), such as WordPress, which primarily serves content publishing and typically lacks comprehensive version management capabilities.

[0004] However, in the aforementioned existing technologies, code version control systems, which handle discrete modifications of the same content, do not provide a channel for actively counting all derived versions and performing reverse aggregation of each version. This makes it difficult to achieve unified management of multiple versions and easily leads to version omissions or losses. Furthermore, online document collaboration platforms and wiki systems tightly couple the editing and publishing states of content, making it impossible to save all versions generated during the editing process. Therefore, the content management methods provided by existing technologies cannot adequately guarantee the security of content generated by distributed editing. Summary of the Invention

[0005] This invention provides a content management method, system, device, and storage medium, aiming to achieve physical isolation between the content editing state and the publishing state, while automatically aggregating multiple versions obtained through distributed collaboration, thereby improving the security and management efficiency of multi-version content.

[0006] In a first aspect, embodiments of the present invention provide a content management method, including: Upon receiving a target replication instruction, retrieve the target snapshot content and content source identifier from the public protocol area; In the private workspace, the target snapshot content is stored as a target replica document, and the content source identifier is marked to the target replica document; Upon receiving a content editing instruction associated with the target replica document, the target content of the target replica document is updated according to the content editing instruction; Upon receiving a content publishing instruction associated with the target replica document, the target replica document with the updated target content is published to the snapshot publishing space in the public protocol area that matches the content source identifier, thereby obtaining a target publishing snapshot, and the content source identifier is marked on the target publishing snapshot.

[0007] Optionally, the content source identifier includes: a snapshot source space identifier, used to mark the snapshot publishing space of the target replicated snapshot in the public protocol area; The step of marking the content source identifier to the target replica document includes: The snapshot source space identifier is marked as the document source space identifier of the target replicated document; The step of tagging the content source identifier to the target published snapshot includes: The document source space identifier of the target replicated document is marked as the snapshot source space identifier of the target published snapshot.

[0008] Optionally, the content source identifier includes: the snapshot publication identifier of the target replica snapshot in the public protocol area; The step of marking the content source identifier to the target replica document includes: The snapshot publication identifier is marked as the document modification source identifier of the target replicated document; The step of tagging the content source identifier to the target published snapshot includes: Mark the document modification source identifier of the target replicated document as the snapshot modification source identifier of the target published snapshot; After marking the document modification source identifier of the target replicated document as the snapshot modification source identifier of the target published snapshot, the method further includes: Update the document modification source identifier of the target copied document to the snapshot publication identifier of the target published snapshot in the public protocol area.

[0009] Optionally, the step of marking the content source identifier to the target replica document further includes: The snapshot publication identifier is marked as the document replication source identifier of the target replicated document; The step of marking the content source identifier to the target published snapshot also includes: The document replication source identifier of the target replicated document is marked as the snapshot replication source identifier of the target published snapshot.

[0010] Optionally, after publishing the target replica document with the updated target content to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining the target publishing snapshot, and marking the content source identifier to the target publishing snapshot, the method further includes: Upon receiving a contribution statistics instruction for the target published snapshot, the target replica snapshot is obtained based on the snapshot replica source identifier of the target published snapshot; The content contribution of the target published snapshot is calculated by comparing and calculating the content of the target published snapshot with the target replicated snapshot. Repeatedly execute the process of obtaining the target replica snapshot based on the snapshot replica source identifier of the target replica snapshot and calculating the content contribution, until the target replica snapshot with an empty snapshot replica source identifier is obtained, and calculate the content contribution based on the content of the target snapshot of the target replica snapshot with an empty snapshot replica source identifier.

[0011] Optionally, the step of performing content comparison calculations on the target published snapshot and the target replicated snapshot to obtain the content contribution of the target published snapshot includes: The target published snapshot and the target replicated snapshot are respectively subjected to content structuring processing to obtain first content structure data and second content structure data; Based on the second content structure data, obtain the newly added nodes, modified nodes, and deleted nodes in the first content structure data; According to the preset contribution rules, the newly added node, the modified node, and the deleted node are weighted and calculated to obtain the content contribution of the target published snapshot.

[0012] Optionally, after publishing the target replica document with the updated target content to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining the target publishing snapshot, and marking the content source identifier to the target publishing snapshot, the method further includes: Mark the current timestamp as the spatial update timestamp of the snapshot publishing space; After updating the target content of the target replicated document according to the content editing instructions, the method further includes: Mark the current timestamp as the document update timestamp of the target replicated document; Upon receiving a batch release instruction associated with the target replica document, obtain the document update timestamp and the document source space identifier of the target replica document; If the document source space identifier is not empty, obtain the space update timestamp of the snapshot publishing space that matches the document source space identifier; If it is determined that the document update timestamp is later than the space update timestamp, the target replica document is published to the snapshot publishing space to obtain the target published snapshot.

[0013] Secondly, embodiments of the present invention provide a content management system, including: a content management device, a public protocol area, and a private work area; The content management device is used for: Upon receiving a target replication instruction, the target snapshot content and content source identifier of the target replication snapshot are obtained from the public protocol area. In the private workspace, the target snapshot content is stored as a target replica document, and the content source identifier is marked on the target replica document; Upon receiving a content editing instruction associated with the target replica document, the target content of the target replica document is updated according to the content editing instruction; Upon receiving a content publishing instruction associated with the target replica document, the target replica document with the updated target content is published to the snapshot publishing space in the public protocol area that matches the content source identifier, thereby obtaining a target publishing snapshot, and the content source identifier is marked on the target publishing snapshot.

[0014] Thirdly, embodiments of the present invention provide a content management device, including: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the content management method provided in any embodiment of the present invention.

[0015] Fourthly, embodiments of the present invention provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform the content management method provided in any embodiment of the present invention.

[0016] This invention provides a content management method, system, device, and storage medium. Upon receiving a target replication instruction, it obtains the target snapshot content and content source identifier of the target replication snapshot from the public protocol area, stores the target snapshot content as a target replication document in the private workspace, and marks the content source identifier onto the target replication document. Upon receiving a content editing instruction associated with the target replication document, it updates the target content of the target replication document according to the content editing instruction. Upon receiving a content publishing instruction associated with the target replication document, it publishes the target replication document with updated target content to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining a target publishing snapshot, and marking the content source identifier onto the target publishing snapshot. This overcomes the deficiencies of existing technologies in managing multiple versions of content, achieves physical isolation between the content editing state and the publishing state, and automatically aggregates multiple versions obtained through distributed collaboration, thereby improving the security and management efficiency of multi-version content. Attached Figure Description

[0017] Figure 1 A flowchart of a content management method provided in Embodiment 1 of the present invention; Figure 2 This is a schematic diagram of a snapshot version chain in the same snapshot publishing space provided in Embodiment 1 of the present invention; Figure 3 This is a schematic diagram of a snapshot contribution tracing version chain provided in Embodiment 1 of the present invention; Figure 4 This is a schematic diagram of the structure of a content management system provided in Embodiment 2 of the present invention; Figure 5 This is a schematic diagram of the structure of a content management device provided in Embodiment 3 of the present invention. Detailed Implementation

[0018] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0019] Example 1 Figure 1 This is a flowchart of a content management method provided in Embodiment 1 of the present invention. This embodiment is applicable to the management of content generated by distributed editing. The method can be executed by a content management device, which can be implemented by hardware and / or software and is generally integrated into an electronic device, such as a computer device. The method specifically includes: Step 110: Upon receiving the target replication instruction, obtain the target snapshot content and content source identifier of the target replication snapshot from the public protocol area.

[0020] The public protocol area is a pre-defined area for storing and displaying user-published content. Once content is published to the public protocol area, it creates an immutable snapshot, which can be accessed by any user. The private workspace is a pre-defined area for users to edit and manage content. Unpublished content and / or content copied from the public protocol area can be stored as editable documents in the user's private workspace, and each private workspace and its documents can only be accessed by authorized users. Therefore, based on the physical isolation between the public protocol area and the private workspace, the security and reliability management of content publishing and editing states can be effectively achieved, ensuring the traceability of each version.

[0021] Specifically, a target forgery command can be used to instruct a user with content editing permissions to retrieve snapshot content published in the public protocol area to their private workspace. The target forgery snapshot is the snapshot whose content the target forgery command needs to retrieve. The target snapshot content can include the complete content of the target forgery snapshot. Typically, when a user with content editing permissions needs to edit the content of a target forgery snapshot in the public protocol area, they can initiate a request through corresponding operations, thereby generating a corresponding target forgery command. This command then copies the complete content of the target forgery snapshot to a private workspace accessible to the user, creating a new document for the user to edit.

[0022] Furthermore, each target replica snapshot is also marked with a content source identifier to indicate the content source of the target replica snapshot. This typically includes the snapshot of the content source and / or the publication and storage location of the snapshot in the public protocol area. Accordingly, when any target replica snapshot is a snapshot of a document initially created by a user in a private workspace and then published to the public protocol area, its content source identifier can be used to mark itself and / or its spatial location in the public protocol area; when any target replica snapshot is a document obtained and edited by a user by replicating other snapshots from the public protocol area before being published to the public protocol area, its content source identifier can be used to mark the other replicated snapshots and / or the spatial location of that snapshot in the public protocol area.

[0023] Step 120: In the private workspace, store the target snapshot content as a target replica document and mark the content source identifier to the target replica document.

[0024] The target copied document can be a document obtained through copying, whose initial content is completely consistent with the target snapshot content.

[0025] Specifically, after obtaining the target snapshot content and content source identifier of the target replica snapshot in the public protocol area, the target snapshot content can be directly stored as the content of the target replica document in the corresponding user's private workspace, completing one replication of the content; at this time, the content source of the target replica document can inherit the content source of the target replica snapshot, so it can be marked according to the content source identifier.

[0026] Step 130: Upon receiving a content editing instruction associated with the target replica document, update the target content of the target replica document according to the content editing instruction.

[0027] Content editing commands are instructions used to modify the content of a document. Target content update is the operation of updating the target copied document based on the changes made in the content editing commands.

[0028] Specifically, users can edit document content in their private workspaces with access and editing permissions, generating corresponding content editing instructions. When a content editing instruction associated with the target replicated document is received, the target content of the replicated document is updated according to the instruction, so that the current content of the document is updated accordingly based on the user's editing operation.

[0029] It should be noted that the content editing commands associated with the target replicated document are not limited to those that edit the initial content of the target replicated document when it is first created in the private workspace. They can also include editing commands for the target replicated document after multiple updates to its target content. Typically, once the target replicated document is first created in the private workspace, it will remain editable. Any editing operation performed by the user within their permissions will trigger an update to the target content, ensuring that each change caused by the user's editing operation takes effect on the target replicated document, ultimately resulting in the latest updated version of the target replicated document.

[0030] Step 140: Upon receiving a content publishing instruction associated with the target replica document, publish the target replica document with updated target content to the snapshot publishing space in the public protocol area that matches the content source identifier, obtain the target publishing snapshot, and mark the content source identifier to the target publishing snapshot.

[0031] The content publishing instruction can be used to publish documents from a private workspace to a public protocol area to create a snapshot. The snapshot publishing space can be the space in the public protocol area used for publishing and storing snapshots. The target publishing snapshot can be the snapshot created by publishing a target copy of the document to the public protocol area.

[0032] Specifically, users can publish a target replica document after editing its content, generating a corresponding content publishing instruction. When a content publishing instruction associated with the target replica document is received, the target replica document with the latest updated content can be published.

[0033] Furthermore, the public protocol area can store and display a large number of snapshots, each requiring a portion of the public protocol area's snapshot publishing space. Since the target replica document inherits the content source identifier of the target replica snapshot, the target published snapshot formed when the target replica document is published to the public protocol area can be stored and displayed in the corresponding snapshot publishing space based on the content source identifier. This allows each snapshot publishing space in the public protocol area to store snapshots with the same content source identifier, thereby achieving aggregated management of multiple versions of snapshots based on the same original content within the same snapshot publishing space.

[0034] Furthermore, since the content source of the target release snapshot is the target forged document, it can continue to inherit the content source identifier. The target release snapshot marked with the content source identifier will be stored and displayed in the public protocol area in an immutable form. When other target forging instructions need to forge it and form a document in any private workspace, its content source identifier can still be obtained, so that each new version of the content can inherit the original content source based on the content source identifier.

[0035] The technical solution of this embodiment, upon receiving a target replication instruction, obtains the target snapshot content and content source identifier of the target replication snapshot in the public protocol area, stores the target snapshot content as a target replication document in the private workspace, and marks the content source identifier on the target replication document. Upon receiving a content editing instruction associated with the target replication document, the target content of the target replication document is updated according to the content editing instruction. Upon receiving a content publishing instruction associated with the target replication document, the target replication document with updated target content is published to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining a target publishing snapshot, and marking the content source identifier on the target publishing snapshot. This solution overcomes the deficiencies in the management of multiple versions of content in the prior art, achieves physical isolation between the content editing state and the publishing state, and automatically aggregates multiple versions obtained from distributed collaboration, thereby improving the security and management efficiency of multiple version content.

[0036] Based on any of the above implementation methods, Embodiment 1 of the present invention also provides specific optional implementation methods for configuring content source identifiers.

[0037] In one alternative implementation, the content source identifier may include: a snapshot source space identifier, used to mark the snapshot publishing space of the target replicated snapshot in the public protocol area.

[0038] Accordingly, marking the content source identifier to the target replica document may include: marking the snapshot source space identifier as the document source space identifier of the target replica document.

[0039] Accordingly, marking the content source identifier to the target published snapshot may include: marking the document source space identifier of the target copied document as the snapshot source space identifier of the target published snapshot.

[0040] The document source space identifier marks the snapshot publication space in the public protocol area to which the content of the target replicated document originates. For any target replicated document, its initial content can be the content of a target replicated snapshot already published in the public protocol area. In this case, the document source space identifier of the target replicated document marks the snapshot publication space of the target replicated snapshot. When this part of the document is edited and published as a snapshot, the new snapshot inherits the mark of the document source space identifier, forming a snapshot source space identifier, which is used to mark the content source of the new snapshot.

[0041] In an optional implementation, the content management method may further include: upon receiving a document creation instruction, generating a target creation document in a private workspace and marking the document source space identifier of the target creation document as empty; upon receiving a content editing instruction associated with the target creation document, updating the target content of the target creation document according to the content editing instruction; upon receiving a content publishing instruction associated with the target creation document, publishing the target creation document with updated target content to an unoccupied publishing space in a public protocol area to obtain a target publishing snapshot, marking the global identifier of the unoccupied publishing space as the snapshot source space identifier of the target publishing snapshot, and updating the document source space identifier of the target creation document to the global identifier of the unoccupied publishing space.

[0042] The content of the target document is not obtained through copying, but rather is created by the user in a private workspace based on document creation and content editing instructions. Therefore, before its initial publication, its document source space identifier can be empty. After this document is published to the public protocol area and a corresponding snapshot is formed, any unoccupied publication space not occupied by previously published snapshots can be designated as its snapshot publication space. Simultaneously, the global space identifier can be used as both the snapshot source space identifier and the document source space identifier. Specifically, the global space identifier can be a globally unique identifier for unoccupied publication space. The public protocol area can be pre-divided into multiple spaces. When a newly created document is first published as a snapshot, any unoccupied publication space can be selected as its snapshot publication space; alternatively, when a newly created document is first published as a snapshot, unoccupied publication space can be allocated from all free space in the public protocol area as its snapshot publication space. Furthermore, when any target copy instruction copies the snapshot to a new document, it can obtain the snapshot source space identifier and mark it as the document source space identifier of the new document; when the new document is edited and published, it will be published to the corresponding snapshot publishing space, forming the corresponding snapshot and snapshot source space identifier.

[0043] The above implementation assigns the same document source space identifier and snapshot source space identifier to the edit-state documents and published-state snapshots of multiple versions of content derived from the same initial content, and publishes the snapshots in the same snapshot publishing space in the public protocol area. This ensures that no matter how many users copy or modify the content, the resulting snapshots are always automatically aggregated into the same logical space, enabling rapid aggregation and management of derived versions.

[0044] In one alternative implementation, the content source identifier may include: the snapshot publication identifier of the target replica snapshot in the public protocol area.

[0045] Accordingly, marking the content source identifier to the target replica document may include: marking the snapshot publication identifier as the document modification source identifier of the target replica document.

[0046] Accordingly, marking the content source identifier to the target release snapshot may include: marking the document modification source identifier of the target copied document as the snapshot modification source identifier of the target release snapshot. Further, after marking the document modification source identifier of the target copied document as the snapshot modification source identifier of the target release snapshot, it may also include: updating the document modification source identifier of the target copied document to the snapshot release identifier of the target release snapshot in the public protocol area.

[0047] The snapshot publication identifier can be a globally unique identifier generated when a snapshot is published in the public protocol area. The document modification source identifier can mark the snapshot corresponding to the version of content in the document on which the modifications were based. The snapshot modification source identifier can mark the previous version of the snapshot.

[0048] Specifically, any snapshot published in the public protocol area can be marked with a snapshot publication identifier. When the snapshot is copied as a target copy document, any content modification made in the target copy document is based on the content of the snapshot. Therefore, the document modification source identifier of the target copy document can be marked as the snapshot publication identifier of its target copy snapshot.

[0049] When a target replica document, edited based on a target replica snapshot, is published as a new target release snapshot, the content of that target release snapshot is modified based on the content of the aforementioned target replica snapshot. The aforementioned target replica snapshot can be considered as the previous version of the target release snapshot. Therefore, the snapshot modification source identifier of the target release snapshot can inherit the document modification source identifier. After the target release snapshot is published, any modifications made to the target replica document can be considered as being based on the content of the target release snapshot. In this case, the document modification source identifier of the target replica document can be updated to the snapshot release identifier obtained when the target release snapshot was published.

[0050] Optionally, the document modification source identifier of a target created document that has never been published can be empty; when the target created document is published as a target published snapshot, the snapshot modification source identifier of the target published snapshot inherits the document modification source identifier of the target created document, while the document modification source identifier of the target created document is updated to the snapshot published identifier of the latest published target published snapshot.

[0051] The above implementation method, based on document modification source identifier and snapshot modification source identifier, can record the iteration relationship between each content version in detail.

[0052] In an optional implementation, tagging the content source identifier to the target replica document may further include: tagging the snapshot publication identifier as the document replica source identifier of the target replica document.

[0053] Accordingly, marking the content source identifier to the target published snapshot may also include: marking the document replica source identifier of the target replicated document as the snapshot replica source identifier of the target published snapshot.

[0054] The document replica source identifier can mark the snapshot from which the document is replicated. The snapshot replica source identifier can mark the snapshot from which the content replicated in the snapshot originates.

[0055] Specifically, for a target replicated document created by replicating a snapshot, it needs to be marked with a document replica source identifier. Unlike the document modification source identifier, the document replica source identifier of a target replicated document does not change after it is published as a target release snapshot. That is, the document replica source identifier of any target replicated document is generated when it is created through the replicating operation and does not change dynamically, thus permanently recording the replica source of the target replicated document. When a target replicated document is published as a target release snapshot, the target release snapshot can inherit its document replica source identifier as the snapshot replica source identifier.

[0056] If a target replica document, created by replicating any target snapshot, is edited and published multiple times, the snapshot modification source identifier of each published target snapshot can point to the previously published snapshot, while the document modification source identifier of the target replica document is dynamically updated to point to the target published snapshot; and the corresponding snapshot replica source identifier and document replica source identifier always statically point to the target replica snapshot.

[0057] Optionally, the document forking source identifier of a target created document that has never been published can be empty; when the target created document is published as a target published snapshot, the snapshot forking source identifier of the target published snapshot inherits the document forking source identifier of the target created document, which is also empty.

[0058] The above implementation method further configures the document replication source identifier and snapshot replication source identifier to record the replication process, so that the content inheritance relationship between snapshots of different versions can be obtained more clearly and efficiently.

[0059] In the above optional implementations, document types can be categorized into target copied documents and target created documents based on their source. In one optional implementation, the content management method may further include: upon receiving a target copy instruction associated with a target copied document, generating a target copied document in the private workspace where the target copied document resides, and marking the document source space identifier, document modification source identifier, and document copy source identifier of the target copied document as empty. The target copied document is a new document formed by copying all the content of the target copied document.

[0060] Based on any of the above embodiments, Embodiment 1 of the present invention also provides an optional method for avoiding duplicate publication of the same content. In an optional embodiment, upon receiving a content publication instruction associated with a target replica document, publishing the target replica document with updated target content to a snapshot publication space in the public protocol area that matches the content source identifier may include: obtaining the current content fingerprint and the published content fingerprint of the target replica document with updated target content; if the current content fingerprint and the published content fingerprint are different, publishing the target replica document to the snapshot publication space in the public protocol area to obtain a target publication snapshot.

[0061] The current content fingerprint can be data obtained by performing specific operations on the current content of the document, while the published content fingerprint can be data obtained by performing the same specific operations on the content of the snapshot formed by the last publication of the document. The difference between the current content fingerprint and the published content fingerprint indicates that the content of the document has changed between the two publications, and it can be published again. Further optionally, after publishing the target replicated document to the snapshot publication space in the public protocol area and obtaining the target publication snapshot, the published content fingerprint of the target replicated document is updated to the current content fingerprint to record the content of the document's latest publication as a snapshot.

[0062] The above implementation method can obtain the content fingerprint data of the document based on a pre-set calculation method, realize the content comparison between two publications, and avoid the same content being repeatedly published as a snapshot.

[0063] In an optional implementation, after updating the target content of the target replica document according to the content editing instructions, the method may further include: marking the current timestamp as the document update timestamp of the target replica document. Correspondingly, after publishing the target replica document with updated target content to the snapshot publishing space in the public protocol area to obtain the target published snapshot, the method may further include: marking the current timestamp as the space update timestamp of the snapshot publishing space.

[0064] The document update timestamp records the last time the document's content was changed. The space update timestamp records the last time a snapshot was published in the corresponding snapshot publishing space.

[0065] Accordingly, in an optional implementation, after updating the target content of the target replica document according to the content editing instruction, the method may further include: upon receiving a batch publishing instruction associated with the target replica document, obtaining the document update timestamp and the document source space identifier of the target replica document; obtaining the space update timestamp of the snapshot publishing space that matches the document source space identifier; and, if it is determined that the document update timestamp is later than the space update timestamp, publishing the target replica document to the snapshot publishing space to obtain the target published snapshot.

[0066] The batch publish command can be used to publish multiple documents sharing the same snapshot publishing space in batches. Since all documents to be published in a batch publish command can be published to the same snapshot publishing space to form a snapshot, the corresponding snapshot publishing space can be determined based on the document's source space identifier, and the space update timestamp of that snapshot publishing space can be obtained. The time relationship between the document's update timestamp and the space update timestamp is then determined. If any document's update timestamp is later than the space update timestamp, it indicates that the document's content has not been published to the snapshot publishing space since the latest update, and therefore it can be published. Conversely, if any document's source space identifier is empty, it indicates that the document has never been published, and therefore it can be published directly.

[0067] In one optional implementation, multiple documents sharing the same snapshot publishing space can be stored in the same folder within a private workspace. Batch publishing instructions can be generated through publishing operations on the folder. Accordingly, the snapshots formed after batch publishing of documents in the same folder can be displayed in the form of a book. Specifically, the structure of the book can be determined by identifying the modification and replication relationships between snapshots based on content source identifiers.

[0068] The above implementation provides a method for quickly locating documents that need to be published in a batch of documents based on timestamps, avoiding duplicate publication of content, improving the efficiency of batch content management, and saving computing resources.

[0069] Based on the above optional implementation methods, Embodiment 1 of the present invention also provides an optional method for obtaining content contribution.

[0070] In an optional implementation, after publishing the target replica document with updated target content to the snapshot publishing space in the public protocol area that matches the content source identifier to obtain a target publishing snapshot, and marking the content source identifier to the target publishing snapshot, the method may further include: upon receiving a contribution statistics instruction for the target publishing snapshot, obtaining a target replica snapshot based on the snapshot replica source identifier of the target publishing snapshot; performing content comparison calculations on the target publishing snapshot and the target replica snapshot to obtain the content contribution of the target publishing snapshot; repeatedly executing the process of obtaining a target replica snapshot based on the snapshot replica source identifier of the target replica snapshot and calculating the content contribution, until a target replica snapshot with an empty snapshot replica source identifier is obtained, and calculating the content contribution based on the target snapshot content of the target replica snapshot with an empty snapshot replica source identifier.

[0071] The contribution statistics command can be used to obtain the degree of contribution made by users who participated in editing during the formation of the current content of the target published snapshot. Content comparison calculation can be an operation that calculates the content contribution corresponding to the content differences between the target published snapshot and the target replicated snapshot. Content contribution can be data that evaluates the importance of content differences within the current complete content of the target published snapshot, reflecting the contribution level of the corresponding snapshot publisher user.

[0072] For any published snapshot, contribution statistics can be obtained through contribution statistics commands to assess the contribution of each user when multiple users collaborate on the same content. This process can be implemented based on the snapshot replication source identifier. Specifically, if the snapshot replication source identifier of any target published snapshot is not empty, it indicates that its content was not completed solely by the user who performed the publishing operation, but rather obtained by that user after replicating and editing the content of another published snapshot. The target replicated snapshot pointed to by the snapshot replication source identifier is the replicated published snapshot. In this case, the content change of the target published snapshot relative to the target replicated snapshot can be considered as being formed by the editing of its publishing user, and can be used to determine the degree of contribution of that user to its content. Therefore, the content contribution of the target published snapshot can be calculated by comparing the content of the target published snapshot and the target replicated snapshot.

[0073] Furthermore, if the snapshot replica source identifier of the target replica snapshot is also not empty, it indicates that the content of the target replica snapshot was not solely created by the user who performed the publishing operation. In this case, the target replica snapshot pointed to by its snapshot replica source identifier is obtained, and the two are compared and calculated in the same way to obtain the content contribution. This process is repeated until the snapshot replica source identifier of the final target replica snapshot is empty, indicating that its content was created and published for the first time by the user who performed the publishing operation. The user's contribution can then be directly evaluated based on its content.

[0074] In one optional implementation, comparing and calculating the content contribution of the target release snapshot and the target replica snapshot to obtain the content contribution of the target release snapshot may include: performing content structuring processing on the target release snapshot and the target replica snapshot respectively to obtain first content structure data and second content structure data; obtaining new nodes, modified nodes, and deleted nodes in the first content structure data based on the second content structure data; and performing node weighted calculation on the new nodes, modified nodes, and deleted nodes according to preset contribution rules to obtain the content contribution of the target release snapshot.

[0075] Content structuring can be an operation that presents snapshot content in a pre-defined structure according to a preset data processing method. Specifically, it can be an operation that generates structured data by using nodes to record each part of the content and using the relationships between nodes to record the semantic structure relationships of each part of the content. The first content structure data and the second content structure data are the structured data obtained by content structuring of the target published snapshot and the target replicated snapshot, respectively.

[0076] Specifically, a new node can be a node that exists in the first content structure data but not in the second content structure data, indicating that the content recorded by this node was added and written by the publisher of the target snapshot. A modified node can be a node that exists in both the first and second content structure data but records different content, indicating that the content recorded by this node was modified by the publisher of the target snapshot from the content copied from the target snapshot. A deleted node can be a node that exists in the second content structure data but not in the first content structure data, indicating that the content recorded by this node was deleted by the publisher of the target snapshot from the content copied from the target snapshot. For user add, modify, and delete operations, weights can be pre-set according to the importance of the operation to the content, forming a preset contribution rule. Therefore, according to the preset contribution rule, node weighted calculations can be performed on add, modify, and delete nodes, and the sum of the user contribution levels reflected by the three types of nodes can be calculated as the content contribution of the target snapshot.

[0077] Specifically, the node-weighted calculation may optionally include the process of calculating the sum of the products of the number of nodes of each type and their weights. For example, the content contribution score determined by the node-weighted calculation according to a preset contribution rule can be expressed as: Score = SUM(Count_add) W_add)+SUM(Count_mod W_mod)-SUM(Count_del W_del); Here, Count_add represents the number of new nodes, and W_add represents the weight of the new nodes, which can be set to 1; Count_mod represents the number of modified nodes, and W_mod represents the weight of the modified nodes, which can be set to 0.5; Count_del represents the number of deleted nodes, and W_del represents the weight of the deleted nodes, which can be set to 0.2.

[0078] In an optional implementation, after obtaining the contribution scores of all content, the method may further include: calculating the contribution statistics of the target published snapshot based on the contribution scores of each content. The contribution statistics can be used to describe the percentage of contribution made by users who participated in editing during the formation of the current content of the target published snapshot.

[0079] Specifically, based on the content contribution of each snapshot and the publisher user, the user contribution of each user is calculated. This can be achieved by summing the content contribution of snapshots published by the same user. Furthermore, the contribution percentage of each user can be obtained by normalizing the contribution of all users, serving as the contribution statistics. For example, to obtain the contribution statistics for snapshot C, it can be determined that it was derived from snapshot B, which in turn was derived from snapshot A. Snapshot A was the first publication of the document, thus the version chain is determined to be "ABC". Using the above implementation method, the content contribution of snapshots A, B, and C are obtained as 10, 6, and 3.8, respectively, and the publisher users of snapshots A, B, and C are all different. Therefore, the contribution statistics for the publisher users of snapshots A, B, and C to snapshot C are 50.5%, 30.3%, and 19.2%, respectively.

[0080] For example, Figure 2 This is a schematic diagram of a snapshot version chain within the same snapshot publishing space, provided in Embodiment 1 of the present invention. Figure 3 This is a schematic diagram of a snapshot contribution tracing version chain provided in Embodiment 1 of the present invention. Figure 2 As shown, snapshots of versions S2 to S15, derived from the snapshot of version S1 published by user Alice, are all published in the unified space represented by the dashed box, and based on the iteration or replication relationship between the snapshot content, Figure 2 The solid arrows in the image represent the path of version evolution. Furthermore, when it's necessary to calculate the content contribution of version S15, the snapshot replica source identifier can be used to determine... Figure 2 The dashed arrow in the middle represents the contribution tracing version chain, thus obtaining... Figure 3 The version chain structure is shown. It is evident that using snapshot replication source identifiers to calculate the contribution of any snapshot version can greatly simplify version tracing, improve statistical efficiency, and save computing resources.

[0081] Based on any of the above implementation methods, Embodiment 1 of the present invention also provides specific optional implementation methods for the design of data entity structures in the public protocol area and the private work area.

[0082] In one optional implementation, a public snapshot table can be pre-defined in the public protocol area to store published snapshots. Snapshots can be stored in the public protocol area in a specific structured format. Specifically, the public snapshot table can use a snapshot publication identifier as the primary key field, and also include fields recording the target snapshot content and the content source identifier for each snapshot. When a document is published to the public protocol area, a new snapshot record can be added to the public snapshot table, storing the snapshot publication identifier, target snapshot content, and content source identifier in the corresponding fields. Optionally, if the content source identifier includes at least two of the following: snapshot source space identifier, snapshot modification source identifier, and snapshot replication source identifier, each identifier can be recorded in different pre-defined fields. Further optionally, the snapshot modification source identifier and snapshot replication source identifier in the public snapshot table can point to their own primary keys.

[0083] In one optional implementation, a logical space table can be pre-defined in the public protocol area to record snapshot publishing spaces. Specifically, the logical space table can use a globally unique identifier for the snapshot publishing space as its primary key field. When any document is first published to the public protocol area, a new space record can be added to the logical space table, storing the global identifier of that space. This global identifier can then be identified as the document's source space identifier and the snapshot source space identifier of the snapshot formed after publication. Further optionally, the snapshot source space identifier in the public snapshot table can point to the primary key in the logical space table.

[0084] In an optional implementation, a private document table can be pre-set in the private workspace to store documents, which can be stored in a specific structured format. Specifically, the private document table can use the globally unique identifier of the document as the primary key field, and also include fields recording the real-time updates of each document's content and content source identifier. When a document is created or replicated in the private workspace for the first time, a new document record can be added to the private document table, storing the globally unique identifier of the document, its content, and its content source identifier in the corresponding fields. Optionally, if the content source identifier includes at least two of the following: document source space identifier, document modification source identifier, and document replication source identifier, each identifier can be recorded in different pre-set fields. Further optionally, the document source space identifier in the private document table can point to the primary key in the logical space table; the document modification source identifier and the document replication source identifier can point to the primary key in the public snapshot table.

[0085] Further optionally, user permissions, related timestamps, and other fields can be pre-set in the public snapshot table, private document table, and / or logical space table, and indexes and security policies for content management can be established, etc., without limitation.

[0086] Further optional features include a user table, a folder table in the private workspace, and a book table in the public protocol area.

[0087] Alternatively, a global directory node table can be pre-set to record the content organization structure of global documents and snapshots in a tree structure. Each document and snapshot can be recorded as a node in the directory node table, and its related identifiers or attributes can be recorded in the corresponding fields.

[0088] Example 2 Figure 4 This is a schematic diagram of the structure of a content management system provided in Embodiment 2 of the present invention, as shown below. Figure 4 As shown, the content management system includes: a content management device 410, a public protocol area 420, and a private workspace 430, wherein the content management device 410 can be used for: Upon receiving a target replication instruction, the target snapshot content and content source identifier of the target replication snapshot are obtained from the public protocol area 420. In the private workspace 430, the target snapshot content is stored as a target replica document, and the content source identifier is marked to the target replica document; Upon receiving a content editing instruction associated with the target replica document, the target content of the target replica document is updated according to the content editing instruction; Upon receiving a content publishing instruction associated with the target replica document, the target replica document with the updated target content is published to the snapshot publishing space in the public protocol area 420 that matches the content source identifier, thereby obtaining a target publishing snapshot, and the content source identifier is marked on the target publishing snapshot.

[0089] The technical solution of this embodiment, upon receiving a target replication instruction, obtains the target snapshot content and content source identifier of the target replication snapshot in the public protocol area, stores the target snapshot content as a target replication document in the private workspace, and marks the content source identifier on the target replication document. Upon receiving a content editing instruction associated with the target replication document, the target content of the target replication document is updated according to the content editing instruction. Upon receiving a content publishing instruction associated with the target replication document, the target replication document with updated target content is published to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining a target publishing snapshot, and marking the content source identifier on the target publishing snapshot. This solution overcomes the deficiencies in the management of multiple versions of content in the prior art, achieves physical isolation between the content editing state and the publishing state, and automatically aggregates multiple versions obtained from distributed collaboration, thereby improving the security and management efficiency of multiple version content.

[0090] Optionally, the content source identifier may include: a snapshot source space identifier, used to mark the snapshot publishing space of the target replica snapshot in the public protocol area 420; the content management device 410 may mark the content source identifier to the target replica document as the document source space identifier of the target replica document; the content management device 410 may mark the content source identifier to the target publishing snapshot as the document source space identifier of the target replica document as the snapshot source space identifier of the target publishing snapshot.

[0091] Optionally, the content source identifier may include: the snapshot publication identifier of the target replica snapshot in the public protocol area 420; the content management device 410 may mark the content source identifier to the target replica document by marking the snapshot publication identifier as the document modification source identifier of the target replica document; the content management device 410 may also mark the content source identifier to the target published snapshot by marking the document modification source identifier of the target replica document as the snapshot modification source identifier of the target published snapshot; after marking the document modification source identifier of the target replica document as the snapshot modification source identifier of the target published snapshot, the content management device 410 may further be used to update the document modification source identifier of the target replica document to the snapshot publication identifier of the target published snapshot in the public protocol area 420.

[0092] Optionally, the content management device 410 may mark the content source identifier to the target replica document, or may further be configured to mark the snapshot publication identifier as the document replica source identifier of the target replica document; the content management device 410 may also mark the content source identifier to the target publication snapshot, or may further be configured to mark the document replica source identifier of the target replica document as the snapshot replica source identifier of the target publication snapshot.

[0093] Optionally, after publishing the target replica document with the updated target content to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining a target publishing snapshot, and marking the content source identifier to the target publishing snapshot, the content management device 410 can also be used to: upon receiving a contribution statistics instruction for the target publishing snapshot, obtain the target replica snapshot based on the snapshot replica source identifier of the target publishing snapshot; perform content comparison calculation on the target publishing snapshot and the target replica snapshot to obtain the content contribution degree of the target publishing snapshot; repeatedly execute the process of obtaining the target replica snapshot based on the snapshot replica source identifier of the target replica snapshot and calculating the content contribution degree until a target replica snapshot with an empty snapshot replica source identifier is obtained, and calculate the content contribution degree based on the target snapshot content of the target replica snapshot with an empty snapshot replica source identifier.

[0094] Optionally, the content management device 410 performs content comparison calculations on the target published snapshot and the target replicated snapshot to obtain the content contribution of the target published snapshot. This can be configured as follows: performing content structuring processing on the target published snapshot and the target replicated snapshot respectively to obtain first content structure data and second content structure data; obtaining new nodes, modified nodes, and deleted nodes in the first content structure data based on the second content structure data; and performing node weighted calculations on the new nodes, modified nodes, and deleted nodes according to preset contribution rules to obtain the content contribution of the target published snapshot.

[0095] Optionally, after publishing the target replica document with the updated target content to the snapshot publishing space in the public protocol area that matches the content source identifier to obtain a target publishing snapshot, and marking the content source identifier to the target publishing snapshot, the content management device 410 can also be used to: mark the current timestamp as the space update timestamp of the snapshot publishing space; after updating the target content of the target replica document according to the content editing instruction, the content management device 410 can also be used to: mark the current timestamp as the document update timestamp of the target replica document; when receiving a batch publishing instruction associated with the target replica document, obtain the document update timestamp and the document source space identifier of the target replica document; when the document source space identifier is not empty, obtain the space update timestamp of the snapshot publishing space that matches the document source space identifier; when it is determined that the document update timestamp is later than the space update timestamp, publish the target replica document to the snapshot publishing space to obtain the target publishing snapshot.

[0096] The content management system provided in this embodiment of the invention can execute the content management method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0097] Example 3 Figure 5 This is a schematic diagram of the structure of a content management device provided in Embodiment 3 of the present invention, as shown below. Figure 5 As shown, the content management device includes a processor 510, a memory 520, an input device 530, and an output device 540; the number of processors 510 in the content management device can be one or more. Figure 5 Taking a processor 510 as an example; the processor 510, memory 520, input device 530, and output device 540 in the content management device can be connected via a bus or other means. Figure 5 Taking the example of a connection between China and Israel via a bus.

[0098] The memory 520, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules (e.g., content management devices) corresponding to the content management method in this embodiment of the invention. The processor 510 executes various functional applications and data processing of the content management device by running the software programs, instructions, and modules stored in the memory 520, thereby implementing the aforementioned content management method.

[0099] The memory 520 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on terminal usage. Furthermore, the memory 520 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include memory remotely located relative to the processor 510, which can be connected to a content management device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0100] Input device 530 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the content management device. Output device 540 may include display devices such as a display screen.

[0101] Example 4 Embodiment 4 of the present invention also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a content management method, including: Upon receiving a target replication instruction, retrieve the target snapshot content and content source identifier from the public protocol area; In the private workspace, the target snapshot content is stored as a target replica document, and the content source identifier is marked to the target replica document; Upon receiving a content editing instruction associated with the target replica document, the target content of the target replica document is updated according to the content editing instruction; Upon receiving a content publishing instruction associated with the target replica document, the target replica document with the updated target content is published to the snapshot publishing space in the public protocol area that matches the content source identifier, thereby obtaining a target publishing snapshot, and the content source identifier is marked on the target publishing snapshot.

[0102] Of course, the computer-executable instructions provided in the embodiments of the present invention are not limited to the method operations described above, but can also perform related operations in the content management method provided in any embodiment of the present invention.

[0103] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0104] It is worth noting that in the above embodiments of the content management system, the various areas and devices included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each part are only for easy distinction between each other and are not used to limit the scope of protection of the present invention.

[0105] Although the present invention has been described in detail above with general descriptions, specific embodiments, and experiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.

Claims

1. A content management method, characterized in that, include: Upon receiving a target replication instruction, retrieve the target snapshot content and content source identifier from the public protocol area; In the private workspace, the target snapshot content is stored as a target replica document, and the content source identifier is marked to the target replica document; Upon receiving a content editing instruction associated with the target replica document, the target content of the target replica document is updated according to the content editing instruction; Upon receiving a content publishing instruction associated with the target replica document, the target replica document with the updated target content is published to the snapshot publishing space in the public protocol area that matches the content source identifier, thereby obtaining a target publishing snapshot, and the content source identifier is marked on the target publishing snapshot.

2. The method according to claim 1, characterized in that, The content source identifier includes: a snapshot source space identifier, used to mark the snapshot publishing space of the target replicated snapshot in the public protocol area; The step of marking the content source identifier to the target replica document includes: The snapshot source space identifier is marked as the document source space identifier of the target replicated document; The step of tagging the content source identifier to the target published snapshot includes: The document source space identifier of the target replicated document is marked as the snapshot source space identifier of the target published snapshot.

3. The method according to claim 2, characterized in that, The content source identifier includes: the snapshot publication identifier of the target replica snapshot in the public protocol area; The step of marking the content source identifier to the target replica document includes: The snapshot publication identifier is marked as the document modification source identifier of the target replicated document; The step of tagging the content source identifier to the target published snapshot includes: Mark the document modification source identifier of the target replicated document as the snapshot modification source identifier of the target published snapshot; After marking the document modification source identifier of the target replicated document as the snapshot modification source identifier of the target published snapshot, the method further includes: Update the document modification source identifier of the target copied document to the snapshot publication identifier of the target published snapshot in the public protocol area.

4. The method according to claim 3, characterized in that, The step of marking the content source identifier to the target replicated document also includes: The snapshot publication identifier is marked as the document replication source identifier of the target replicated document; The step of marking the content source identifier to the target published snapshot also includes: The document replication source identifier of the target replicated document is marked as the snapshot replication source identifier of the target published snapshot.

5. The method according to claim 4, characterized in that, After publishing the updated target replica document to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining the target publishing snapshot, and marking the content source identifier to the target publishing snapshot, the method further includes: Upon receiving a contribution statistics instruction for the target published snapshot, the target replica snapshot is obtained based on the snapshot replica source identifier of the target published snapshot; The content contribution of the target published snapshot is calculated by comparing and calculating the content of the target published snapshot with the target replicated snapshot. Repeatedly execute the process of obtaining the target replica snapshot based on the snapshot replica source identifier of the target replica snapshot and calculating the content contribution, until the target replica snapshot with an empty snapshot replica source identifier is obtained, and calculate the content contribution based on the content of the target snapshot of the target replica snapshot with an empty snapshot replica source identifier.

6. The method according to claim 5, characterized in that, The step of comparing and calculating the content contribution of the target published snapshot and the target replicated snapshot to obtain the content contribution of the target published snapshot includes: The target published snapshot and the target replicated snapshot are respectively subjected to content structuring processing to obtain first content structure data and second content structure data; Based on the second content structure data, obtain the newly added nodes, modified nodes, and deleted nodes in the first content structure data; According to the preset contribution rules, the newly added node, the modified node, and the deleted node are weighted and calculated to obtain the content contribution of the target published snapshot.

7. The method according to claim 4, characterized in that, After publishing the updated target replica document to the snapshot publishing space in the public protocol area that matches the content source identifier, obtaining the target publishing snapshot, and marking the content source identifier to the target publishing snapshot, the method further includes: Mark the current timestamp as the spatial update timestamp of the snapshot publishing space; After updating the target content of the target replicated document according to the content editing instructions, the method further includes: Mark the current timestamp as the document update timestamp of the target replicated document; Upon receiving a batch release instruction associated with the target replica document, obtain the document update timestamp and the document source space identifier of the target replica document; Obtain the space update timestamp of the snapshot publishing space that matches the document source space identifier; If it is determined that the document update timestamp is later than the space update timestamp, the target replica document is published to the snapshot publishing space to obtain the target published snapshot.

8. A content management system, characterized in that, The method for implementing the content management method as described in any one of claims 1-7 includes: a content management device, a public protocol area, and a private work area; The content management device is used for: Upon receiving a target replication instruction, the target snapshot content and content source identifier of the target replication snapshot are obtained from the public protocol area. In the private workspace, the target snapshot content is stored as a target replica document, and the content source identifier is marked on the target replica document; Upon receiving a content editing instruction associated with the target replica document, the target content of the target replica document is updated according to the content editing instruction; Upon receiving a content publishing instruction associated with the target replica document, the target replica document with the updated target content is published to the snapshot publishing space in the public protocol area that matches the content source identifier, thereby obtaining a target publishing snapshot, and the content source identifier is marked on the target publishing snapshot.

9. A content management device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the content management method as described in any one of claims 1-7.

10. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the content management method as described in any one of claims 1-7.

Images