A data evaluation system based on standard data assets

Abstract

The present invention relates to the field of intelligent management technology, and in particular to a data evaluation system based on standard data assets, comprising: a disassembler, an encoder, a coding directory, a reuse directory and a processor, wherein data assets are divided into standard functional bodies, and the standard functional bodies are further divided into standard data assets, and data assets are divided and marked. The standard functional bodies and standard data assets are marked separately, thereby reducing the amount of data for reuse checks on the standard functional bodies and standard data assets, so that the reuse status of standard functional bodies and standard data assets can be retrieved in massive data assets, and while effectively improving the reuse detection efficiency, the calling efficiency of the reused standard data assets is effectively improved.

Description

Technical Field

[0001] The present invention relates to the field of intelligent management technology, and in particular to a data evaluation system based on standard data assets. Background Art

[0002] Standard data assets refer to structured or unstructured data recorded electronically or otherwise, such as text, images, voice, video, web pages, databases, sensor signals, etc., which can be measured or traded and can directly or indirectly bring economic and social benefits.

[0003] The evaluation of data assets can effectively improve the circulation of high-quality data assets, enabling them to be applied in a wider range of fields.

[0004] Chinese Patent Authorization Announcement No.: CN117972169B discloses a data asset processing method and system based on algorithm evaluation control, the method comprising: obtaining the target data asset to be processed; calculating the label scores of the target data asset in multiple label dimensions according to preset scoring rules; determining the storage processing parameters of the target data asset according to the label scores of the target data asset in multiple label dimensions; storing the target data asset according to the storage processing parameters. It can be seen that the present invention can score the different dimensions of data assets according to the scoring rules, and then determine the storage parameters of the assets based on this, so as to fully combine the value of different dimensions of assets to determine a more reasonable and efficient storage method, and improve the rationality and efficiency of storage.

[0005] However, the above method has the following problems: it is impossible to accurately evaluate the corresponding number of reproductions of reused data assets, and it is impossible to accurately evaluate the callability performance of functions composed of data assets. Summary of the invention

[0006] To this end, the present invention provides a data evaluation system based on standard data assets to overcome the problems in the prior art that it is impossible to accurately evaluate the corresponding number of reproduction times of reused data assets, and it is impossible to accurately evaluate the callable performance of functions composed of data assets, resulting in reduced accuracy in the evaluation of the reproduction value of data assets and further reduced efficiency in calling data assets.

[0007] To achieve the above object, the present invention provides a data evaluation system based on standard data assets, comprising:

[0008] A disassembler is used to disassemble the data assets in the database into several functional areas according to the preset space, and separate each functional area to form several standard functional bodies;

[0009] The encoder, in response to the separation of the standard functional bodies, solidifies each standard functional body in the database according to a preset space, wherein:

[0010] For any standard function body, a corresponding preamble is set at the front end of the storage spaces occupied by the standard function body, and a corresponding postamble is set at the back end thereof, and each storage space corresponding to each standard function body that has been set is recorded as a standard data asset;

[0011] A coding directory, which is used to set the mapping relationship between each corresponding preamble and each postamble according to the data asset, including:

[0012] The connection relationship between the post-code of any standard data asset in the data asset and / or the standard function body and the pre-code of the next standard data asset, and the pre-code of the starting standard data asset and the post-code of the ending standard data asset of the data asset and / or the standard function body;

[0013] A reuse catalogue, which is used to determine the corresponding replaceable functional bodies according to the content of each standard functional body, and to determine the corresponding replaceable assets according to each standard data asset;

[0014] A processor, which is used to sort the reuse times according to the preamble and postamble corresponding to the replaceable function or the replaceable asset, and output a reuse time evaluation of the corresponding replaceable function;

[0015] The replaceable function is a standard function that appears repeatedly in a number of data assets;

[0016] The replaceable assets are standard data assets that appear repeatedly in several standard functional bodies;

[0017] For any standard data asset, it corresponds to a single prefix and a single suffix;

[0018] The reuse times include asset reuse times and function reuse times.

[0019] Furthermore, when the disassembler disassembles the data assets, it disassembles the data assets according to the preset space, wherein, for a number of preset spaces allocated to any standard functional body, only standard data assets corresponding to the standard functional body are stored.

[0020] Furthermore, each functional area set by the disassembler can be independently operated under corresponding conditions, and each standard data asset separated by the encoder can be read by the processor;

[0021] For a single functional interval, it can consist of at least one standard data asset, and for a functional interval including several standard data assets, it consists only of standard data assets.

[0022] Further, the encoder determines the storage space of the corresponding preset space according to the processing capability of the processor, wherein, for a single preset space, when storing, the preamble is placed at the front end of the corresponding storage space, and the postamble is placed at the back end of the corresponding storage space;

[0023] The storage space is a physical storage area of ​​the preset space. For the preamble, its corresponding starting character is aligned with the starting character space of the storage space. For the postamble, its corresponding ending character is aligned with the ending character space of the storage space.

[0024] Furthermore, when recording any data asset, the coding directory records a number of standard data assets corresponding to the data asset and records each preamble and postamble in sequence according to the order of the standard functional bodies;

[0025] When calling the data asset, the data asset is called according to the coding directory using the preamble and postamble and the corresponding sequence.

[0026] Furthermore, the coding directory also records the standard functional bodies, and when recording any standard functional body, records are made according to the preamble and postamble of several standard data assets contained in the standard functional body and the corresponding sequence;

[0027] The database responds to the compilation of the coding directory, merges the reused standard data assets or the standard functional bodies, and generates corresponding merging instructions;

[0028] When merging, for any standard data asset, the database retains at least one complete data of the standard data.

[0029] Furthermore, the reuse directory records the number of times the standard data assets are merged in response to the merge instruction, and generates a merge number queue for each standard data asset, records several standard data assets that have been merged no less than once as the replaceable assets, and records the merge number corresponding to the replaceable assets as the asset reuse number.

[0030] Furthermore, the reuse directory responds to the merging instruction, and counts the number of occurrences of each standard function body in the database according to the preamble and postamble of the standard function body in the encoding directory, and records the counting result as the function reuse number of the standard function body.

[0031] Furthermore, the processor forms a corresponding asset reuse list and a function reuse list according to the number of times the asset is reused and the number of times the function is reused, and arranges them in reverse order.

[0032] Furthermore, the processor is also provided with a function reuse times interval and an asset reuse times interval;

[0033] For the standard function body whose function reuse times are within the function reuse times interval, the processor records it as a high-value standard function body;

[0034] For the standard data asset whose asset reuse times are within the asset reuse times interval, the processor records it as a high-value data asset;

[0035] Wherein, the function reuse frequency interval is negatively correlated with the capacity of the database;

[0036] The asset reuse times interval is positively correlated with the capacity of the encoding directory.

[0037] Compared with the prior art, the beneficial effect of the present invention lies in that, by dividing data assets into standard functional bodies, and further dividing standard functional bodies into standard data assets, data assets are split and marked, and the amount of data required for reuse checks on standard functional bodies and standard data assets is reduced by marking standard functional bodies and standard data assets separately, thereby being able to retrieve the reuse status of standard functional bodies and standard data assets in massive data assets, effectively improving the efficiency of reuse detection while effectively improving the calling efficiency of reused standard data assets.

[0038] Furthermore, by breaking down data assets into several standard functional bodies and modularizing each data asset, the data asset can be applied and inserted into other data assets with the same functions. This effectively improves the visibility of duplicate content in data assets and the calling efficiency of reusable standard data assets.

[0039] Furthermore, by further disassembling the standard functional body, standard data assets that can be stored in a certain space are formed, so that each standard data asset can be stored in the same storage area and can be quickly called, thereby further improving the calling efficiency of reusable standard data assets.

[0040] Furthermore, by using the directory to call standard functional bodies and standard data assets, the latency of reading all resources is reduced, the efficiency of calling reusable resources is effectively improved, and the stability of each data asset is effectively improved.

[0041] Furthermore, by recording the number of times each standard function body and standard data asset is reused and sorting them, this operation can enable each standard function body or standard data asset to remain active, and highly called standard function bodies and standard data assets to be in a higher active state, thereby effectively improving the stability of each data asset. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 It is a structural schematic diagram of a data evaluation system based on standard data assets of the present invention;

[0043] Figure 2 This is a structural relationship diagram of standard functional sports data assets according to an embodiment of the present invention;

[0044] Figure 3 This is a logic diagram for calling standard data assets according to an embodiment of the present invention. DETAILED DESCRIPTION

[0045] In order to make the objects and advantages of the present invention more clearly understood, the present invention is further described below in conjunction with embodiments; it should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0046] The preferred embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only used to explain the technical principles of the present invention and are not intended to limit the protection scope of the present invention.

[0047] It should be noted that, in the description of the present invention, terms such as "up", "down", "left", "right", "inside" and "outside" indicating directions or positional relationships are based on the directions or positional relationships shown in the drawings. This is merely for the convenience of description and does not indicate or imply that the device or element must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it cannot be understood as a limitation on the present invention.

[0048] In addition, it should be noted that in the description of the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For those skilled in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0049] See also Figure 1 As shown, it is a structural schematic diagram of the data evaluation system based on standard data assets of the present invention, including:

[0050] A disassembler is used to disassemble the data assets in the database into several functional areas according to the preset space, and separate each functional area to form several standard functional bodies;

[0051] The encoder responds to the separation of the standard functional bodies and solidifies each standard functional body in the database according to the preset space, wherein:

[0052] For any standard function body, a corresponding preamble is set at the front end of the storage spaces occupied by the standard function body, and a corresponding postamble is set at the back end thereof, and each storage space corresponding to each standard function body that has been set is recorded as a standard data asset;

[0053] The coding directory is used to set the mapping relationship between each pre-code and each post-code according to the data asset, including:

[0054] The connection relationship between the post-code of any standard data asset and the pre-code of the next standard data asset in the data asset and / or standard function body, and the pre-code of the starting standard data asset and the post-code of the ending standard data asset of the data asset and / or standard function body;

[0055] A reuse catalogue, which is used to determine the corresponding replaceable functional bodies according to the content of each standard functional body, and to determine the corresponding replaceable assets according to each standard data asset;

[0056] A processor, which is used to sort the reuse times according to the prefix and suffix corresponding to the replaceable function or the replaceable asset, and output the reuse times evaluation of the corresponding replaceable function;

[0057] Among them, replaceable functions are standard functions that appear repeatedly in several data assets;

[0058] Interchangeable assets are standard data assets that appear repeatedly in several standard functional bodies;

[0059] For any standard data asset, it corresponds to a single prefix and a single suffix;

[0060] The number of reuses includes the number of asset reuses and the number of function reuses.

[0061] By dividing data assets into standard function bodies, and further dividing standard function bodies into standard data assets, data assets are split and marked, and the standard function bodies and standard data assets are marked separately, the amount of data required for reuse checks on standard function bodies and standard data assets is reduced, so that the reuse status of standard function bodies and standard data assets can be retrieved in massive data assets, which effectively improves the efficiency of reuse detection and the efficiency of calling reusable standard data assets.

[0062] Specifically, when the disassembler disassembles the data assets, it disassembles the data assets according to the preset spaces, wherein a number of preset spaces allocated to any standard functional body only store the standard data assets corresponding to the standard functional body.

[0063] When editing the preamble and postamble, you can edit them as follows:

[0064] Example 1: See Table 1 User Information Preamble and Postamble Allocation Table

[0065] Prefix: 3f4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1

[0066] Data: User message

[0067] Postcode: 0f1e2d3c4b5a6f7e8d9c0b1a2f3e4d5c6b7a8

[0068] Table 1 User information preamble and postamble allocation table

[0069]

[0070] Example 2: See Table 2 File transfer instruction preamble and postamble allocation table

[0071] Prefix: a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8

[0072] Data: File transfer instructions

[0073] Suffix code: 987654321098765432109876543210987654321

[0074] Table 2 File transfer instruction preamble and postamble allocation table

[0075]

[0076] Example 3: See Table 3 Transaction details pre-code and post-code allocation table

[0077] Prefix code: fedcba9876543210fedcba9876543210

[0078] Data: Transaction details

[0079] Suffix code: 0123456789abcdef0123456789abcdef

[0080] Table 3 Transaction details pre-code and post-code allocation table

[0081]

[0082] Example 4: See Table 4 User login information pre-code and post-code allocation table

[0083] Prefix: 1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9

[0084] Data: User login information

[0085] Postcode:f0e1d2c3b4a5f6e7d8c9b0a1f2e3d4c5b6a7

[0086] Table 4 User login information pre-code and post-code allocation table

[0087]

[0088] Example 5: See Table 5 Internet of Things Device Communication Preamble Code and Postamble Code Allocation Table

[0089] Prefix code: 8765432109876543210987654321098765432

[0090] Data: Device status

[0091] Suffix code: abcdef0123456789abcdef0123456789

[0092] Table 5. Allocation table of pre-code and post-code for IoT device communication

[0093]

[0094] It is understandable that the above allocation is only an example. In a specific implementation, the above preamble and postamble do not appear in any standard data asset.

[0095] In the above embodiment, the preset space is 4096Kb.

[0096] See also Figure 2 As shown, it is a structural relationship diagram of the standard function body and data assets in an embodiment of the present invention. It should be particularly pointed out that the data assets in the figure are composed of four standard function bodies. The preamble, standard function body, and postamble in the figure are a whole of the standard function body, and there is no gap between the parts in the figure on the storage hardware;

[0097] By breaking down data assets into several standard functional bodies and modularizing each data asset, data assets can be applied and inserted into other data assets with the same functions. This effectively improves the visibility of duplicate content in data assets and the efficiency of calling reusable standard data assets.

[0098] Specifically, each functional area set by the disassembler can operate independently under corresponding conditions, and each standard data asset separated by the encoder can be read by the processor;

[0099] For a single functional interval, it can consist of at least one standard data asset, and for a functional interval including several standard data assets, it consists only of standard data assets.

[0100] See also Figure 3 As shown, it is a standard data asset call logic diagram of an embodiment of the present invention. In the figure, the standard function body is composed of 8 annotated data assets, wherein the preamble α of the first standard data asset constitutes the first preamble of the standard function body, the postamble Ω of the last standard data asset constitutes the last postamble of the standard function body, and the remaining standard assets are connected end to end to constitute the standard function body;

[0101] The preamble α and the postamble Ω constitute the preamble and postamble of the standard function body;

[0102] It should be noted that a single standard data asset occupies a standard space, which stores the preamble, standard data asset, and postamble of the standard data asset, wherein the preamble occupies the front end of the standard space and the postamble occupies the end of the standard space.

[0103] The encoder determines the storage space of the corresponding preset space according to the processing capability of the processor, wherein, for a single preset space, when storing, the preamble is placed at the front end of the corresponding storage space, and the postamble is placed at the back end of the corresponding storage space;

[0104] The storage space is a physical storage area of ​​a preset space. For the preamble, its corresponding starting character is aligned with the starting character space of the storage space. For the postamble, its corresponding ending character is aligned with the ending character space of the storage space.

[0105] By further disassembling the standard functional body, standard data assets that can be stored in a certain space are formed, so that each standard data asset can be stored in the same storage area and can be quickly called, thereby further improving the calling efficiency of reusable standard data assets.

[0106] Specifically, when recording any data asset, the coding directory records several standard data assets corresponding to the data asset and records each preamble and postamble in sequence according to the order of the standard functional bodies;

[0107] When calling data assets, the data assets are called according to the coding directory using the prefix and suffix codes and the corresponding sequence.

[0108] Specifically, the coding directory also records the standard function body. When recording any standard function body, it records the standard function body according to the prefix and suffix codes of several standard data assets contained in the standard function body and the corresponding sequence;

[0109] The database responds to the compilation of the coding directory, merges the reusable standard data assets or standard functional bodies, and generates corresponding merging instructions;

[0110] When merging, for any standard data asset, the database retains at least one complete data of the standard data.

[0111] In a database, a standard function body may refer to a set of database objects with specific functions, such as stored procedures and functions. When recording these function bodies, you need to record the prefix and suffix codes of the standard data assets (such as tables and views) they depend on, as well as the order in which these data assets are used. This helps maintain data integrity and consistency, and also facilitates tracking the dependencies between data flows and function bodies.

[0112] The compilation of coding catalogs is usually for the purpose of standardizing the management of data and functional entities. In this process, it is necessary to identify and merge standard data assets or standard functional entities that are reused in multiple places. Doing so can reduce data redundancy, improve data consistency, and optimize database performance.

[0113] Merge instructions are a series of operations used to merge duplicate data assets or functional bodies into a unified location for easier management and maintenance. These instructions may include data migration, updating references, refactoring code, etc.

[0114] Keep at least one complete data:

[0115] During the merge process, it is very important to ensure that at least one instance retains the complete data of the standard data assets. This prevents data loss and ensures that all applications and services that rely on this data can work properly during the merge process.

[0116] By using the directory to call standard functions and standard data assets, the latency of reading all resources is reduced, the efficiency of calling reusable resources is effectively improved, and the stability of each data asset is effectively improved.

[0117] Specifically, the reuse directory records the number of times the standard data assets are merged in response to the merge instruction, and generates a merge number queue for each standard data asset, records several standard data assets that have been merged no less than once as replaceable assets, and records the number of merges corresponding to the replaceable assets as the number of asset reuses.

[0118] Specifically, the reuse directory responds to the merge instruction, and counts the number of occurrences of each standard function body in the database according to the preamble and postamble of the standard function body in the encoding directory, and records the counting result as the function reuse number of the standard function body.

[0119] Specifically, the processor forms a corresponding asset reuse list and function reuse list according to the number of asset reuse times and the number of function reuse times, and arranges them in reverse order.

[0120] By recording the number of times each standard function body and standard data asset is reused and sorting them, this operation can enable each standard function body or standard data asset to remain active, and highly called standard function bodies and standard data assets to be in a highly active state, thereby effectively improving the stability of each data asset.

[0121] Specifically, the processor also has a function reuse times interval and an asset reuse times interval;

[0122] For a standard function body whose function reuse times are within the function reuse times interval, the processor records it as a high-value standard function body;

[0123] For standard data assets whose asset reuse times are within the asset reuse times range, the processor records them as high-value data assets;

[0124] Among them, the interval of function reuse times is negatively correlated with the capacity of the database;

[0125] The interval of asset reuse times is positively correlated with the capacity of the encoding directory.

[0126] In implementation, when the database capacity is large, the function reuse interval can be set lower:

[0127] For example, for a database with a total capacity of 40T, the corresponding function reuse times range is 20-60 times;

[0128] For a database with a total capacity of 20T, the corresponding function reuse times range is 150-200 times;

[0129] It can be understood that by setting the function reuse interval in the above manner, a smaller database can be loaded with more data assets to a certain extent, and a larger database can be loaded with less repeated data assets, so as to improve the corresponding space utilization respectively;

[0130] The interval of asset reuse times is positively correlated with the capacity of the encoding directory;

[0131] It is understandable that the number of times an asset is reused is only stored by the encoding directory, and the greater the load of the encoding directory, the greater the amount of data that can be reused.

[0132] When setting the reuse interval, an algorithm can be deployed based on a service function chain according to a effective function sequence (LEFS). The algorithm aims to jointly optimize function reuse and bandwidth requirements, and gradually searches for relay nodes according to LEFS while controlling the path length until the service request is met.

[0133] It should be noted that the above-mentioned function reuse frequency interval and asset reuse frequency interval should be set according to the actual scenario. After the initial setting, when reducing or expanding the capacity, adjustments should be made according to the direction recorded in this plan.

[0134] So far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present invention is obviously not limited to these specific embodiments. Without departing from the principle of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present invention.

[0135] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A data evaluation system based on standard data assets, characterized in that: include: A disassembler is used to disassemble the data assets in the database into several functional areas according to the preset space, and separate each functional area to form several standard functional bodies; The encoder, in response to the separation of the standard functional bodies, solidifies each standard functional body in the database according to the preset space, wherein: For any standard function body, a corresponding preamble is set at the front end of the storage spaces occupied by the standard function body, and a corresponding postamble is set at the back end thereof, and each storage space corresponding to each standard function body that has been set is recorded as a standard data asset; A coding directory, which is used to set the mapping relationship between each corresponding preamble and each postamble according to the data asset, including: The connection relationship between the post-code of any standard data asset in the data asset and / or the standard function body and the pre-code of the next standard data asset, and the pre-code of the starting standard data asset and the post-code of the ending standard data asset of the data asset and / or the standard function body; A reuse catalogue, which is used to determine the corresponding replaceable functional bodies according to the content of each standard functional body, and to determine the corresponding replaceable assets according to each standard data asset; A processor, which is used to sort the reuse times according to the preamble and postamble corresponding to the replaceable function or the replaceable asset, and output a reuse time evaluation of the corresponding replaceable function; The replaceable function is a standard function that appears repeatedly in a number of data assets; The replaceable assets are standard data assets that appear repeatedly in several standard functional bodies; For any standard data asset, it corresponds to a single prefix and a single suffix; The reuse times include asset reuse times and function reuse times.

2. The data evaluation system based on standard data assets according to claim 1, characterized in that: When the disassembler disassembles the data assets, the disassembler disassembles the data assets according to the preset spaces, wherein a plurality of preset spaces allocated to any standard functional body only store the standard data assets corresponding to the standard functional body.

3. The data evaluation system based on standard data assets according to claim 1, characterized in that: Each functional area set by the disassembler can be independently operated under corresponding conditions, and each standard data asset separated by the encoder can be read by the processor; For a single functional interval, it can consist of at least one standard data asset, and for a functional interval including several standard data assets, it consists only of standard data assets.

4. The data evaluation system based on standard data assets according to any one of claims 2 or 3, characterized in that: The encoder determines the storage space of the corresponding preset space according to the processing capability of the processor, wherein, for a single preset space, when storing, the preamble is placed at the front end of the corresponding storage space, and the postamble is placed at the back end of the corresponding storage space; The storage space is a physical storage area of ​​the preset space. For the preamble, its corresponding starting character is aligned with the starting character space of the storage space. For the postamble, its corresponding ending character is aligned with the ending character space of the storage space.

5. The data evaluation system based on standard data assets according to claim 4, characterized in that: When recording any data asset, the coding directory records several standard data assets corresponding to the data asset and records the preambles and postambles in sequence according to the order of the standard functional bodies; When calling the data asset, the data asset is called according to the coding directory using the preamble and postamble and the corresponding sequence.

6. The data evaluation system based on standard data assets according to claim 5, characterized in that: The coding directory also records the standard functional bodies. When recording any standard functional body, the coding directory records the standard functional body according to the preamble and postamble of several standard data assets contained in the standard functional body and the corresponding sequence. The database responds to the compilation of the coding directory, merges the reused standard data assets or the standard functional bodies, and generates corresponding merging instructions; When merging, for any standard data asset, the database retains at least one complete data of the standard data.

7. The data evaluation system based on standard data assets according to claim 6, characterized in that: The reuse directory records the number of times the standard data assets are merged in response to the merge instruction, and generates a merge number queue for each standard data asset, records several standard data assets that have been merged no less than once as the replaceable assets, and records the number of merges corresponding to the replaceable assets as the asset reuse number.

8. The data evaluation system based on standard data assets according to claim 6, characterized in that: The reuse directory responds to the merging instruction, and counts the number of occurrences of each standard function body in the database according to the preamble and postamble of the standard function body in the encoding directory, and records the counting result as the function reuse number of the standard function body.

9. The data evaluation system based on standard data assets according to any one of claims 7 or 8, characterized in that: The processor forms a corresponding asset reuse list and a function reuse list according to the asset reuse times and the function reuse times, and arranges them in reverse order.

10. The data evaluation system based on standard data assets according to claim 9, characterized in that: The processor is also provided with a function reuse times interval and an asset reuse times interval; For the standard function body whose function reuse times are within the function reuse times interval, the processor records it as a high-value standard function body; For the standard data asset whose asset reuse times are within the asset reuse times interval, the processor records it as a high-value data asset; Wherein, the function reuse frequency interval is negatively correlated with the capacity of the database; The asset reuse times interval is positively correlated with the capacity of the encoding directory.

Images