Archive management method and device, electronic equipment and storage medium

Abstract

The application discloses an archive management method and device, electronic equipment and storage medium. The archive management method comprises the following steps: receiving to-be-managed archives sent by different data sources, classifying each to-be-managed archive based on the record object information corresponding to each to-be-managed archive, obtaining an archive set corresponding to each record object, selecting a unified identifier from the superior archive identifiers corresponding to each to-be-managed archive of the archive set, taking the unified identifier as the superior archive identifier to which each to-be-managed archive in the archive set belongs, achieving the normalization of multi-level archives of the same record object, avoiding resource waste caused by the regeneration of a combined archive, and simplifying the execution logic of archive combination.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, electronic device, and storage medium for file management. Background Technology

[0002] Traditional record management simply archives and stores the records reported by various subordinate platforms. This is usually achieved by merging multiple records into a single merged record. This involves a large amount of data processing. Furthermore, if the record structure is complex, it will greatly increase the computing and storage resources required for archiving, resulting in a slow archiving speed and thus poor record management effectiveness. Summary of the Invention

[0003] This application provides at least one document management method, document management device, electronic device, and computer-readable storage medium.

[0004] The first aspect of this application provides a file management method, comprising: receiving files to be managed sent from different data sources, wherein the files to be managed contain the superior file identifier of the file to be managed in the corresponding data source; classifying each file to be managed based on the recorded object information corresponding to each file to be managed, thereby obtaining a file set corresponding to each recorded object; selecting a unified identifier from the superior file identifiers corresponding to each file to be managed in the file set, and using the unified identifier as the superior file identifier of each file to be managed in the file set.

[0005] In one embodiment, selecting a unified identifier from the superior file identifiers corresponding to each file to be managed in the file set includes: calculating the quality score of each file to be managed in the file set; selecting the file to be managed whose quality score meets the preset requirements as the unified file; and using the superior file identifier corresponding to the unified file as the unified identifier.

[0006] In one embodiment, the file to be managed is associated with multiple subordinate files; calculating the quality score of each file to be managed in the file set includes: counting the number of subordinate files associated with each file to be managed in the file set; and obtaining the quality score of each file to be managed in the file set based on the file count results.

[0007] In one embodiment, the quality score of each file to be managed in the file set is obtained based on the statistical results of the number of files, including: obtaining the number score of the subordinate files of each file to be managed in the file set based on the statistical results of the number of files; and calculating the parameter quality of the subordinate files associated with each file to be managed in the file set to obtain the parameter score of the subordinate files of each file to be managed in the file set; and performing weighted calculation on the number score of the subordinate files and the parameter score of the subordinate files of each file to be managed in the file set to obtain the quality score of each file to be managed in the file set.

[0008] In one embodiment, calculating the quality score of each file to be managed in the file set includes: obtaining the parameter items contained in the file to be managed; calculating the parameter completeness of the file to be managed based on the parameter item content corresponding to each parameter item; and obtaining the quality score of each file to be managed in the file set based on the parameter completeness of each file to be managed.

[0009] In one embodiment, the file to be managed is associated with a superior file through a superior file identifier in the corresponding data source. The superior file is used to store the recorded object information. Before classifying each file to be managed based on the recorded object information corresponding to each file to obtain the file set corresponding to each recorded object, the method further includes: if the superior file associated with the file to be managed does not store recorded object information, then the file to be managed is regarded as a file to be filed; extracting the identity representation parameters from the file to be filed; comparing the identity representation parameters with the identity information in the preset identity information database, and using the successfully compared identity information as the recorded object information corresponding to the file to be filed; returning the recorded object information corresponding to the file to be filed to the data source corresponding to the file to be filed, so that the data source corresponding to the file to be filed stores the recorded object information corresponding to the file to be filed in the superior file associated with the file to be filed.

[0010] In one embodiment, after using the unified identifier as the identifier of the superior file to which each file to be managed belongs in the file set, the method further includes: receiving a file query request sent by the query requester, determining the unified identifier corresponding to the file query request; querying the file associated with the unified identifier of the file query request; and returning the queried file to the query requester.

[0011] The second aspect of this application provides a file management device, comprising: a data receiving module for receiving files to be managed sent from different data sources, wherein the files to be managed contain the superior file identifier of the file to be managed in the corresponding data source; a classification module for classifying each file to be managed based on the recorded object information corresponding to each file to be managed, thereby obtaining a file set corresponding to each recorded object; and a unification module for selecting a unified identifier from the superior file identifiers corresponding to each file to be managed in the file set, and using the unified identifier as the superior file identifier of each file to be managed in the file set.

[0012] A third aspect of this application provides an electronic device, including a memory and a processor, wherein the processor is used to execute program instructions stored in the memory to implement the above-described file management method.

[0013] The fourth aspect of this application provides a computer-readable storage medium having program instructions stored thereon, which, when executed by a processor, implement the above-described file management method.

[0014] The above solution receives files to be managed from different data sources. Each file contains the identifier of its parent file in the corresponding data source. Based on the record object information of each file, the system categorizes each file to obtain a file set corresponding to each record object. A unified identifier is then selected from the parent file identifiers of each file in the file set and used as the parent file identifier of each file in the file set. This achieves the normalization of multi-level files with the same record object, avoids the waste of resources caused by regenerating and merging files, and simplifies the execution logic of file merging.

[0015] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this application. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0017] Figure 1 This is a flowchart illustrating a file management method in an exemplary embodiment of this application;

[0018] Figure 2 This is a file architecture diagram illustrating an exemplary embodiment of this application;

[0019] Figure 3 This is a schematic diagram illustrating the relationship between multiple levels of files as shown in an exemplary embodiment of this application;

[0020] Figure 4 This is a schematic diagram illustrating the uniformity of identifiers in an exemplary embodiment of this application;

[0021] Figure 5 This is a schematic diagram illustrating an application scenario of an exemplary embodiment of this application;

[0022] Figure 6 This is a block diagram illustrating a file management device in an exemplary embodiment of this application;

[0023] Figure 7 This is a schematic diagram of the structure of an embodiment of the electronic device of this application;

[0024] Figure 8 This is a schematic diagram of the structure of an embodiment of the computer-readable storage medium of this application. Detailed Implementation

[0025] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0026] In the following description, specific details such as particular system architectures, interfaces, and technologies are presented for illustrative purposes rather than for limiting purposes, in order to provide a thorough understanding of this application.

[0027] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "many" in this document means two or more. Moreover, the term "at least one" in this document means any combination of at least two of any one or more of a plurality of elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from A, B, and C.

[0028] The file management method provided in the embodiments of this application will be described below.

[0029] Please see Figure 1 , Figure 1 This is a flowchart illustrating a file management method in an exemplary embodiment of this application.

[0030] like Figure 1 As shown, in an exemplary embodiment, the file management method includes at least steps S110 to S130, which are described in detail below:

[0031] Step S110: Receive files to be managed from different data sources. The files to be managed contain the parent file identifier of the file to be managed in the corresponding data source.

[0032] The data source is used to acquire and record relevant data of the recorded object to form an archive, such as image data generated by the recorded object in various activities, and attribute information of the recorded object. The recorded object includes, but is not limited to, pedestrians, vehicles, and pets. The data recorded in the archive includes, but is not limited to, images, trajectories, and attribute information of the recorded object. The attribute information of the recorded object includes, but is not limited to, the type, name, and identity information of the recorded object. It is understood that the type of recorded object and the content of the archive can be flexibly designed according to actual application conditions, and this application does not impose any limitations on them.

[0033] It is important to emphasize that the archives involved in this application are hierarchically structured. Different levels of archives are used to store different types of data to optimize the data storage architecture and facilitate subsequent maintenance and application of this data. For example, the archive hierarchy is divided into first-level archives, second-level archives, and third-level archives, from highest to lowest. First-level archives are the superior archives of second-level archives, and second-level archives are the superior archives of third-level archives. A superior archive can be associated with one or more subordinate archives. Archives at different levels can be linked through archive identifiers. For instance, second-level archive B1 stores the archive identifier of first-level archive A1 to indicate that second-level archive B1 is a subordinate archive of first-level archive A1.

[0034] For example, taking the application of archives in a scenario of storing facial information as an example, the archive architecture of this application will be described, such as... Figure 2 As shown, the first-level archive includes a portrait archive for storing human attribute information; the second-level archive includes a face archive for storing facial images and a body archive for storing posture images; and the third-level archive includes a face trajectory archive for storing facial trajectories and a body trajectory archive for storing limb trajectories. The field design for each archive can be as follows: Figure 3 As shown, the fields in a portrait profile include, but are not limited to, profile creation time, portrait profile ID (IdentityDocument), target person's identity information, target person's face cover image, and body cover image; the fields in a face profile include, but are not limited to, profile creation time, the corresponding portrait profile ID, and face profile ID; the fields in a body profile include, but are not limited to, profile creation time, the corresponding portrait profile ID, and body profile ID; the fields in a face trajectory profile include, but are not limited to, profile creation time, the corresponding face profile ID, and face trajectory profile ID; the fields in a body trajectory profile include, but are not limited to, profile creation time, the corresponding body profile ID, and body trajectory profile ID. Therefore, face profiles and body profiles are associated with their corresponding parent profiles through the field "corresponding portrait profile ID," meaning that the field "corresponding portrait profile ID" is the identifier of the parent profile to which the face profile and body profile belong.

[0035] Therefore, storing different types of data through archives at different levels optimizes the data storage architecture and facilitates data management. However, when dealing with archive architectures with multiple levels, merging archives from different data sources becomes complex due to the complexity of the archive architecture. The merging logic needs to consider archives at each level, leading to complex merging logic and high computational resource requirements. Based on this, this application provides an archive management method.

[0036] The file management method of this application can be applied to a central file aggregation platform, which is communicatively connected to at least one data source to receive files to be managed uploaded by each data source. The files to be managed uploaded by the data source can be complete data of a file; alternatively, the files can be partial data of a file, such as when the data source selects key data items of the file to be uploaded, generates a file to be managed based on these key data items, and then uploads the generated file to the central file aggregation platform. This application does not limit the specific content of the files to be managed uploaded by the data source.

[0037] The files to be managed contain the identifier of the parent file of the corresponding data source to which the file to be managed belongs. The parent file identifier is used to indicate the parent file to which the file to be managed belongs.

[0038] Step S120: Based on the record object information corresponding to each record to be managed, classify each record to be managed to obtain the record set corresponding to each record object.

[0039] The recorded object information is used to indicate the relevant information of the object recorded in the file corresponding to the file to be managed. The recorded object information may be the identity information of the recorded object, the image information of the recorded object, etc.

[0040] The same record object can exist in different data sources. It is necessary to classify each received record object according to the record object information corresponding to each record object to obtain the record set corresponding to each record object.

[0041] For example, if object 'a' has its facial data collected by the acquisition device of data source 1, and data source 1 stores the facial profile of object 'a', and object 'a' has its facial data collected by the acquisition device of data source 2, and data source 2 also stores the facial profile of object 'a', then object 'a' will receive facial profiles for management from both data source 1 and data source 2. Therefore, the object information is extracted from the facial profiles for management sent by each data source. This object information includes, but is not limited to, the object's identity information and facial image contained in the facial profiles for management. Then, each facial profile for management is divided based on the object information to obtain a set of facial profiles corresponding to each object.

[0042] In some implementations, the central archive platform also has an archive generation function, so the archives to be managed contained in the archive collection can include not only those sent by the data source, but also those generated by the central archive platform itself.

[0043] Step S130: Select a unified identifier from the superior file identifiers corresponding to each file to be managed in the file set, and use the unified identifier as the superior file identifier to which each file to be managed in the file set belongs.

[0044] Each file to be managed has a corresponding superior file identifier, which can be selected from multiple superior file identifiers according to preset identifier selection rules.

[0045] For example, there are multiple preset identifier selection rules. The identifier selection rules can be selected according to the number of files to be managed in the file set, the type of data source corresponding to the files to be managed, etc. Based on the selected identifier selection rules, a unified identifier is selected from the parent file identifiers corresponding to each file to be managed in the file set, thereby improving the accuracy of the selected unified identifier.

[0046] The unified identifier corresponding to the selected archive set is used as the superior archive identifier for each archive to be managed in the archive set, so as to realize the logical merging of archives.

[0047] For example, by establishing a relationship between the unified identifier and the identifier of each file to be managed in the file collection, the relationship between files to be managed corresponding to the same recorded object can be indicated. Subsequently, by querying the unified identifier, all file identifiers of the corresponding recorded object can be obtained, and thus all related files of that recorded object can be obtained. Since the file information of the data source is not modified, but rather the files associated with the recorded object are traced in the data source through the file identifier, compared to the existing technology that requires merging and storing all files of the recorded object in each data source on a central archive platform, this application logically associates the files to be managed for the same recorded object through the unified identifier, eliminating the need to regenerate a merged file of multiple files. This not only saves storage resources but also simplifies the execution logic of file merging and saves computational resources.

[0048] For example, such as Figure 4 As shown, multiple data sources send files to be managed to the central archive platform. Based on the information of the recorded objects corresponding to each file, the files are categorized, resulting in a collection of files corresponding to each recorded object. Figure 3 Taking the illustrated file structure as an example, the file set corresponding to target person P1 contains multiple face files, such as... Figure 4As shown in Table 1, a face profile contains the face profile ID and the image profile ID of the image profile to which the face profile belongs. A unified identifier, "P11111111," is selected from multiple image profile IDs and used as the image profile ID for each face profile in the profile set. If the image profile ID of each face profile in the profile set is modified to the unified identifier "P11111111," the modification result is as follows. Figure 4 As shown in Table 2.

[0049] In some implementations, the files to be managed in this application are files at the adjacent level of the highest-level file. For example, if the highest-level file is a first-level file, then the files to be managed are second-level files. By unifying the file identifiers of the first-level files stored in the second-level files, files at all levels of the same recorded object can be associated.

[0050] This application receives files to be managed from different data sources. Each file contains the identifier of its parent file in the corresponding data source. Based on the record object information of each file, the file is classified to obtain a file set corresponding to each record object. A unified identifier is selected from the parent file identifiers of each file in the file set and used as the parent file identifier of each file in the file set. This achieves file normalization for the same record object, avoids the waste of resources caused by regenerating and merging files, and simplifies the execution logic of file merging.

[0051] The following is an example illustrating the process of selecting a unified identifier:

[0052] In some implementations, a unified identifier is selected from the superior file identifiers corresponding to each file to be managed in the file set, including: calculating the quality score of each file to be managed in the file set, selecting the file to be managed that meets the preset requirements as the unified file, and using the superior file identifier corresponding to the unified file as the unified identifier.

[0053] The quality score reflects the quality of the files to be managed. Files whose quality scores meet the preset requirements can be the files with the highest quality scores in the file collection.

[0054] By selecting files from the file collection that meet the preset quality score requirements as unified files, and using the corresponding superior file identifier as the unified identifier, the accuracy of obtaining the unified identifier is improved.

[0055] For example, the files to be managed are associated with multiple subordinate files; calculate the quality score of each file to be managed in the file set, and select the files to be managed that meet the preset requirements as unified files from the file set, including: counting the number of subordinate files associated with each file to be managed in the file set; and obtaining the quality score of each file to be managed in the file set based on the file count results.

[0056] Each file to be managed corresponds to a subordinate file. By counting the number of subordinate files associated with each file to be managed, a quality score is obtained for each file to be managed.

[0057] For example, with Figure 3 Taking the illustrated file structure as an example, the files to be managed include face files, and each face file corresponds to a lower-level file, face trajectory files. The number of face trajectory files corresponding to each received face file is counted. The more face trajectory files there are, the higher the quality of the data source that generated the face trajectory file and the face file, and thus the higher the quality of the face file ID. Therefore, based on the number of face trajectory files associated with a face file, a quality score is obtained for each face file. The higher the number of associated face trajectory files, the higher the quality score of the corresponding face file; conversely, the lower the number of associated face trajectory files, the lower the quality score of the corresponding face file.

[0058] Then, based on the quality score, each file to be managed in the file set is sorted, and the file with the highest quality score is selected as the unified file from the sorting results.

[0059] In some implementations, in addition to considering the number of subordinate files associated with the file to be managed, the quality of the file parameters of the subordinate files associated with the file to be managed can also be further considered. For example, the quality score of each file to be managed in the file set can be obtained based on the file quantity statistics, including: obtaining the number score of subordinate files of each file to be managed in the file set based on the file quantity statistics; and calculating the parameter quality of the subordinate files associated with each file to be managed in the file set to obtain the parameter score of the subordinate files of each file to be managed in the file set; and performing weighted calculations on the number score of subordinate files and the parameter score of subordinate files of each file to be managed in the file set to obtain the quality score of each file to be managed in the file set.

[0060] The quality parameters of lower-level archives are used to reflect the quality of lower-level archives.

[0061] The quality of parameters in lower-level archives can be determined by the completeness of the parameters, the quality of the parameter content (such as the clarity of image parameters, whether there is stuttering in audio or video parameters), and the deployment location of the acquisition equipment corresponding to the parameters.

[0062] After obtaining the parameter quality of each subordinate file of the file to be managed, the parameter score of the subordinate file of the file to be managed is calculated. For example, the parameter quality of each subordinate file can be added together, and then the sum of the parameter quality can be divided by the number of subordinate files. The average parameter quality of the resulting subordinate files is used as the parameter score of the subordinate file of the file to be managed.

[0063] Then, obtain the quantity weight corresponding to the quantity score of the lower-level archives and the parameter weight corresponding to the parameter score of the lower-level archives. Based on the quantity weight, calculate the weighted quantity score of the lower-level archives of each archive to be managed in the archive set. Also, calculate the weighted parameter score of the lower-level archives of each archive to be managed in the archive set based on the parameter weight. Finally, sum the quantity score weight and the parameter score weight to obtain the quality score of each archive to be managed in the archive set.

[0064] In some implementations, the quality score of the file to be managed can be calculated by calculating the parameter quality of the subordinate files associated with each file to be managed in the file set, and then calculating the parameter quality of each subordinate file associated with the file to be managed.

[0065] In some implementations, the quality score of each file to be managed in the file set is calculated, and the files to be managed that meet the preset requirements are selected as unified files from the file set. This includes: obtaining the parameter items contained in the files to be managed; calculating the parameter completeness of the files to be managed based on the parameter item content corresponding to each parameter item; and obtaining the quality score of each file to be managed in the file set based on the parameter completeness of each file to be managed.

[0066] The files to be managed contain multiple parameter items. Due to differences in data sources, some parameter items in the files may lack corresponding content. Therefore, the process involves obtaining all the parameter items in the files to be managed, calculating the parameter completeness of each file based on its corresponding content, and then obtaining a quality score for each file in the file set based on its parameter completeness. A higher parameter completeness results in a higher quality score, and vice versa.

[0067] For example, if the file to be managed contains a record object identity field, and the parameter item corresponding to the record object identity field of file 1 to be managed is not empty, while the parameter item corresponding to the record object identity field of file 2 to be managed is empty, then the quality score of file 1 to be managed is higher than the quality score of file 2 to be managed.

[0068] In some implementations, the file to be managed is associated with a superior file through a superior file identifier in the corresponding data source. The superior file is used to store the recorded object information. However, the recorded object information in the superior file of some data sources is empty. In this case, the superior file and other files associated with the superior file can be used as files to be filed. The steps for filing the files to be filed include: if the superior file associated with the file to be managed does not store recorded object information, then the file to be managed is used as the file to be filed; extracting the identity representation parameters from the file to be filed; comparing the identity representation parameters with the identity information in a preset identity information database, and using the successfully compared identity information as the recorded object information corresponding to the file to be filed; and returning the recorded object information corresponding to the file to be filed to the data source corresponding to the file to be filed, so that the data source corresponding to the file to be filed stores the recorded object information corresponding to the file to be filed in the superior file associated with the file to be filed.

[0069] Identity representation parameters are used to represent the identity parameters of the recorded object in the archive to be filed, including but not limited to the image, audio, and text description of the recorded object. The specific parameter content can be flexibly selected according to the actual application scenario, and this application does not limit it.

[0070] The central archive platform can pre-store an identity information database containing the identity information of multiple known recorded individuals. For example, if the recorded individuals are pedestrians on the streets of a target area, the identity information database is used to store the identity information of the permanent residents of that target area, such as ID card number, ID photo, age, and gender.

[0071] Extract the identity representation parameters from the file to be filed, compare the identity representation parameters with the identity information in the preset identity information database, use the successfully compared identity information as the record object information corresponding to the file to be filed, and return the record object information corresponding to the file to be filed to the data source corresponding to the file to be filed, so that the data source corresponding to the file to be filed will store the record object information corresponding to the file to be filed in the parent file associated with the file to be filed, thus realizing the filing of the file that has not been filed.

[0072] In some implementations, after using the unified identifier as the identifier of the superior file to which each file to be managed belongs in the file set, the method further includes: receiving a file query request sent by a query requester, determining the unified identifier corresponding to the file query request; querying the file associated with the unified identifier of the file query request; and returning the queried file to the query requester.

[0073] For example, the archives corresponding to the recorded object contain images of the recorded object. The central archive aggregation platform supports image-based document search. For each recorded object, it can select the best representational image of the recorded object from all the images contained in the archives associated with the unified identifier of the recorded object. This selection can be based on factors such as image clarity, the proportion of the recorded object in the image, and the posture of the recorded object in the image, ensuring the accuracy of the best representational image and facilitating subsequent image-based document search. Then, based on a neural network model, features are extracted from the best representational image to obtain the feature vector corresponding to the best representational image. This feature vector is then associated and stored with the unified identifier corresponding to the recorded object. Further, the archive query request sent by the querying party contains a query image. Features are extracted from the query image in the archive query request to obtain a target feature vector. The vector distance between the target feature vector and each pre-stored feature vector is calculated. The smaller the vector distance, the more similar the two vectors are. The unified identifier corresponding to the feature vector with the shortest vector distance is selected as the unified identifier corresponding to the archive query request.

[0074] Then, the system queries the files associated with the unified identifier of the file query request and returns the retrieved files to the requesting party. The files associated with the unified identifier of the file query request include, but are not limited to: the file to be managed associated with the unified identifier, the parent file corresponding to the file to be managed, and the child file corresponding to the file to be managed. The files returned to the requesting party can be flexibly selected according to the actual application and the specific needs of the requesting party; this application does not impose any limitations on this.

[0075] For example, with Figure 4 For example, if the unified identifier of the determined file query request is the image file ID "P11111111", and the query results show that the face file IDs associated with the image file ID "P11111111" include "P22222222" and "P44444444", the face files corresponding to "P22222222" and "P44444444" can both be returned to the query requester. Alternatively, the face file with the highest quality score can be selected from the face files corresponding to "P22222222" and "P44444444" and returned to the query requester. Furthermore, the face file with the highest quality score, as well as the subordinate files associated with that face file, can also be returned to the query requester. This application does not limit the scope of this application.

[0076] by Figure 2 and Figure 3 The following example of the file structure illustrates an exemplary application scenario of this application:

[0077] For example, please see Figure 5 , Figure 5This is a schematic diagram illustrating an application scenario of an exemplary embodiment of this application, such as... Figure 5 As shown, the central image aggregation platform communicates with multiple data sources through a Software as a Service (SaaS) gateway. These data sources may include the open-source stream processing platform Kafka and its corresponding image aggregation platform. The Kafka-based image aggregation platform aggregates and archives the collected facial images, body images, and trajectory information of each recorded object to obtain corresponding facial profiles, body profiles, facial trajectory profiles, and body trajectory profiles for each recorded object. Then, the image aggregation platform sends these facial profiles, body profiles, facial trajectory profiles, and body trajectory profiles to the central image aggregation platform for centralized management via its corresponding Kafka and SaaS gateway.

[0078] The data receiving module of the central data aggregation platform receives face files, body files, face trajectory files, and body trajectory files uploaded from various image aggregation platforms. It then performs logical association processing on the received data. This logical association processing may include: classifying the face and body files based on the recorded object information corresponding to each face and body file, obtaining a file set for each recorded object. This file set includes face and body files of a unified recorded object. Then, based on the number of face and body trajectory files associated with each face and body file in the file set, the face or body file with the most associated files is selected as the unified file, and the image file ID to which this unified file belongs is used as the unified identifier. The image file IDs to which each face and body file in the file set belong are then modified to the unified identifier.

[0079] It is understood that in the specific implementation of this application, data related to identity information, facial images, and human images are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0080] This application receives files to be managed from different data sources. Each file contains the identifier of its parent file in the corresponding data source. Based on the record object information of each file, the file is classified to obtain a file set corresponding to each record object. A unified identifier is selected from the parent file identifiers of each file in the file set and used as the parent file identifier of each file in the file set. This achieves the normalization of multi-level files with the same record object, avoids the waste of resources caused by regenerating and merging files, and simplifies the execution logic of file merging.

[0081] Figure 6 This is a block diagram illustrating a file management device according to an exemplary embodiment of this application. Figure 6 As shown, the exemplary file management device 600 includes: a data receiving module 610, a classification module 620, and a unification module 630. Specifically:

[0082] The data receiving module 610 is used to receive files to be managed sent from different data sources, wherein the files to be managed contain the identifier of the superior file to which the file to be managed belongs in the corresponding data source;

[0083] The classification module 620 is used to classify each file to be managed based on the recorded object information corresponding to each file to be managed, so as to obtain the file set corresponding to each recorded object.

[0084] The unified module 630 is used to select a unified identifier from the superior file identifiers corresponding to each file to be managed in the file set, and use the unified identifier as the superior file identifier to which each file to be managed in the file set belongs.

[0085] In the aforementioned exemplary file management device, by receiving files to be managed from different data sources, each file to be managed is classified based on the recorded object information corresponding to each file to be managed, resulting in file sets corresponding to each recorded object. A unified identifier is selected from the superior file identifiers corresponding to each file to be managed in the file set, and the unified identifier is used as the superior file identifier to which each file to be managed in the file set belongs. This achieves the normalization of multi-level files with the same recorded object, avoids the waste of resources caused by regenerating and merging files, and simplifies the execution logic of file merging.

[0086] The functions of each module can be found in the implementation examples of the file management method, and will not be repeated here.

[0087] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of an embodiment of the electronic device of this application. The electronic device 700 includes a memory 701 and a processor 702. The processor 702 is used to execute program instructions stored in the memory 701 to implement the steps in any of the above-described file management method embodiments. In a specific implementation scenario, the electronic device 700 may include, but is not limited to, a microcomputer or a server. In addition, the electronic device 700 may also include mobile devices such as laptops and tablets, which are not limited here.

[0088] Specifically, processor 702 controls itself and memory 701 to implement the steps in any of the above-described file management method embodiments. Processor 702 can also be referred to as a CPU (Central Processing Unit). Processor 702 may be an integrated circuit chip with signal processing capabilities. Processor 702 can also be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor. Furthermore, processor 702 can be implemented using integrated circuit chips.

[0089] Please see Figure 8 , Figure 8 This is a schematic diagram of a computer-readable storage medium according to an embodiment of the present application. The computer-readable storage medium 800 stores program instructions 810 that can be executed by a processor. The program instructions 810 are used to implement the steps in any of the above-described file management method embodiments.

[0090] In some embodiments, the functions or modules of the apparatus provided in this disclosure can be used to perform the methods described in the above method embodiments. The specific implementation can be referred to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0091] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

[0092] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus implementations described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0093] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for managing archives, characterized in that, The data source is used to record data of the recorded objects to form archives. These archives are hierarchically structured, and archives at different levels are linked through archive identifiers. The method includes: Receive files to be managed from different data sources, wherein the files to be managed contain the parent file identifier of the file to be managed in the corresponding data source; Based on the record object information corresponding to each record object, each record object is classified to obtain a set of records corresponding to each record object. A unified identifier is selected from the superior file identifiers corresponding to each file to be managed in the file set, and the unified identifier is used as the superior file identifier to which each file to be managed in the file set belongs. The unified identifier logically associates files to be managed that have the same record object.

2. The method according to claim 1, characterized in that, The step of selecting a unified identifier from the parent file identifiers corresponding to each file to be managed in the file set includes: Calculate the quality score of each file to be managed in the file set; Select files from the file set that meet the preset quality score requirements as unified files; The identifier of the superior archive corresponding to the unified archive is used as the unified identifier.

3. The method according to claim 2, characterized in that, The files to be managed are associated with multiple subordinate files; the calculation of the quality score for each file to be managed in the file set includes: Count the number of subordinate files associated with each file to be managed in the aforementioned file set; Based on the statistical results of the number of archives, the quality score of each archive to be managed in the archive set is obtained.

4. The method according to claim 3, characterized in that, The quality score for each file to be managed in the file set is obtained based on the statistical results of the number of files, including: Based on the statistical results of the number of archives, a score is obtained for the number of subordinate archives for each archive to be managed in the archive set; and, Calculate the parameter quality of the subordinate files associated with each file to be managed in the file set, and obtain the parameter score of the subordinate files of each file to be managed in the file set; The quality score of each file to be managed in the file set is obtained by weighting the scores of the number of subordinate files and the parameter scores of the subordinate files for each file to be managed in the file set.

5. The method according to claim 2, characterized in that, The calculation of the quality score for each file to be managed in the file set includes: Obtain the parameter items contained in the file to be managed; The parameter completeness of the file to be managed is calculated based on the parameter content corresponding to each parameter item; Based on the parameter completeness of each of the files to be managed, a quality score is obtained for each file in the file set.

6. The method according to claim 1, characterized in that, The files to be managed are associated with a superior file through a superior file identifier in the corresponding data source, and the superior file is used to store the information of the recorded objects; before classifying each file to be managed based on the recorded object information corresponding to each file to obtain the file set corresponding to each recorded object, the method further includes: If the parent file associated with the file to be managed does not store the object information, then the file to be managed will be treated as a file to be filed. Extract the identity representation parameters from the files to be filed; The identity representation parameters are compared with the identity information in the preset identity information database, and the identity information that is successfully compared is used as the recording object information corresponding to the file to be filed. The record object information corresponding to the file to be filed is returned to the data source corresponding to the file to be filed, so that the data source corresponding to the file to be filed stores the record object information corresponding to the file to be filed in the parent file associated with the file to be filed.

7. The method according to any one of claims 1 to 6, characterized in that, After using the unified identifier as the identifier of the superior file to which each file to be managed belongs in the file set, the method further includes: Receive a file query request sent by the query requester and determine the unified identifier corresponding to the file query request; Retrieve the files associated with the Uniform Identifier of the file retrieval request; The retrieved files are returned to the requesting party.

8. A file management device, characterized in that, The data source is used to record data of the objects being recorded, forming archives. These archives are hierarchically structured, and archives at different levels are linked through archive identifiers, including: The data receiving module is used to receive files to be managed sent from different data sources, wherein the files to be managed contain the parent file identifier of the file to be managed in the corresponding data source; The classification module is used to classify each file to be managed based on the recorded object information corresponding to each file to be managed, so as to obtain the file set corresponding to each recorded object. The unified module is used to select a unified identifier from the parent file identifiers corresponding to each file to be managed in the file set, and use the unified identifier as the parent file identifier to which each file to be managed belongs in the file set. The unified identifier logically associates files to be managed that have the same record object.

9. An electronic device, characterized in that, It includes a memory and a processor, the processor being configured to execute program instructions stored in the memory to implement the method of any one of claims 1 to 7.

10. A computer-readable storage medium having program instructions stored thereon, characterized in that, When the program instructions are executed by the processor, they implement the method of any one of claims 1 to 7.

Images