CN109670796B - Engineering data management method and system - Google Patents
Engineering data management method and system Download PDFInfo
- Publication number
- CN109670796B CN109670796B CN201811626411.6A CN201811626411A CN109670796B CN 109670796 B CN109670796 B CN 109670796B CN 201811626411 A CN201811626411 A CN 201811626411A CN 109670796 B CN109670796 B CN 109670796B
- Authority
- CN
- China
- Prior art keywords
- engineering
- project
- metadata
- data
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The invention provides a method and a system for managing engineering data, which determine a required metadata source from a pre-established metadata base by acquiring operation request information of pre-imported engineering data information, call the engineering data in the metadata source, convert the engineering data into corresponding project entities, determine engineering project items corresponding to each project entity in the project entities based on the corresponding relationship between the pre-established project entities and the engineering project items, and finally execute corresponding operations according to metadata types, keywords and the engineering project items corresponding to the operation information to determine operation results corresponding to the operation information. By means of the method, the project data are made into entries in advance, and when a subsequent user performs corresponding operation on the project data, the purpose that the required operation result is obtained quickly and efficiently based on the project data after the entries are made is achieved.
Description
Technical Field
The invention relates to the technical field of data management, in particular to a method and a system for engineering data management.
Background
At present, traveling by taking a subway is more and more popular, so more and more countries and cities pay attention to the construction of the subway, and the storage and the reference of a large amount of drawings, data and other data generated from planning to construction of the subway are more and more important. In the existing subway engineering data management method, the whole data is used as a basic unit for storage and query.
In the prior art, the entire data may include investigation, design, construction, environmental and third party monitoring of the project, etc., according to the project classification. Furthermore, the investigation includes initial investigation, detailed investigation and the like; the design is divided into a structure diagram of a safety entrance structure, a plane diagram of an air duct structure and the like; the construction is divided into a general plane diagram of a shaft monitoring point, a construction shaft monitoring scheme, a construction organization design and the like; the environment is divided into survey reports and the like; the third-party monitoring can be divided into an interval third-party monitoring scheme, a shaft third-party monitoring scheme and the like.
Therefore, the scheme in the prior art can only search the whole data, and can not quickly acquire more detailed data.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and a system for managing engineering materials, so as to achieve the purpose of obtaining detailed materials in the engineering materials more quickly and efficiently.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
a method for managing engineering data comprises:
acquiring operation request information of pre-imported engineering material information, wherein the operation request information comprises a keyword, engineering professional classification and operation information used for indicating a user to carry out on the pre-imported engineering material information, and the keyword at least comprises an engineering name;
determining a metadata type corresponding to the engineering professional classification and a metadata type corresponding to the operation request information;
determining a metadata source corresponding to the engineering professional classification based on the metadata type corresponding to the engineering professional classification and a pre-established metadata base, wherein the pre-established metadata base comprises the metadata source corresponding to the pre-imported engineering information;
calling the engineering data in the metadata source, and converting the engineering data into corresponding project entities;
determining an engineering project item corresponding to each project entity in the project entities based on a pre-established corresponding relationship between the project entities and the engineering project items;
and executing corresponding operation according to the metadata type corresponding to the operation information, the keyword and the project item, and determining an operation result corresponding to the operation information.
Preferably, the process of pre-establishing the metadata database includes:
acquiring and analyzing engineering data information to be imported, and acquiring engineering professional classification and engineering item classification, wherein the engineering professional classification comprises all project entities forming engineering project data, and the engineering item classification comprises engineering project items determined based on the engineering project classification;
establishing a one-to-one corresponding relation between each project entity and the project item;
determining the metadata type corresponding to each project entity, and converting each project entity into the engineering data corresponding to each metadata type;
establishing a metadata source corresponding to the engineering data information to be imported based on the metadata type and the engineering data corresponding to the metadata type;
and establishing a metadata database according to the acquired metadata source.
Preferably, determining the metadata source corresponding to the engineering major classification based on the metadata type corresponding to the engineering major classification and a pre-established metadata database includes:
if the metadata type corresponding to the engineering professional classification is any node in the engineering project, acquiring a metadata source corresponding to the node in a pre-established metadata base;
and determining the metadata source as the metadata source corresponding to the engineering professional classification.
Preferably, if the metadata type corresponding to the operation information is data query metadata, the keyword includes an engineering name, an item entry and an item entity, and the determining the operation result corresponding to the operation information by executing corresponding operation according to the metadata type corresponding to the operation information, the keyword and the engineering item entry includes:
inquiring the project item corresponding to the keyword based on the data inquiry metadata corresponding to the operation information and the project name and the project item in the keyword;
and querying and determining the project entity consistent with the project entity in the keyword in the project item as an operation result.
Preferably, if the metadata type corresponding to the operation information is data download metadata, the keyword includes an engineering name, an item entry and an item entity, and the determining the operation result corresponding to the operation information by executing corresponding operation according to the metadata type corresponding to the operation information, the keyword and the engineering item entry includes:
downloading metadata based on the data corresponding to the operation information, and inquiring the project item corresponding to the keyword according to the project name and the project item in the keyword;
querying the project entities in the project item items consistent with the project entities in the keywords;
and calling the project entity and downloading.
Preferably, the method further comprises the following steps:
acquiring log behavior record data in a preset time period, wherein the log behavior record data is used for recording behavior data corresponding to corresponding operations executed by a user for importing engineering material information or aiming at the pre-imported engineering material information;
analyzing the log behavior record data, and determining the engineering data with the operation times larger than a preset value in the preset time period.
An engineering data management system, comprising:
the system comprises an acquisition module, a display module and a display module, wherein the acquisition module is used for acquiring operation request information of pre-imported engineering material information, the operation request information comprises a keyword, engineering professional classification and operation information for indicating a user to carry out on the pre-imported engineering material information, and the keyword at least comprises an engineering name;
the type determining module is used for determining the metadata type corresponding to the engineering major classification and the metadata type corresponding to the operation request information;
the data source determining module is used for determining the metadata source corresponding to the engineering professional classification based on the metadata type corresponding to the engineering professional classification and a pre-established metadata base, wherein the pre-established metadata base comprises the metadata source corresponding to the pre-imported engineering information;
the calling module is used for calling the engineering data in the metadata source and converting the engineering data into corresponding project entities;
the item determining module is used for determining the project item corresponding to each project entity in the project entities based on the corresponding relation between the project entities and the project items established in advance;
and the operation module is used for executing corresponding operations according to the metadata type corresponding to the operation information, the keywords and the project item and determining an operation result corresponding to the operation information.
Preferably, the method further comprises the following steps:
the analysis module is used for acquiring and analyzing the information of the engineering data to be imported, and acquiring engineering professional classification and engineering item classification, wherein the engineering professional classification comprises all project entities forming the engineering project data, and the engineering item classification comprises engineering project items determined based on the engineering project classification;
the first establishing module is used for establishing the one-to-one corresponding relation between each project entity and the project item;
the conversion module is used for determining the metadata types corresponding to the project entities and converting the project entities into the engineering data corresponding to the metadata types;
the second establishing module is used for establishing a metadata source corresponding to the engineering data information to be imported based on the metadata type and the engineering data corresponding to the metadata type;
and the third establishing module is used for establishing a metadata database according to the acquired metadata source.
Preferably, the data source determining module is specifically configured to, if the metadata type corresponding to the engineering professional classification is any node in the engineering project, obtain a metadata source corresponding to the node in a pre-established metadata database, and determine that the metadata source is the metadata source corresponding to the engineering professional classification.
Preferably, the operation module is specifically configured to, if the metadata type corresponding to the operation information is data query metadata, query an engineering project entry corresponding to the keyword based on the data query metadata corresponding to the operation information and the engineering name and the project entry in the keyword, and query and determine that the project entity in the engineering project entry that is consistent with the project entity in the keyword is an operation result;
or, the operation module is specifically configured to download metadata based on the data corresponding to the operation information, and to query an engineering project entry corresponding to the keyword based on the engineering name and the project entry in the keyword, query the project entity in the engineering project entry that is consistent with the project entity in the keyword, and call the project entity and download.
The engineering data management method determines a required metadata source from a pre-established metadata base by acquiring operation request information of pre-imported engineering data information, calls engineering data in the metadata source, converts the engineering data into corresponding project entities, determines engineering project items corresponding to each project entity in the project entities based on a pre-established corresponding relationship between the project entities and the engineering project items, and finally executes corresponding operations according to metadata types, keywords and the engineering project items corresponding to the operation information to determine operation results corresponding to the operation information. By means of the method, the project data are made into entries in advance, and when a subsequent user performs corresponding operation on the project data, the purpose that the required operation result is obtained quickly and efficiently based on the project data after the entries are made is achieved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flowchart illustrating a method for managing engineering data according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a structure of a project item according to an embodiment of the present invention;
fig. 3a is a schematic flow chart of pre-establishing a metadata database according to an embodiment of the present invention;
FIG. 3b is a schematic diagram of a hierarchical structure of engineering project data according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a query execution operation according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a download operation according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating an analysis of log record data according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of an engineering data management system according to an embodiment of the present disclosure;
FIG. 8 is a schematic structural diagram of another engineering data management system according to an embodiment of the present disclosure;
FIG. 9 is a schematic diagram of another engineering data management system according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, 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 phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
As can be seen from the background art, a user can only obtain the entire data of an engineering project based on the engineering data management method disclosed in the prior art, but for more detailed contents in the engineering project, for example, any node in the life cycle of the engineering project cannot be directly obtained, and the user needs to search the entire data by himself. Thereby affecting the efficiency and perception of the user in finding the material.
Therefore, the embodiment of the invention discloses an engineering data management method, which carries out itemization on engineering data when importing engineering data information through pre-establishing a metadata base so that a subsequent user can directly find a required project entity based on engineering data items when finding corresponding data. The specific implementation manner is explained in detail by the following examples.
Metadata is defined as data that describes data and its environment, an attribute. The metadata is predefined in the embodiment of the present invention. Specifically, in the embodiment of the present invention, the metadata includes service metadata, technical metadata, operation metadata, and the like. The service metadata mainly comprises metadata definitions of relevant data of each node in the whole life cycle of project construction, node-oriented exploration, design, construction, third-party monitoring and the like; the technical metadata mainly comprises user metadata, data access metadata, program composition metadata and the like; the operation metadata mainly includes data loading/updating metadata, data output metadata, program composition metadata, data query metadata, and the like.
The engineering data management disclosed by the embodiment of the invention is mainly based on the data of subway construction, but not limited to the data of subway construction.
Fig. 1 is a schematic flow chart of a method for managing engineering data according to an embodiment of the present invention, which mainly includes the following steps.
Step S101: and acquiring operation request information of the engineering material information imported in advance.
In step S101, the operation request information includes a keyword, a project professional classification, and operation information for instructing a user to perform operation on the pre-imported project material information.
The keyword includes at least a project name.
Optionally, the keyword may be any keyword indicating a main title or a sub-title of the engineering material information, for example, the main title of the engineering material information is "beijing subway construction material", where "beijing subway" may be used as the keyword. The subheading of the Beijing subway construction data comprises the Beijing subway six-number line construction data, the Beijing subway 5-number line construction data and the like, wherein the Beijing subway six-number line can be used as a keyword. The subheading of the Beijing subway line six construction data comprises white stone bridge south station-car public village west station construction data, north sea north station-south gong and drum lane station construction data and the like, wherein characters similar to the white stone bridge south station-car public village west station can be used as keywords.
The engineering major classification refers to each node forming the whole life cycle in the engineering project construction process. For example: the engineering professional classification comprises nodes such as investigation, design, construction, environment and third-party monitoring.
In a specific implementation, the division may be further performed. For example: the survey can be divided into preliminary survey, detailed survey and the like. The design can be divided into a structure diagram of a safety entrance, a plane diagram of an entrance structure, a plane diagram of an air duct structure and the like. The construction can be divided into a general plane diagram of the shaft monitoring points, a construction shaft monitoring scheme, a construction organization design and the like. The environment may be classified as a survey report, etc. The third-party monitoring can be divided into an interval third-party monitoring scheme and a shaft third-party monitoring scheme.
The operation information includes operations of inquiry, downloading, storing and the like. The embodiments of the present invention are not limited to the above-disclosed operations, but may also include other operations, such as modifications and the like.
Step S102: and determining the metadata type corresponding to the engineering professional classification and the metadata type corresponding to the operation information.
In step S102, attributes of the engineering major classification and attributes of the operation information, which are indicated by metadata types, are extracted, respectively.
For example, engineering specialties are classified as: and (4) surveying. And surveying as a node in the engineering project by referring to the content of the public related metadata, wherein the corresponding metadata type is service metadata.
If the operation information is: and (6) querying. Referring to the above disclosure about metadata, the query attribute belongs to the operation metadata, and the specific corresponding metadata type is data query metadata.
Step S103: and determining a metadata source corresponding to the engineering professional classification based on the metadata type corresponding to the engineering professional classification and a pre-established metadata database.
In step S103, if the metadata type corresponding to the engineering major classification is any node in the engineering project, a metadata source corresponding to the node in a pre-established metadata base is obtained, and the metadata source is determined to be the metadata source corresponding to the engineering major classification.
In a specific implementation, the pre-established metadata base related in step S103 includes a metadata source corresponding to the pre-imported engineering material information. The metadata source includes engineering project data information and project entries corresponding to each data information.
The structure of the item entry is shown in fig. 2. Wherein 200 refers to basic information of an engineering project, 201 refers to geological data information, 202 refers to environmental parameter data information, 203 refers to design construction data information, and 204 refers to monitoring data information. Fig. 2 is merely an illustration, and the engineering project data involved in the process of specifically creating project entries is related to specific engineering project data.
Step S104: and calling the engineering data in the metadata source, and converting the engineering data into corresponding project entities.
In step S104, based on the metadata source corresponding to the determined engineering information, the engineering data corresponding to the engineering information in the metadata source is called. It should be noted that the metadata source cannot directly store the corresponding material information, such as the project entity. The engineering data corresponding to the engineering data information is stored.
Step S105: and determining the project item corresponding to each project entity in the project entities based on the corresponding relation between the project entities and the project items established in advance.
In step S105, based on the called engineering data, the engineering project entry corresponding to each project entity is called from the engineering data based on the pre-established corresponding relationship between the project entity and the engineering project entry.
Step S106: and executing corresponding operation according to the metadata type, the keywords and the project item corresponding to the operation information, and determining an operation result corresponding to the operation information.
In the process of executing step S106, based on the above metadata sources, engineering project entries and project entities determined layer by layer, corresponding operations are executed on the keywords and the engineering project entries according to the metadata types corresponding to the operation information. And if the operation is query, querying each project entity under the project item corresponding to the keyword or the project entity corresponding to the keyword. And if the operation is downloading, downloading each project entity under the project item corresponding to the keyword or the specific project entity corresponding to the keyword.
The engineering material management method disclosed by the embodiment of the invention comprises the steps of determining a required metadata source from a pre-established metadata base by acquiring operation request information of pre-imported engineering material information, calling engineering material data in the metadata source, converting the engineering material data into corresponding project entities, determining an engineering project item corresponding to each project entity in the project entities based on the corresponding relation between the pre-established project entities and the engineering project items, and finally executing corresponding operation according to the metadata type, the keywords and the engineering project items corresponding to the operation information to determine an operation result corresponding to the operation information. By means of the project data being itemized in advance, when a subsequent user carries out corresponding operation on the project data, the purpose that the required operation result is obtained quickly and efficiently based on the itemized project data is achieved.
In a specific implementation, the related pre-established metadata base is a metadata base established according to engineering material information. The specific pre-established process is shown in fig. 3a, and includes the following steps:
step S301: and acquiring and analyzing the engineering data information to be imported, and acquiring engineering professional classification and engineering item classification.
In step S301, the basic features of the engineering material information to be imported are analyzed. As shown in table 1, the basic features of the survey data are shown in the embodiment of the present invention. As shown in table 2, a basic feature of a design data is shown in the embodiment of the present invention. As shown in table 3, the basic characteristics of the construction data disclosed in the embodiments of the present invention are shown. As shown in table 4, the basic characteristics of the third-party monitoring data disclosed in the embodiments of the present invention are shown.
Table 1: station-underground excavation-Beijing ten-line (lotus bridge station-lotus bridge station) survey data basic characteristics
Table 2: basic characteristics of station-underground excavation-Beijing ten-size line (lotus bridge station-lotus bridge station) design data
Table 3: basic characteristics of station-underground excavation-Beijing ten-line (lotus bridge station-lotus bridge station) construction data
TABLE 4 basic characteristics of third-party monitoring data of station-underground excavation-Beijing ten-line (Lotus bridgestation-Lotus bridgestation)
The analysis based on the basic features is mainly the analysis of basic feature hierarchy, which is used to determine the project professional classification, the data form, the stored data content and the project item classification contained in the analysis.
According to the hierarchical division, the engineering major classification includes engineering project data including project entities constituting the engineering project data. The project entity generally refers to the entities of the cover, directory, text, diagram, table, etc. of the engineering data.
The project item classification includes project item entries determined based on the project item classification. According to the hierarchical division, the project item classification can be divided into:
FIG. 3b shows a specific hierarchy of engineering project data. Therein, the professional classifications and the items are classified as a first level A1.
The professional classification is continuously divided, and the second layer A2 is engineering project data. Continuing to divide the project data, the third layer A3 is a project entity layer, which mainly comprises: covers, directories, chapters, custom entries, illustrations, tables, and the like. Where chapters and custom entries can continue to be divided. The section continues to divide into a fourth level A4, including illustrations and tables. The custom entries continue to be divided into a fourth level A4, including illustrations and tables.
The classification of the items continues to be divided, and the second layer A2 is the item division. And continuously dividing the items, wherein the third time A3 is the project item.
The above hierarchical structure of the engineering project data is only an example. Other engineering project data can be divided in the above manner, or can be more detailed. As long as the hierarchical division is satisfied.
Step S302: and establishing a one-to-one corresponding relation between each project entity and the project item.
In step S302, based on the disclosed hierarchical division in step S301, step S302 is executed to establish a one-to-one correspondence relationship between each project entity and a specific project item. After the project data are ensured to be itemized, corresponding operation can be carried out on project entities under the determined project items.
For example, an illustration needs to be queried. The project item to which the illustration belongs may be determined first and then a query may be made under the project item. By establishing the one-to-one correspondence between each project entity and the specific project item, the corresponding operation is executed on each project entity more quickly and efficiently.
Step S303: and determining the metadata type corresponding to each project entity, and converting each project entity into the engineering data corresponding to each metadata type.
In step S303, since the metadata is defined as data describing data and its environment, which is an attribute, and the project entity is the data content in the specific project data, the data content needs to be converted when being stored in the metadata database, that is, converted into the project data corresponding to the metadata type, so as to be stored. Therefore, the metadata type corresponding to the project entity needs to be determined.
In particular implementations, the metadata types corresponding to the project entities include document-related metadata, chart-related metadata, geological-related metadata, and so forth.
Step S304: and establishing a metadata source corresponding to the engineering data information to be imported based on the metadata type and the engineering data corresponding to the metadata type.
In step S304, the one-to-one correspondence relationship between each project entity determined in step S302 and the project item is obtained, the project data determined in step S303 is executed, and the metadata source corresponding to the project data information to be imported is established. The metadata source contains a variety of correspondences.
Step S305: and establishing a metadata database according to the acquired metadata source.
In step S305, the metadata source corresponding to the obtained engineering data information to be imported is used as a part of data of the metadata database, and a database, that is, the metadata database, required in the engineering data management system disclosed in the embodiment of the present invention is established.
It should be noted that, after the initial metadata base is established, if a user needs to add new engineering data information, the above-mentioned execution steps of establishing the metadata source of the engineering data information are still adopted to establish the metadata source of the newly added engineering data information.
In a specific implementation, the step S106 shown in fig. 1 is different according to different operation information and specific operations performed by the keywords. The following are exemplified:
if the metadata type corresponding to the operation information is data query metadata, and the keyword includes a project name, a project entry, and a project entity, a specific implementation process of step S106 is shown in fig. 4, and includes:
step S401: inquiring the project item corresponding to the keyword based on the data inquiry metadata corresponding to the operation information and the project name and the project item in the keyword;
step S402: and querying and determining the project entities in the project item items consistent with the project entities in the keywords as operation results.
If the metadata type corresponding to the operation information is data download metadata, and the keyword includes an engineering name, an item entry, and an item entity, a specific implementation process of step S106 is shown in fig. 5, and includes:
step S501: based on the data downloading metadata corresponding to the operation information, and the project names and project entries in the keywords, querying the project entries corresponding to the keywords;
step S502: querying the project entities in the project items which are consistent with the project entities in the keywords;
step S503: and calling the project entity and downloading.
Based on the engineering data management method disclosed by the embodiment of the invention, corresponding behavior record data can be generated and stored in a log mode in the process of executing the specific operations such as importing, querying and downloading. The analysis of the log behavior record data on the user operation can determine the engineering material information commonly used by the user or required currently in the current time period. Based on the method, the corresponding engineering data information can be perfected. As shown in fig. 6, the specific analysis process of the log record data mainly includes the following steps:
step S601: and acquiring log behavior record data in a preset time period.
In step S601, the log behavior record data is used to record behavior data corresponding to corresponding operations executed by a user to import the engineering material information or for the pre-imported engineering material information.
The preset time is set by a user, and the log behavior record data in the set time period can be obtained according to the set time.
Step S602: analyzing the log behavior record data, and determining the engineering data with the operation times larger than a preset value in the preset time period.
In step S602, the engineering data frequently operated by the user in the time period is determined by using the manner that the operation times in the preset time period is greater than the preset value.
The method for determining the engineering data frequently operated by the user in the time period is not limited to this, and optionally, a counting method may also be adopted, and if the preset count is exceeded, the engineering data is regarded as the commonly used engineering data.
By analyzing the log behavior record data, the embodiment of the invention can guide a user or a data manager to perfect the determined common engineering data information in the current time period.
Based on the engineering data management method disclosed in the embodiment of the present invention, an engineering data management system is correspondingly disclosed in the embodiment of the present invention, and the following embodiments are specifically described in detail.
Fig. 7 is a schematic structural diagram of an engineering data management system according to an embodiment of the present invention, the engineering data management system mainly includes: an obtaining module 701, a type determining module 702, a data source determining module 703, a calling module 704, an item determining module 705 and an operating module 706.
The obtaining module 701 is configured to obtain operation request information for pre-imported engineering material information, where the operation request information includes a keyword, an engineering major classification, and operation information for instructing a user to perform on the pre-imported engineering material information, and the keyword at least includes an engineering name.
A type determining module 702, configured to determine a metadata type corresponding to the engineering major classification and a metadata type corresponding to the operation request information.
A data source determining module 703, configured to determine, based on the metadata type corresponding to the engineering major classification and a pre-established metadata base, a metadata source corresponding to the engineering major classification, where the pre-established metadata base includes the metadata source corresponding to the pre-imported engineering material information.
In a specific implementation, the data source determining module 703 is specifically configured to, if the metadata type corresponding to the engineering major classification is any node in an engineering project, obtain a metadata source corresponding to the node in a pre-established metadata base, and determine that the metadata source is the metadata source corresponding to the engineering major classification.
And the calling module 704 is configured to call the engineering data in the metadata source, and convert the engineering data into a corresponding project entity.
The item determining module 705 is configured to determine, based on a pre-established correspondence between project entities and project items, a project item entry corresponding to each of the project entities.
An operation module 706, configured to execute corresponding operations according to the metadata type corresponding to the operation information, the keyword, and the project entry, and determine an operation result corresponding to the operation information.
In a specific implementation, optionally, the operation module 706 is specifically configured to, if the metadata type corresponding to the operation information is data query metadata, where the keyword includes an engineering name, an item entry, and an item entity, query, based on the data query metadata corresponding to the operation information and the engineering name and the item entry in the keyword, the engineering item entry corresponding to the keyword, and query and determine, as an operation result, the item entity in the engineering item entry that is consistent with the item entity in the keyword.
Optionally, the operation module 706 is specifically configured to download metadata based on the data corresponding to the operation information, and query an engineering project entry corresponding to the keyword based on the engineering name and the project entry in the keyword, query the project entity in the engineering project entry that is consistent with the project entity in the keyword, and call and download the project entity.
Referring to fig. 7, as shown in fig. 8, the engineering data management system 700 according to the embodiment of the present disclosure further includes a default unit 707.
The preset unit 707 includes:
the analysis module is used for acquiring and analyzing the engineering data information to be imported, and acquiring engineering professional classification and engineering item classification, wherein the engineering professional classification comprises all project entities forming the engineering project data, and the engineering item classification comprises engineering project items determined based on the engineering project classification.
And the first establishing module is used for establishing the one-to-one corresponding relation between each project entity and the project item.
And the conversion module is used for determining the metadata type corresponding to each project entity and converting each project entity into the engineering data corresponding to each metadata type.
And the second establishing module is used for establishing a metadata source corresponding to the engineering material information to be imported based on the metadata type and the engineering material data corresponding to the metadata type.
And the third establishing module is used for establishing a metadata database according to the acquired metadata source.
Referring to fig. 7, as shown in fig. 9, the engineering material management system 700 according to the embodiment of the present disclosure further includes a log analysis module 708.
A log analysis module 708 comprising:
the acquisition module is used for acquiring log behavior record data in a preset time period.
And the analysis module is used for analyzing the log behavior record data and determining the engineering data of which the operation times are greater than a preset value in the preset time period.
In summary, the engineering data management method and the engineering data management system disclosed in the embodiments of the present invention determine a required metadata source from a pre-established metadata base by acquiring operation request information for pre-imported engineering data information, call engineering data in the metadata source, convert the engineering data into corresponding project entities, determine project items corresponding to each project entity in the project entities based on a pre-established correspondence between the project entities and the project items, and finally perform corresponding operations according to metadata types, the keywords, and the project items corresponding to the operation information to determine operation results corresponding to the operation information. By means of the method, the project data are made into entries in advance, and when a subsequent user performs corresponding operation on the project data, the purpose that the required operation result is obtained quickly and efficiently based on the project data after the entries are made is achieved.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments, which are substantially similar to the method embodiments, are described in a relatively simple manner, and reference may be made to some descriptions of the method embodiments for relevant points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. 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 invention. Thus, the present invention 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 (10)
1. A method for managing engineering data, comprising:
acquiring operation request information of pre-imported engineering material information, wherein the operation request information comprises a keyword, an engineering professional classification and operation information used for indicating a user to carry out on the pre-imported engineering material information, the keyword at least comprises an engineering name, the engineering professional classification is nodes forming the whole life cycle in the engineering project construction process, and the nodes comprise a survey node, a design node, a construction node, an environment node and a third-party monitoring node;
determining a metadata type corresponding to the engineering professional classification and a metadata type corresponding to the operation request information;
determining a metadata source corresponding to the engineering professional classification based on the metadata type corresponding to the engineering professional classification and a pre-established metadata base, wherein the pre-established metadata base comprises the metadata source corresponding to the pre-imported engineering information;
calling engineering data in the metadata source, and converting the engineering data into corresponding project entities;
determining an engineering project entry corresponding to each project entity in the project entities based on a pre-established corresponding relationship between the project entities and the engineering project entries;
and executing corresponding operation according to the metadata type, the keywords and the project item corresponding to the operation information, and determining an operation result corresponding to the operation information.
2. The method according to claim 1, wherein the pre-established procedure of the metadata database comprises:
acquiring and analyzing information of engineering data to be imported, and acquiring engineering professional classification and engineering item classification, wherein the engineering professional classification comprises all project entities forming the engineering project data, and the engineering item classification comprises engineering project items determined based on the engineering project classification;
establishing a one-to-one corresponding relation between each project entity and the project item;
determining the metadata type corresponding to each project entity, and converting each project entity into the engineering data corresponding to each metadata type;
establishing a metadata source corresponding to the engineering data information to be imported based on the metadata type and the engineering data corresponding to the metadata type;
and establishing a metadata database according to the acquired metadata source.
3. The method of claim 1, wherein determining the metadata source corresponding to the engineering specialty classification based on the metadata type corresponding to the engineering specialty classification and a pre-established metadata base comprises:
if the metadata type corresponding to the engineering professional classification is any node in the engineering project, acquiring a metadata source corresponding to the node in a pre-established metadata base;
and determining the metadata source as the metadata source corresponding to the engineering professional classification.
4. The method according to any one of claims 1 to 3, wherein if the metadata type corresponding to the operation information is data query metadata, the keyword includes a project name, a project entry and a project entity, and the determining the operation result corresponding to the operation information by performing corresponding operation according to the metadata type corresponding to the operation information, the keyword and the project entry comprises:
inquiring the project item corresponding to the keyword based on the data inquiry metadata corresponding to the operation information and the project name and the project item in the keyword;
and querying and determining the project entities in the project item items consistent with the project entities in the keywords as operation results.
5. The method according to any one of claims 1 to 3, wherein if the metadata type corresponding to the operation information is data download metadata, the keyword includes an engineering name, an item entry and an item entity, and the determining the operation result corresponding to the operation information by performing a corresponding operation according to the metadata type corresponding to the operation information, the keyword and the engineering item entry comprises:
downloading metadata based on the data corresponding to the operation information, and inquiring the project item corresponding to the keyword according to the project name and the project item in the keyword;
querying the project entities in the project item items consistent with the project entities in the keywords;
and calling the project entity and downloading.
6. The method according to any one of claims 1-3, further comprising:
acquiring log behavior record data in a preset time period, wherein the log behavior record data is used for recording behavior data corresponding to corresponding operations executed by a user for importing engineering material information or aiming at the pre-imported engineering material information;
analyzing the log behavior record data, and determining the engineering data with the operation times larger than a preset value in the preset time period.
7. An engineering data management system, comprising:
the system comprises an acquisition module, a display module and a display module, wherein the acquisition module is used for acquiring operation request information of pre-imported engineering material information, the operation request information comprises a keyword, an engineering professional classification and operation information used for indicating a user to carry out on the pre-imported engineering material information, the keyword at least comprises an engineering name, the engineering professional classification is each node forming the whole life cycle in the engineering project construction process, and the nodes comprise a survey node, a design node, a construction node, an environment node and a third-party monitoring node;
the type determining module is used for determining the metadata type corresponding to the engineering professional classification and the metadata type corresponding to the operation request information;
the data source determining module is used for determining the metadata source corresponding to the engineering professional classification based on the metadata type corresponding to the engineering professional classification and a pre-established metadata base, wherein the pre-established metadata base comprises the metadata source corresponding to the pre-imported engineering data information;
the calling module is used for calling the engineering data in the metadata source and converting the engineering data into corresponding project entities;
the item determining module is used for determining the project item corresponding to each project entity in the project entities based on the corresponding relation between the project entities and the project items established in advance;
and the operation module is used for executing corresponding operations according to the metadata type corresponding to the operation information, the keywords and the project item and determining an operation result corresponding to the operation information.
8. The system of claim 7, further comprising:
the analysis module is used for acquiring and analyzing the information of the engineering data to be imported, and acquiring engineering professional classification and engineering item classification, wherein the engineering professional classification comprises all project entities forming the engineering project data, and the engineering item classification comprises engineering project items determined based on the engineering project classification;
the first establishing module is used for establishing the one-to-one corresponding relation between each project entity and the project item;
the conversion module is used for determining the metadata types corresponding to the project entities and converting the project entities into the engineering data corresponding to the metadata types;
the second establishing module is used for establishing a metadata source corresponding to the engineering data information to be imported based on the metadata type and the engineering data corresponding to the metadata type;
and the third establishing module is used for establishing a metadata database according to the acquired metadata source.
9. The system of claim 7,
the data source determining module is specifically configured to, if the metadata type corresponding to the engineering professional classification is any node in an engineering project, obtain a metadata source corresponding to the node in a pre-established metadata database, and determine that the metadata source is the metadata source corresponding to the engineering professional classification.
10. The system according to any one of claims 7-9,
the operation module is specifically configured to, if the metadata type corresponding to the operation information is data query metadata, query, based on the data query metadata corresponding to the operation information and the project names and the project entries in the keywords, the project entries corresponding to the keywords, and query and determine, as an operation result, the project entities in the project entries that are consistent with the project entities in the keywords;
or, the operation module is specifically configured to query an engineering project entry corresponding to the keyword based on the data download metadata corresponding to the operation information, and the engineering name and the project entry in the keyword, query the project entity in the engineering project entry that is consistent with the project entity in the keyword, and call the project entity and download.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811626411.6A CN109670796B (en) | 2018-12-28 | 2018-12-28 | Engineering data management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811626411.6A CN109670796B (en) | 2018-12-28 | 2018-12-28 | Engineering data management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109670796A CN109670796A (en) | 2019-04-23 |
| CN109670796B true CN109670796B (en) | 2023-03-14 |
Family
ID=66147473
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811626411.6A Active CN109670796B (en) | 2018-12-28 | 2018-12-28 | Engineering data management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109670796B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101196900A (en) * | 2007-12-27 | 2008-06-11 | 中国移动通信集团湖北有限公司 | Information searching method based on metadata |
| CN104881751A (en) * | 2015-06-04 | 2015-09-02 | 北京建工土木工程有限公司 | System and method for construction material management based on building information model |
| CN107193859A (en) * | 2017-03-29 | 2017-09-22 | 广州地铁设计研究院有限公司 | A kind of data management method and data supervision system |
| CN107423886A (en) * | 2017-06-29 | 2017-12-01 | 中国建筑局（集团）有限公司 | Engineering data management by synchronization system and management method based on Track Table |
| CN108121825A (en) * | 2018-01-15 | 2018-06-05 | 霍亮 | Topographic data manages system |
-
2018
- 2018-12-28 CN CN201811626411.6A patent/CN109670796B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101196900A (en) * | 2007-12-27 | 2008-06-11 | 中国移动通信集团湖北有限公司 | Information searching method based on metadata |
| CN104881751A (en) * | 2015-06-04 | 2015-09-02 | 北京建工土木工程有限公司 | System and method for construction material management based on building information model |
| CN107193859A (en) * | 2017-03-29 | 2017-09-22 | 广州地铁设计研究院有限公司 | A kind of data management method and data supervision system |
| CN107423886A (en) * | 2017-06-29 | 2017-12-01 | 中国建筑局（集团）有限公司 | Engineering data management by synchronization system and management method based on Track Table |
| CN108121825A (en) * | 2018-01-15 | 2018-06-05 | 霍亮 | Topographic data manages system |
Non-Patent Citations (1)
| Title |
|---|
| 测绘生产资料管理系统的设计与实现;解丽等;《地理信息世界》;20160425;第23卷(第02期);第125-130页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109670796A (en) | 2019-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11106626B2 (en) | Managing changes to one or more files via linked mapping records | |
| US10255377B2 (en) | Taxonomy driven site navigation | |
| CN100468394C (en) | Computer search with correlation | |
| US9037579B2 (en) | Generating dynamic hierarchical facets from business intelligence artifacts | |
| RU2674313C2 (en) | Populating user contact entries | |
| US9305176B2 (en) | Database generation from a spreadsheet | |
| US11526769B2 (en) | Encoding knowledge graph entries with searchable geotemporal values for evaluating transitive geotemporal proximity of entity mentions | |
| US20130085987A1 (en) | Downloading method and device | |
| CN102760058B (en) | Massive software project sharing method oriented to large-scale collaborative development | |
| CN109522480A (en) | A kind of information recommendation method, device, electronic equipment and storage medium | |
| CN104361042A (en) | Information retrieval method and device | |
| CN107729483B (en) | Classification display method, classification display device, terminal and computer-readable storage medium | |
| KR20060044524A (en) | Business application entity subscription synch operation management | |
| CN109815232B (en) | Method and system for retrieving and processing data ranking by using binary search tree | |
| CN110928903B (en) | Data extraction method and device, equipment and storage medium | |
| CN105760380A (en) | Database query method, device and system | |
| CN110020063A (en) | Method for vertical search and system | |
| CN110704524A (en) | House source recording method, device and equipment and computer readable storage medium | |
| CN111414410A (en) | Data processing method, device, equipment and storage medium | |
| CN103488525A (en) | Determination of user preference relevant to scene | |
| KR20120034383A (en) | Automatic map update system and method thereof | |
| US11216894B2 (en) | Image-based semantic accommodation search | |
| CN109670796B (en) | Engineering data management method and system | |
| CN101566987A (en) | Secondary information source database system and source processing method thereof | |
| CN103853437A (en) | Candidate item obtaining method and device |
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 |