CN110851663A - Method and apparatus for managing metadata - Google Patents
Method and apparatus for managing metadata Download PDFInfo
- Publication number
- CN110851663A CN110851663A CN201911069218.1A CN201911069218A CN110851663A CN 110851663 A CN110851663 A CN 110851663A CN 201911069218 A CN201911069218 A CN 201911069218A CN 110851663 A CN110851663 A CN 110851663A
- Authority
- CN
- China
- Prior art keywords
- attribute information
- metadata
- node
- label
- service
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
- G06F16/9024—Graphs; Linked lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Library & Information Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a method and a device for managing metadata. The method comprises the following steps: acquiring service metadata; determining a label node for describing attribute information of the service according to the service metadata; constructing map information of the label nodes according to the subordination relation of the attribute information corresponding to the label nodes; establishing a corresponding relation between the technical metadata acquired in advance and attribute information corresponding to the label nodes in the label map; and managing the technical metadata and the service metadata which have corresponding relations in the label map.
Description
Technical Field
The present disclosure relates to the field of information processing, and more particularly, to a method and apparatus for managing metadata.
Background
Metadata is data describing data, descriptive information for data and information resources. The Metadata (Metadata) is data (data about other data) describing other data, or structural data (structured data) for providing information on a certain resource. Functionally, the metadata may provide user-based information, such as metadata that records business description information for data items that can assist a user in using the data; in addition, management and maintenance of data by the system may also be supported, as metadata about the data item storage method can support the system in accessing data in the most efficient manner.
In the field of data warehousing, metadata is divided into technical metadata and business metadata by purpose. The technical metadata is obscure, the naming of the technical metadata is not standard, the formats are not uniform, the searching and the classification are difficult according to the difference of the data quality and the difference of the service range, and the association between the service information and the service is more difficult to find.
Disclosure of Invention
In order to solve any technical problem, embodiments of the present application provide a method and apparatus for managing metadata.
To achieve the object of the embodiments of the present application, an embodiment of the present application provides a method for managing metadata, including:
acquiring service metadata;
determining a label node for describing attribute information of the service according to the service metadata;
constructing map information of the label nodes according to the subordination relation of the attribute information corresponding to the label nodes;
establishing a corresponding relation between the technical metadata acquired in advance and attribute information corresponding to the label nodes in the label map;
and managing the technical metadata and the service metadata which have corresponding relations in the label map.
In an exemplary embodiment, the determining, according to the service metadata, a tag node for describing attribute information of a service includes:
determining a service corresponding to the service metadata, and using the service as a first-layer label node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and according to the classification result of the attribute information, taking the attribute information of the same classification level as the label node of the same layer, wherein when the classification result of the attribute information comprises at least two classification levels, the attribute information of at least one node in the (i + 1) th level belongs to the attribute information of one label node of the (i) th layer, and i is an integer greater than or equal to 1.
In an exemplary embodiment, the determining, according to the service metadata, a tag node for describing attribute information of a service further includes:
recording instance information between the label node and a lower layer label node subordinate to the label node;
the managing technical metadata and business metadata having a correspondence in the tag map includes:
when a reading request of the technical metadata is received, according to pre-acquired instance information between a tag node and a lower-layer tag node, determining first propagation path information of the read technical metadata from a first-layer tag node to a last-layer tag node, acquiring the technical metadata from the technical metadata corresponding to the last-layer tag node, and responding to the reading request;
and/or the presence of a gas in the gas,
when an analysis request of the technical metadata is received, second propagation path information of the analyzed technical metadata from a label node at the last layer to a label node at the first layer is determined according to pre-acquired example information between the label node and a label node at the lower layer, and the attribute information of the label node through which the backward propagation path information passes is utilized to respond to the analysis request.
In an exemplary embodiment, before the mapping between the technical metadata obtained in advance and the attribute information corresponding to the tag node is established in the tag map, the method further includes;
configuring propagation attribute information for the technical metadata;
the establishing of the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the tag nodes in the tag map includes:
when the corresponding relationship between at least one technical metadata configured with the same propagation attribute information and one target label node is established, the corresponding relationship between other technical metadata configured with the same propagation attribute and the target label node is established.
In an exemplary embodiment, after configuring the propagation attribute information for the technical metadata, the method further comprises;
configuring cascading deletion attribute information for the technical metadata configured with the propagation attribute information;
after the corresponding relationship between the technical metadata acquired in advance and the attribute information corresponding to the tag node is established in the tag map, the method further comprises the following steps:
and when the corresponding relation between at least one technical metadata configured with the same propagation attribute information and one target label node is deleted, deleting the corresponding relation between other technical metadata with the same propagation attribute and the target label node.
An apparatus for managing metadata, comprising a processor and a memory, the memory storing a computer program, the processor for invoking the computer program in the memory to implement operations comprising:
acquiring service metadata;
determining a label node for describing attribute information of the service according to the service metadata;
constructing map information of the label nodes according to the subordination relation of the attribute information corresponding to the label nodes;
establishing a corresponding relation between the technical metadata acquired in advance and attribute information corresponding to the label nodes in the label map;
and managing the technical metadata and the service metadata which have corresponding relations in the label map.
In an exemplary embodiment, the processor is configured to invoke a computer program in the memory to implement the operation of determining a tag node for describing attribute information of a service according to the service metadata, including:
determining a service corresponding to the service metadata, and using the service as a first-layer label node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and according to the classification result of the attribute information, taking the attribute information of the same classification level as the label node of the same layer, wherein when the classification result of the attribute information comprises at least two classification levels, the attribute information of at least one node in the (i + 1) th level belongs to the attribute information of one label node of the (i) th layer, and i is an integer greater than or equal to 1.
In an exemplary embodiment, the processor is configured to invoke a computer program in the memory to implement the operation of determining a tag node for describing attribute information of a service according to the service metadata, including:
recording instance information between the label node and a lower layer label node subordinate to the label node;
the processor is configured to invoke a computer program in the memory to implement the operations of managing technical metadata and business metadata for correspondence in the tag map, including:
when a reading request of the technical metadata is received, according to pre-acquired instance information between a tag node and a lower-layer tag node, determining first propagation path information of the read technical metadata from a first-layer tag node to a last-layer tag node, acquiring the technical metadata from the technical metadata corresponding to the last-layer tag node, and responding to the reading request;
and/or the presence of a gas in the gas,
when an analysis request of the technical metadata is received, second propagation path information of the analyzed technical metadata from a label node at the last layer to a label node at the first layer is determined according to pre-acquired example information between the label node and a label node at the lower layer, and the attribute information of the label node through which the backward propagation path information passes is utilized to respond to the analysis request.
In an exemplary embodiment, before the processor is configured to invoke the computer program in the memory to implement the operation of establishing the correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, the processor is further configured to invoke the computer program in the memory to implement the following operations, including;
configuring propagation attribute information for the technical metadata;
the processor is configured to invoke a computer program in the memory to implement the operation of establishing a correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, and includes:
when the corresponding relationship between at least one technical metadata configured with the same propagation attribute information and one target label node is established, the corresponding relationship between other technical metadata configured with the same propagation attribute and the target label node is established.
In an exemplary embodiment, after the processor is configured to invoke the computer program in the memory to implement the operation of configuring propagation attribute information for technical metadata, the processor is configured to invoke the computer program in the memory to further implement operations comprising;
configuring cascading deletion attribute information for the technical metadata configured with the propagation attribute information;
after the processor is configured to invoke the computer program in the memory to implement the operation of establishing the correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, the processor is further configured to invoke the computer program in the memory to implement the following operations, including:
and when the corresponding relation between at least one technical metadata configured with the same propagation attribute information and one target label node is deleted, deleting the corresponding relation between other technical metadata with the same propagation attribute and the target label node.
According to the embodiment provided by the application, the service metadata are acquired, the label nodes used for describing the attribute information of the service are determined according to the service metadata, the map information of the label nodes is established according to the subordination relation of the attribute information corresponding to the label nodes, the corresponding relation between the pre-acquired technical metadata and the attribute information corresponding to the label nodes is established in the label map, the technical metadata and the service metadata with the corresponding relation in the label map are managed, the label nodes are set by means of the service metadata, the corresponding technical metadata are established on the basis of the label nodes, the corresponding relation between the technical metadata and the service metadata is established, the technical metadata can be analyzed conveniently, the service can be analyzed and counted conveniently, and the processing efficiency is improved.
Additional features and advantages of the embodiments of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the embodiments of the application. The objectives and other advantages of the embodiments of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the embodiments of the present application and are incorporated in and constitute a part of this specification, illustrate embodiments of the present application and together with the examples of the embodiments of the present application do not constitute a limitation of the embodiments of the present application.
FIG. 1 is a flow chart of a method for managing metadata as provided by an embodiment of the present application;
fig. 2 is a schematic diagram of a connection relationship between tag nodes according to an embodiment of the present application
FIG. 3 is a schematic diagram of a graph database according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the embodiments of the present application, features in the embodiments and the examples may be arbitrarily combined with each other without conflict.
In order to solve the problem of difficult association between technical metadata and business, the inventor finds that business metadata and technical metadata need to be associated; after the association is realized, the business analyst can operate the corresponding technical metadata only by understanding and retrieving the business metadata, so that the data is more efficiently used and integrated to be used as data support for an upper-layer business system.
Fig. 1 is a flowchart of a method for managing metadata according to an embodiment of the present application. The method shown in fig. 1 comprises:
in one exemplary embodiment, the service metadata includes: the business name, business definition, business description, etc. are used to represent various attributes and concepts in the enterprise environment, and compared with the technical metadata, the business metadata can enable the user to understand and use the data in the enterprise environment better, for example, the user can clearly understand the meaning of each index, the calculation method of the index, etc. by looking over the business metadata.
The source of the service metadata may be at least one of:
enterprise Resource Planning (ERP) systems, which store a large amount of business metadata, such as financial calculation formulas, process logic, business rules, etc.;
the head of the enterprise report is also a business metadata, particularly columns containing total numbers, average numbers and the like with summary properties, and some calculation formulas in the report;
tables, such as EXCEL headers and formulas, are also important business metadata. Unlike reports, most tables have a single column of "descriptions", and some tables have a column of codes and code descriptions, which are useful business metadata;
the file, such as title, author, modification time, etc., is relatively difficult to obtain business metadata in the file content, and machine learning and other technologies are involved.
Business Intelligence (BI) analysis tools, a common operation used by BI tools is a "drill-in" operation, which defines various classification structures of an enterprise, such as product level and organizational structure level, by drilling up and down, which are important Business metadata;
data warehouses, which typically require extensive research to investigate how to integrate multiple data sources before they are built, have a large amount of business metadata in their files related to the data warehouse building process
in an exemplary embodiment, a business analyst creates a tag node through a system page, and fills in the name and description information of the tag node; for the created label node, attribute definition can be selected to be added, and the content is the data type and the attribute name of the attribute, wherein the data type can include: shaping, floating point, boolean, list, constant, enumeration, string, etc.;
in an exemplary embodiment, the label node can have a plurality of hierarchies, and the attribute names of the label nodes in the same hierarchy are not repeated; the label node of the lower layer can inherit the existing attribute information of the label node of the upper layer, and further limit the attribute information on the basis of the attribute information.
In an exemplary embodiment, the determining, according to the service metadata, a tag node for describing attribute information of a service includes:
determining a service corresponding to the service metadata, and using the service as a first-layer label node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and according to the classification result of the attribute information, taking the attribute information of the same classification level as the label node of the same layer, wherein when the classification result of the attribute information comprises at least two classification levels, the attribute information of at least one node in the (i + 1) th level belongs to the attribute information of one label node of the (i) th layer, and i is an integer greater than or equal to 1.
For example, taking data management of a department structure of a research and development company as an example, if the data management is divided according to attributes of geographic locations, names of first-layer label nodes may be set as domestic, names of second-layer label nodes are beijing, shanghai and guangzhou respectively, and third-layer label nodes corresponding to labels named as beijing may include a hai lake area, a chang ping area and a happy area.
103, constructing map information of the label nodes according to the subordination relation of the attribute information corresponding to the label nodes;
in an exemplary embodiment, label nodes with subordination relations are connected, propagation path information of information among the label nodes is determined, and map information of the label nodes is constructed.
104, establishing a corresponding relation between the technical metadata acquired in advance and attribute information corresponding to the label nodes in the label map;
in an exemplary embodiment, the technology metadata acquired in advance is labeled or batch labeled by using the established label nodes, and the establishment of the corresponding relationship between the technology metadata and the label nodes is completed.
in an exemplary embodiment, the required technical metadata may be known based on the attribute information of the service, or after a certain technical metadata is read, a tag node having a corresponding relationship with the technical metadata is traced back according to the technical metadata, and the technical metadata is understood according to the attribute information of the tag node, so that the parsing operation is facilitated.
The method provided by the embodiment of the application acquires service metadata, determines a tag node for describing attribute information of a service according to the service metadata, constructs map information of the tag node according to the subordination relationship of the attribute information corresponding to the tag node, establishes a corresponding relationship between the pre-acquired technical metadata and the attribute information corresponding to the tag node in the tag map, manages the technical metadata and the service metadata with the corresponding relationship in the tag map, establishes the corresponding relationship between the technical metadata and the service metadata by means of the tag node set by the service metadata and the corresponding technical metadata based on the tag node, facilitates the analysis and statistics of the technical metadata and the service, and improves the processing efficiency.
The method provided by the embodiments of the present application is explained as follows:
in an exemplary embodiment, the determining, according to the service metadata, a tag node for describing attribute information of a service further includes: and recording instance information between the label node and the lower layer label node subordinate to the label node.
Recording instance information of lower-layer label nodes subordinate to the label nodes for the label nodes; and recording the label node corresponding to the belonged instance for the lower layer label node subordinate to the label node.
Fig. 2 is a schematic diagram of a connection relationship between tag nodes according to an embodiment of the present application. As shown in FIG. 2, a first level of label nodes are created in a graph database, all created labels being instances thereof, i.e., a two-way instance relationship is created.
When adding an attribute to a created label node, the description information of the attribute may include a name of the attribute, a data type of the attribute, and a default value of the attribute, and the information may be processed into a key value that meets a preset rule and then stored. Since the node attributes of the graph database can only be stored as Map structures, the expression format of the attributes stored in the corresponding tag nodes can be processed as shown in table 1 below.
The description is given by taking the example of adding two attributes, wherein the data type of the attribute A is string type, and the default value is null; the data type of the attribute B is an int type, and the default value is 1; the corresponding storage structure is seen in table 1.
| Key (Key: ATTR __ { attribute name } _ { attribute information item }) | Value (Value) |
| ATTR__A_name | A |
| ATTR__A_type | string |
| ATTR__A_defaultValue | null |
| ATTR__B_name | B |
| ATTR__B_type | int |
| ATTR__B_defaultValue | 1 |
TABLE 1
When the attribute information is acquired, grouping operation is carried out according to the attribute names of the keys, and then all attribute information items in each group are backfilled into the attribute object to be returned.
FIG. 3 is a schematic diagram of a graph database according to an embodiment of the present application. As shown in fig. 3, company a is the name of a first-layer tag node (which may also be the name of the group of tag models), the second layer is at least two tag nodes divided according to the classification policy of the attribute information, one of the tag nodes is a business department, under the tag node of the business department, according to the setting condition of the business department of company a, the business name may be a personnel department, a technical department, a financial department, and the like, each technical metadata establishes a corresponding relationship with the business department through a tag relationship, and the tag relationship stores the business name information of the technical metadata.
When setting corresponding label nodes for technical metadata, respective attribute values can be set for each technical metadata, which greatly enriches analysis of service personnel, for example, a label node is named as business department, and is added with attributes named as business name, then the label node is marked on a technical metadata A table, and the label node attribute value is set as personnel department and B table, and the label node attribute value is set as technical department, so that the service personnel can retrieve the table in the technical metadata which is not well understood originally according to the Chinese name of the business part. The values of these attributes are all in a tagged relationship.
In an exemplary embodiment, the managing technical metadata and business metadata having correspondence in the tag map includes:
when a reading request of the technical metadata is received, according to the pre-acquired instance information between the label node and the lower layer label node, determining first propagation path information of the read technical metadata from the first layer label node to the last layer label node, acquiring the technical metadata from the technical metadata corresponding to the last layer label node, and responding to the reading request.
Taking the graph database shown in fig. 3 as an example, after receiving a request for reading a report form of the finance department of company a in 10 months, firstly, the tag node of company a is found, and the first-layer tag node is determined; and under the first layer of label nodes, searching technical metadata with a business name of financial department from the mark relationship according to the fact that the part to be acquired is financial department, and searching report information of 10 months from the technical metadata of the financial department to obtain the required report.
Similarly, when an analysis request of the technical metadata is received, second propagation path information of the analyzed technical metadata from a label node at the last layer to a label node at the first layer is determined according to the pre-acquired instance information between the label node and a label node at the lower layer, and the attribute information of the label node through which the backward propagation path information passes is utilized to respond to the analysis request.
Taking the graph database shown in fig. 3 as an example, after a request of a 10-month report is read, firstly, it is determined that the mark information corresponding to the 10-month financial report is a business name as a financial department, and according to the label node corresponding to the mark relationship, it is determined that the label node of the business department is a label node belonging to company a, so that it is determined that the technical metadata is the 10-month report of the financial department of company a, which greatly facilitates understanding and analysis of the technical metadata.
The method realizes the marking of the attribute information by means of the example relationship between the label nodes and the marking relationship between the label nodes and the technical metadata, when the label nodes marked under a certain label node are searched, the quick search can be completed only by determining the nodes of the label nodes, and vice versa, and for the search of the label node attributes, the results can be obtained only by traversing the relationship once, and the method is very efficient. Compared with the traditional database or the traditional method of marking specific data, the storage structure saves the storage space, has low complexity and has very high query efficiency and modification efficiency.
In the schematic diagram shown in fig. 3, the dependency relationship between the service metadata is provided by way of example, the corresponding relationship between the service metadata and the technical metadata is provided by way of a tag relationship, and under the connection relationship determined by the dependency relationship and the corresponding relationship, a plurality of pieces of propagation path information are formed, and fast traversal can be realized by means of the propagation path information, which is very efficient.
When the technical metadata is labeled, the label node is subjected to supplementary description to describe whether the label node is propagated or not, whether the propagation of the label node is deleted when the entity (the labeled technical metadata thereof) is deleted, and the defined attribute of the label node can be assigned.
In an exemplary embodiment, before the mapping between the technical metadata obtained in advance and the attribute information corresponding to the tag node is established in the tag map, the method further includes;
configuring propagation attribute information for the technical metadata;
the establishing of the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the tag nodes in the tag map includes:
when the corresponding relationship between at least one technical metadata configured with the same propagation attribute information and one target label node is established, the corresponding relationship between other technical metadata configured with the same propagation attribute and the target label node is established.
In an exemplary embodiment, after configuring the propagation attribute information for the technical metadata, the method further comprises;
configuring cascading deletion attribute information for the technical metadata configured with the propagation attribute information;
after the corresponding relationship between the technical metadata acquired in advance and the attribute information corresponding to the tag node is established in the tag map, the method further comprises the following steps:
and when the corresponding relation between at least one technical metadata configured with the same propagation attribute information and one target label node is deleted, deleting the corresponding relation between other technical metadata with the same propagation attribute and the target label node.
In an exemplary embodiment, when the technical metadata is labeled with nodes, two Boolean-type parameters are selected to be filled in, and a directionless labeling relation is established, wherein the directionless labeling relation comprises attribute information of propagation and cascade deletion attribute information; wherein:
after a technical metadata is assigned to establish a corresponding relationship with a tag node A, the technical metadata is marked with the tag A, and if the technical metadata has a propagation attribute, the tag node with the propagation attribute is also automatically marked.
Similarly, if a technical metadata deletes the correspondence relationship with the tag node a, indicating that the technical metadata deletes the tag a, when the technical metadata has the cascade deletion attribute, once the tag node of the entity is deleted, the tag node, to which other entities having an association relationship are propagated, also deletes the correspondence relationship with the tag node a.
An embodiment of the present application provides an apparatus for managing metadata, including a processor and a memory, where the memory stores a computer program, and the processor is configured to call the computer program in the memory to implement the following operations, including:
acquiring service metadata;
determining a label node for describing attribute information of the service according to the service metadata;
constructing map information of the label nodes according to the subordination relation of the attribute information corresponding to the label nodes;
establishing a corresponding relation between the technical metadata acquired in advance and attribute information corresponding to the label nodes in the label map;
and managing the technical metadata and the service metadata which have corresponding relations in the label map.
In an exemplary embodiment, the processor is configured to invoke a computer program in the memory to implement the operation of determining a tag node for describing attribute information of a service according to the service metadata, including:
determining a service corresponding to the service metadata, and using the service as a first-layer label node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and according to the classification result of the attribute information, taking the attribute information of the same classification level as the label node of the same layer, wherein when the classification result of the attribute information comprises at least two classification levels, the attribute information of at least one node in the (i + 1) th level belongs to the attribute information of one label node of the (i) th layer, and i is an integer greater than or equal to 1.
In an exemplary embodiment, the processor is configured to invoke a computer program in the memory to implement the operation of determining a tag node for describing attribute information of a service according to the service metadata, including:
recording instance information between the label node and a lower layer label node subordinate to the label node;
the processor is configured to invoke a computer program in the memory to implement the operations of managing technical metadata and business metadata for correspondence in the tag map, including:
when a reading request of the technical metadata is received, according to pre-acquired instance information between a tag node and a lower-layer tag node, determining first propagation path information of the read technical metadata from a first-layer tag node to a last-layer tag node, acquiring the technical metadata from the technical metadata corresponding to the last-layer tag node, and responding to the reading request;
and/or the presence of a gas in the gas,
when an analysis request of the technical metadata is received, second propagation path information of the analyzed technical metadata from a label node at the last layer to a label node at the first layer is determined according to pre-acquired example information between the label node and a label node at the lower layer, and the attribute information of the label node through which the backward propagation path information passes is utilized to respond to the analysis request.
In an exemplary embodiment, before the processor is configured to invoke the computer program in the memory to implement the operation of establishing the correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, the processor is further configured to invoke the computer program in the memory to implement the following operations, including;
configuring propagation attribute information for the technical metadata;
the processor is configured to invoke a computer program in the memory to implement the operation of establishing a correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, and includes:
when the corresponding relationship between at least one technical metadata configured with the same propagation attribute information and one target label node is established, the corresponding relationship between other technical metadata configured with the same propagation attribute and the target label node is established.
In an exemplary embodiment, after the processor is configured to invoke the computer program in the memory to implement the operation of configuring propagation attribute information for technical metadata, the processor is configured to invoke the computer program in the memory to further implement operations comprising;
configuring cascading deletion attribute information for the technical metadata configured with the propagation attribute information;
after the processor is configured to invoke the computer program in the memory to implement the operation of establishing the correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, the processor is further configured to invoke the computer program in the memory to implement the following operations, including:
and when the corresponding relation between at least one technical metadata configured with the same propagation attribute information and one target label node is deleted, deleting the corresponding relation between other technical metadata with the same propagation attribute and the target label node.
The device provided by the embodiment of the application acquires service metadata, determines a tag node for describing attribute information of a service according to the service metadata, constructs map information of the tag node according to the dependency relationship of the attribute information corresponding to the tag node, establishes a corresponding relationship between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, manages the technical metadata and the service metadata of the corresponding relationship in the tag map, establishes the corresponding relationship between the technical metadata and the service metadata by means of the tag node set by the service metadata and the corresponding technical metadata based on the tag node, facilitates analysis and statistics of the technical metadata and the service, and improves the processing efficiency.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
Claims (10)
1. A method of managing metadata, comprising:
acquiring service metadata;
determining a label node for describing attribute information of the service according to the service metadata;
constructing map information of the label nodes according to the subordination relation of the attribute information corresponding to the label nodes;
establishing a corresponding relation between the technical metadata acquired in advance and attribute information corresponding to the label nodes in the label map;
and managing the technical metadata and the service metadata which have corresponding relations in the label map.
2. The method of claim 1, wherein determining a label node for describing attribute information of a service according to the service metadata comprises:
determining a service corresponding to the service metadata, and using the service as a first-layer label node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and according to the classification result of the attribute information, taking the attribute information of the same classification level as the label node of the same layer, wherein when the classification result of the attribute information comprises at least two classification levels, the attribute information of at least one node in the (i + 1) th level belongs to the attribute information of one label node of the (i) th layer, and i is an integer greater than or equal to 1.
3. The method of claim 2, wherein:
the determining, according to the service metadata, a tag node for describing attribute information of a service further includes:
recording instance information between the label node and a lower layer label node subordinate to the label node;
the managing technical metadata and business metadata having a correspondence in the tag map includes:
when a reading request of the technical metadata is received, according to pre-acquired instance information between a tag node and a lower-layer tag node, determining first propagation path information of the read technical metadata from a first-layer tag node to a last-layer tag node, acquiring the technical metadata from the technical metadata corresponding to the last-layer tag node, and responding to the reading request;
and/or the presence of a gas in the gas,
when an analysis request of the technical metadata is received, second propagation path information of the analyzed technical metadata from a label node at the last layer to a label node at the first layer is determined according to pre-acquired example information between the label node and a label node at the lower layer, and the attribute information of the label node through which the backward propagation path information passes is utilized to respond to the analysis request.
4. The method of claim 1, wherein:
before establishing a corresponding relationship between the technical metadata acquired in advance and the attribute information corresponding to the tag nodes in the tag map, the method further comprises the following steps;
configuring propagation attribute information for the technical metadata;
the establishing of the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the tag nodes in the tag map includes:
when the corresponding relationship between at least one technical metadata configured with the same propagation attribute information and one target label node is established, the corresponding relationship between other technical metadata configured with the same propagation attribute and the target label node is established.
5. The method of claim 4, wherein:
after configuring the propagation attribute information for the technical metadata, the method further comprises the following steps;
configuring cascading deletion attribute information for the technical metadata configured with the propagation attribute information;
after the corresponding relationship between the technical metadata acquired in advance and the attribute information corresponding to the tag node is established in the tag map, the method further comprises the following steps:
and when the corresponding relation between at least one technical metadata configured with the same propagation attribute information and one target label node is deleted, deleting the corresponding relation between other technical metadata with the same propagation attribute and the target label node.
6. An apparatus for managing metadata, comprising a processor and a memory, the memory storing a computer program, the processor configured to invoke the computer program in the memory to implement operations comprising:
acquiring service metadata;
determining a label node for describing attribute information of the service according to the service metadata;
constructing map information of the label nodes according to the subordination relation of the attribute information corresponding to the label nodes;
establishing a corresponding relation between the technical metadata acquired in advance and attribute information corresponding to the label nodes in the label map;
and managing the technical metadata and the service metadata which have corresponding relations in the label map.
7. The apparatus of claim 6, wherein the processor is configured to invoke a computer program in the memory to implement the operation of determining a tag node for attribute information describing a service based on the service metadata, comprising:
determining a service corresponding to the service metadata, and using the service as a first-layer label node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and according to the classification result of the attribute information, taking the attribute information of the same classification level as the label node of the same layer, wherein when the classification result of the attribute information comprises at least two classification levels, the attribute information of at least one node in the (i + 1) th level belongs to the attribute information of one label node of the (i) th layer, and i is an integer greater than or equal to 1.
8. The apparatus of claim 7, wherein:
the processor is configured to invoke a computer program in the memory to implement the operation of determining a tag node for describing attribute information of a service according to the service metadata, and includes:
recording instance information between the label node and a lower layer label node subordinate to the label node;
the processor is configured to invoke a computer program in the memory to implement the operations of managing technical metadata and business metadata for correspondence in the tag map, including:
when a reading request of the technical metadata is received, according to pre-acquired instance information between a tag node and a lower-layer tag node, determining first propagation path information of the read technical metadata from a first-layer tag node to a last-layer tag node, acquiring the technical metadata from the technical metadata corresponding to the last-layer tag node, and responding to the reading request;
and/or the presence of a gas in the gas,
when an analysis request of the technical metadata is received, second propagation path information of the analyzed technical metadata from a label node at the last layer to a label node at the first layer is determined according to pre-acquired example information between the label node and a label node at the lower layer, and the attribute information of the label node through which the backward propagation path information passes is utilized to respond to the analysis request.
9. The apparatus of claim 6, wherein:
the processor is configured to call the computer program in the memory to implement the following operations before the operation of establishing the correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map is implemented;
configuring propagation attribute information for the technical metadata;
the processor is configured to invoke a computer program in the memory to implement the operation of establishing a correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, and includes:
when the corresponding relationship between at least one technical metadata configured with the same propagation attribute information and one target label node is established, the corresponding relationship between other technical metadata configured with the same propagation attribute and the target label node is established.
10. The apparatus of claim 9, wherein:
after the processor is configured to invoke the computer program in the memory to implement the operation of configuring the propagation attribute information for the technical metadata, the processor is configured to invoke the computer program in the memory to further implement operations comprising;
configuring cascading deletion attribute information for the technical metadata configured with the propagation attribute information;
after the processor is configured to invoke the computer program in the memory to implement the operation of establishing the correspondence between the technical metadata acquired in advance and the attribute information corresponding to the tag node in the tag map, the processor is further configured to invoke the computer program in the memory to implement the following operations, including:
and when the corresponding relation between at least one technical metadata configured with the same propagation attribute information and one target label node is deleted, deleting the corresponding relation between other technical metadata with the same propagation attribute and the target label node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911069218.1A CN110851663B (en) | 2019-11-05 | 2019-11-05 | Method and device for managing metadata |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911069218.1A CN110851663B (en) | 2019-11-05 | 2019-11-05 | Method and device for managing metadata |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110851663A true CN110851663A (en) | 2020-02-28 |
| CN110851663B CN110851663B (en) | 2023-07-25 |
Family
ID=69598160
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911069218.1A Active CN110851663B (en) | 2019-11-05 | 2019-11-05 | Method and device for managing metadata |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110851663B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112037036A (en) * | 2020-09-02 | 2020-12-04 | 中国银行股份有限公司 | Bank business information analysis method and device based on metadata |
| CN112084340A (en) * | 2020-08-24 | 2020-12-15 | 杭州电子科技大学 | Management method for organizational structure change version based on neo4j graph database |
| CN112613853A (en) * | 2020-12-31 | 2021-04-06 | 平安养老保险股份有限公司 | Data aggregation method and device, computer equipment and readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090216728A1 (en) * | 2008-02-26 | 2009-08-27 | Jeffrey Brainerd | Graphic representations of data relationships |
| CN104750681A (en) * | 2013-12-25 | 2015-07-01 | ***通信集团辽宁有限公司 | Method and device for processing mass data |
| CN108733713A (en) * | 2017-04-21 | 2018-11-02 | 阿里巴巴集团控股有限公司 | Data query method and device in data warehouse |
| CN109213747A (en) * | 2018-08-08 | 2019-01-15 | 麒麟合盛网络技术股份有限公司 | A kind of data managing method and device |
| CN109726235A (en) * | 2018-11-27 | 2019-05-07 | 东软集团股份有限公司 | Method for interchanging data, device, readable storage medium storing program for executing, electronic equipment and system |
| CN109739867A (en) * | 2018-12-29 | 2019-05-10 | 北京航天数据股份有限公司 | A kind of industry metadata management method and system |
| CN109815378A (en) * | 2019-01-31 | 2019-05-28 | 三盟科技股份有限公司 | A kind of data tracing method and system based on metadata link |
| CN109857822A (en) * | 2018-12-29 | 2019-06-07 | 国家开发银行 | Meta-model conversion method and management system based on chart database |
-
2019
- 2019-11-05 CN CN201911069218.1A patent/CN110851663B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090216728A1 (en) * | 2008-02-26 | 2009-08-27 | Jeffrey Brainerd | Graphic representations of data relationships |
| CN104750681A (en) * | 2013-12-25 | 2015-07-01 | ***通信集团辽宁有限公司 | Method and device for processing mass data |
| CN108733713A (en) * | 2017-04-21 | 2018-11-02 | 阿里巴巴集团控股有限公司 | Data query method and device in data warehouse |
| CN109213747A (en) * | 2018-08-08 | 2019-01-15 | 麒麟合盛网络技术股份有限公司 | A kind of data managing method and device |
| CN109726235A (en) * | 2018-11-27 | 2019-05-07 | 东软集团股份有限公司 | Method for interchanging data, device, readable storage medium storing program for executing, electronic equipment and system |
| CN109739867A (en) * | 2018-12-29 | 2019-05-10 | 北京航天数据股份有限公司 | A kind of industry metadata management method and system |
| CN109857822A (en) * | 2018-12-29 | 2019-06-07 | 国家开发银行 | Meta-model conversion method and management system based on chart database |
| CN109815378A (en) * | 2019-01-31 | 2019-05-28 | 三盟科技股份有限公司 | A kind of data tracing method and system based on metadata link |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112084340A (en) * | 2020-08-24 | 2020-12-15 | 杭州电子科技大学 | Management method for organizational structure change version based on neo4j graph database |
| CN112037036A (en) * | 2020-09-02 | 2020-12-04 | 中国银行股份有限公司 | Bank business information analysis method and device based on metadata |
| CN112613853A (en) * | 2020-12-31 | 2021-04-06 | 平安养老保险股份有限公司 | Data aggregation method and device, computer equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110851663B (en) | 2023-07-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104794123B (en) | A kind of method and device building NoSQL database indexes for semi-structured data | |
| US8700581B2 (en) | Systems and methods for providing a map of an enterprise system | |
| CN110851663B (en) | Method and device for managing metadata | |
| US6772137B1 (en) | Centralized maintenance and management of objects in a reporting system | |
| CN106407303A (en) | Data storage method and apparatus, and data query method and apparatus | |
| US20180144061A1 (en) | Edge store designs for graph databases | |
| JP6928677B2 (en) | Data processing methods and equipment for performing online analysis processing | |
| US20190377827A1 (en) | Method and system for scalable search using microservice and cloud based search with records indexes | |
| US9158599B2 (en) | Programming framework for applications | |
| CN102999637B (en) | According to the method and system that file eigenvalue is file automatic powder adding add file label | |
| US7035842B2 (en) | Method, system, and program for defining asset queries in a digital library | |
| US11868328B2 (en) | Multi-record index structure for key-value stores | |
| JP2004030221A (en) | Method for automatically detecting table to be modified | |
| US6999966B2 (en) | Content management system and methodology for implementing a complex object using nested/recursive structures | |
| US11068459B2 (en) | Computer implemented and computer controlled method, computer program product and platform for arranging data for processing and storage at a data storage engine | |
| CN113704248B (en) | Block chain query optimization method based on external index | |
| US20160364426A1 (en) | Maintenance of tags assigned to artifacts | |
| US20180144060A1 (en) | Processing deleted edges in graph databases | |
| CN116127154A (en) | Knowledge tag recommendation method and device, electronic equipment and storage medium | |
| CN110609926A (en) | Data tag storage management method and device | |
| CN113391916A (en) | Organization architecture data processing method, device, computer equipment and storage medium | |
| CN114510465B (en) | Data management method, device and computer readable storage medium | |
| CN110928979B (en) | Method and apparatus for managing technical metadata | |
| US12013822B1 (en) | Discovery of data sets | |
| CN113779319B (en) | Efficient set operation system based on tree |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |