CN110851663B - Method and device for managing metadata - Google Patents
Method and device for managing metadata Download PDFInfo
- Publication number
- CN110851663B CN110851663B CN201911069218.1A CN201911069218A CN110851663B CN 110851663 B CN110851663 B CN 110851663B CN 201911069218 A CN201911069218 A CN 201911069218A CN 110851663 B CN110851663 B CN 110851663B
- Authority
- CN
- China
- Prior art keywords
- metadata
- attribute information
- node
- tag
- label
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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 tag node for describing attribute information of the service according to the service metadata; constructing map information of the label node according to the affiliation of the attribute information corresponding to the label node; establishing a corresponding relation between the technical metadata obtained in advance and attribute information corresponding to the label nodes in the label map; and managing technical metadata and business metadata with corresponding relations in the label map.
Description
Technical Field
The embodiment of the application relates to the field of information processing, in particular to a method and a device for managing metadata.
Background
Metadata is data that describes data, descriptive information about data and information resources. The Metadata is data (data about other data) describing other data, or is structural data (structured data) for providing information about a certain resource. Functionally, metadata may provide user-based information, such as metadata that records business description information of data items, that can help users use the data; in addition, system management and maintenance of data may be supported, such as metadata about the data item storage method may support the system to access data in a most efficient manner.
In the data warehouse field, metadata is divided into technical metadata and business metadata by purpose. The technical metadata is obscure, and according to different data quality and different service ranges, the technical metadata is not named normally, is not uniform in format, is difficult to find and classify, and is more difficult to detect service information and service association.
Disclosure of Invention
In order to solve any technical problem, the embodiment of the application provides a method and a device for managing metadata.
To achieve the object of the embodiments of the present application, the embodiments of the present application provide a method for managing metadata, including:
acquiring service metadata;
determining a tag node for describing attribute information of the service according to the service metadata;
constructing map information of the label node according to the affiliation of the attribute information corresponding to the label node;
establishing a corresponding relation between the technical metadata obtained in advance and attribute information corresponding to the label nodes in the label map;
and managing technical metadata and business metadata with 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 taking the service as a first layer tag node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and taking the attribute information of the same classification level as the label node of the same layer according to the classification result of the attribute information, 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 a tag node and a lower-layer tag node subordinate to the tag node;
the managing the technical metadata and the business metadata with the corresponding relation in the label map includes:
when a reading request of technical metadata is received, determining first propagation path information of the read technical metadata from a first layer of tag nodes to a last layer of tag nodes according to example information between a pre-acquired tag node and a lower layer of tag nodes, acquiring the technical metadata in the technical metadata corresponding to the last layer of tag nodes, and responding to the reading request;
and/or the number of the groups of groups,
when an analysis request of technical metadata is received, determining second propagation path information of the analyzed technical metadata from a tag node of a last layer to a tag node of a first layer according to the pre-acquired instance information between the tag node and a lower layer tag node, and responding to the analysis request by utilizing attribute information of the tag node through which the reverse propagation path information passes.
In an exemplary embodiment, before the mapping relationship between the technical metadata obtained in advance and the attribute information corresponding to the label node is established in the label map, the method further includes;
configuring propagation attribute information for technical metadata;
the establishing a corresponding relation between the pre-acquired technical metadata and the attribute information corresponding to the label node in the label map comprises the following steps:
when at least one technical metadata configured with the same propagation attribute information and a target tag node establish a corresponding relation, other technical metadata configured with the same propagation attribute and the target tag node establish a corresponding relation.
In an exemplary embodiment, after the configuring propagation attribute information for the technical metadata, the method further includes;
configuring cascade deletion attribute information for technical metadata configured with propagation attribute information;
after the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the label node is established in the label map, the method further comprises the following steps:
and deleting the corresponding relation between the other technical metadata with the same propagation attribute and the target tag node after deleting the corresponding relation between the at least one technical metadata configured with the same propagation attribute information and the target tag 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 perform operations comprising:
acquiring service metadata;
determining a tag node for describing attribute information of the service according to the service metadata;
constructing map information of the label node according to the affiliation of the attribute information corresponding to the label node;
establishing a corresponding relation between the technical metadata obtained in advance and attribute information corresponding to the label nodes in the label map;
and managing technical metadata and business metadata with 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 taking the service as a first layer tag node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and taking the attribute information of the same classification level as the label node of the same layer according to the classification result of the attribute information, 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 a tag node and a lower-layer tag node subordinate to the tag node;
the processor is configured to call a computer program in the memory to implement the operation of managing technical metadata and business metadata in which correspondence exists in the tag map, and includes:
when a reading request of technical metadata is received, determining first propagation path information of the read technical metadata from a first layer of tag nodes to a last layer of tag nodes according to example information between a pre-acquired tag node and a lower layer of tag nodes, acquiring the technical metadata in the technical metadata corresponding to the last layer of tag nodes, and responding to the reading request;
and/or the number of the groups of groups,
when an analysis request of technical metadata is received, determining second propagation path information of the analyzed technical metadata from a tag node of a last layer to a tag node of a first layer according to the pre-acquired instance information between the tag node and a lower layer tag node, and responding to the analysis request by utilizing attribute information of the tag node through which the reverse propagation path information passes.
In an exemplary embodiment, before the processor is configured to call the computer program in the memory to implement the operation of establishing a correspondence between the technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, the processor is configured to call the computer program in the memory to implement further operations including;
configuring propagation attribute information for technical metadata;
the processor is configured to call a computer program in the memory to implement the operation of establishing a correspondence between technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, where the operation includes:
when at least one technical metadata configured with the same propagation attribute information and a target tag node establish a corresponding relation, other technical metadata configured with the same propagation attribute and the target tag node establish a corresponding relation.
In one exemplary embodiment, after the processor is configured to invoke the computer program in the memory to perform the operation of configuring propagation attribute information for technical metadata, the processor is configured to invoke the computer program in the memory to further perform operations comprising;
configuring cascade deletion attribute information for technical metadata configured with propagation attribute information;
the processor is configured to call the computer program in the memory to implement the operation of establishing a correspondence between the technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, and then the processor is configured to call the computer program in the memory to implement the following operation, including:
and deleting the corresponding relation between the other technical metadata with the same propagation attribute and the target tag node after deleting the corresponding relation between the at least one technical metadata configured with the same propagation attribute information and the target tag node.
According to the embodiment provided by the embodiment of the application, the service metadata are acquired, the tag node for describing the attribute information of the service is determined according to the service metadata, the map information of the tag node is constructed according to the subordinate relation of the attribute information corresponding to the tag node, the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the tag node is built in the tag map, the technical metadata and the service metadata with the corresponding relation in the tag map are managed, the tag node arranged by the service metadata is used, the corresponding technical metadata is built based on the tag node, the corresponding relation between the technical metadata and the service metadata is built, analysis and statistics of the technical metadata are convenient, and the processing efficiency is improved.
Additional features and advantages of embodiments of the application will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of embodiments of the application. The objectives and other advantages of the embodiments of the present application will 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 technical solutions of the embodiments of the present application, and are incorporated in and constitute a part of this specification, illustrate the technical solutions of the embodiments of the present application and not constitute a limitation to the technical solutions of the embodiments of the present application.
FIG. 1 is a flow chart of a method of managing metadata provided by an embodiment of the present application;
fig. 2 is a schematic diagram of a connection relationship between label 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
For the purpose of making 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 hereinafter with reference to the accompanying drawings. It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be arbitrarily combined with each other.
In order to solve the difficulty of associating technical metadata with services, the inventor discovers that the service metadata and the technical metadata need to be associated; after the association is realized, service analysts can operate the corresponding technical metadata only by understanding and searching the service metadata, so that the data can be used and integrated more efficiently to support the upper service 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 the following steps:
step 101, acquiring service metadata;
in one exemplary embodiment, the business metadata includes: the business names, business definitions, business descriptions and the like are used for representing various attributes and concepts in the enterprise environment, and compared with the technical metadata, the business metadata can enable a user to better understand and use the data in the enterprise environment, for example, the user can clearly understand the meaning of each index, the calculation method of the index and the like through looking up the business metadata.
The source of the business metadata may be by at least one of:
an enterprise resource planning (Enterprise Resource Planning, ERP) system that stores a large amount of business metadata, such as financial computational formulas, process logic, business rules, etc.;
enterprise report forms, the header of which is also business metadata, especially those containing total, average and other columns with summary properties, some calculation formulas in the report forms and the like;
tables, such as the header and formulas of EXCEL, are also important business metadata. Unlike reports, most tables have a single column of "description" and some tables have a column of codes and code descriptions, which are useful business metadata;
the acquisition of business metadata in the file content is relatively difficult, and the technology of machine learning and the like is involved.
Business intelligence (Business Intelligence, BI) analysis tools, which are often used by BI tools are "drill-down" operations, which are important business metadata by drilling up and down to define various taxonomies of the enterprise, such as product level and organizational structure level, etc.;
data warehouse, prior to building a data warehouse, typically requires extensive investigation to investigate how to integrate multiple data sources, such as the presence of a large amount of business metadata in files associated with the data warehouse building process
102, determining a label node for describing attribute information of a service according to the service metadata;
in one exemplary embodiment, a service analyst creates tag nodes through a system page and fills in names and description information of the tag nodes; for the created tag node, the attribute definition of the tag node may be optionally added, and the content is a data type and an attribute name of the attribute, wherein the data type may include: shaping, floating point, boolean, list, constant, enumeration, string, etc.;
in an exemplary embodiment, the tag node may have multiple levels, and attribute names of tag nodes in the same level are not repeated; the lower layer label node can inherit the attribute information of the existing upper layer label node, and further limit the attribute information based on 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 taking the service as a first layer tag node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and taking the attribute information of the same classification level as the label node of the same layer according to the classification result of the attribute information, 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 the data management of a department structure of a research and development company as an example, if the data management is divided according to the attribute of the geographic location, the names of the first-layer tag nodes may be set as domestic, the names of the second-layer tag nodes are respectively Beijing, shanghai and Guangzhou, and the third-layer tag nodes corresponding to the tags named as Beijing may include a lake region, a Change region and a Daxing region.
Step 103, constructing map information of the label node according to the affiliation of the attribute information corresponding to the label node;
in one exemplary embodiment, tag nodes having affiliations are connected, propagation path information of information between the tag nodes is determined, and map information of the tag nodes is constructed.
104, establishing a corresponding relation between the technical metadata obtained in advance and attribute information corresponding to the label nodes in the label map;
in an exemplary embodiment, the technical metadata obtained in advance is marked or labeled in batches by using the established label nodes, so that the establishment of the corresponding relation between the technical metadata and the label nodes is completed.
Step 105, managing technical metadata and business metadata with corresponding relations in the label map;
in an exemplary embodiment, the required technical metadata can be obtained based on the attribute information of the service, or after a certain technical metadata is read, the label node with the corresponding relation 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 label node, so that the analysis operation is convenient.
According to the method provided by the embodiment of the application, the service metadata are acquired, the tag node used for describing the attribute information of the service is determined according to the service metadata, the map information of the tag node is constructed according to the subordinate relation of the attribute information corresponding to the tag node, the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the tag node is built in the tag map, the technical metadata and the service metadata with the corresponding relation in the tag map are managed, the tag node arranged by the service metadata is used, the corresponding technical metadata is built based on the tag node, the corresponding relation between the technical metadata and the service metadata is built, analysis and statistics of the technical metadata are facilitated, and the processing efficiency is improved.
The following describes the method provided in the embodiment of the present application:
in an exemplary embodiment, the determining, according to the service metadata, a tag node for describing attribute information of a service further includes: instance information between a tag node and an underlying tag node subordinate to the tag node is recorded.
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 label node subordinate to the label node.
Fig. 2 is a schematic diagram of a connection relationship between label nodes according to an embodiment of the present application. As shown in fig. 2, a first layer of label nodes are built in the graph database, and all created labels are instances thereof, i.e., a bi-directional instance relationship is created.
When adding the attribute to the created label node, the description information of the attribute may include the name of the attribute, the data type of the attribute and the default value of the attribute, and the information may be processed into a key value conforming to 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 label nodes can be processed in the manner shown in the following table 1.
Two attributes are added for illustration, 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 memory 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 performed according to the attribute names of the keys, and then all attribute information items in each grouping are backfilled into the attribute object for return.
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 a first layer of label node names (which may also be the names of the group of label models), the second layer is at least two label nodes that are divided according to a classification policy of attribute information, one label node is a service department, under the label node of the service department, according to the setting condition of the service department of company a, the service name may be a personnel department, a technical department, a financial department, and the like, and each technical metadata establishes a corresponding relationship with the service department through a label relationship, where the service name information of the technical metadata is stored.
When the corresponding tag node is set for the technical metadata, the respective attribute value can be set for each technical metadata, so that analysis of a great variety of service personnel, for example, a tag node name is named as a service department, an attribute named as a service name is added, the tag node is marked in a technical metadata A table, the tag node attribute value is set as a personnel part, a B table, and the tag node attribute value is set as a technical part, and then the service personnel can search the table in the technical metadata which is not well understood originally according to the Chinese name of the service part. The values of these attributes are all in a presence flag relationship.
In an exemplary embodiment, the managing the technical metadata and the business metadata of the correspondence relationship in the tag map includes:
when a reading request of technical metadata is received, determining first propagation path information of the read technical metadata from a first layer of tag nodes to a last layer of tag nodes according to example information between a pre-acquired tag node and a lower layer of tag nodes, acquiring the technical metadata in the technical metadata corresponding to the last layer of tag nodes, 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 of 10 months of financial department of company a, firstly searching for a label node of company a, and determining a first layer of label nodes; and searching technical metadata with service names of financial parts from the marked relation under the first-layer label node according to the part to be acquired as the financial parts, and searching report information of 10 months from the technical metadata of the financial parts to obtain a required report.
Similarly, when an analysis request of technical metadata is received, determining second propagation path information of the analyzed technical metadata from the tag node of the last layer to the tag node of the first layer according to the pre-acquired instance information between the tag node and the lower layer tag node, and responding to the analysis request by utilizing attribute information of the tag node through which the reverse propagation path information passes.
Taking the graph database shown in fig. 3 as an example, after a request of a 10 month report is read, firstly determining that the label information corresponding to the 10 month financial report is a business name as a financial part, and determining the label node of the business department at the label node corresponding to the label relation, and further determining that the label node of the business department is subordinate to the company a, thereby determining that the technical metadata is the 10 month report of the financial part of the company a, and greatly facilitating understanding and analysis of the technical metadata.
By means of the instance relation among the label nodes and the marking relation among the label nodes and the technical metadata, marking of attribute information is achieved, when the label nodes marked under a certain label node are searched, quick searching can be completed only by determining the nodes reaching the label node, and vice versa, and in the searching of the label node attributes, the common relation exists, and a result can be obtained only by traversing the relation once, so that the method is quite efficient. Compared with the traditional database or the traditional method of labeling specific data, the storage structure saves storage space, has low complexity and high query efficiency and modification efficiency.
In the schematic diagram shown in fig. 3, the affiliation 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 marking relationship, and under the connection relationship determined by the affiliation and the corresponding relationship together, a plurality of propagation path information is formed, and by means of the propagation path information, the rapid traversal can be realized, so that the efficiency is very high.
In the labeling of technical metadata, a supplementary explanation is provided for the label node, to explain whether it is propagated, whether it is deleted when an entity (its labeled technical metadata) is deleted, and the attribute defined by the label node can be assigned.
In an exemplary embodiment, before the mapping relationship between the technical metadata obtained in advance and the attribute information corresponding to the label node is established in the label map, the method further includes;
configuring propagation attribute information for technical metadata;
the establishing a corresponding relation between the pre-acquired technical metadata and the attribute information corresponding to the label node in the label map comprises the following steps:
when at least one technical metadata configured with the same propagation attribute information and a target tag node establish a corresponding relation, other technical metadata configured with the same propagation attribute and the target tag node establish a corresponding relation.
In an exemplary embodiment, after the configuring propagation attribute information for the technical metadata, the method further includes;
configuring cascade deletion attribute information for technical metadata configured with propagation attribute information;
after the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the label node is established in the label map, the method further comprises the following steps:
and deleting the corresponding relation between the other technical metadata with the same propagation attribute and the target tag node after deleting the corresponding relation between the at least one technical metadata configured with the same propagation attribute information and the target tag node.
In an exemplary embodiment, when labeling technical metadata, selecting to fill in two Boolean type parameters, and establishing an unoriented marking relationship, wherein the unoriented marking relationship comprises attribute information and cascade deletion attribute information which are propagated or not; wherein:
after a technical metadata is assigned a correspondence with a tag node a, it means that the technical metadata is tagged a, and if the technical metadata has a propagation attribute, the tag node is also automatically tagged with the propagation attribute.
Similarly, if one technical metadata deletes the corresponding relation with the tag node A, the technical metadata deletes the tag A, and when the technical metadata has cascade deletion attribute, once the tag node of the entity is deleted, the tag node with the association relation transmitted by other entities also deletes the corresponding relation 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 tag node for describing attribute information of the service according to the service metadata;
constructing map information of the label node according to the affiliation of the attribute information corresponding to the label node;
establishing a corresponding relation between the technical metadata obtained in advance and attribute information corresponding to the label nodes in the label map;
and managing technical metadata and business metadata with 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 taking the service as a first layer tag node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
and taking the attribute information of the same classification level as the label node of the same layer according to the classification result of the attribute information, 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 a tag node and a lower-layer tag node subordinate to the tag node;
the processor is configured to call a computer program in the memory to implement the operation of managing technical metadata and business metadata in which correspondence exists in the tag map, and includes:
when a reading request of technical metadata is received, determining first propagation path information of the read technical metadata from a first layer of tag nodes to a last layer of tag nodes according to example information between a pre-acquired tag node and a lower layer of tag nodes, acquiring the technical metadata in the technical metadata corresponding to the last layer of tag nodes, and responding to the reading request;
and/or the number of the groups of groups,
when an analysis request of technical metadata is received, determining second propagation path information of the analyzed technical metadata from a tag node of a last layer to a tag node of a first layer according to the pre-acquired instance information between the tag node and a lower layer tag node, and responding to the analysis request by utilizing attribute information of the tag node through which the reverse propagation path information passes.
In an exemplary embodiment, before the processor is configured to call the computer program in the memory to implement the operation of establishing a correspondence between the technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, the processor is configured to call the computer program in the memory to implement further operations including;
configuring propagation attribute information for technical metadata;
the processor is configured to call a computer program in the memory to implement the operation of establishing a correspondence between technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, where the operation includes:
when at least one technical metadata configured with the same propagation attribute information and a target tag node establish a corresponding relation, other technical metadata configured with the same propagation attribute and the target tag node establish a corresponding relation.
In one exemplary embodiment, after the processor is configured to invoke the computer program in the memory to perform the operation of configuring propagation attribute information for technical metadata, the processor is configured to invoke the computer program in the memory to further perform operations comprising;
configuring cascade deletion attribute information for technical metadata configured with propagation attribute information;
the processor is configured to call the computer program in the memory to implement the operation of establishing a correspondence between the technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, and then the processor is configured to call the computer program in the memory to implement the following operation, including:
and deleting the corresponding relation between the other technical metadata with the same propagation attribute and the target tag node after deleting the corresponding relation between the at least one technical metadata configured with the same propagation attribute information and the target tag node.
According to the device provided by the embodiment of the application, the service metadata are acquired, the tag node for describing the attribute information of the service is determined according to the service metadata, the map information of the tag node is constructed according to the subordinate relation of the attribute information corresponding to the tag node, the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the tag node is built in the tag map, the technical metadata and the service metadata with the corresponding relation in the tag map are managed, the tag node arranged by the service metadata is used, the corresponding technical metadata is built based on the tag node, the corresponding relation between the technical metadata and the service metadata is built, analysis and statistics of the technical metadata are facilitated, and the processing efficiency is improved.
Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules/units in the apparatus, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the 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 cooperatively by several physical components. 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 both 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 known to those skilled 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 be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, 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.
Claims (6)
1. A method of managing metadata, comprising:
acquiring service metadata;
determining a tag node for describing attribute information of the service according to the service metadata;
constructing map information of the label node according to the affiliation of the attribute information corresponding to the label node, wherein the map information comprises the following components: connecting label nodes with subordination relations, determining information of propagation paths of information among the label nodes, and constructing map information of the label nodes;
in the label map, labeling operation is carried out on the technical metadata acquired in advance by using the established label nodes, and a corresponding relation is established between the technical metadata and attribute information corresponding to the label nodes;
managing technical metadata and business metadata with corresponding relations in the label map;
wherein, the determining the tag node for describing the attribute information of the service according to the service metadata includes:
determining a service corresponding to the service metadata, and taking the service as a first layer tag node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
according to the classification result of the attribute information, the attribute information with the same classification level is used as the label node of the same layer; and recording instance information between the tag node and a lower-layer tag node subordinate to the tag node, wherein when a classification result of the attribute information comprises at least two classification levels, attribute information of at least one node in the i+1th level subordinate to the attribute information of one tag node in the i-th level, i being an integer greater than or equal to 1;
wherein, the managing the technical metadata and the business metadata with the correspondence in the tag map includes:
when a reading request of technical metadata is received, determining first propagation path information of the read technical metadata from a first layer of tag nodes to a last layer of tag nodes according to example information between a pre-acquired tag node and a lower layer of tag nodes, acquiring the technical metadata in the technical metadata corresponding to the last layer of tag nodes, and responding to the reading request;
and/or the number of the groups of groups,
when an analysis request of technical metadata is received, determining second propagation path information of the analyzed technical metadata from a tag node of a last layer to a tag node of a first layer according to the pre-acquired instance information between the tag node and a lower layer tag node, and responding to the analysis request by utilizing attribute information of the tag node through which the second propagation path information passes.
2. The method according to claim 1, characterized in that:
before the corresponding relation between the technical metadata obtained in advance and the attribute information corresponding to the label node is established in the label map, the method further comprises the steps of;
configuring propagation attribute information for technical metadata;
the establishing a corresponding relation between the pre-acquired technical metadata and the attribute information corresponding to the label node in the label map comprises the following steps:
when at least one technical metadata configured with the same propagation attribute information and a target tag node establish a corresponding relation, other technical metadata configured with the same propagation attribute and the target tag node establish a corresponding relation.
3. The method according to claim 2, characterized in that:
after the propagation attribute information is configured for the technical metadata, the method further comprises;
configuring cascade deletion attribute information for technical metadata configured with propagation attribute information;
after the corresponding relation between the technical metadata acquired in advance and the attribute information corresponding to the label node is established in the label map, the method further comprises the following steps:
and deleting the corresponding relation between the other technical metadata with the same propagation attribute and the target tag node after deleting the corresponding relation between the at least one technical metadata configured with the same propagation attribute information and the target tag node.
4. An apparatus for managing metadata, comprising a processor and a memory, the memory storing a computer program, the processor operable to invoke the computer program in the memory to perform operations comprising:
acquiring service metadata;
determining a tag node for describing attribute information of the service according to the service metadata;
constructing map information of the label node according to the affiliation of the attribute information corresponding to the label node, wherein the map information comprises the following components: connecting label nodes with subordination relations, determining information of propagation paths of information among the label nodes, and constructing map information of the label nodes;
in the label map, labeling operation is carried out on the technical metadata acquired in advance by using the established label nodes, and a corresponding relation is established between the technical metadata and attribute information corresponding to the label nodes;
managing technical metadata and business metadata with corresponding relations in the label map;
wherein determining a tag node for describing attribute information of a service according to the service metadata comprises:
determining a service corresponding to the service metadata, and taking the service as a first layer tag node;
determining a classification result of attribute information corresponding to each service according to a preset attribute information classification strategy of each service;
according to the classification result of the attribute information, the attribute information with the same classification level is used as the label node of the same layer; and recording instance information between the tag node and a lower-layer tag node subordinate to the tag node, wherein when a classification result of the attribute information comprises at least two classification levels, attribute information of at least one node in the i+1th level subordinate to the attribute information of one tag node in the i-th level, i being an integer greater than or equal to 1;
wherein, the managing the technical metadata and the business metadata with the correspondence in the tag map includes:
when a reading request of technical metadata is received, determining first propagation path information of the read technical metadata from a first layer of tag nodes to a last layer of tag nodes according to example information between a pre-acquired tag node and a lower layer of tag nodes, acquiring the technical metadata in the technical metadata corresponding to the last layer of tag nodes, and responding to the reading request;
and/or the number of the groups of groups,
when an analysis request of technical metadata is received, determining second propagation path information of the analyzed technical metadata from a tag node of a last layer to a tag node of a first layer according to the pre-acquired instance information between the tag node and a lower layer tag node, and responding to the analysis request by utilizing attribute information of the tag node through which the second propagation path information passes.
5. The apparatus according to claim 4, wherein:
before the processor is used for calling the computer program in the memory to realize the operation of establishing the corresponding relation between the technical metadata obtained in advance and the attribute information corresponding to the label node in the label map, the processor is used for calling the computer program in the memory to realize the following operation, and the method comprises the following steps of;
configuring propagation attribute information for technical metadata;
the processor is configured to call a computer program in the memory to implement the operation of establishing a correspondence between technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, where the operation includes:
when at least one technical metadata configured with the same propagation attribute information and a target tag node establish a corresponding relation, other technical metadata configured with the same propagation attribute and the target tag node establish a corresponding relation.
6. The apparatus according to claim 5, wherein:
the processor is configured to invoke the computer program in the memory to perform the operations of configuring propagation attribute information for technical metadata, the processor is configured to invoke the computer program in the memory to perform operations comprising;
configuring cascade deletion attribute information for technical metadata configured with propagation attribute information;
the processor is configured to call the computer program in the memory to implement the operation of establishing a correspondence between the technical metadata obtained in advance and attribute information corresponding to a tag node in the tag map, and then the processor is configured to call the computer program in the memory to implement the following operation, including:
and deleting the corresponding relation between the other technical metadata with the same propagation attribute and the target tag node after deleting the corresponding relation between the at least one technical metadata configured with the same propagation attribute information and the target tag 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 CN110851663A (en) | 2020-02-28 |
| CN110851663B true 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) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112084340A (en) * | 2020-08-24 | 2020-12-15 | 杭州电子科技大学 | Management method of organizational structure change version based on neo4j graph database |
| CN112037036B (en) * | 2020-09-02 | 2024-02-27 | 中国银行股份有限公司 | Banking 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 |
| CN116069979A (en) * | 2021-11-03 | 2023-05-05 | 中国移动通信集团湖南有限公司 | Method for classifying metadata types, electronic equipment, and storage media |
| CN114201585B (en) * | 2021-12-14 | 2025-10-10 | 中国建设银行股份有限公司 | Information processing method, device, equipment, storage medium and computer program product |
| CN114996234B (en) * | 2022-06-17 | 2024-08-13 | 同盾科技有限公司 | Data acquisition method and device, computer storage medium and electronic equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5643654B2 (en) * | 2008-02-26 | 2014-12-17 | アビニシオ テクノロジー エルエルシー | Graph representation of data relevance |
| CN104750681B (en) * | 2013-12-25 | 2018-02-23 | 中国移动通信集团辽宁有限公司 | A kind of processing method and processing device of mass data |
| CN109726235A (en) * | 2018-11-27 | 2019-05-07 | 东软集团股份有限公司 | Method for interchanging data, device, readable storage medium storing program for executing, electronic equipment and system |
| CN109857822A (en) * | 2018-12-29 | 2019-06-07 | 国家开发银行 | Meta-model conversion method and management system based on chart database |
| CN109739867B (en) * | 2018-12-29 | 2021-01-12 | 北京航天数据股份有限公司 | Industrial 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 |
-
2019
- 2019-11-05 CN CN201911069218.1A patent/CN110851663B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110851663A (en) | 2020-02-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110851663B (en) | Method and device for managing metadata | |
| CN111177302B (en) | Service bill processing method, device, computer equipment and storage medium | |
| US7761455B2 (en) | Loading data from a vertical database table into a horizontal database table | |
| US6772137B1 (en) | Centralized maintenance and management of objects in a reporting system | |
| US8924373B2 (en) | Query plans with parameter markers in place of object identifiers | |
| JP6928677B2 (en) | Data processing methods and equipment for performing online analysis processing | |
| US20180144061A1 (en) | Edge store designs for graph databases | |
| CN106407303A (en) | Data storage method and apparatus, and data query method and apparatus | |
| CN113391916B (en) | Organizational structure data processing method, device, computer equipment and storage medium | |
| 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 | |
| CN111506621A (en) | Data statistical method and device | |
| US11868328B2 (en) | Multi-record index structure for key-value stores | |
| CN102193990A (en) | Pattern database and realization method thereof | |
| US20040002983A1 (en) | Method and system for detecting tables to be modified | |
| CN113704248B (en) | Block chain query optimization method based on external index | |
| CN115544183A (en) | Data visualization method and device, computer equipment and storage medium | |
| CN103455335A (en) | Multilevel classification Web implementation method | |
| US9158599B2 (en) | Programming framework for applications | |
| CN110879799B (en) | Method and device for labeling technical metadata | |
| CN110929120B (en) | Method and apparatus for managing technical metadata | |
| US20180144060A1 (en) | Processing deleted edges in graph databases | |
| CN119692450A (en) | Method, device and storage medium for handling user problems | |
| CN114895875B (en) | Zero-code visual information system metadata production application method and system | |
| CN110609926A (en) | Data tag storage management method and device | |
| Gupta et al. | A Study on Various Database Models: Relational, Graph, and Hybrid Databases |
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 |