CN115718893A - Metadata management method and device - Google Patents
Metadata management method and device Download PDFInfo
- Publication number
- CN115718893A CN115718893A CN202211531209.1A CN202211531209A CN115718893A CN 115718893 A CN115718893 A CN 115718893A CN 202211531209 A CN202211531209 A CN 202211531209A CN 115718893 A CN115718893 A CN 115718893A
- Authority
- CN
- China
- Prior art keywords
- metadata
- management
- checking
- priority
- rule table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 163
- 238000000034 method Methods 0.000 claims abstract description 23
- 238000012986 modification Methods 0.000 claims description 14
- 230000004048 modification Effects 0.000 claims description 14
- 238000012545 processing Methods 0.000 claims description 10
- 238000012790 confirmation Methods 0.000 claims description 6
- 238000013523 data management Methods 0.000 abstract description 4
- 239000002699 waste material Substances 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013075 data extraction Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012946 outsourcing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a metadata management method and a metadata management device, which can be applied to the field of data management. The method comprises the following steps: classifying the stored unchecked metadata according to a preset metadata type; according to a preset value grading table, carrying out value grading on the sorted metadata to obtain the management priority of the metadata and obtain a metadata group to be managed; and checking the metadata group to be managed through a preset checking rule table, and sending a checking result to a user management end. Therefore, the metadata management method classifies the stored metadata according to the metadata types, ensures that each piece of stored unchecked metadata is covered, establishes a management priority for management and check of the metadata, checks the metadata quality on the premise of not wasting check resources, and ensures the accuracy of the metadata, thereby improving the accuracy of management of the metadata.
Description
Technical Field
The present application relates to the field of data management technologies, and in particular, to a metadata management method and apparatus.
Background
At present, data is increasing at an unprecedented rate, and in the era of big outbreak of data, data governance is the basis in the process of realizing data asset creation value of enterprises. The simplest definition of metadata is "data describing data", which has a wide range of information and describes the data itself, the concept of data representation, the relationship between data and concept, and the like. Metadata can help organizations understand their own data, systems, and processes, and help users assess data quality, which is essential for the management of databases and applications.
The metadata itself also needs to be managed. Tools for metadata management in the prior art are currently generally classified into four types, including: the metadata management method realized by the metadata extraction tool, the front-end presentation tool, the modeling tool and the metadata storage tool can only collect and store the metadata, but cannot check and check the quality of the collected and stored metadata (hereinafter referred to as check and check). The failure of quality check of metadata directly results in inaccuracy of metadata, and thus the metadata management method in the prior art lacks accuracy. Therefore, how to design an accurate metadata management method becomes a technical problem which needs to be solved in the field.
Disclosure of Invention
In view of this, embodiments of the present application provide a metadata management method and apparatus, which are intended to meet a requirement of checking metadata quality when managing metadata.
In a first aspect, an embodiment of the present application provides a metadata management method, where the method includes:
classifying the stored unchecked metadata according to a preset metadata type;
according to a preset value grading table, carrying out value grading on the sorted metadata to obtain the management priority of the metadata and obtain a metadata group to be managed;
and checking the metadata group to be managed through a preset checking rule table, and sending a checking result to a user management end.
Optionally, the performing value classification on the classified metadata to obtain a management priority of the metadata, and obtaining a metadata group to be managed includes:
obtaining the value corresponding to each metadata according to the value grading table corresponding to the classified metadata;
determining the management priority of the corresponding metadata according to the value; wherein the management priorities include, first management priority > second management priority > third management priority;
and forming the metadata with the first management priority into a metadata group to be managed.
Optionally, after the metadata with the first management priority is grouped into the metadata group to be managed, the method further includes:
sending the metadata with the second management priority to a user management end;
and marking the metadata with the third management priority as the metadata to be suspended for processing and storing.
Optionally, the checking the metadata group to be managed through a preset checking rule table, and sending the checking result to the user management end includes:
judging whether the metadata in the metadata group to be managed accords with the content of a check rule table; the preset checking rule table comprises a suspected hit checking rule table and an accurate hit checking rule table;
if the metadata accords with the accurate hit and checks the content of the rule table, marking the metadata as the metadata to be modified;
if the metadata only accords with the suspected hit checking rule table content, marking the metadata as metadata to be determined;
and sending the metadata to be modified and the metadata to be determined to a user management end as a checking result.
Optionally, after sending the check result to the user management end, the method further includes:
and marking the stored metadata which does not accord with the content of the checking rule table after checking as checked metadata.
Optionally, the metadata management method further includes:
receiving modification metadata fed back by a user management end;
judging whether the metadata in the storage corresponding to the modified metadata is unchecked metadata or not;
and if the metadata is not checked, the unchecked metadata is replaced by the modified metadata, and if the metadata is not checked, the modified metadata is cached and a modification confirmation request is sent to a user management terminal.
In a second aspect, an embodiment of the present application provides a metadata management apparatus, including:
the classification module is used for classifying the stored unchecked metadata according to the preset metadata types;
the grading module is used for carrying out value grading on the sorted metadata according to a preset value grading table to obtain the management priority of the metadata and obtain a metadata group to be managed;
and the checking module is used for checking the metadata group to be managed through a preset checking rule table and sending a checking result to the user management terminal.
Optionally, the grading module is specifically configured to:
obtaining the value corresponding to each metadata according to the value grading table corresponding to the classified metadata;
determining the management priority of the corresponding metadata according to the value; wherein the management priorities include, first management priority > second management priority > third management priority;
and forming the metadata with the first management priority into a metadata group to be managed.
Optionally, the ranking module is further configured to:
after the metadata with the first management priority form a metadata group to be managed, the metadata with the second management priority is sent to a user management end;
the metadata having the third management priority is marked as suspended processing metadata and stored.
Optionally, the checking module is specifically configured to:
judging whether the metadata in the metadata group to be managed conforms to the content of a check rule table; the preset checking rule table comprises a suspected hit checking rule table and an accurate hit checking rule table;
if the metadata accords with the accurate hit and checks the content of the rule table, marking the metadata as the metadata to be modified;
if the metadata only accords with the suspected hit checking rule table content, marking the metadata as metadata to be determined;
and sending the metadata to be modified and the metadata to be determined to a user management end as a checking result.
The embodiment of the application provides a metadata management method, which comprises the following steps: classifying the stored unchecked metadata according to the type of the preset metadata, grading the value of the classified metadata according to a preset value grading table to obtain a metadata group to be managed, checking the metadata through a preset checking rule table, and sending a checking result to a user management terminal. Therefore, the metadata management method classifies the stored metadata according to the metadata types, ensures that each piece of stored unchecked metadata is covered, establishes a management priority for management and check of the metadata, checks the metadata quality on the premise of not wasting check resources, and ensures the accuracy of the metadata, thereby improving the accuracy of management of the metadata.
In addition, the application also provides a metadata management device, and the technical effect of the metadata management device corresponds to the method, which is not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments or the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, and obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart of a method of managing metadata according to an embodiment of the present application;
fig. 2 is a flowchart of metadata checking and determining provided in an embodiment of the present application;
fig. 3 is a schematic structural diagram of a metadata management apparatus according to an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The simplest definition of metadata is "data describing data", and the information range of metadata is wide, and includes not only technical and business processes, data rules and constraints, but also logical data structures and physical data structures, and the like. It describes the data itself (e.g., database, data elements, data model), the concept of data representation (e.g., business process, application system, software code, technical infrastructure), the association (relationship) between data and concept. Metadata can help organizations understand their own data, systems and processes, and help users assess data quality, which is essential for the management of databases and applications.
Data management requires metadata, which itself also needs to be managed. Continuously optimizing metadata management helps to increase the trustworthiness of data, increase the value of strategic information, increase operational efficiency, avoid the use of outdated or incorrect data, reduce the time to clean up data, and improve communication between data users and developers.
Currently, the tools that manufacturers have related to metadata can be roughly classified into four categories: data extraction tools, namely extracting, converting and integrating data in a business system, which only provide technical metadata and hardly provide support for the business metadata; front-end presentation tool: and the relational table is mapped into a fact table and a dimension table related to the service to support a multidimensional service view, so that multidimensional analysis is performed on the data. Providing a semantic layer of business metadata corresponding to technical metadata; modeling tools: business modeling tools for non-technical personnel that can provide a higher level of business-specific semantics; metadata storage facility: metadata is typically stored in a dedicated database, just like a "black box," that does not externally know how the metadata used and generated by these tools is stored.
However, there is no universal solution for quality checking of metadata. How the quality of metadata acquired by the four tools is, whether the metadata can be trusted or not cannot be known exactly. Since the metadata covers both the business attributes and the technical attributes of the data. Metadata quality management requires coordination and coordination of various teams in an organization, including business management departments, development departments, data management departments, and the like. Therefore, in the background of lacking an efficient solution, the integrity and quality of metadata are hard to be improved.
An embodiment of the present application provides a metadata management method, a flowchart of which is shown in fig. 1, and includes the following steps:
and S10, classifying the stored unchecked metadata according to the preset metadata type.
One piece of metadata comprises three parts, namely a system, a database and a data table, and after the metadata is preliminarily classified according to the three parts, the metadata can be further classified according to a classification mode preset by a user, for example: the system is divided into an offline system, an offline system to be offline, a normal operation independent research and development or combined development system and a normal operation outsourcing system according to the system operation condition. The database is divided into a main library, an archiving library, a backup library and a query library. The data table is divided into a normal use table, an interface or service table, a third party access table, a table accessed by other systems of the department, a temporary table or a history table or a physical table or a product table or a revocation table.
The classification manner may be determined by a user according to specific requirements, and the present application is not specifically limited herein.
And S20, carrying out value grading on the sorted metadata according to a preset value grading table to obtain the management priority of the metadata, and obtaining a metadata group to be managed.
The value ranking table may be as shown in table 1, and the values corresponding to the metadata after classification are obtained. Determining the management priority of each different type of metadata according to the value of the metadata, such as system value grading, high value corresponding to a normal operation system, medium value corresponding to an offline system and an offline system to be offline (incremental data are not generated any more in the system, but stock data still have use value); grading the library value, wherein the main library corresponds to high value, and the filing library or the backup library or the query library corresponds to low value; the table value is graded, the system generates data, and the normal use table and the third-party access table correspond to high value; tables accessed by other systems (metadata of the tables should be managed at a source system), temporary tables or historical tables or physical tables or product tables or revocation tables (most of the tables are technical data tables) correspond to low values.
So that the metadata can be accurately managed subsequently, thereby avoiding the waste of management resources.
TABLE 1
And S30, checking the metadata group to be managed through a preset checking rule table, and sending a checking result to a user management end.
And checking the metadata group to be managed through a checking rule table preset by the user, and sending a checking result to the user management end for the user to confirm. The checking result can be sent to the user management end in the form of a form, so that the user can know which metadata conform to the contents of the checking rule table.
The preset checking rule table may be set according to the requirement of the user, and the application is not specifically limited herein.
Therefore, the metadata management method classifies the stored metadata according to the metadata types, ensures that each piece of stored unchecked metadata is covered, establishes the management priority for the management and checking of the metadata, checks the metadata quality on the premise of not wasting checking resources, and ensures the accuracy of the metadata, thereby improving the accuracy of the management of the metadata.
In some embodiments, step S20 specifically includes:
obtaining the value corresponding to each metadata according to the value grading table corresponding to the classified metadata;
determining the management priority of the corresponding metadata according to the value; wherein the management priorities include, first management priority > second management priority > third management priority;
the management priorities are divided according to the values in the table 1, and the metadata with three values, namely high, medium and low, are respectively corresponding to the first priority, the second priority and the third priority.
And forming the metadata with the first management priority into a metadata group to be managed.
And adopting a direct management strategy for the metadata with high priority to form a management metadata group so as to check the management metadata group in the following.
And sending the metadata with the second management priority to the user management side.
And adopting a policy of managing the metadata with the medium priority as appropriate, and sending the metadata with the medium priority to a user management end to ensure that a user determines the metadata. And if the user determines to manage the metadata, distributing high priority to the corresponding metadata, otherwise, distributing low priority to the corresponding metadata.
The metadata having the third management priority is marked as suspended processing metadata and stored.
And marking the metadata detected as the low priority to suspend processing, not participating in subsequent checking, and directly storing the metadata in the database.
In some specific embodiments, for convenience of further understanding, the checking process in step S30 may specifically include, as shown in the metadata checking and determining flowchart of the metadata management method in fig. 2:
s31, receiving the metadata group to be managed.
And receiving a management metadata group consisting of metadata with high management priority after the metadata is subjected to value grading in the step S20.
S32, judging whether the metadata in the metadata group to be managed conforms to the content of the check rule table; the preset checking rule table comprises a suspected hit checking rule table and an accurate hit checking rule table.
Table 2 is a suspected hit check table, table 3 is an accurate hit check table, and both tables 2 and 3 show the correspondence between the check rule types and the check rules. As shown in table 2, the check rule in the suspected hit table is relatively a range concept, and the metadata quality is not necessarily unqualified after hit, and further judgment is required manually. As shown in table 3, the checking rule in the accurate hit table is relatively an accurate fixed concept, and after hit, it can be determined that the corresponding metadata is not qualified.
TABLE 2
TABLE 3
And S33, marking the stored metadata which does not accord with the content of the checking rule table after checking as checked metadata.
All stored metadata which do not accord with the content of the checking rule table after checking are marked as checked metadata so as to avoid repeated checking in the following process and cause resource waste.
And S34, judging whether the metadata accords with the accurate hit checking rule table content.
In step S33, it is determined that any of the check rule table contents is satisfied, and in step S34, it is determined whether the table contents are satisfied with the exact hit check rule table, and the metadata conforming to the exact hit check rule table is selected.
And S35, if the metadata accords with the accurate hit checking rule table content, marking the metadata as metadata to be modified.
As long as the metadata conforms to the accurate hit checking rule table content, whether the metadata conforms to the suspected hit checking rule table content or not, the metadata is marked as the metadata to be modified, and the metadata corresponds to the specific content which the metadata conforms to.
And S36, if the metadata only accords with the contents of the suspected hit checking rule table, marking the metadata as metadata to be determined.
And when the metadata conforming to the content of the check table is judged not to conform to the accurate hit check rule table content, determining that the metadata only conforms to the suspected hit check rule table content, marking the metadata as the metadata to be determined, and corresponding the metadata to the specific content conforming to the metadata.
And sending the metadata to be modified and the metadata to be determined to a user management end as a checking result.
In some specific embodiments, the metadata management method further includes:
receiving modification metadata fed back by a user management end;
judging whether the metadata in the storage corresponding to the modified metadata is unchecked metadata or not;
and if the metadata is not checked, the unchecked metadata is replaced by the modified metadata, and if the metadata is not checked, the modified metadata is cached and a modification confirmation request is sent to a user management terminal.
And when the user management end needs to modify the stored metadata, receiving the modified metadata sent by the user management end. And determining whether the metadata to be modified is unchecked metadata, and if the metadata is unchecked, indicating that the metadata is the metadata to be modified. If the metadata is not unchecked, the metadata may be checked metadata or the processing metadata is suspended, and the received modified metadata is cached to avoid repeated transmission. And sends a modification confirmation request to the user management side whether to confirm the modification (the metadata is checked) or whether the modification is worth (the metadata is suspended to be processed). If the non-unchecked data is modified, the modified metadata is marked as unchecked metadata.
Based on the metadata management method provided by the above embodiment, an embodiment of the present application provides a device for performing the above metadata management. Fig. 3 is a schematic diagram of the structure of the metadata management apparatus, and the metadata management apparatus includes:
and the classification module 10 is configured to classify the stored unchecked metadata according to a preset metadata type.
The metadata is classified primarily according to the three parts, and then can be further classified according to a classification mode preset by a user.
And the grading module 20 is configured to perform value grading on the sorted metadata according to a preset value grading table to obtain a management priority of the metadata, and obtain a metadata group to be managed.
Wherein the value ranking table may be as shown in table 1 above, to obtain the value corresponding to the metadata after having been classified. The management priorities of each of the heterogeneous metadata are determined according to the values of the metadata so that the metadata can be accurately managed in the following, thereby avoiding waste of management resources.
And the checking module 30 is configured to check the metadata group to be managed through a preset checking rule table, and send a checking result to the user management side.
And checking the metadata group to be managed through a checking rule table preset by the user, and sending a checking result to the user management end for the user to confirm.
In some embodiments, the ranking module is specifically configured to:
obtaining the value corresponding to each metadata according to the value grading table corresponding to the classified metadata;
determining the management priority of the corresponding metadata according to the value; wherein the management priorities include, first management priority > second management priority > third management priority;
the management priorities are divided according to the values in the table 1, and the metadata with three values, namely high, medium and low, are respectively corresponding to the first priority, the second priority and the third priority.
And forming the metadata with the first management priority into a metadata group to be managed.
And adopting a direct management strategy for the metadata with high priority to form a management metadata group so as to check the management metadata group in the following.
And sending the metadata with the second management priority to the user management side.
And adopting a policy of managing the metadata with the medium priority as appropriate, and sending the metadata with the medium priority to a user management end to ensure that a user determines the metadata. If the user determines to manage the metadata, the corresponding metadata are allocated with high priority, otherwise, the corresponding metadata are allocated with low priority.
The metadata having the third management priority is marked as suspended processing metadata and stored.
And marking the metadata detected as the low priority to suspend processing, not participating in subsequent checking, and directly storing the metadata in the database.
In some embodiments, the checking module is specifically configured to:
judging whether the metadata in the metadata group to be managed conforms to the content of a check rule table; the preset checking rule table comprises a suspected hit checking rule table and an accurate hit checking rule table;
if the metadata accords with the accurate hit and checks the content of the rule table, marking the metadata as the metadata to be modified;
if the metadata only accords with the suspected hit checking rule table content, marking the metadata as metadata to be determined;
and sending the metadata to be modified and the metadata to be determined to a user management end as a checking result.
And marking the stored metadata which does not accord with the content of the checking rule table after checking as checked metadata.
As long as the metadata conforms to the accurate hit checking rule table content, whether the metadata conforms to the suspected hit checking rule table content or not, the metadata is marked as the metadata to be modified, and the metadata corresponds to the specific content which the metadata conforms to.
And when the metadata conforming to the checking table content is judged not to conform to the accurate hit checking rule table content, determining that the metadata only conforms to the suspected hit checking rule table content, marking the metadata as the metadata to be determined, and corresponding the metadata to the specific content conforming to the metadata.
In some embodiments, the metadata management apparatus further includes:
receiving modification metadata fed back by a user management end;
judging whether the metadata in the storage corresponding to the modified metadata is unchecked metadata or not;
and if the metadata is not checked, the unchecked metadata is replaced by the modified metadata, and if the metadata is not checked, the modified metadata is cached and a modification confirmation request is sent to a user management terminal.
And when the user management end needs to modify the stored metadata, receiving the modified metadata sent by the user management end. And determining whether the metadata to be modified is unchecked metadata, and if the metadata is unchecked, indicating that the metadata is the metadata to be modified. If the metadata is not unchecked, the metadata may be checked metadata or the processing metadata is suspended, and the received modified metadata is cached to avoid repeated transmission. And sends a modification confirmation request to the user management side whether to confirm the modification (the metadata is checked) or whether the modification is worth (the metadata is suspended to be processed). If the non-unchecked data is modified, the modified metadata is marked as unchecked metadata.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
The above detailed descriptions of the solutions provided in the present application, and the specific examples applied herein are set forth to explain the principles and implementations of the present application, and the above descriptions of the examples are only used to help understand the method and its core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific implementation manner and the application scope may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A method of metadata management, the method comprising:
classifying the stored unchecked metadata according to a preset metadata type;
according to a preset value grading table, carrying out value grading on the sorted metadata to obtain the management priority of the metadata and obtain a metadata group to be managed;
and checking the metadata group to be managed through a preset checking rule table, and sending a checking result to a user management end.
2. The method of claim 1, wherein the value-ranking the classified metadata to obtain a management priority of the metadata and obtain a metadata group to be managed, comprises:
obtaining the value corresponding to each metadata according to the value grading table corresponding to the classified metadata;
determining the management priority of the corresponding metadata according to the value; wherein the management priorities include, first management priority > second management priority > third management priority;
and forming the metadata with the first management priority into a metadata group to be managed.
3. The method according to claim 2, further comprising, after grouping the metadata having the first management priority into the metadata group to be managed:
sending the metadata with the second management priority to a user management end;
the metadata having the third management priority is marked as suspended processing metadata and stored.
4. The method according to claim 1, wherein the checking the metadata group to be managed through a preset checking rule table, and sending the checking result to the user management side comprises:
judging whether the metadata in the metadata group to be managed conforms to the content of a check rule table; the preset checking rule table comprises a suspected hit checking rule table and an accurate hit checking rule table;
if the metadata accords with the accurate hit and checks the content of the rule table, marking the metadata as the metadata to be modified;
if the metadata only accords with the suspected hit checking rule table content, marking the metadata as metadata to be determined;
and sending the metadata to be modified and the metadata to be determined to a user management end as a checking result.
5. The method of claim 4, after sending the checking result to the user management end, further comprising:
and marking the stored metadata which does not accord with the content of the checking rule table after checking as checked metadata.
6. The method of claim 5, wherein the metadata management method further comprises:
receiving modification metadata fed back by a user management end;
judging whether the metadata in the storage corresponding to the modified metadata is unchecked metadata or not;
and if the metadata is not checked, the unchecked metadata is replaced by the modified metadata, and if the metadata is not checked, the modified metadata is cached and a modification confirmation request is sent to a user management end.
7. A metadata management apparatus, characterized in that the apparatus comprises:
the classification module is used for classifying the stored unchecked metadata according to the preset metadata types;
the grading module is used for carrying out value grading on the sorted metadata according to a preset value grading table to obtain the management priority of the metadata and obtain a metadata group to be managed;
and the checking module is used for checking the metadata group to be managed through a preset checking rule table and sending a checking result to the user management terminal.
8. The apparatus of claim 7, wherein the ranking module is specifically configured to:
obtaining the value corresponding to each metadata according to the value grading table corresponding to the classified metadata;
determining the management priority of the corresponding metadata according to the value; wherein the management priorities include, first management priority > second management priority > third management priority;
and forming the metadata with the first management priority into a metadata group to be managed.
9. The apparatus of claim 8, wherein the ranking module is further configured to:
after the metadata with the first management priority form a metadata group to be managed, the metadata with the second management priority is sent to a user management end;
the metadata having the third management priority is marked as suspended processing metadata and stored.
10. The apparatus according to claim 7, wherein the checking module is specifically configured to:
judging whether the metadata in the metadata group to be managed conforms to the content of a check rule table; the preset checking rule table comprises a suspected hit checking rule table and an accurate hit checking rule table;
if the metadata accords with the accurate hit and checks the content of the rule table, marking the metadata as the metadata to be modified;
if the metadata only accords with the suspected hit checking rule table content, marking the metadata as metadata to be determined;
and sending the metadata to be modified and the metadata to be determined to a user management end as a checking result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211531209.1A CN115718893A (en) | 2022-12-01 | 2022-12-01 | Metadata management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211531209.1A CN115718893A (en) | 2022-12-01 | 2022-12-01 | Metadata management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115718893A true CN115718893A (en) | 2023-02-28 |
Family
ID=85257247
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211531209.1A Pending CN115718893A (en) | 2022-12-01 | 2022-12-01 | Metadata management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115718893A (en) |
-
2022
- 2022-12-01 CN CN202211531209.1A patent/CN115718893A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8832148B2 (en) | Enterprise evidence repository | |
| CN110515912A (en) | Log processing method, device, computer installation and computer readable storage medium | |
| CN106682096A (en) | Method and device for log data management | |
| CN112199433A (en) | Data management system for city-level data middling station | |
| CN111324606B (en) | Data slicing method and device | |
| CN111400288A (en) | Data quality inspection method and system | |
| CN114880405A (en) | Data lake-based data processing method and system | |
| CN1717686A (en) | Automatic data consolidation | |
| CN111353762A (en) | Method and system for managing regulations and regulations | |
| CN116719799A (en) | Environment-friendly data management method, device, computer equipment and storage medium | |
| CN111221698A (en) | Task data acquisition method and device | |
| CN109829615B (en) | Target task multistage monitoring device and method based on proprietary cloud | |
| CN112433888B (en) | Data processing method and device, storage medium and electronic equipment | |
| CN113746684A (en) | Network equipment management method and device, computer equipment and storage medium | |
| US20200387802A1 (en) | Dynamically adaptable rules and communication system for managing process controls | |
| CN117472874A (en) | Government affair data resource integrated management system and method based on big data analysis | |
| US11210352B2 (en) | Automatic check of search configuration changes | |
| CN115718893A (en) | Metadata management method and device | |
| WO2023103346A1 (en) | Method and apparatus for creating quantum vehicle model accessory basic database, electronic device, and storage medium | |
| CN115525778A (en) | Enterprise document processing method, device and storage medium | |
| CN111143322A (en) | Data standard treatment system and method | |
| CN111209284A (en) | Metadata-based table dividing method and device | |
| CN113515542A (en) | Method and device for associating pipeline data | |
| CN116702008A (en) | System risk management method, device, terminal equipment and storage medium | |
| CN112819620A (en) | Method and device for collecting rating data of financial institution |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |