CN112540970A - Metadata blood relationship analysis method and system based on version management - Google Patents
Metadata blood relationship analysis method and system based on version management Download PDFInfo
- Publication number
- CN112540970A CN112540970A CN202011431180.0A CN202011431180A CN112540970A CN 112540970 A CN112540970 A CN 112540970A CN 202011431180 A CN202011431180 A CN 202011431180A CN 112540970 A CN112540970 A CN 112540970A
- Authority
- CN
- China
- Prior art keywords
- metadata
- version number
- individual
- blood relationship
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 79
- 239000008280 blood Substances 0.000 title claims abstract description 75
- 210000004369 blood Anatomy 0.000 title claims abstract description 75
- 230000008859 change Effects 0.000 claims abstract description 47
- 238000012545 processing Methods 0.000 claims abstract description 22
- 238000000034 method Methods 0.000 claims abstract description 20
- 230000000007 visual effect Effects 0.000 claims abstract description 8
- 238000009877 rendering Methods 0.000 claims abstract description 6
- 238000007726 management method Methods 0.000 claims description 46
- 230000004048 modification Effects 0.000 claims description 9
- 238000012986 modification Methods 0.000 claims description 9
- 238000013459 approach Methods 0.000 claims description 2
- 238000004148 unit process Methods 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 16
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000004075 alteration Effects 0.000 description 3
- 210000003462 vein Anatomy 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003313 weakening effect Effects 0.000 description 1
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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24573—Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a metadata blood relationship analysis method and a metadata blood relationship analysis system based on version management, wherein the method comprises the following steps: processing the individual version number of the individual state information for identifying the single metadata according to the operation request, and recording change information by using a data consanguinity mode; determining a plurality of metadata corresponding to an analysis request according to the analysis request, and acquiring a blood relationship record of each metadata corresponding to the analysis request; respectively creating nodes corresponding to each metadata corresponding to the analysis request, and connecting the nodes corresponding to the metadata with association according to the association between the blood relationship records of each metadata corresponding to the analysis request to acquire the blood relationship of the metadata; and displaying the metadata blood relationship through a visual graph, and highlighting and rendering a connecting line related to a preset specified node. The invention solves the problem of low efficiency of the version management mode of the metadata and improves the efficiency of the version management of the metadata.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a metadata blood relationship analysis method and system based on version management.
Background
At present, the traditional metadata version management mode is based on information management of metadata, metadata information data are directly listed in a system, only results can be seen, an analysis function of historical metadata change processes and incidence relations is lacked, the metadata information data always exist in a single metadata record information mode, the efficiency is low, the change history of the metadata cannot be traced, and the like, and the metadata version cannot be effectively managed.
Therefore, a metadata blood relationship analysis method based on version management is needed, which traces back the change history of metadata and improves the efficiency of metadata version management.
Disclosure of Invention
The invention provides a metadata blood relationship analysis method and a metadata blood relationship analysis system based on version management, which aim to solve the problem of how to efficiently process metadata versions.
In order to solve the above problem, according to an aspect of the present invention, there is provided a metadata blood relationship analysis method based on version management, the method including:
processing the individual version number of the individual state information for identifying the single metadata according to the operation request, and recording change information by using a data consanguinity mode;
determining a plurality of metadata corresponding to an analysis request according to the analysis request, and acquiring a blood relationship record of each metadata corresponding to the analysis request;
respectively creating nodes corresponding to each metadata corresponding to the analysis request, and connecting the nodes corresponding to the metadata with incidence relation in the blood relationship records according to the incidence relation among the blood relationship records of each metadata corresponding to the analysis request to acquire the blood relationship of the metadata;
and displaying the metadata blood relationship through a visual graph, and highlighting and rendering a connecting line related to a preset specified node.
Preferably, the metadata includes: pointer metadata, grouping metadata, metadata names for directory metadata, and metadata entries.
Preferably, the processing, according to the operation request, a global version number of the overall state information for identifying all metadata or an individual version number of the individual state information for identifying individual metadata includes:
when the operation request is a new operation request, generating an initial version number of the designated metadata;
and when the operation request is a modification operation request, updating the individual version number of the specified metadata according to a preset adjustment strategy, and forbidding updating the original global version number of the specified metadata and the global version number of the new metadata obtained after the update operation is executed.
Preferably, the recording of change information using a data consanguinity mode includes:
recording all metadata and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; an indicator symbol; the indication symbol is used for indicating the category of the operation request, and connecting the metadata and descendant metadata obtained after the operation requests of different categories are carried out on the metadata.
Preferably, wherein the method further comprises:
setting a global version number used for identifying the overall state information of all metadata, adding 1 to the current global version number according to a preset period, and taking the obtained value as an updated global version number to update the global version number.
According to another aspect of the present invention, there is provided a metadata consanguinity analysis system based on version management, the system including:
a change information recording unit for processing an individual version number of individual state information for identifying individual metadata according to the operation request and recording the change information using a data consanguinity mode;
the analysis request processing unit is used for determining a plurality of metadata corresponding to the analysis request according to the analysis request and acquiring a blood relationship record of each metadata corresponding to the analysis request;
a metadata blood relationship obtaining unit, configured to respectively create a node corresponding to each metadata corresponding to the analysis request, and connect nodes corresponding to metadata having an association relationship in the blood relationship records according to the association relationship between blood relationship records of each metadata corresponding to the analysis request, so as to obtain a metadata blood relationship;
and the display unit is used for displaying the metadata blood relationship through a visual graph and highlighting and rendering a connecting line related to a preset designated node.
Preferably, the metadata includes: pointer metadata, grouping metadata, metadata names for directory metadata, and metadata entries.
Preferably, the processing of the global version number of the overall state information for identifying all metadata or the individual version number of the individual state information for identifying individual metadata according to the operation request includes:
when the operation request is a new operation request, generating an initial version number of the designated metadata;
and when the operation request is a modification operation request, updating the individual version number of the specified metadata according to a preset adjustment strategy, and forbidding updating the original global version number of the specified metadata and the global version number of the new metadata obtained after the update operation is executed.
Preferably, the change information recording unit records the change information using a data consanguinity method, and includes:
recording all metadata and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; an indicator symbol; the indication symbol is used for indicating the category of the operation request, and connecting the metadata and descendant metadata obtained after the operation requests of different categories are carried out on the metadata.
Preferably, wherein the system further comprises:
and the global version number processing unit is used for setting a global version number used for identifying the overall state information of all metadata, adding 1 to the current global version number according to a preset period, and taking the obtained value as an updated global version number to update the global version number.
The invention provides a metadata blood relationship analysis method and a metadata blood relationship analysis system based on version management, which realize the integral version management of full metadata through a global version number; the version management of the historical change record of the single metadata is realized through the individual version number, the blood relationship among the individual versions of the multiple metadata can be obtained through a blood relationship analysis method, the blood relationship of the metadata appointed by a metadata blood relationship visualization graphic system is highlighted and displayed, the problem that the version management mode of the metadata is low in efficiency is solved, and the version management efficiency of the metadata is improved.
Drawings
A more complete understanding of exemplary embodiments of the present invention may be had by reference to the following drawings in which:
FIG. 1 is a flow diagram of a metadata lineage analysis method 100 based on version management, according to an embodiment of the invention;
FIG. 2 is a flow diagram of metadata version management and blood-based analysis according to an embodiment of the present invention;
FIG. 3 is an architecture diagram of a metadata lineage analysis system based on version management according to an embodiment of the invention;
FIG. 4 is a flow chart of metadata headquarters management and blood margin analysis according to an embodiment of the present invention;
FIG. 5 is an exemplary diagram of an interface of a version management based blood relationship analysis system according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a metadata blood relationship analysis system 600 based on version management according to an embodiment of the present invention.
Detailed Description
The exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, however, the present invention may be embodied in many different forms and is not limited to the embodiments described herein, which are provided for complete and complete disclosure of the present invention and to fully convey the scope of the present invention to those skilled in the art. The terminology used in the exemplary embodiments illustrated in the accompanying drawings is not intended to be limiting of the invention. In the drawings, the same units/elements are denoted by the same reference numerals.
Unless otherwise defined, terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Further, it will be understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense.
FIG. 1 is a flow diagram of a metadata blood relationship analysis method 100 based on version management according to an embodiment of the present invention. As shown in fig. 1, in the metadata consanguinity analysis method based on version management according to the embodiment of the present invention, the overall version management of the full amount of metadata is implemented by using a global version number; the version management of the historical change record of the single metadata is realized through the individual version number, the blood relationship among the individual versions of the multiple metadata can be obtained through a blood relationship analysis method, the blood relationship of the metadata appointed by a metadata blood relationship visualization graphic system is highlighted and displayed, the problem that the version management mode of the metadata is low in efficiency is solved, and the version management efficiency of the metadata is improved. The metadata vein analysis method 100 based on version management provided by the embodiment of the invention starts from step 101, processes the individual version number of the individual state information for identifying the single metadata according to the operation request in step 101, and records the change information by using the data vein mode.
Preferably, the metadata includes: pointer metadata, grouping metadata, metadata names for directory metadata, and metadata entries.
Preferably, the processing, according to the operation request, a global version number of the overall state information for identifying all metadata or an individual version number of the individual state information for identifying individual metadata includes:
when the operation request is a new operation request, generating an initial version number of the designated metadata;
and when the operation request is a modification operation request, updating the individual version number of the specified metadata according to a preset adjustment strategy, and forbidding updating the original global version number of the specified metadata and the global version number of the new metadata obtained after the update operation is executed.
Preferably, the recording of change information using a data consanguinity mode includes:
recording all metadata and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; an indicator symbol; the indication symbol is used for indicating the category of the operation request, and connecting the metadata and descendant metadata obtained after the operation requests of different categories are carried out on the metadata.
Preferably, wherein the method further comprises: setting a global version number used for identifying the overall state information of all metadata, adding 1 to the current global version number according to a preset period, and taking the obtained value as an updated global version number to update the global version number.
In the embodiment of the present invention, as shown in fig. 2, fig. 3 and fig. 4, the metadata college analysis is implemented by the metadata version management module and the metadata blood relationship analysis module.
The objects managed by the metadata version management module comprise index metadata, grouping metadata and directory metadata. The metadata version management module includes: the system comprises a global version setting unit, a global version updating unit, an individual version changing unit and an individual version history recording unit.
In the present invention, the global version setting unit is configured to set a global version number of the metadata management system. Wherein the global version number is used to identify the overall state information of all metadata in the metadata management system.
In the present invention, the global version updating unit is configured to update the entire amount of metadata in the metadata repository of the metadata management system, and record a global version number thereof. Wherein adjusting the global version number according to the change operation comprises: and integrally recording the full metadata state snapshots in the metadata database of the metadata management system in each period, marking the global version number of the snapshot, and adjusting the global version number. And adjusting the global version number of the specified metadata according to the type of the change operation. Under the condition that each pair of metadata in the metadata management system executes one change operation, updating the global version number once, wherein the updating comprises the following steps: and adding 1 to the global version number, and taking the obtained value as the updated global version number.
In the present invention, the individual version changing unit is configured to perform a changing operation on the specified metadata and update the individual version number of the specified metadata only once. Wherein, in a case where the change operation is a new addition operation, the new addition operation is for instructing generation of an initial individual version of the specified metadata. And adjusting the initial individual version number of the specified metadata according to the type of the change operation. And when the change operation is a modification operation, the modification operation is used for adjusting the individual version number of the specified metadata to update, and forbidding updating of the original global version number of the specified metadata and the global version number of the metadata obtained after the update operation is executed. At the same time, at least the following information is recorded using a data-lineage approach: all metadata in the metadata management system and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; and an indication symbol for indicating a designated change operation and connecting the metadata and the metadata of the subsequent generation after the designated change operation is performed on the metadata. The descendant metadata may be derived metadata associated with the specified metadata, for example, the descendant metadata may be new metadata generated after a new addition operation is performed on the metadata.
In the present invention, an individual version history recording unit for recording at least the following information using the metadata consanguineous analysis library before or after adjusting the individual version number of the metadata according to the alteration operation: all metadata in the metadata management system and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; and an indication symbol for indicating a designated change operation and connecting the metadata and the metadata of the subsequent generation after the designated change operation is performed on the metadata.
In step 102, a plurality of metadata corresponding to the analysis request are determined according to the analysis request, and a blood relationship record of each metadata corresponding to the analysis request is obtained.
In step 103, nodes corresponding to each metadata corresponding to the analysis request are respectively created, and according to the association relationship between the blood relationship records of each metadata corresponding to the analysis request, the nodes corresponding to the metadata having the blood relationship records with the association relationship are connected to obtain the blood relationship of the metadata.
In step 104, the metadata blood relationship is displayed through a visual graph, and a connection line related to a preset designated node is highlighted and displayed.
In the invention, the blood relationship among a plurality of metadata is obtained by utilizing a metadata blood relationship analysis module. Specifically, the method comprises the following steps:
(1) the determining unit determines a plurality of metadata according to preset requirements.
(2) The acquisition unit acquires a blood relationship of a plurality of metadata from a metadata blood relationship analysis library. Obtaining a blood-related relationship between a plurality of metadata, comprising: determining a plurality of metadata according to preset requirements; and obtaining the blood relationship of a plurality of metadata from the metadata blood relationship analysis library.
(3) The association unit creates a plurality of nodes respectively corresponding to the plurality of metadata, and establishes a connection line between the plurality of nodes based on the blood relationship. The method is used for establishing the association relationship among the plurality of metadata through the upward blood relationship and/or downward influence relationship of each metadata in the plurality of metadata.
(4) And the display unit displays the metadata blood relationship through a visual graphic system. And establishing a connection line between a plurality of nodes corresponding to the plurality of metadata based on the incidence relation. Determining connecting lines related to a designated node in the plurality of nodes, and highlighting and displaying the connecting lines related to the designated node; determining connecting lines related to other nodes except the designated node in the plurality of nodes; and weakening the connecting lines related to other nodes except the specified node in the plurality of nodes for rendering and displaying. Fig. 5 is a diagram illustrating an example of an interface of a version management-based blood relationship analysis system.
The global version number of the metadata is used for identifying the overall change information of all the metadata in the database of the metadata management system. The metadata individual version number is used to identify history change information of all metadata and its descendant metadata in the metadata management system. There is no logical connection between the two. And the metadata blood reason analysis only aims at the historical change condition of the individual version number of the metadata, and does not display the historical record of the global version number of the metadata. And only history records of the individual version numbers of the metadata are stored in the metadata blood margin analysis library. The blooding margin analysis method can effectively manage the version of the metadata, realizes the traceability of the change history of the metadata and improves the efficiency of managing the version of the metadata.
Fig. 6 is a schematic structural diagram of a metadata blood relationship analysis system 600 based on version management according to an embodiment of the present invention. As shown in fig. 6, a metadata relationship analysis system 600 based on version management according to an embodiment of the present invention includes a change information recording unit 601, an analysis request processing unit 602, a metadata relationship obtaining unit 603, and a presentation unit 604.
Preferably, the alteration information recording unit 601 is configured to process an individual version number of individual status information for identifying individual metadata according to the operation request, and record the alteration information using a data lineage.
Preferably, the metadata includes: pointer metadata, grouping metadata, metadata names for directory metadata, and metadata entries.
Preferably, the processing of the global version number of the overall state information for identifying all metadata or the individual version number of the individual state information for identifying individual metadata by the change information recording unit 601 according to the operation request includes:
when the operation request is a new operation request, generating an initial version number of the designated metadata;
and when the operation request is a modification operation request, updating the individual version number of the specified metadata according to a preset adjustment strategy, and forbidding updating the original global version number of the specified metadata and the global version number of the new metadata obtained after the update operation is executed.
Preferably, the change information recording unit 601, which records change information using a data-based system, includes:
recording all metadata and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; an indicator symbol; the indication symbol is used for indicating the category of the operation request, and connecting the metadata and descendant metadata obtained after the operation requests of different categories are carried out on the metadata.
Preferably, the analysis request processing unit 602 is configured to determine, according to an analysis request, a plurality of metadata corresponding to the analysis request, and obtain a blood relationship record of each metadata corresponding to the analysis request.
Preferably, the metadata relationship obtaining unit 603 is configured to respectively create a node corresponding to each metadata corresponding to the analysis request, and connect nodes corresponding to metadata having a relationship in relationship records according to a relationship between relationship records of each metadata corresponding to the analysis request, so as to obtain a metadata relationship.
Preferably, the displaying unit 604 is configured to display the metadata blood relationship through a visual graph, and highlight a connection line related to a preset designated node.
Preferably, wherein the system further comprises:
and the global version number processing unit is used for setting a global version number used for identifying the overall state information of all metadata, adding 1 to the current global version number according to a preset period, and taking the obtained value as an updated global version number to update the global version number.
The metadata blood relationship analysis system 600 based on version management according to the embodiment of the present invention corresponds to the metadata blood relationship analysis method 100 based on version management according to another embodiment of the present invention, and is not described herein again.
The invention has been described with reference to a few embodiments. However, other embodiments of the invention than the one disclosed above are equally possible within the scope of the invention, as would be apparent to a person skilled in the art from the appended patent claims.
Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the [ device, component, etc ]" are to be interpreted openly as referring to at least one instance of said device, component, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting the same, and although the present invention is described in detail with reference to the above embodiments, those of ordinary skill in the art should understand that: modifications and equivalents may be made to the embodiments of the invention without departing from the spirit and scope of the invention, which is to be covered by the claims.
Claims (10)
1. A metadata blood relationship analysis method based on version management, which is characterized by comprising the following steps:
processing the individual version number of the individual state information for identifying the single metadata according to the operation request, and recording change information by using a data consanguinity mode;
determining a plurality of metadata corresponding to an analysis request according to the analysis request, and acquiring a blood relationship record of each metadata corresponding to the analysis request;
respectively creating nodes corresponding to each metadata corresponding to the analysis request, and connecting the nodes corresponding to the metadata with incidence relation in the blood relationship records according to the incidence relation among the blood relationship records of each metadata corresponding to the analysis request to acquire the blood relationship of the metadata;
and displaying the metadata blood relationship through a visual graph, and highlighting and rendering a connecting line related to a preset specified node.
2. The method of claim 1, wherein the metadata comprises: pointer metadata, grouping metadata, metadata names for directory metadata, and metadata entries.
3. The method according to claim 1, wherein the processing a global version number for identifying overall state information of all metadata or an individual version number for identifying individual state information of individual metadata according to the operation request comprises:
when the operation request is a new operation request, generating an initial version number of the designated metadata;
and when the operation request is a modification operation request, updating the individual version number of the specified metadata according to a preset adjustment strategy, and forbidding updating the original global version number of the specified metadata and the global version number of the new metadata obtained after the update operation is executed.
4. The method of claim 1, wherein the recording of change information using a data-based consanguinity approach comprises:
recording all metadata and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; an indicator symbol; the indication symbol is used for indicating the category of the operation request, and connecting the metadata and descendant metadata obtained after the operation requests of different categories are carried out on the metadata.
5. The method of claim 1, further comprising:
setting a global version number used for identifying the overall state information of all metadata, adding 1 to the current global version number according to a preset period, and taking the obtained value as an updated global version number to update the global version number.
6. A version management based metadata consanguinity analysis system, the system comprising:
a change information recording unit for processing an individual version number of individual state information for identifying individual metadata according to the operation request and recording the change information using a data consanguinity mode;
the analysis request processing unit is used for determining a plurality of metadata corresponding to the analysis request according to the analysis request and acquiring a blood relationship record of each metadata corresponding to the analysis request;
a metadata blood relationship obtaining unit, configured to respectively create a node corresponding to each metadata corresponding to the analysis request, and connect nodes corresponding to metadata having an association relationship in the blood relationship records according to the association relationship between blood relationship records of each metadata corresponding to the analysis request, so as to obtain a metadata blood relationship;
and the display unit is used for displaying the metadata blood relationship through a visual graph and highlighting and rendering a connecting line related to a preset designated node.
7. The system of claim 6, wherein the metadata comprises: pointer metadata, grouping metadata, metadata names for directory metadata, and metadata entries.
8. The system according to claim 6, wherein the change information recording unit processes, according to the operation request, a global version number of the overall state information for identifying all metadata or an individual version number of the individual state information for identifying individual metadata, including:
when the operation request is a new operation request, generating an initial version number of the designated metadata;
and when the operation request is a modification operation request, updating the individual version number of the specified metadata according to a preset adjustment strategy, and forbidding updating the original global version number of the specified metadata and the global version number of the new metadata obtained after the update operation is executed.
9. The system according to claim 6, wherein the change information recording unit records change information using a data-based consanguinity method, and includes:
recording all metadata and descendant metadata of all metadata; change operations performed on all metadata; individual version numbers of all metadata; an individual version number of descendant metadata of all metadata; an indicator symbol; the indication symbol is used for indicating the category of the operation request, and connecting the metadata and descendant metadata obtained after the operation requests of different categories are carried out on the metadata.
10. The system of claim 6, further comprising:
and the global version number processing unit is used for setting a global version number used for identifying the overall state information of all metadata, adding 1 to the current global version number according to a preset period, and taking the obtained value as an updated global version number to update the global version number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011431180.0A CN112540970A (en) | 2020-12-07 | 2020-12-07 | Metadata blood relationship analysis method and system based on version management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011431180.0A CN112540970A (en) | 2020-12-07 | 2020-12-07 | Metadata blood relationship analysis method and system based on version management |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112540970A true CN112540970A (en) | 2021-03-23 |
Family
ID=75019712
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011431180.0A Pending CN112540970A (en) | 2020-12-07 | 2020-12-07 | Metadata blood relationship analysis method and system based on version management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112540970A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113138973A (en) * | 2021-04-20 | 2021-07-20 | 建信金融科技有限责任公司 | Data management system and working method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105787051A (en) * | 2016-02-26 | 2016-07-20 | 广州品唯软件有限公司 | Analysis method and device based on metadata model |
| CN107545030A (en) * | 2017-07-17 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Processing method, device and the equipment of data genetic connection |
| CN110245149A (en) * | 2019-06-25 | 2019-09-17 | 北京明略软件***有限公司 | The method for edition management and device of metadata |
| CN110399423A (en) * | 2019-07-24 | 2019-11-01 | 北京明略软件***有限公司 | Processing method and processing device, storage medium and the electronic device of metadata genetic connection |
| CN111694858A (en) * | 2020-04-28 | 2020-09-22 | 平安科技（深圳）有限公司 | Data blood margin analysis method, device, equipment and computer readable storage medium |
-
2020
- 2020-12-07 CN CN202011431180.0A patent/CN112540970A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105787051A (en) * | 2016-02-26 | 2016-07-20 | 广州品唯软件有限公司 | Analysis method and device based on metadata model |
| CN107545030A (en) * | 2017-07-17 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Processing method, device and the equipment of data genetic connection |
| CN110245149A (en) * | 2019-06-25 | 2019-09-17 | 北京明略软件***有限公司 | The method for edition management and device of metadata |
| CN110399423A (en) * | 2019-07-24 | 2019-11-01 | 北京明略软件***有限公司 | Processing method and processing device, storage medium and the electronic device of metadata genetic connection |
| CN111694858A (en) * | 2020-04-28 | 2020-09-22 | 平安科技（深圳）有限公司 | Data blood margin analysis method, device, equipment and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113138973A (en) * | 2021-04-20 | 2021-07-20 | 建信金融科技有限责任公司 | Data management system and working method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108132957B (en) | Database processing method and device | |
| US10692048B2 (en) | Apparatus and method for generating a chronological timesheet | |
| US9519692B2 (en) | Visualizing related events within a timeline | |
| US10346381B2 (en) | Atomic update operations in a data storage system | |
| US20070276825A1 (en) | Query reuse through recommend parameter flexibility | |
| US10692593B1 (en) | Identifying events in a badge of a graphical user interface | |
| US20070234306A1 (en) | Tracing performance of machine-readable instructions | |
| CN113138973B (en) | Data management system and working method | |
| US20070143250A1 (en) | Adaptable database system | |
| US9934292B2 (en) | Dynamic presentation of a results set by a form-based software application | |
| US20100070893A1 (en) | Data quality administration framework | |
| CN111737148A (en) | Automatic regression testing method and device, computer equipment and storage medium | |
| US8219858B2 (en) | Method for testing hard disks under an extensible firmware interface | |
| CN112540970A (en) | Metadata blood relationship analysis method and system based on version management | |
| CN104123104B (en) | Daily record control system and method | |
| CN113010208A (en) | Version information generation method, version information generation device, version information generation equipment and storage medium | |
| CN116823464B (en) | Data asset management platform, electronic device, and computer-readable storage medium | |
| CN112000971A (en) | File permission recording method, system and related device | |
| AU2007228610B2 (en) | Data input method | |
| CN102682038A (en) | Database change method and device | |
| CN111933228B (en) | Method and device for realizing project distribution and management system in clinical research | |
| CN111813880B (en) | Homeland space planning project management method, system and storage medium | |
| CN109450874B (en) | User account monitoring method and device | |
| JP2009134535A (en) | Device for supporting software development, method of supporting software development, and program for supporting software development | |
| US10552387B1 (en) | Managing data using a simulation of purging |
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 |