Design file historical version retrieval method and device based on container historical name

Abstract

The invention discloses a container historical name-based design file historical version retrieval method and device, and the method comprises the steps: storing the metadata of each design file and the historical version thereof in a collaborative design platform, the metadata comprising a file name, a historical version, editing time, a container name and associated information; creating an index for the container name in the metadata to obtain a container index database, and storing the container name and the use frequency thereof contained in each historical version of the design file; calculating the weight value of each historical version according to the use frequency of the container name in the container index database, the editing time and the matching degree of the search keyword to obtain a weight model; and performing weight sorting on the container names input by the user according to the weight model, and sorting and displaying the historical versions according to the output weight values. According to the method, the container name is used as a retrieval condition, so that the efficiency and experience of searching the historical version by the user are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of software design, and particularly to a method and device for retrieving historical versions of design files based on container historical names. Background Art

[0002] With the popularization of design collaboration tool platforms, teams often need to manage a large number of historical versions of files in design projects. Especially during the design process, different versions of design files are often stored in the collaboration tool platform for subsequent retrieval and comparison. However, due to the inconsistent naming conventions of design files, when users search for historical versions, they often need to rely on file names or timestamps for queries, resulting in low search efficiency and the inability to quickly find the required versions.

[0003] Most existing design tools are based on standard search conditions such as file names, dates, or editors, but often ignore the importance of key components (such as containers) in the internal structure of design files. The containers included in design files may represent certain specific design parts or modules, and the names of the containers remain stable during design evolution. Therefore, searching based on container historical names can more accurately help users find specific historical versions of design files.

[0004] To solve the above problems, the present invention develops a method and device for retrieving historical versions of design files based on container historical names. By using the container name as a retrieval condition, the efficiency of users searching for historical versions in design collaboration tools is improved, and the most relevant historical versions are preferentially presented to users. Summary of the Invention

[0005] In view of the above problems, a method and device for retrieving historical versions of design files based on container historical names are proposed to improve the efficiency and experience of users searching for historical versions in design collaboration tools.

[0006] According to one aspect of the present invention, a method for retrieving historical versions of design files based on container historical names is provided, including:

[0007] Storing metadata of each design file and its historical versions in a collaborative design platform, where the metadata includes file name, historical version, editing time, container name, and association information;

[0008] Creating an index for the container names in the metadata to obtain a container index library, and storing the container names included in each historical version of the design file and their usage frequencies;

[0009] Calculating the weight value of each historical version according to the usage frequency, editing time, and matching degree of search keywords of the container names in the container index library to obtain a weight model;

[0010] Sort the container names input by the user according to the weight model, and sort and display each historical version according to the output weight value.

[0011] In an optional manner, the weight model includes a container name frequency weight, a time weight, a file version weight, and a matching degree weight;

[0012] Among them, the container name frequency weight is the frequency that appears in the corresponding historical version file, and the higher the frequency, the greater the weight;

[0013] The time weight is the time in the corresponding historical version file, and the closer the time is to the current time, the higher the time weight;

[0014] The matching degree weight is the matching degree between the container name input by the user and the container name of the corresponding historical version.

[0015] In an optional manner, when displaying the historical versions, support the user to select, view, download, or restore the historical versions.

[0016] In an optional manner, the associated information includes the reference, inheritance, or combination relationship between containers;

[0017] When calculating the weight values of each historical version, if the container name searched by the user exists in the associated information, then increase the weight of the historical versions corresponding to the other containers in the associated information.

[0018] In an optional manner, the file version weight is adjusted according to the maturity of the historical version; among them, the maturity includes the number of times the file is referenced by other design files, the number of times it is rolled back by the user, and the number of defects repaired.

[0019] In an optional manner, when the user views the historical version, compare the selected historical version with the version of the current design file or other historical versions; among them, the content of the difference comparison includes the add, delete, modify, and query operation records of the container name, container attributes, and the association relationship between containers;

[0020] Present the difference results of the difference comparison in a highlighted display or a visual chart.

[0021] In an optional manner, the metadata further includes the attribute override information of the container instance; among them, the attribute override information of the container instance includes the attribute change records of each container instance relative to its source container.

[0022] In an alternative approach, when the user selects to restore a historical version, the container instances in the current design file are replaced with the container instances in the historical version; wherein, the attribute override information of the container instances is automatically updated, or multiple selected container instances are replaced with the container instances in the historical version to restore the local state of the design file.

[0023] In an alternative approach, the association relationship further includes an attribute association relationship of container variants, and the attribute association relationship of container variants includes an attribute mapping relationship between different variants of the container; wherein, the attribute mapping relationship includes a color variant and a size variant.

[0024] According to another aspect of the present application, there is provided a device for retrieving historical versions of a design file based on a container historical name, including:

[0025] A metadata storage module for storing metadata of each design file and its historical versions in a collaborative design platform, wherein the metadata includes a file name, a historical version, an editing time, a container name, and association information;

[0026] A container index module for creating an index for the container names in the metadata to obtain a container index library, and storing the container names included in each historical version of the design file and their usage frequencies;

[0027] A weight calculation module for calculating weight values of each historical version according to the usage frequencies of the container names, the editing time, and the matching degree of search keywords in the container index library to obtain a weight model;

[0028] A weight sorting module for sorting the container names input by the user according to the weight model, and sorting and displaying each historical version according to the output weight values.

[0029] According to yet another aspect of the present application, there is provided a computing device, including: a processor, a memory, a communication interface, and a communication bus, and the processor, the memory, and the communication interface complete communication with each other through the communication bus;

[0030] The memory is used for storing at least one executable instruction, and the executable instruction causes the processor to perform operations corresponding to the above method for retrieving historical versions of a design file based on a container historical name.

[0031] The solution provided in the above embodiments of the present invention stores the metadata of each design file and its historical versions in a collaborative design platform, where the metadata includes file name, historical version, editing time, container name, and association information; creates an index for the container names in the metadata to obtain a container index library, and stores the container names included in each historical version of the design file and their usage frequencies; calculates the weight values of each historical version according to the usage frequencies of the container names, editing time, and matching degree of search keywords in the container index library to obtain a weight model; sorts the container names input by the user according to the weight model, and sorts and displays each historical version according to the output weight values. By using the container name as a retrieval condition, the present invention preferentially displays the most relevant historical versions to the user, improving the efficiency and experience of designers searching for historical versions in a design collaboration tool.

[0032] The above description is only an overview of the technical solution of the present invention. In order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the specification. And in order to make the above description and other purposes, features, and advantages of the present invention more obvious and understandable, the following specifically describes the embodiments of the present invention. Brief Description of the Drawings

[0033] By reading the following detailed description of the preferred embodiments, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only for the purpose of showing the preferred embodiments and are not considered to be a limitation of the present invention. Moreover, throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:

[0034] Figure 1 shows a flowchart of a method for retrieving historical versions of design files based on container historical names according to an embodiment of the present invention;

[0035] Figure 2 shows a functional structure diagram of a device for retrieving historical versions of design files based on container historical names according to an embodiment of the present invention;

[0036] Figure 3 shows a structural diagram of a computing device provided by an embodiment of the present application. Detailed Description of the Embodiments

[0037] Hereinafter, the exemplary embodiments of the present invention will be described in more detail with reference to the drawings. Although the exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided so that the present invention can be more thoroughly understood and the scope of the present invention can be fully conveyed to those skilled in the art.

[0038] Before implementing the embodiments of the present invention, the technical terms or custom terms involved in the following text are uniformly explained herein:

[0039] Component: It allows the UI to be divided into independent and reusable parts. In practical applications, components are often organized into a tree-like structure with nested layers.

[0040] Container: Formerly known as "drawing board", it is an important design component of design software, such as iPhone container, A4 paper container.

[0041] Instance: An instance refers to a specific reference to a component. What the user drags out from the component list or copies and pastes from a component is an "instance", rather than the component itself.

[0042] Variable component: A component placed in a component set container that is given multiple attributes (defining the nature and relationships of the variable component) and values (defining the specific characteristics or parameters of the attributes).

[0043] Variable instance: An instance of a variable component.

[0044] The following through specific embodiments, the method and device for retrieving historical versions of design files based on container historical names proposed by the present invention are described in detail.

[0045] Embodiment 1:

[0046] Figure 1 The functional structure diagram of the method for retrieving historical versions of design files based on container historical names according to the embodiments of the present invention is shown. Specifically, as Figure 1 shown, it includes the following steps:

[0047] Step S101, storing the metadata of each design file and its historical versions in a collaborative design platform, where the metadata includes file name, historical version, edit time, container name, and association information.

[0048] In this embodiment, historical version management is performed according to the containers inside the design file, which can facilitate the designer team members to quickly find the historical versions they care about and provide more refined version tracing and recovery capabilities. Among them, the metadata can be stored in a database or directly embedded in the design file itself. The association information includes information such as associated files, associated tasks, and associated users.

[0049] In an optional manner, the association information includes reference, inheritance, or composition relationships between containers;

[0050] When calculating the weight values of each historical version, if the container name searched by the user exists in the association information, the weights of the historical versions corresponding to other containers in the association information are increased.

[0051] In this embodiment, through the association information, it is easier for designers to discover associated containers and quickly locate relevant design files and historical versions. If the container name searched by the user exists in the association information, the weight of the historical versions of the relevant containers is increased, and the weight of the historical versions can be adjusted according to the relationship type (reference, inheritance, composition) and the relationship depth (direct association, indirect association).

[0052] In an alternative way, the metadata further includes attribute override information of container instances; wherein, the attribute override information of container instances includes the attribute change records of each container instance relative to its source container.

[0053] In this embodiment, the attribute override information records the history of each attribute change. If it is necessary to roll back to the previous configuration, it is convenient to find and apply the previous attribute settings. By recording attribute changes, the configuration consistency of container instances can be ensured, and the time of each change can be traced.

[0054] Step S102: Create an index for the container names in the metadata to obtain a container index library, and store the container names and their usage frequencies included in each historical version of the design file.

[0055] In this embodiment, storing the container names included in each historical version of the design file can track the change information of the container names. Among them, the index library not only stores the container names, but also records the usage frequencies of the containers in each historical version, so as to provide more relevant results during retrieval.

[0056] Step S103: Calculate the weight values of each historical version according to the usage frequency, editing time of the container names in the container index library, and the matching degree of the search keywords, and obtain a weight model.

[0057] In this embodiment, the higher the usage frequency of the container version, the higher the weight; the higher the weight of the container version edited recently; the higher the weight of the version with a higher matching degree between the search keyword and the container name. The above three weight values are weighted and summed to obtain a weight model. Among them, the weight model includes the frequency weight of the container name, the time weight, the file version weight, and the matching degree weight. The frequency weight of the container name is the frequency of occurrence in the corresponding historical version file, and the higher the frequency, the greater the weight; the time weight is the time in the corresponding historical version file, and the closer the time is to the current time, the higher the time weight; the matching degree weight is the matching degree between the container name input by the user and the container name of the corresponding historical version. By assigning different importance to the usage frequency, editing time, and the matching degree of the search keywords through the weight model, the historical version that best matches the user's search intention can be preferentially displayed, reducing the time for the user to screen and compare.

[0058] In an alternative approach, the weights of the file versions are adjusted according to the maturity of the historical versions; wherein, the maturity includes the number of times the file is referenced by other design files, the number of times it is rolled back by users, and the number of defects fixed.

[0059] In this embodiment, the weight of the version rolled back by the user is reduced to avoid using versions with problems, reduce unnecessary regression, and versions with fewer fixed defects are usually more reliable. Priority is given to mature versions, reducing the time for problem troubleshooting and fixing, improving design efficiency, and avoiding blindly selecting the latest version.

[0060] For example, the design file includes two historical versions, design.v1.1 (number of references: 10, number of rollbacks: 2, number of defects: 1) and design.v1.2 (number of references: 5, number of rollbacks: 0, number of defects: 0).

[0061] After Z-score standardization, the version weights of each historical version are shown in Table 1.

[0062] Table 1

[0063]

[0064] As can be seen from Table 1, the weight of design.v1.1 is higher, and when choosing a version, design.v1.1 is preferred. Also, when merging design.v1.1 and design.v1.2, if there are conflicts, the modifications of design.v1.1 are preferentially retained.

[0065] Step S104, perform a weight sorting on the container names input by the user according to the weight model, and sort and display each historical version according to the output weight value.

[0066] In this embodiment, when displaying historical versions, users are supported to select, view, download, or restore historical versions. When the user views a historical version, the selected historical version is compared with the version of the current design file or other historical versions; wherein, the content of the difference comparison includes the add, delete, modify, and query operation records of the container name, container attributes, and the association relationship between containers; the difference results of the difference comparison are presented in a highlighted display or a visual chart. In this embodiment, the association relationship also includes the attribute association relationship of container variants, and the attribute association relationship of container variants includes the attribute mapping relationship between different variants of the container; wherein, the attribute mapping relationship includes color variants and size variants.

[0067] In an alternative approach, when the user selects to restore a historical version, the container instances in the current design file are replaced with the container instances in the historical version. Among them, the attribute override information of the container instances is automatically updated, or multiple selected container instances are replaced with the container instances in the historical version to restore the partial state of the design file.

[0068] In this embodiment, compared with fully rolling back the entire design file, the user is allowed to selectively restore the historical versions of specific container instances, avoiding the loss of unnecessary modifications. By replacing multiple selected container instances, the partial state of the design file can be restored, such as restoring the design style or layout of a specific area without affecting the design of other areas. Therefore, by automatically updating the attribute override information of the container instances, it is ensured that the restored container instances are consistent with the design intention of the historical version. Figure 1 In a multi-person collaborative design environment, since only local modifications need to be traced back without affecting the state of the entire design file, restoring the historical versions of specific container instances reduces conflicts with other designers. Designers can quickly try different design solutions and easily trace back to the previous state when needed, accelerating the design iteration process and design experience.

[0069] For example, the design file contains a button container instance of "Button1". Among them, the initial version (V1): the color of "Button1" is blue and the size is 100x30. The modified version (V2): the designer changes the color of "Button1" to red. The current version (V3): another designer changes the size of "Button1" to 120x40.

[0070] If the current designer wishes to restore the color of "Button1" to blue in version V1 but requires the size to remain 120x40 in version V3.

[0071] Then the "Button1" container instance can be selected. In the historical version browsing interface, select version V1 and click the "Replace" button to replace "Button1" with version V1. Then the color of "Button1" is automatically updated to blue, but the size remains 120x40 in version V3.

[0072] The solution provided in the above embodiments of the present invention stores the metadata of each design file and its historical versions in a collaborative design platform, where the metadata includes file name, historical version, editing time, container name, and association information; creates an index for the container names in the metadata to obtain a container index library, and stores the container names included in each historical version of the design file and their usage frequencies; calculates the weight values of each historical version according to the usage frequencies, editing times, and matching degrees of search keywords of the container names in the container index library to obtain a weight model; sorts the container names input by the user according to the weight model, and sorts and displays each historical version according to the output weight values. By using the container name as a retrieval condition, the present invention preferentially displays the most relevant historical versions to the user, improving the efficiency and experience of designers searching for historical versions in a design collaboration tool.

[0073] Embodiment 2:

[0074] Figure 2 The functional structure diagram of the device for retrieving historical versions of design files based on container historical names according to the embodiments of the present invention is shown. As Figure 2 shown, the device includes:

[0075] A metadata storage module 201 for storing the metadata of each design file and its historical versions in a collaborative design platform, where the metadata includes file name, historical version, editing time, container name, and association information;

[0076] A container index module 202 for creating an index for the container names in the metadata to obtain a container index library, and storing the container names included in each historical version of the design file and their usage frequencies;

[0077] A weight calculation module 203 for calculating the weight values of each historical version according to the usage frequencies, editing times, and matching degrees of search keywords of the container names in the container index library to obtain a weight model;

[0078] A weight sorting module 204 for sorting the container names input by the user according to the weight model, and sorting and displaying each historical version according to the output weight values.

[0079] In an optional manner, the weight model includes a container name frequency weight, a time weight, a file version weight, and a matching degree weight;

[0080] wherein, the container name frequency weight is the frequency of occurrence in the corresponding historical version file, and the higher the frequency, the greater the weight;

[0081] The time weight is the time in the corresponding historical version file. The closer the time is to the current time, the higher the time weight.

[0082] The matching degree weight is the matching degree between the container name entered by the user and the container name in the corresponding historical version.

[0083] In an optional manner, when presenting the historical versions, the user is supported to select, view, download, or restore the historical versions.

[0084] In an optional manner, the associated information includes the reference, inheritance, or composition relationship between containers.

[0085] When calculating the weight values of each historical version, if the container name searched by the user exists in the associated information, the weights of the historical versions corresponding to the other containers in the associated information are increased.

[0086] In an optional manner, the file version weight is adjusted according to the maturity of the historical version; wherein, the maturity includes the number of times the file is referenced by other design files, the number of times it is rolled back by the user, and the number of defects repaired.

[0087] In an optional manner, when the user views the historical version, the selected historical version is compared with the version of the current design file or other historical versions; wherein, the content of the difference comparison includes the add, delete, modify, and query operation records of the container name, the container attributes, and the association relationship between containers.

[0088] The difference results of the difference comparison are presented in the form of highlighting or a visualization chart.

[0089] In an optional manner, the metadata further includes the attribute override information of the container instance; wherein, the attribute override information of the container instance includes the attribute change records of each container instance relative to its source container.

[0090] In an optional manner, when the user selects to restore the historical version, the container instances in the current design file are replaced with the container instances in the historical version; wherein, the attribute override information of the container instances is automatically updated, or multiple selected container instances are replaced with the container instances in the historical version to restore the local state of the design file.

[0091] In an optional manner, the association relationship further includes the attribute association relationship of the container variant, and the attribute association relationship of the container variant includes the attribute mapping relationship between different variants of the container; wherein, the attribute mapping relationship includes color variants and size variants.

[0092] The solution provided by the above embodiments of the present invention stores the metadata of each design file and its historical versions in a collaborative design platform, where the metadata includes file name, historical version, editing time, container name, and association information; creates an index for the container names in the metadata to obtain a container index library, and stores the container names included in each historical version of the design file and their usage frequencies; calculates the weight values of each historical version according to the usage frequencies of the container names, editing time, and matching degree of search keywords in the container index library to obtain a weight model; sorts the container names input by the user according to the weight model, and sorts and displays each historical version according to the output weight values. By using the container name as a retrieval condition, the present invention preferentially displays the most relevant historical versions to the user, improving the efficiency and experience of designers searching for historical versions in a design collaboration tool.

[0093] Embodiment 3:

[0094] Figure 3 FIG. shows a schematic structural diagram of an embodiment of a computing device of the present invention, and the specific implementation of the computing device is not limited in the specific embodiments of the present invention.

[0095] As Figure 3 shown, the computing device may include: a processor 302, a communication interface 304, a memory 306, and a communication bus 308.

[0096] Among them: The processor 302, the communication interface 304, and the memory 306 communicate with each other through the communication bus 308. The communication interface 304 is used to communicate with network elements of other devices such as clients or other servers. The processor 302 is used to execute the program 310, and specifically can execute the relevant steps in the above embodiments of the method for retrieving historical versions of design files based on container historical names.

[0097] Specifically, the program 310 may include program code, and the program code includes computer operation instructions.

[0098] The processor 302 may be a central processing unit CPU, or a specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present invention. One or more processors included in the computing device may be of the same type of processor, such as one or more CPUs; or may be of different types of processors, such as one or more CPUs and one or more ASICs.

[0099] A memory 306 for storing a program 310. The memory 306 may include high-speed RAM memory and may also include non-volatile memory, such as at least one disk memory.

[0100] According to the solution provided by the present invention, metadata of each design file and its historical versions are stored in a co-design platform, where the metadata includes file name, historical version, editing time, container name, and association information; an index is created for the container name in the metadata to obtain a container index library, and the container names included in each historical version of the design file and their usage frequencies are stored; weight values of each historical version are calculated according to the usage frequencies of the container names, editing time, and matching degrees of search keywords in the container index library to obtain a weight model; the container names input by a user are sorted by weight according to the weight model, and each historical version is sorted and displayed according to the output weight values. By using the container name as a retrieval condition, the present invention preferentially displays the most relevant historical versions to the user, improving the efficiency and experience of designers searching for historical versions in a design collaboration tool.

[0101] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems may also be used in conjunction with the teachings provided herein. The structure required to construct such a system will be apparent from the above description. In addition, the embodiments of the present invention are not directed to any particular programming language. It should be understood that the content of the present invention described herein can be implemented using various programming languages, and the description of a particular language above is for the purpose of disclosing the best mode of the present invention.

[0102] In the specification provided herein, a large number of specific details are set forth. However, it can be understood that the embodiments of the present invention may be practiced without these specific details. In some instances, well-known methods, structures, and technologies have not been shown in detail so as not to obscure the understanding of this specification.

[0103] Similarly, it should be understood that, in order to streamline the present invention and assist in understanding one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, the disclosed method should not be construed as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as reflected in the following claims, the inventive aspects lie in less than all the features of the single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into the detailed description, with each claim standing on its own as a separate embodiment of the present invention.

[0104] Those skilled in the art can understand that the modules in the devices in the embodiments can be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments can be combined into one module or unit or component, and in addition, they can be divided into multiple sub-modules or sub-units or sub-components. Except that at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all the features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all the processes or units of any method or device so disclosed. Unless otherwise clearly stated, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) can be replaced by an alternative feature that provides the same, equivalent, or similar purpose.

[0105] In addition, those skilled in the art can understand that although some of the embodiments herein include certain features included in other embodiments rather than other features, the combination of the features of different embodiments means that it is within the scope of the present invention and forms different embodiments. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

[0106] Each component embodiment of the present invention can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) can be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of the present invention. The present invention can also be implemented as a device or apparatus program (such as a computer program and a computer program product) for executing part or all of the methods described herein. Such a program for implementing the present invention can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0107] It should be noted that the above embodiments are illustrative of the present invention rather than restrictive thereof, and alternative embodiments can be designed by those skilled in the art without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in the claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention can be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In the unit claims listing several devices, several of these devices can be embodied by the same item of hardware. The use of the words first, second, and third, etc. does not denote any order. These words can be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be construed as limiting the order of execution.

Claims

1. A design file historical version retrieval method based on container historical name, characterized in that: include: Storing metadata of each design file and its historical versions in the collaborative design platform, wherein the metadata includes file name, historical version, editing time, container name and associated information; Creating an index for the container name in the metadata to obtain a container index library, and storing the container names and usage frequencies contained in each historical version of the design file; Calculating the weight value of each historical version according to the usage frequency, editing time and matching degree of the search keyword of the container name in the container index library to obtain a weight model; The container names input by the user are weighted and sorted according to the weight model, and each historical version is sorted and displayed according to the output weight value.

2. The design file history version retrieval method based on container history name according to claim 1 is characterized in that: The weight model includes container name frequency weight, time weight, file version weight and matching weight; The container name frequency weight is the frequency of occurrence in the corresponding historical version file, and the higher the frequency, the greater the weight; The time weight is the time in the corresponding historical version file. The closer the time is to the current time, the higher the time weight is. The matching weight is the matching degree between the container name input by the user and the corresponding historical version container name.

3. The design file history version retrieval method based on container history name according to claim 1 is characterized in that: When displaying the historical versions, users are supported to select, view, download or restore the historical versions.

4. The design file history version retrieval method based on container history name according to claim 1 is characterized in that: The association information includes reference, inheritance or combination relationship between containers; When calculating the weight value of each historical version, if the container name searched by the user exists in the associated information, the weight of the historical versions corresponding to other containers in the associated information is increased.

5. The design file history version retrieval method based on container history name according to claim 2 is characterized in that: The file version weight is adjusted according to the maturity of the historical version; wherein the maturity includes the number of times the file is referenced by other design files, the number of times it is rolled back by users, and the number of defects repaired.

6. The design file history version retrieval method based on container history name according to claim 3 is characterized in that: When the user views the historical version, the selected historical version is compared with the version of the current design file or other historical versions; wherein the content of the difference comparison includes the operation records of adding, deleting, modifying and checking the container name, the container attributes and the association relationship between containers; The difference comparison results are presented in the form of highlighted or visual charts.

7. The design file history version retrieval method based on container history name according to claim 3 is characterized in that: The metadata also includes attribute coverage information of the container instance; wherein the attribute coverage information of the container instance includes attribute change records of each container instance relative to its source container.

8. The design file history version retrieval method based on container history name according to claim 7 is characterized in that: When the user chooses to restore the historical version, the container instance in the current design file is replaced with the container instance in the historical version; wherein the property override information of the container instance is automatically updated, or multiple selected container instances are replaced with the container instances in the historical version to restore the local state of the design file.

9. The design file history version retrieval method based on container history name according to claim 4 is characterized in that: The association relationship further includes an attribute association relationship of container variants, and the attribute association relationship of container variants includes an attribute mapping relationship between different variants of the container; wherein the attribute mapping relationship includes color variants and size variants.

10. A design file history version retrieval device based on container history name, characterized in that: include: A metadata storage module, used to store metadata of each design file and its historical versions in the collaborative design platform, wherein the metadata includes file name, historical version, editing time, container name and associated information; A container index module, used to create an index for the container name in the metadata to obtain a container index library, and store the container names and their usage frequencies contained in each historical version of the design file; A weight calculation module, used to calculate the weight value of each historical version according to the usage frequency, editing time and matching degree of search keywords of the container name in the container index library to obtain a weight model; The weight sorting module is used to weight-sort the container names input by the user according to the weight model, and sort and display each historical version according to the output weight value.

Images