CN117454450B - Assembly data management method, device, storage medium and computer equipment - Google Patents

Assembly data management method, device, storage medium and computer equipment Download PDF

Info

Publication number
CN117454450B
CN117454450B CN202311786360.4A CN202311786360A CN117454450B CN 117454450 B CN117454450 B CN 117454450B CN 202311786360 A CN202311786360 A CN 202311786360A CN 117454450 B CN117454450 B CN 117454450B
Authority
CN
China
Prior art keywords
import
data
unit
target
node
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
Application number
CN202311786360.4A
Other languages
Chinese (zh)
Other versions
CN117454450A (en
Inventor
管飞虎
胡展
冯征文
何洪举
沈跃佳
聂雅琴
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zwcad Software Co ltd
Original Assignee
Zwcad Software Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zwcad Software Co ltd filed Critical Zwcad Software Co ltd
Priority to CN202311786360.4A priority Critical patent/CN117454450B/en
Publication of CN117454450A publication Critical patent/CN117454450A/en
Application granted granted Critical
Publication of CN117454450B publication Critical patent/CN117454450B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/90335—Query processing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Geometry (AREA)
  • Human Computer Interaction (AREA)
  • Evolutionary Computation (AREA)
  • Computer Hardware Design (AREA)
  • Computational Linguistics (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

According to the assembly data management method, the device, the storage medium and the computer equipment, when the fact that a user builds the hybrid diagram of the target assembly file is detected, the latest object mapping table corresponding to the target assembly file can be obtained, a plurality of import units are arranged in the object mapping table, information of target import data in the target assembly file is recorded, and a reference unit is arranged in the import units and records a reference relation of the corresponding target import data. After the object mapping table is obtained, each import unit can be converted into an import node, the reference units in the import units are converted into reference nodes, and then edges between the import nodes and the reference nodes can be constructed according to the corresponding relation between the reference units, so that a target mixed graph of the target assembly file is obtained. The application adopts the mode of generating the target hybrid map according to the object mapping table after the object mapping table of the assembly file is pre-constructed to improve the management efficiency of the assembly data.

Description

Assembly data management method, device, storage medium and computer equipment
Technical Field
The present application relates to the field of data processing technologies, and in particular, to an assembly data management method, an assembly data management device, a storage medium, and a computer device.
Background
In the design scene of large-scale complex assembly, because the number of parts is large, the design level is deep, the design relationship is complex, the design of the large-scale complex assembly often needs the data interaction between different files, the reasonable data reference and the correct data updating sequence can ensure the correct size and position of the assembled part model, and the errors and problems in the assembly process are avoided.
In order to better maintain and manage the assembly data, the prior art generally converts the reference relationship between the designed assembly files into a relationship chart according to the assembly design scene and stores the relationship chart. Because there is stronger association between design data among each assembly file, when the design data of one assembly file is changed, other associated design data need to be changed synchronously, and in the design process of an assembly scene, the design data often need to be subjected to detail adjustment, so that the stored relation chart is updated frequently, the updating of the relation chart is easy to be missed, the correctness of the relation chart is further influenced, and the management effect of the assembly data is poor.
Disclosure of Invention
The application aims to at least solve one of the technical defects, in particular to the technical defects that the updating of the relation chart is easy to cause missing in the prior art, thereby affecting the correctness of the relation chart and resulting in poor management effect of assembly data.
The application provides an assembly data management method, which comprises the following steps:
When detecting that a user builds a hybrid diagram of a target assembly file, acquiring an up-to-date object mapping table corresponding to the target assembly file, wherein the target assembly file comprises a plurality of target import data and reference relations when the import data of other assembly files are referenced in at least one target import data, and the object mapping table comprises an import unit corresponding to each target import data and a reference unit which is arranged in at least one import unit and characterizes the reference relations of the target import data;
Traversing each import unit in the object mapping table, and generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit;
And constructing edges between each import node and each reference node according to the corresponding relation between each reference unit and each import unit to obtain a target mixed graph of the target assembly file so as to realize management of assembly data in the target assembly file.
Optionally, the obtaining the latest object mapping table corresponding to the target assembly file includes:
obtaining an object identifier of the target assembly file;
Searching the object identifier in a database to obtain an object mapping table corresponding to the target assembly file; and the database is pre-constructed with object mapping tables corresponding to the target assembly files.
Optionally, the process for constructing the object mapping table includes:
When a reference relation of a target assembly file is established, analyzing the target assembly file to obtain a data ID and a reference relation of each target import data in the target assembly file;
Creating an import set corresponding to the target assembly file, and generating an import unit corresponding to each target import data in the import set according to each data ID;
and determining the import data of other assembly files corresponding to each reference relation, generating corresponding reference units in each import unit according to each reference relation and the import data of each other assembly file, and taking the built import set as an object mapping table of the target assembly file.
Optionally, the generating the import node corresponding to each import unit and the reference node corresponding to the reference unit in at least one import unit includes:
determining other assembly files from which each reference unit in the at least one lead-in unit is derived;
Constructing an initial mixed graph of the object mapping table, and generating the target assembly file and an import set node corresponding to each other assembly file in the initial mixed graph;
And generating an import node corresponding to each import unit in the import set node of the target assembly file, and generating a reference node corresponding to each reference unit from each other assembly file in the import set node of the other assembly file.
Optionally, the constructing an edge between each import node and the reference node according to the correspondence between each reference unit and the import unit includes:
For each correspondence between a referencing unit and an importation unit:
determining an import node and a reference node in the corresponding relation and a driving type of the reference node;
judging whether the driving type is mirror image driving or not;
if yes, creating an undirected edge between the import node and the reference node;
if not, determining a reference guide between the import node and the reference node, and creating a directed edge between the import node and the reference node according to the reference guide.
Optionally, each import unit in the object mapping table stores a data ID of the corresponding import data;
The updating process of the object mapping table comprises the following steps:
When the user is detected to update the target assembly file, an object mapping table corresponding to the target assembly file is obtained, and target import data updated in the target assembly file is used as change data;
Determining a data ID and a change type of the change data, indexing the data ID in the object mapping table, and determining an importing unit corresponding to the data ID according to an indexing result as a unit to be updated of the object mapping table;
And updating the unit to be updated according to the change type and the change data so as to update the object mapping table.
Optionally, the determining, according to the index result, the importing unit corresponding to the data ID as the unit to be updated of the object mapping table includes:
judging whether the index result is empty or not;
If yes, generating an import unit corresponding to the change data in the object mapping table, and taking the generated import unit as a unit to be updated of the object mapping table;
if not, taking an importing unit corresponding to the data ID in the object mapping table as a unit to be updated of the object mapping table.
Optionally, the updating the unit to be updated according to the change type and the change data includes:
Determining a reference relation corresponding to the change data and the imported data of other assembly files corresponding to the reference relation, and updating the unit to be updated according to the change type, the reference relation and the imported data of the other assembly files;
wherein the change type comprises the addition, modification and deletion of the reference relation and the addition, modification and deletion of the imported data.
The application also provides an assembly data management device, which comprises:
The mapping table acquisition module is used for acquiring an up-to-date object mapping table corresponding to a target assembly file when detecting that a user constructs a hybrid diagram of the target assembly file, wherein the target assembly file comprises a plurality of target import data and a reference relation when the import data of other assembly files are referenced in at least one target import data, and the object mapping table comprises an import unit corresponding to each target import data and a reference unit which is arranged in at least one import unit and characterizes the reference relation of the target import data;
The node generation module is used for traversing each import unit in the object mapping table and generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit;
And the mixed graph construction module is used for constructing edges between each leading-in node and the leading-in node according to the corresponding relation between each leading-in unit and each leading-in unit to obtain a target mixed graph of the target assembly file so as to realize the management of assembly data in the target assembly file.
The present application also provides a storage medium characterized in that: the storage medium has stored therein computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the assembly data management method as set forth in any of the above embodiments.
The application also provides a computer device, characterized by comprising: one or more processors, and memory;
the memory has stored therein computer readable instructions which, when executed by the one or more processors, perform the steps of the assembly data management method as set forth in any of the above embodiments.
From the above technical solutions, the embodiment of the present application has the following advantages:
When detecting that a user constructs a hybrid map of a target assembly file, the assembly data management method, device, storage medium and computer equipment provided by the application can acquire a latest object mapping table corresponding to the target assembly file, wherein the target assembly file comprises a plurality of target import data and reference relations when the import data of other assembly files are referenced in at least one target import data, and the object mapping table comprises an import unit corresponding to each target import data and a reference unit which is arranged in at least one import unit and characterizes the reference relations of the target import data; after the object mapping table corresponding to the target assembly file is obtained, traversing each import unit in the object mapping table, generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit, and constructing edges between each import node and the reference node according to the corresponding relation between each reference unit and the import unit to obtain a target hybrid map of the target assembly file, so that the generated target hybrid map can be synchronous with the reference relation in the target assembly file, and the accuracy of the target hybrid map is improved. According to the method, the correctness of the generated target hybrid diagram can be improved by the mode of generating the target hybrid diagram according to the object mapping table after the object mapping table of the assembly file is pre-constructed, and the management efficiency of assembly data is further improved.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the description below are only some embodiments of the application, and that other drawings can be obtained from these drawings without inventive faculty for a person skilled in the art.
Fig. 1 is a flow chart of an assembly data management method according to an embodiment of the present application;
FIG. 2 is a schematic structural diagram of an object mapping table according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a target hybrid diagram according to an embodiment of the present application;
Fig. 4 is a schematic flow chart of an assembly data management device according to an embodiment of the present application;
fig. 5 is a schematic diagram of an internal structure of a computer device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In the design scene of large-scale complex assembly, because the number of parts is large, the design level is deep, the design relationship is complex, the design of the large-scale complex assembly often needs the data interaction between different files, the reasonable data reference and the correct data updating sequence can ensure the correct size and position of the assembled part model, and the errors and problems in the assembly process are avoided.
In order to better maintain and manage the assembly data, the prior art generally converts the reference relationship between the designed assembly files into a relationship chart according to the assembly design scene and stores the relationship chart. Because there is stronger association between design data among each assembly file, when the design data of one assembly file is changed, other associated design data need to be changed synchronously, and in the design process of an assembly scene, the design data often need to be subjected to detail adjustment, so that the stored relation chart is updated frequently, the updating of the relation chart is easy to be missed, the correctness of the relation chart is further influenced, and the management effect of the assembly data is poor.
Based on the above, the application provides the following technical scheme, and the specific scheme is as follows:
In one embodiment, as shown in fig. 1, fig. 1 is a flow chart of an assembly data management method according to an embodiment of the present application; the application provides an assembly data management method, which specifically comprises the following steps:
S110: when detecting that a user constructs a hybrid diagram of the target assembly file, acquiring an up-to-date object mapping table corresponding to the target assembly file.
In this step, when the user needs to view the hybrid map of the assembly file, the assembly file to be viewed may be selected on the query interface in the file management system, and after receiving the selection signal of the user, the file management system may use the assembly file selected by the user as the target assembly file, and then the file management system may obtain the latest object mapping table corresponding to the target assembly file, so that the hybrid map of the target assembly file may be constructed based on the object mapping table.
The mixed graph refers to a graph structure formed by nodes and edges, and is used for representing complex relations and processes of various data in a file. The target assembly file is composed of a plurality of target import data, and a reference relationship between at least one target import data and import data in other assembly files is recorded. And the object mapping table is composed of a plurality of import units, each import unit corresponds to one target import data in the target assembly file, and if the target import data has a reference relationship, a reference unit corresponding to the reference relationship is constructed in the corresponding import unit.
Schematically, as shown in fig. 2, fig. 2 is a schematic structural diagram of an object mapping table according to an embodiment of the present application; the object mapping table illustrated in fig. 2 is constructed with a plurality of import units, and each import unit is constructed with a plurality of reference units. The object mapping table characterizes the target assembly file, the importing unit characterizes target importing data in the target assembly file, and the referencing unit characterizes referencing relation of the target importing data. Therefore, when the reference relation does not exist in the target import data, the import unit corresponding to the import data in the object mapping table does not need to construct the reference unit.
Further, in order to index and quickly locate each element in the object mapping table, the file management system may add a corresponding data ID in the element when generating the import element or the reference element. In addition, the file management system may store attribute information of the corresponding target import data in the import unit, and store attribute information and a drive type of the import data in the corresponding other assembly file in the reference unit.
S120: traversing each import unit in the object mapping table, and generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit.
In this embodiment, after the object mapping table of the target assembly file is obtained in step S110, the file management system may traverse each import unit in the object mapping table, convert the traversed import unit into an import node, and when there is a reference unit in the traversed import unit, convert the reference unit into the reference node.
Specifically, when generating the import node, the file management system may generate an import node based on the import unit, where the generated import node records the data ID and attribute information of the target import data corresponding to the import unit. When the import unit exists, the file management system may generate a reference node recorded with a data ID, attribute information, and a drive type of import data in the corresponding other assembly file according to the reference unit. After the reference node is generated, the file management system may establish a correspondence between the reference node and the import node based on the data ID of the corresponding import node.
S130: and constructing edges between each import node and each reference node according to the corresponding relation between each reference unit and each import unit to obtain a target mixed graph of the target assembly file so as to realize management of assembly data in the target assembly file.
In this embodiment, after each import unit and each reference unit are generated in step S120, the file management system may construct edges between each import node and each reference node according to the corresponding relationship between each reference unit and each import unit, so as to obtain a target hybrid map of the target assembly file, so that the reference relationship of the import node in the constructed target hybrid map can be synchronized with the reference relationship in the target assembly file, thereby ensuring the correctness of the target hybrid map and further improving the management effect of the assembly data.
It is understood that the edges constructed under different correspondence are different, and the correspondence may include reference, referred to, and mutual reference. Therefore, when constructing the edge between the leading-in node and the reference node, the file management system needs to determine the corresponding relation between the reference unit and the leading-in unit, and further can construct the corresponding edge according to the corresponding relation, so as to avoid confusing the reference relation in the target mixed graph.
In the above embodiment, when it is detected that the user constructs the hybrid map of the target assembly file, the latest object mapping table corresponding to the target assembly file may be obtained, where the target assembly file includes a plurality of target import data and reference relationships when the import data of other assembly files are referenced in at least one target import data, and the object mapping table includes an import unit corresponding to each target import data and a reference unit provided in at least one import unit and characterizing the reference relationships of the target import data, so that the present application may pre-store all the reference relationships of the assembly file to the external file through the object mapping table, and reduce a process of resolving the reference relationships of the assembly file each time the hybrid map is constructed; after the object mapping table corresponding to the target assembly file is obtained, traversing each import unit in the object mapping table, generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit, and constructing edges between each import node and the reference node according to the corresponding relation between each reference unit and the import unit to obtain a target hybrid map of the target assembly file, so that the generated target hybrid map can be synchronous with the reference relation in the target assembly file, and the accuracy of the target hybrid map is improved. According to the method, the correctness of the generated target hybrid diagram can be improved by the mode of generating the target hybrid diagram according to the object mapping table after the object mapping table of the assembly file is pre-constructed, and the management effect of the assembly data is further improved.
In one embodiment, the obtaining the latest object mapping table corresponding to the target assembly file in step S110 may include:
s111: and obtaining the object identification of the target assembly file.
S112: and searching the object identifier in the database to obtain an object mapping table corresponding to the target assembly file.
In this embodiment, when the file management system obtains the object mapping table, the file management system may first obtain the object identifier of the target assembly file, and then may retrieve the object identifier in the database, and obtain the object mapping table corresponding to the target assembly file according to the retrieval result.
It can be understood that the database of the present application is pre-constructed with object mapping tables corresponding to each target assembly file, and each object mapping table is built with an index structure with the object identifier. Wherein object identification refers to an identifier for identifying and managing data objects, which generally includes information such as the name, ID, version, etc. of the object for uniquely identifying and managing the data object.
Specifically, the file management system may first obtain attribute information of the target assembly file when storing the object mapping table in the database, where the attribute information includes, but is not limited to, information such as file name, data ID, file type, and creation time. The file management system may then generate an object identification based on the attribute information and create an index relationship between the object identification and the object mapping table in the database using ELASTIC SEARCH search tools. The ELASTIC SEARCH search tool adopted by the application means that the reverse index technology of Lucene is used for realizing faster filtering than the relational database, and other modes capable of realizing the database search in the application can be used as the preferred scheme of the application without limitation.
In one embodiment, the process of constructing the object mapping table in step S110 may include:
s113: when the reference relation of the target assembly file is established, the target assembly file is analyzed to obtain the data ID and the reference relation of each target import data in the target assembly file.
S114: and creating an import set corresponding to the target assembly file, and generating an import unit corresponding to each target import data in the import set according to each data ID.
S115: and determining the import data of other assembly files corresponding to each reference relation, generating corresponding reference units in each import unit according to each reference relation and the import data of each other assembly file, and taking the built import set as an object mapping table of the target assembly file.
In this embodiment, after the file management system detects that the user establishes and stores the reference relationship of the target assembly file, the file management system may parse the target assembly file, and obtain the data ID and the reference relationship of each target import data in the target assembly file according to the parsing result; then the file management system can create an import set corresponding to the target assembly file, and generate an import unit corresponding to each target import data in the import set according to each data ID; the file management system can determine the import data of other assembly files corresponding to each reference relation, generate corresponding reference units in each import unit according to each reference relation and the import data of each other assembly file, and finally the file management system can take the built import set as an object mapping table of the target assembly file.
It can be understood that when the file management system creates the import set corresponding to the target assembly file, the object identifier of the target assembly file can be obtained and added into the import set, so as to establish the corresponding relationship between the import set and the target assembly file, thereby better managing and maintaining the database.
Specifically, each data ID obtained by parsing in the present application represents one target import data, so the file management system may generate an import unit with the same number as the data IDs in the import set, and sequentially add each data ID to the import unit to construct a correspondence between the import unit and the target import data, and then the file management system may perform attribute reading on the target import data in the target assembly file, and add the attribute information of each target import data to the corresponding import unit after reading the attribute information of each target import data. The file management system may further analyze the reference relationship of each target import data to obtain the import data of other assembly files corresponding to each reference relationship, and the data ID, attribute information and driving type of the import data of each other assembly file, then the file management system may generate the reference units with the same number as the reference relationship of the target import data corresponding to the import unit in the import unit, sequentially add the data ID, attribute information and driving type of the import data of other assembly files corresponding to the reference relationship in the target import data to the generated reference units, so as to complete the construction of the import set, and finally the file management system may use the constructed import set as the object mapping table of the target assembly file.
In one embodiment, generating the import node corresponding to each import unit and the reference node corresponding to the reference unit in at least one import unit in step S120 may include:
S121: other assembly files from which each referencing unit in the at least one import unit originates are determined.
S122: and constructing an initial mixed graph of the object mapping table, and generating a target assembly file and an import set node corresponding to each other assembly file in the initial mixed graph.
S123: and generating an import node corresponding to each import unit in the import set node of the target assembly file, and generating a reference node corresponding to each reference unit from each other assembly file in the import set node of the other assembly file.
In this embodiment, when the file management system generates the node of the object mapping table, other assembly files from each reference unit in at least one import unit may be determined first, and an initial hybrid diagram of the object mapping table may be constructed, then the target assembly file and the import set node corresponding to each other assembly file may be generated in the initial hybrid diagram, finally the file management system may generate the import node corresponding to each import unit in the import set node of the target assembly file, and generate the reference node corresponding to each reference unit derived from each other assembly file in the import set node of each other assembly file.
It can be understood that each unit in the object mapping table is any imported data in the assembly file, so that in order to prevent the generated nodes from being disordered in distribution and unknown in source, the file management system can also confirm the assembly file from each unit when converting each unit in the object mapping table into a node, so that the importing set node of each assembly file can be generated, and further, corresponding nodes can be generated in each importing set node, and ordered distribution of each node in the hybrid graph is realized, so that the assembly file from each node is clear at a glance.
Specifically, for each reference unit in at least one import unit, the file management system may determine other assembly files from which the reference unit originates according to attribute information stored in the reference unit, where any two other assembly files from which the reference unit originates may be the same or different, and the disclosure is not limited herein. After determining other assembly files from which each reference unit originates, the file management system can generate an import set node which is consistent with the number of the target assembly files and other assembly files, and add object identifiers of the target assembly files and the other assembly files into the corresponding import set nodes so as to establish a corresponding relationship between the import set nodes and the assembly files. Finally, the file management system may generate an import node corresponding to each import unit in the import set node of the target assembly file, and generate a reference node corresponding to each reference unit derived from each other assembly file in the import set node of the other assembly file.
Schematically, as shown in fig. 3, fig. 3 is a schematic structural diagram of a target hybrid diagram according to an embodiment of the present application; taking a target mixed graph created by the ingress manager as an example, in the target mixed graph, file0, file1 and File2 are all ingress set nodes, in the expanded term, file1 is an ingress set node of a target assembly File, and File1: A is an ingress node in ingress set node File 1; file0 and File2 are lead-in set nodes of other assembly files, and File0:B and File2:A are all reference nodes of File1:A, wherein, file0:B is derived from File0, so that the reference nodes are generated in lead-in set node File0, while File2:A is derived from File2, so that the reference nodes are generated in lead-in set node File 2. In addition, the reference relationship between File0:B and File1:A is recorded under Edge0, while the reference relationship between File1:A and File2:A is recorded under Edge 1.
In one embodiment, constructing the edge between each import node and the reference node according to the correspondence between each reference unit and the import unit in step S130 may include:
S131: and determining the import node and the reference node in the corresponding relation and the driving type of the reference node according to the corresponding relation between each reference unit and the import unit.
S132: judging whether the driving type is mirror image driving or not; if yes, go to step S133, otherwise go to step S134.
S133: an undirected edge is created between the import node and the reference node.
S134: a reference guide between the import node and the reference node is determined, and a directed edge is created between the import node and the reference node based on the reference guide.
In this embodiment, when constructing an edge between an import node and a reference node, the file management system determines, for each reference unit and a corresponding relationship between the import units, the import node and the reference node in the corresponding relationship, and a driving type of the reference node, and determines whether the driving type is mirror driving, if so, creates an undirected edge between the import node and the reference node; if not, a reference guide between the import node and the reference node is determined, and a directed edge is created between the import node and the reference node based on the reference guide.
It is understood that the types of drives of the referencing nodes may include value drives, geometry drives, position drives, and mirror drives. Wherein, the value driving refers to a driving mode based on parameter values, and is used for referencing parameter values in other assembly files; the geometric driving refers to a driving mode based on geometric relation and is used for referencing the surface primitives in other assembly files; the position driving refers to a driving mode based on a position relation and is used for referring to position information in other assembly files; the mirror image driving refers to a driving mode based on a symmetrical relation, which is used for referencing data in other assembly files, and the influence between the referenced data and source data is that when one data changes, the other data also changes. Therefore, when constructing the edge between the leading-in node and the reference node, the file management system can firstly judge whether the driving type of the reference node is the driving type, and select a corresponding edge creation method according to the judging result.
Specifically, when the file management system determines that the drive type of the reference node is mirror drive, it is explained that the import data corresponding to the reference node and the target import data corresponding to the import node affect each other, so that an undirected edge can be created between the reference node and the reference node. When the file management system determines that the drive type of the reference node is not mirror drive, the file management system indicates that the import data corresponding to any one of the reference node and the import node is changed, and the import change corresponding to the other node is not affected, so that the reference direction between the import node and the reference node can be determined, and a directed edge can be created between the import node and the reference node according to the reference direction. The reference steering herein may include import and export, and when the reference steering is import, the file management system may create a directed edge with the import node as the import and the reference node as the export; when the reference director is export, the file management system may create a directed edge that exports with the import node and imports with the reference node.
In one embodiment, each import unit in the object mapping table in step S110 stores a data ID of the corresponding import data; the updating process of the object mapping table may include:
S116: when the user is detected to update the target assembly file, an object mapping table corresponding to the target assembly file is acquired, and target import data updated in the target assembly file is used as change data.
S117: and determining the data ID and the change type of the change data, indexing the data ID in the object mapping table, and determining an importing unit corresponding to the data ID according to an indexing result as a unit to be updated of the object mapping table.
S118: and updating the unit to be updated according to the change type and the change data so as to update the object mapping table.
In one embodiment, when the file management system detects that the user updates the target assembly file, the file management system may acquire an object mapping table corresponding to the target assembly file, and use the target import data updated in the target assembly file as change data, then the file management system may determine a data ID and a change type of the change data to index the data ID in the object mapping table, and after determining an import unit corresponding to the data ID according to the index result, use the import unit as a unit to be updated of the object mapping table, so that the unit to be updated may be updated according to the change type and the change data, and further update the object mapping table.
Specifically, after a user updates a target assembly file in an update interface in a file management system, the file management system can compare the difference between the updated target assembly file and a target assembly file before updating, and takes imported data with the difference in the comparison result as change data, so that the data ID and the change type of the change data can be determined; meanwhile, the file management system can also retrieve the object mapping table from the database through the object identification of the target assembly file. After obtaining the object mapping table of the target assembly file and the data ID and the change type of the change data, the file management system can index the data ID in the object mapping table by adopting a search tool, take an index obtaining unit as a unit to be updated of the object mapping table, and finally update the unit to be updated according to the change type and the change data so as to realize the update of the object mapping table. The application can quickly locate the change position in the object mapping table by the updating method, thereby reducing the change range and the data processing amount.
In one embodiment, the determining, in step S117, the import unit corresponding to the data ID according to the index result, as the unit to be updated of the object mapping table, may include:
s171: judging whether the index result is empty or not; if yes, step S172 is executed, and if no, step S173 is executed.
S172: and generating an import unit corresponding to the change data in the object mapping table, and taking the generated import unit as a unit to be updated of the object mapping table.
S173: and taking an importing unit corresponding to the data ID in the object mapping table as a unit to be updated of the object mapping table.
In this embodiment, when determining the unit to be updated of the object mapping table, the file management system may first determine whether the index result of the data ID of the change data is empty, if yes, generate an import unit corresponding to the change data in the object mapping table, and use the generated import unit as the unit to be updated of the object mapping table; if not, taking an importing unit corresponding to the data ID in the object mapping table as a unit to be updated of the object mapping table.
Specifically, when the index result of the data ID of the change data is empty, it indicates that the change data is newly added target import data, so that there is no import unit corresponding to the change data in the object mapping table before updating, and at this time, the file management system may generate a corresponding import unit in the object mapping table according to the change data, and use the import unit as a unit to be updated of the object mapping table. When the index result of the data ID of the change data has data, the existence of the import unit corresponding to the change data in the object mapping table before updating is indicated, so that the file management system can directly take the import unit corresponding to the data ID in the object mapping table as the unit to be updated of the object mapping table.
In one embodiment, the updating the unit to be updated according to the change type and the change data in step S118 may include:
S181: and determining the reference relation corresponding to the change data and the imported data of other assembly files corresponding to the reference relation, and updating the unit to be updated according to the change type, the reference relation and the imported data of other assembly files.
In this embodiment, when the file management system updates the unit to be updated, the reference relationship corresponding to the change data and the imported data of other assembly files corresponding to the reference relationship may be determined first, and then the file management system may update the unit to be updated according to the change type, the reference relationship and the imported data of other assembly files.
It is to be understood that the change type herein may be a change to the reference relationship, including a new addition, a modification, and a deletion of the reference relationship, or a change to the target import data, including a new addition, a modification, and a deletion of the target import data.
Specifically, when the change type is a new addition of the reference relationship or the target import data, the file management system may first obtain the new addition of the reference relationship and the import data of the corresponding other assembly files in the unit to be updated, and then may generate the reference unit corresponding to the import data of the other assembly files in the unit to be updated. When the change type is the reference relation or the modification of the target imported data, the file management system can acquire the reference relation needing to be modified in the unit to be updated first, then delete the reference unit corresponding to the reference relation in the unit to be updated, and regenerate the modified reference unit. When the change type is deletion of the reference relationship, the file management system can directly delete the reference unit corresponding to the reference relationship in the units to be updated. When the change type is deletion of target import data, the file can directly delete the unit to be updated according to the management system.
Further, when the driving type of the reference unit is mirror driving, the modification of the target import data corresponding to the import unit will affect the import data of other assembly files corresponding to the reference unit, so after the modification of the target import data, if the corresponding import unit has the reference unit with the driving type being mirror driving, the file management system synchronously modifies the import data of other assembly files corresponding to the reference unit, then the file management system can take the other assembly files as new target assembly files, take the modified import data as new change data, and synchronously update the object mapping tables of the other assembly files, where the update process is consistent with the update process of the object mapping tables in the above embodiment, and is not repeated herein.
The assembly data management device provided by the embodiment of the present application will be described below, and the assembly data management device described below and the assembly data management method described above may be referred to correspondingly to each other.
In one embodiment, as shown in fig. 4, fig. 4 is a schematic flow chart of an assembly data management device according to an embodiment of the present application; the application also provides an assembly data management device, which comprises a mapping table acquisition module 210, a node generation module 220 and a mixed graph construction module 230, and specifically comprises the following steps:
The mapping table obtaining module 210 is configured to obtain, when detecting that the user constructs the hybrid map of the target assembly file, a latest object mapping table corresponding to the target assembly file.
The node generating module 220 is configured to traverse each import unit in the object mapping table, and generate an import node corresponding to each import unit, and a reference node corresponding to a reference unit in at least one import unit.
The hybrid graph construction module 230 is configured to construct edges between each import node and the reference node according to the correspondence between each reference unit and the import unit, so as to obtain a target hybrid graph of the target assembly file.
In the above embodiment, when it is detected that the user constructs the hybrid map of the target assembly file, the latest object mapping table corresponding to the target assembly file may be obtained, where the target assembly file includes a plurality of target import data and reference relationships when the import data of other assembly files are referenced in at least one target import data, and the object mapping table includes an import unit corresponding to each target import data and a reference unit provided in at least one import unit and characterizing the reference relationships of the target import data, so that the present application may pre-store all the reference relationships of the assembly file to the external file through the object mapping table, and reduce a process of resolving the reference relationships of the assembly file each time the hybrid map is constructed; after the object mapping table corresponding to the target assembly file is obtained, traversing each import unit in the object mapping table, generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit, and constructing edges between each import node and the reference node according to the corresponding relation between each reference unit and the import unit to obtain a target hybrid map of the target assembly file, so that the generated target hybrid map can be synchronous with the reference relation in the target assembly file, and the accuracy of the target hybrid map is improved. According to the method, the correctness of the generated target hybrid diagram can be improved by the mode of generating the target hybrid diagram according to the object mapping table after the object mapping table of the assembly file is pre-constructed, and the management effect of the assembly data is further improved.
In one embodiment, the mapping table acquisition module 210 may include:
The identification acquisition sub-module is used for acquiring the object identification of the target assembly file.
And the identification and retrieval sub-module is used for retrieving the object identification in the database to obtain an object mapping table corresponding to the target assembly file.
In one embodiment, the mapping table acquisition module 210 may further include:
And the file analysis sub-module is used for analyzing the target assembly file when the reference relation of the target assembly file is established, so as to obtain the data ID and the reference relation of each target import data in the target assembly file.
The import unit generation sub-module is used for creating an import set corresponding to the target assembly file and generating an import unit corresponding to each target import data in the import set according to each data ID.
The reference unit generation submodule is used for determining the import data of other assembly files corresponding to each reference relation, generating corresponding reference units in each import unit according to each reference relation and the import data of each other assembly file, and taking the built import set as an object mapping table of the target assembly file.
In one embodiment, the node generation module 220 may include:
the file determination submodule is used for determining other assembly files from which each reference unit in at least one import unit is derived.
And the mixed graph construction sub-module is used for constructing an initial mixed graph of the object mapping table and generating a target assembly file and an import set node corresponding to each other assembly file in the initial mixed graph.
The node generation sub-module is used for generating an import node corresponding to each import unit in the import set node of the target assembly file, and generating a reference node corresponding to each reference unit from each other assembly file in the import set node of the other assembly file.
In one embodiment, the hybrid map construction module 230 may include:
And the type determination submodule is used for determining the leading-in node and the reference node in the corresponding relation and the driving type of the reference node.
And the type judging sub-module is used for judging whether the driving type is mirror image driving.
A first creation sub-module for creating an undirected edge between the import node and the reference node.
And the second creation submodule is used for determining the reference direction between the leading-in node and the reference node and creating a directed edge between the leading-in node and the reference node according to the reference direction.
In one embodiment, the mapping table acquisition module 210 may further include:
and the change data determination submodule is used for acquiring an object mapping table corresponding to the target assembly file when the user is detected to update the target assembly file, and taking the updated target import data in the target assembly file as change data.
And the data ID indexing sub-module is used for determining the data ID and the change type of the changed data, indexing the data ID in the object mapping table, and determining an importing unit corresponding to the data ID according to the indexing result as a unit to be updated of the object mapping table.
And the mapping table updating sub-module is used for updating the unit to be updated according to the change type and the change data so as to update the object mapping table.
In one embodiment, the data ID index sub-module may include:
And the result judging unit is used for judging whether the index result is empty.
The first unit confirming unit is used for generating an importing unit corresponding to the change data in the object mapping table, and taking the generated importing unit as a unit to be updated of the object mapping table.
And the second unit confirming unit is used for taking an importing unit corresponding to the data ID in the object mapping table as a unit to be updated of the object mapping table.
In one embodiment, the mapping table update sub-module may include:
The unit updating unit is used for determining the reference relation corresponding to the change data and the imported data of other assembly files corresponding to the reference relation, and updating the unit to be updated according to the change type, the reference relation and the imported data of other assembly files.
In one embodiment, the present application also provides a storage medium having stored therein computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the assembly data management method as set forth in any one of the above embodiments.
In one embodiment, the present application also provides a computer device having stored therein computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the assembly data management method as set forth in any of the above embodiments.
Schematically, as shown in fig. 5, fig. 5 is a schematic internal structure of a computer device according to an embodiment of the present application, and the computer device 300 may be provided as a server. Referring to FIG. 5, computer device 300 includes a processing component 302 that further includes one or more processors, and memory resources represented by memory 301, for storing instructions, such as applications, executable by processing component 302. The application program stored in the memory 301 may include one or more modules each corresponding to a set of instructions. Further, the processing component 302 is configured to execute instructions to perform the assembly data management method of any of the embodiments described above.
The computer device 300 may also include a power supply component 303 configured to perform power management of the computer device 300, a wired or wireless network interface 304 configured to connect the computer device 300 to a network, and an input output (I/O) interface 305. The computer device 300 may operate based on an operating system stored in the memory 301, such as Windows Server TM, mac OS XTM, unix, linux, free BSDTM, or the like.
It will be appreciated by those skilled in the art that the structure shown in FIG. 5 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the present specification, each embodiment is described in a progressive manner, and each embodiment focuses on the difference from other embodiments, and may be combined according to needs, and the same similar parts may be referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (9)

1. A method of assembly data management, the method comprising:
When detecting that a user builds a hybrid diagram of a target assembly file, acquiring an up-to-date object mapping table corresponding to the target assembly file, wherein the target assembly file comprises a plurality of target import data and reference relations when the import data of other assembly files are referenced in at least one target import data, and the object mapping table comprises an import unit corresponding to each target import data and a reference unit which is arranged in at least one import unit and characterizes the reference relations of the target import data;
Traversing each import unit in the object mapping table, and generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit;
According to the corresponding relation between each reference unit and each lead-in unit, constructing each lead-in node and the edge between the reference nodes to obtain a target mixed graph of the target assembly file so as to realize management of assembly data in the target assembly file;
The construction process of the object mapping table comprises the following steps:
When establishing a reference relation of the target assembly file, analyzing the target assembly file to obtain a data ID and a reference relation of each target import data in the target assembly file;
Creating an import set corresponding to the target assembly file, and generating an import unit corresponding to each target import data in the import set according to each data ID;
Determining the import data of other assembly files corresponding to each reference relation, generating corresponding reference units in each import unit according to each reference relation and the import data of each other assembly file, and taking the built import set as an object mapping table of the target assembly file;
The generating the import node corresponding to each import unit and the reference node corresponding to the reference unit in at least one import unit includes:
determining other assembly files from which each reference unit in the at least one lead-in unit is derived;
Constructing an initial mixed graph of the object mapping table, and generating the target assembly file and an import set node corresponding to each other assembly file in the initial mixed graph;
And generating an import node corresponding to each import unit in the import set node of the target assembly file, and generating a reference node corresponding to each reference unit from each other assembly file in the import set node of the other assembly file.
2. The assembly data management method according to claim 1, wherein the obtaining the latest object mapping table corresponding to the target assembly file includes:
obtaining an object identifier of the target assembly file;
Searching the object identifier in a database to obtain an object mapping table corresponding to the target assembly file; and the database is pre-constructed with object mapping tables corresponding to the target assembly files.
3. The assembly data management method according to claim 1, wherein constructing edges between each import node and the reference node according to correspondence between each reference unit and the import unit comprises:
For each correspondence between a referencing unit and an importation unit:
determining an import node and a reference node in the corresponding relation and a driving type of the reference node;
judging whether the driving type is mirror image driving or not;
if yes, creating an undirected edge between the import node and the reference node;
if not, determining a reference guide between the import node and the reference node, and creating a directed edge between the import node and the reference node according to the reference guide.
4. The assembly data management method according to claim 1, wherein each import unit in the object mapping table stores a data ID of the corresponding import data;
The updating process of the object mapping table comprises the following steps:
When the user is detected to update the target assembly file, an object mapping table corresponding to the target assembly file is obtained, and target import data updated in the target assembly file is used as change data;
Determining a data ID and a change type of the change data, indexing the data ID in the object mapping table, and determining an importing unit corresponding to the data ID according to an indexing result as a unit to be updated of the object mapping table;
And updating the unit to be updated according to the change type and the change data so as to update the object mapping table.
5. The assembly data management method according to claim 4, wherein the determining the import unit corresponding to the data ID according to the index result as the unit to be updated of the object mapping table includes:
judging whether the index result is empty or not;
If yes, generating an import unit corresponding to the change data in the object mapping table, and taking the generated import unit as a unit to be updated of the object mapping table;
if not, taking an importing unit corresponding to the data ID in the object mapping table as a unit to be updated of the object mapping table.
6. The method according to claim 5, wherein the updating the unit to be updated according to the change type and the change data includes:
Determining a reference relation corresponding to the change data and the imported data of other assembly files corresponding to the reference relation, and updating the unit to be updated according to the change type, the reference relation and the imported data of the other assembly files;
wherein the change type comprises the addition, modification and deletion of the reference relation and the addition, modification and deletion of the imported data.
7. An assembly data management device, comprising:
The mapping table acquisition module is used for acquiring an up-to-date object mapping table corresponding to a target assembly file when detecting that a user constructs a hybrid diagram of the target assembly file, wherein the target assembly file comprises a plurality of target import data and a reference relation when the import data of other assembly files are referenced in at least one target import data, and the object mapping table comprises an import unit corresponding to each target import data and a reference unit which is arranged in at least one import unit and characterizes the reference relation of the target import data;
The node generation module is used for traversing each import unit in the object mapping table and generating an import node corresponding to each import unit and a reference node corresponding to a reference unit in at least one import unit;
The mixed graph construction module is used for constructing edges between each leading-in node and each leading-in node according to the corresponding relation between each leading-in unit and each leading-in unit to obtain a target mixed graph of the target assembly file so as to realize the management of assembly data in the target assembly file;
Wherein, the mapping table acquisition module includes:
When establishing a reference relation of the target assembly file, analyzing the target assembly file to obtain a data ID and a reference relation of each target import data in the target assembly file;
Creating an import set corresponding to the target assembly file, and generating an import unit corresponding to each target import data in the import set according to each data ID;
Determining the import data of other assembly files corresponding to each reference relation, generating corresponding reference units in each import unit according to each reference relation and the import data of each other assembly file, and taking the built import set as an object mapping table of the target assembly file;
The node generation module includes:
determining other assembly files from which each reference unit in the at least one lead-in unit is derived;
Constructing an initial mixed graph of the object mapping table, and generating the target assembly file and an import set node corresponding to each other assembly file in the initial mixed graph;
And generating an import node corresponding to each import unit in the import set node of the target assembly file, and generating a reference node corresponding to each reference unit from each other assembly file in the import set node of the other assembly file.
8. A storage medium, characterized by: the storage medium having stored therein computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the assembly data management method of any of claims 1 to 6.
9. A computer device, comprising: one or more processors, and memory;
stored in the memory are computer readable instructions which, when executed by the one or more processors, perform the steps of the assembly data management method of any one of claims 1 to 6.
CN202311786360.4A 2023-12-25 2023-12-25 Assembly data management method, device, storage medium and computer equipment Active CN117454450B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311786360.4A CN117454450B (en) 2023-12-25 2023-12-25 Assembly data management method, device, storage medium and computer equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311786360.4A CN117454450B (en) 2023-12-25 2023-12-25 Assembly data management method, device, storage medium and computer equipment

Publications (2)

Publication Number Publication Date
CN117454450A CN117454450A (en) 2024-01-26
CN117454450B true CN117454450B (en) 2024-05-31

Family

ID=89584072

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311786360.4A Active CN117454450B (en) 2023-12-25 2023-12-25 Assembly data management method, device, storage medium and computer equipment

Country Status (1)

Country Link
CN (1) CN117454450B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002056406A (en) * 2000-08-08 2002-02-22 Clim Ncd:Kk Assembly process support system and recording medium recorded with its data
CN104182569A (en) * 2014-08-01 2014-12-03 沈阳航空航天大学 Three-dimensional visible simulation method for product error accumulation
CN110909439A (en) * 2018-09-14 2020-03-24 中国商用飞机有限责任公司 AR-based assembly method and device and terminal
CN111797277A (en) * 2020-05-19 2020-10-20 武汉乐程软工科技有限公司 Method and device for mapping object system and relation system, computer readable storage medium and terminal equipment
CN112613086A (en) * 2020-11-04 2021-04-06 苏州华兴源创科技股份有限公司 Electrical equipment assembling method and system
CN114138748A (en) * 2021-12-02 2022-03-04 中国建设银行股份有限公司 Database mapping file generation method, device, equipment and storage medium
CN116841536A (en) * 2023-08-30 2023-10-03 成都摹客科技有限公司 Component reference relation reconstruction method, device, system and storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002056406A (en) * 2000-08-08 2002-02-22 Clim Ncd:Kk Assembly process support system and recording medium recorded with its data
CN104182569A (en) * 2014-08-01 2014-12-03 沈阳航空航天大学 Three-dimensional visible simulation method for product error accumulation
CN110909439A (en) * 2018-09-14 2020-03-24 中国商用飞机有限责任公司 AR-based assembly method and device and terminal
CN111797277A (en) * 2020-05-19 2020-10-20 武汉乐程软工科技有限公司 Method and device for mapping object system and relation system, computer readable storage medium and terminal equipment
CN112613086A (en) * 2020-11-04 2021-04-06 苏州华兴源创科技股份有限公司 Electrical equipment assembling method and system
CN114138748A (en) * 2021-12-02 2022-03-04 中国建设银行股份有限公司 Database mapping file generation method, device, equipment and storage medium
CN116841536A (en) * 2023-08-30 2023-10-03 成都摹客科技有限公司 Component reference relation reconstruction method, device, system and storage medium

Also Published As

Publication number Publication date
CN117454450A (en) 2024-01-26

Similar Documents

Publication Publication Date Title
US10970292B1 (en) Graph based resolution of matching items in data sources
CN106033436B (en) Database merging method
US8015165B2 (en) Efficient path-based operations while searching across versions in a repository
CN108228229B (en) Method and system for managing Maven dependence
CN108681603B (en) Method for rapidly searching tree structure data in database and storage medium
CN104573039A (en) Keyword search method of relational database
CN109308300B (en) Logic operation processing method and device, conversion plug-in and storage medium
US11573987B2 (en) System for detecting data relationships based on sample data
US20180137158A1 (en) Foreign key learner
CN116843028A (en) Multi-mode knowledge graph construction method, system, storage medium and electronic equipment
CN112269883A (en) Personnel information query method and device, electronic equipment and storage medium
CN114253995B (en) Data tracing method, device, equipment and computer readable storage medium
CN110347846B (en) Non-connected knowledge graph query method with time constraint
CN108959454B (en) Prompting clause specifying method, device, equipment and storage medium
CN117454450B (en) Assembly data management method, device, storage medium and computer equipment
CN114168591A (en) Method for searching tree structure data path node
CN113722325A (en) Method and device for detecting table information in database, computer equipment and storage medium
KR20130064160A (en) System of entity-relationship model reformulation of sparql query results on rdf data and the method
CN109271350B (en) Database and information point table automatic comparison and synchronization method based on telecontrol communication
CN104636471A (en) Procedure code finding method and device
CN116881512A (en) Cross-system metadata blood-edge automatic analysis method
CN109145167B (en) Content difference comparison method for ICD file and corresponding IED in SCD
CN114356404A (en) Interface document generating method, system and computer readable storage medium
CN113221528A (en) Automatic generation and execution method of clinical data quality evaluation rule based on openEHR model
CN115186023B (en) Data set generation method, device, equipment and medium

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