A content version control method, device, terminal and storage medium

Abstract

The application discloses a content version control method and device, a terminal and a storage medium. The method comprises the following steps: receiving a version revision requirement for target content; when the version revision requirement is a first revision requirement, selecting a target version from at least one general content version according to the first revision requirement; and revising the target content according to the target version. In the content version control method provided by the application, the target version is selected from the general content version according to the received version revision requirement, and the target content is revised according to the target version. According to different revision requirements, the target version is selected from the general content version to revise the target content, and a separate content version does not need to be created, so that repeated work is reduced, and efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of content versioning technology, and in particular to a content versioning control method, device, terminal, and storage medium. Background Technology

[0002] Frequent content collaborations exist within the internet content industry. Timely updates and effective version control are crucial for companies cultivating the content field. Among numerous content partners, different providers have their own sets of compliance standards for collaborative content. Forcing content updates in order to comply with the actual content specifications of most partners is not feasible. Therefore, effectively updating and controlling the version of output content presents a new challenge for content providers, and this is essentially a responsible approach to the entire content lifecycle.

[0003] However, in long-term content collaborations, after a considerable period of time, some content has become unsuitable for the constantly changing network environment, requiring significant modifications or even complete revisions. Currently, most known industry solutions involve copying the content, updating or revising the copy, and then overwriting the problematic content to resolve the issue. This approach is inefficient, repetitive, and for content providers, the frequent copying and duplication of content creates data redundancy, which is also a problem. Allowing this practice to continue unchecked not only exposes the company to these risks but also indirectly shifts the risk of content issues to content partners, which is unacceptable.

[0004] Therefore, existing technologies still need to be improved and enhanced. Summary of the Invention

[0005] To address the aforementioned shortcomings of existing technologies, this invention provides a content version control method, apparatus, terminal, and storage medium, aiming to solve the problem of low work efficiency when content versions need to be revised in existing technologies.

[0006] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows:

[0007] A first aspect of the present invention provides a method for controlling content versions, the method comprising:

[0008] Receive version revision requests for the target content;

[0009] When the version revision requirement is the first revision requirement, the target version is selected from at least one preset general content version according to the first revision requirement;

[0010] The target content is revised according to the target version.

[0011] The content version control method, wherein after receiving a revision request for the target content, the method further includes:

[0012] When the version revision requirement is a second revision requirement, a direct revision is performed on the original version corresponding to the target content.

[0013] The content version control method, wherein selecting a target version from at least one preset general content version according to the revision requirements includes:

[0014] Obtain the target collaborators corresponding to the aforementioned version revision requirements;

[0015] Select the general content version bound to the target partner as the target version;

[0016] If the target partner does not have a bound version of the general content, then the general content version that is closest to the first revision requirement is selected as the target version, and the target version is bound to the target partner.

[0017] The content version control method, wherein revising the target content according to the target version includes:

[0018] When the target version is compatible with the first revision requirement, the original version of the target content is overwritten with the target version;

[0019] When the target version does not match the first revision requirement, the target version is revised in a differentiated manner to obtain a new target version, which is then used to cover the original version of the target content.

[0020] The content version control method, after obtaining the target new version, further includes:

[0021] When the target new version is within the compatibility range of the target version, the target new version shall be used to overwrite the target version.

[0022] The content version control method, wherein after receiving a version revision request for the target content, the method further includes:

[0023] When the target content is a serialized content and a request for new serialized content is received, new serialized content is added based on the current version of the target content.

[0024] The content version control method further includes, before receiving a version revision request for the target content:

[0025] Obtain the historical requirements of your partners;

[0026] Based on the historical needs of the partners, at least one preset version of the general content is established.

[0027] A second aspect of the present invention provides a content version control device, comprising:

[0028] A receiving module, which is used to address version revision requirements for the target content;

[0029] The selection module is used to select a target version from at least one preset general content version according to the first revision requirement when the version revision requirement is a first revision requirement.

[0030] A revision module is used to revise the target content according to the target version.

[0031] A third aspect of the present invention provides a terminal, the terminal including a processor and a computer-readable storage medium communicatively connected to the processor, the computer-readable storage medium being adapted to store a plurality of instructions, the processor being adapted to invoke the instructions in the computer-readable storage medium to perform steps of the control method for implementing the content version as described in any of the preceding claims.

[0032] In a fourth aspect, the present invention provides a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the content version control method described in any of the preceding claims.

[0033] Compared with the prior art, the present invention provides a content version control method, device, terminal, and storage medium. In the content version control method provided by the invention, a target version is selected from the general content version based on the received version revision request, and then the target content is revised according to the target version. Depending on the revision request, it is only necessary to select the target version from the general content version to revise the target content, without having to create a separate content version, thus reducing repetitive work and improving efficiency. Attached Figure Description

[0034] Figure 1 A flowchart illustrating an embodiment of the content version control method provided by the present invention;

[0035] Figure 2 A logical block diagram illustrating the entire process of revising content versions in an embodiment of the content version control method provided by the present invention;

[0036] Figure 3 A schematic diagram of the structural principle of an embodiment of the control device for the content version of this invention;

[0037] Figure 4 A schematic diagram illustrating the principle of an embodiment of the terminal provided by the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and effects of this invention clearer and more explicit, the invention will be further described in detail below 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 are not intended to limit the invention.

[0039] The content version control method provided by this invention can be executed by a terminal. The terminal includes, but is not limited to, various computers, servers, mobile phones, tablets, wearable devices, etc.

[0040] Example 1

[0041] like Figure 1 As shown, one embodiment of the data acquisition method includes the following steps:

[0042] S100: Receive a version revision request for the target content.

[0043] Receive version revision requests for target content from partners.

[0044] Frequent content collaborations exist within the internet content industry. Timely updates and effective version control are crucial for companies cultivating the content field. In long-term content collaborations, after a considerable period, some content may become unsuitable for the evolving online environment, requiring significant modifications or even complete revisions to create new versions. This leads to version revision requests from collaborating partners.

[0045] Before receiving a version revision request for the target content, it also includes:

[0046] S110. Obtain the historical requirements of the partner;

[0047] S120. Based on the historical needs of the partners, establish at least one preset general content version.

[0048] Specifically, before receiving a version revision request for the target content, a comprehensive understanding and learning of each partner's respective areas of expertise is conducted. In-depth research and analysis of the partners' historical requirements are carried out, and at least one general content version is statistically summarized for each partner's area of ​​expertise. For each piece of content, this general content version, along with the original version, is managed as a reusable content version. These reusable general content versions can be further customized and revised, and the revised content only applies to the specified partner. The revision process can be completed quickly, flexibly supporting different versions for various partners and facilitating subsequent revision requests.

[0049] Specifically, in this invention, version revision requests are divided into first revision requests and second revision requests. The second revision request is an urgent update request, issued when a partner needs to make temporary version adjustments; it requires rapid and specific modifications to the current version. The first revision request, on the other hand, is a non-urgent update request.

[0050] S200. When the version revision requirement is a first revision requirement, select a target version from at least one preset general content version according to the first revision requirement.

[0051] Specifically, when the received version revision request is the first revision request, it is usually a request that arises when there is a problem with the content and it needs to be revised. In this case, the target version is selected from the preset general content version according to the revision request.

[0052] Specifically, it is divided into the following steps:

[0053] S210. Obtain the target collaborator corresponding to the version revision requirement.

[0054] The target collaborator is the collaborator that proposes the aforementioned version revision request.

[0055] S220. Select the general content version bound to the target cooperation object as the target version.

[0056] S230. If the target partner does not have a bound version of the general content, then select the general content version that is closest to the first revision requirement as the target version, and bind the target version to the target partner.

[0057] That is, when the target partner is a historical partner, the general content version that was previously bound to the target partner is obtained as the target version for this revision.

[0058] Specifically, content collaboration involves a continuous and long-term process. Some partners will develop different platforms to collaborate with content providers. When these platforms share the same attributes and domains, and content is revised for one of the platforms, the general content version that the partner has already bound is directly selected as the target version for that platform.

[0059] When the target partner is a first-time partner, meaning the target partner does not have a bound version of the general content, the closest version of the general content is selected as the target version and bound to the target partner according to the first revision requirement. Binding the target version to the target partner can also be referred to as authorizing the target version to the target partner.

[0060] In one embodiment, the version revision requirement for the target content also includes a second revision requirement.

[0061] When the revision requirement is a second revision requirement, a direct revision is performed on the original version corresponding to the target content.

[0062] Specifically, the second revision request is an urgent update request, which typically arises when content needs urgent revision due to special circumstances. In this case, the original version of the target content used by the target collaborator can be directly revised to obtain a new version. This revised new version then overrides the original version of the target content used by the target collaborator, and the revised version does not affect the authorized use of the original version of the target content.

[0063] After selecting the target version, proceed to the following steps:

[0064] S300. Revise the target content according to the target version.

[0065] Specifically, revising the target content according to the target version includes:

[0066] S310. When the target version is compatible with the first revision requirement, the original version of the target content is overwritten with the target version.

[0067] S320. When the target version is not compatible with the first revision requirement, the target version is modified to obtain a new target version, which is then used to cover the original version of the target content.

[0068] Specifically, after selecting the closest version of the general content as the target version and binding it with the target partner, it is necessary to analyze whether the target version is compatible with the first revision requirement. If the target version is fully compatible with the first revision requirement, the target version is used to directly overwrite the original version of the target content to complete this revision.

[0069] If the target version is not fully compatible with the first revision requirement, a differential revision is required on the target version. After the differential revision, the target new version is obtained. The target new version is obtained by copying the target version and then performing a differential revision. After obtaining the target new version, the target new version is used to overwrite the original version of the target content to complete this revision.

[0070] In one embodiment, the following steps are also included:

[0071] S340. When the target new version is within the compatibility range of the target version, the target new version is used to overwrite the target version.

[0072] Specifically, when a new target version is obtained, if the target version is within the compatibility range of the target version, the target version is evaluated. If the evaluation finds that the target version is more suitable for the industry corresponding to the target version than the target version, the target version will replace the target version.

[0073] Specifically, the target new version is obtained by copying the target version and then making differentiated revisions. The target version is one of the reusable general content versions. The reusable general content version can process any content in a large amount of cooperation without the need for assistance from the content partner, and can be fully supported by the content provider.

[0074] Specifically, based on the reusable general content version, differentiated modifications are made, fully supporting channel customization. The target new version is tailor-made for the target partner, perfectly enabling one-to-one content revision support. During the revision process, duplicate content version copying is reduced, and rapid revision of urgent content issues is supported. This allows for quick completion of target content revision and updates, reducing data redundancy and improving efficiency. Furthermore, based on the reusable general content version, differentiated modifications are made to support targeted modifications for a single target partner, and significant work has been done at the data isolation level to ensure that content authorization for other content partners is not affected.

[0075] When the target content is a serialized content and a request for new serialized content is received, new serialized content is added based on the current version of the target content.

[0076] In current technologies, forced updates are sometimes used to avoid security issues and correct content in a timely manner. However, this approach can cause gaps in the continuity and thematic coherence of content, especially in serialized works or collaborative projects that continuously release sequels, resulting in a poor reading experience for users.

[0077] In this embodiment, based on the reusable general content version, differentiated modifications are made. When the target content type is a serialized content and a request for new serialized content is received, the new serialized content will be seamlessly integrated into the target new version, and new serialized content will be added based on the target new version. This makes the content more secure, the content management more unified, the content updates faster, and the serialization of content more tightly connected, and also has a certain effect on combating piracy.

[0078] The following example illustrates in detail the control process of the content version control method provided in this embodiment, while referring to... Figure 2 The following is a logical flowchart illustrating the entire process of revising the content:

[0079] Assume that companies A, B, C, and D have each used three versions of the aforementioned generic content and the original version. Specifically, company A uses generic content version a, company B uses generic content version b, company C uses generic content version c, and company D uses the original version y.

[0080] Case 1: When granting new authorization to a new partner, Company E, it is not necessary to create a separate content version. Based on Company E's industry attributes and field, select one of the four previously created reusable general content versions a / b / c / y as the target version and bind it to Company E.

[0081] Case 2: When Company A needs to revise its content, it uses the already bound generic version 'a' as the target version and makes differentiated revisions to obtain a new target version. This revision can be chosen to apply only to Company A or to cover all licenses of the target version (i.e., generic version 'a') used by Company A. If it covers all licenses, the impact of this revision on the generic content version will be assessed. If the revision is within the compatibility range of the generic content version, it will be allowed to be made on generic version 'a', resulting in a new generic content version 'a'. The new generic content version 'a' will be effective for all partners bound to generic version 'a'. Compatibility Effect

[0082] Case 3: When Company B's operations change and the general content version b is no longer suitable, requiring revision and a change in the content version, only the general version in the authorization configuration needs to be changed. For example, if the current operations are more suitable for using general content version c as the company's current content version, then general content version c is selected as the target version, overriding the previously used general content version b. No further special revisions are needed, and the previously used general content version b still exists and can continue to be authorized to other partners.

[0083] Case 4: Company D, which uses the original version y, needs to make urgent revisions to the content due to special circumstances. In this case, the original version y used by Company D can be revised directly, and the revised content will not affect the licensed use of other original versions.

[0084] In summary, this embodiment provides a content version control method, device, terminal, and storage medium. In the content version control method provided by the invention, a target version is selected from a general content version based on the received version revision request, and then the target content is revised according to the target version. Depending on the revision request, it is only necessary to select the target version from the general content version to revise the target content, without having to create a separate content version, which reduces repetitive work and improves efficiency.

[0085] It should be understood that although the steps in the flowcharts shown in the accompanying drawings are displayed sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0086] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0087] Example 2

[0088] Based on the above embodiments, the present invention also provides a content version control device, such as... Figure 3 As shown, the control device for the content version includes:

[0089] A receiving module, which is used to receive version revision requests for target content;

[0090] The selection module is used to select a target version from at least one preset general content version according to the first revision requirement when the version revision requirement is a first revision requirement.

[0091] A revision module is used to revise the target content according to the target version.

[0092] Example 3

[0093] Based on the above embodiments, the present invention also provides a terminal, such as... Figure 4 As shown, the terminal includes a processor 10 and a memory 20. Figure 4 Only some of the terminal components are shown; however, it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0094] In some embodiments, the memory 20 may be an internal storage unit of the terminal, such as a hard disk or memory. In other embodiments, the memory 20 may be an external storage device of the terminal, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD), flash card, etc. Further, the memory 20 may include both internal and external storage devices. The memory 20 is used to store application software and various types of data installed on the terminal. The memory 20 can also be used to temporarily store data that has been output or will be output. In one embodiment, the memory 20 stores a data acquisition program 30, which can be executed by the processor 10 to implement the content version control method described in this application.

[0095] In some embodiments, the processor 10 may be a central processing unit (CPU), a microprocessor, or other chip, used to run program code stored in the memory 20 or process data, such as executing the content version control method, etc.

[0096] In one embodiment, when the processor 10 executes the data acquisition program 30 in the memory 20, the following steps are performed:

[0097] Receive version revision requests for the target content;

[0098] When the version revision requirement is the first revision requirement, the target version is selected from at least one preset general content version according to the first revision requirement;

[0099] The target content is revised according to the target version.

[0100] The method further includes, after receiving the revision request for the target content:

[0101] When the version revision requirement is a second revision requirement, a direct revision is performed on the original version corresponding to the target content.

[0102] The process of selecting a target version from at least one preset general content version based on the revision requirements includes:

[0103] Obtain the target collaborators corresponding to the aforementioned version revision requirements;

[0104] Select the general content version bound to the target partner as the target version;

[0105] If the target partner does not have a bound version of the general content, then the general content version that is closest to the first revision requirement is selected as the target version, and the target version is bound to the target partner.

[0106] The step of revising the target content according to the target version includes:

[0107] When the target version is compatible with the first revision requirement, the original version of the target content is overwritten with the target version;

[0108] When the target version does not match the first revision requirement, the target version is revised in a differentiated manner to obtain a new target version, which is then used to cover the original version of the target content.

[0109] The process of obtaining the target new version also includes:

[0110] When the target new version is within the compatibility range of the target version, the target new version shall be used to overwrite the target version.

[0111] The method further includes, after receiving the version revision request for the target content:

[0112] When the target content is a serialized content and a request for new serialized content is received, new serialized content is added based on the current version of the target content.

[0113] This includes, before receiving a version revision request for the target content, the following:

[0114] Obtain the historical requirements of your partners;

[0115] Based on the historical needs of the partners, at least one preset version of the general content is established.

[0116] Example 4

[0117] The present invention also provides a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the content version control method described above.

[0118] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for controlling content versioning, characterized in that, The method includes: Receive version revision requests for the target content; When the version revision requirement is the first revision requirement, the target version is selected from at least one preset general content version according to the first revision requirement; Revise the target content according to the target version; Before receiving a version revision request for the target content, it also includes: Obtain the historical requirements of your partners; Based on the historical needs of the partners, at least one preset version of the general content is established; The general content version is a reusable content version, and the revisions to the general content version only apply to the collaborating parties. The step of revising the target content according to the target version includes: When the target version is compatible with the first revision requirement, the original version of the target content is overwritten with the target version; When the target version is not compatible with the first revision requirement, the target version is revised in a differentiated manner to obtain a new target version, which is then used to cover the original version of the target content. The target new version is obtained by copying the target version and then making differentiated revisions. The target version is one of the reusable general content versions. The reusable general content version is used to process any content in a large amount of cooperation without the assistance of the content partner and is fully supported by the content provider. The step of selecting a target version from at least one preset general content version according to the first revision requirement includes: Obtain the target collaborators corresponding to the aforementioned version revision requirements; Select the general content version bound to the target partner as the target version; If the target partner does not have a bound version of the general content, then the general content version that is closest to the first revision requirement is selected as the target version, and the target version is bound to the target partner.

2. The content version control method according to claim 1, characterized in that, After receiving the revision request for the target content, the method further includes: When the version revision requirement is a second revision requirement, a direct revision is performed on the original version corresponding to the target content.

3. The content version control method according to claim 1, characterized in that, After obtaining the target new version, the process also includes: When the target new version is within the compatibility range of the target version, the target new version shall be used to overwrite the target version.

4. The content version control method according to claim 1, characterized in that, After receiving the version revision request for the target content, the method further includes: When the target content is a serialized content and a request for new serialized content is received, new serialized content is added based on the current version of the target content.

5. A content version control device, characterized in that, include: A receiving module, which is used to receive version revision requests for target content; The selection module is used to select a target version from at least one preset general content version according to the first revision requirement when the version revision requirement is a first revision requirement. A revision module, configured to revise the target content according to the target version; Before receiving a version revision request for the target content, it also includes: Obtain the historical requirements of your partners; Based on the historical needs of the partners, at least one preset version of the general content is established; The general content version is a reusable content version, and the revisions to the general content version only apply to the collaborating parties. The step of revising the target content according to the target version includes: When the target version is compatible with the first revision requirement, the original version of the target content is overwritten with the target version; When the target version is not compatible with the first revision requirement, the target version is revised in a differentiated manner to obtain a new target version, which is then used to cover the original version of the target content. The target new version is obtained by copying the target version and then making differentiated revisions. The target version is one of the reusable general content versions. The reusable general content version is used to process any content in a large amount of cooperation without the assistance of the content partner and is fully supported by the content provider. The step of selecting a target version from at least one preset general content version according to the first revision requirement includes: Obtain the target collaborators corresponding to the aforementioned version revision requirements; Select the general content version bound to the target partner as the target version; If the target partner does not have a bound version of the general content, then the general content version that is closest to the first revision requirement is selected as the target version, and the target version is bound to the target partner.

6. A terminal, characterized in that, The terminal includes: a processor and a computer-readable storage medium communicatively connected to the processor, the computer-readable storage medium being adapted to store a plurality of instructions, and the processor being adapted to invoke the instructions in the computer-readable storage medium to execute the steps of the control method for implementing the content version as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs that can be executed by one or more processors to implement the steps of the content version control method as described in any one of claims 1-4.

Images