CN118410039A - Ancient architecture resource management system based on multisource data - Google Patents

Abstract

The invention discloses an ancient architecture resource management system based on multi-source data, which comprises a data acquisition unit, a data fusion unit, a data storage unit and a retrieval unit; the data acquisition singular element is used for acquiring various ancient architecture digital resources and analyzing the same to obtain corresponding data contents, data subjects and data types; the data fusion unit fuses the data content, the data theme and the data type corresponding to the ancient architecture according to a preset data storage mapping relation to obtain fusion data; meanwhile, constructing a retrieval identifier and generating storage data with corresponding fusion data; the data storage unit is used for storing the storage data obtained by fusion; and the retrieval unit is used for retrieving the data storage unit according to the input retrieval items to obtain the ancient architecture digital resources corresponding to the retrieval items and all relevant ancient architecture digital resources under the corresponding retrieval identifications. The system provided by the invention can be used for rapidly storing data and improving the retrieval efficiency in the retrieval process.

Description

An ancient building resource management system based on multi-source data

Technical Field

The present invention belongs to the technical field of storage data processing, and in particular relates to an ancient building resource management system based on multi-source data.

Background technique

With the rapid development of information technology and the promotion of digital construction, the scale of various application systems has expanded rapidly, and system applications have gradually penetrated into all walks of life. The data generated by them has also shown an exponential growth trend. Data application has also become a key research and application field, especially the processing and application of multi-source data has also received great attention from all walks of life. However, due to the multi-source nature of data, the data format, content and amount of information from each data source are different. How to use effective methods to reasonably coordinate multi-source data and integrate them, fully integrate useful information, and improve the ability to make correct decisions in a changing environment.

Information on ancient buildings generally includes three-dimensional models, videos, pictures, documents, papers, patents and other content. Therefore, there are different types of files, which leads to many problems in the preservation of digital resource data of ancient buildings.

Patent document CN11222190A discloses an ancient building management system, which includes a processing module, a management interface, a data module, an information resource module, and an information collection module; the management interface is used to obtain management instructions for ancient building objects, and output the processing results of the processing module for the management instructions; the processing module is used to obtain the to-be-processed data of the management instructions from the data module and/or the information resource module, and perform the operation corresponding to the management instructions based on the to-be-processed data to obtain the processing results; the information collection module is used to collect the data of the ancient building objects, and transmit the collected data of the ancient building objects to the data module and/or the information resource module. This method directly stores and uses the ancient building data, but does not take into account that the data actually includes not only text data of the same format, but also image data and audio data.

Patent document CN114756548A discloses an ancient building digitization system based on BIM technology, which includes a user management module, an ancient building digitization collection module, an ancient building digitization application display module, an ancient building digitization management module and an ancient building information model database, and the ancient building digitization system based on BIM technology completely integrates the collected data to form a complete information model. The data stored in this method are all original ancient building data, so it may not be possible to quickly feedback related data information in the subsequent retrieval process.

Summary of the invention

In order to solve the above problems, the present invention provides an ancient building resource management system based on multi-source data. When faced with storing data with a large amount of data, a wide range of sources and a variety of data types, the system can quickly store data and increase retrieval efficiency during the retrieval process.

An ancient building resource management system based on multi-source data includes a data acquisition unit, a data fusion unit and a retrieval unit.

The data collection unit is used to collect and analyze various ancient building digital resources to obtain corresponding data content, data subject and data type;

The data fusion unit fuses the data content, data subject and data type corresponding to the ancient building according to a preset data storage mapping relationship to obtain fused data;

At the same time, a retrieval identifier is constructed and stored data is generated with the corresponding fusion data;

The data storage unit is used to store the storage data obtained by fusion;

The retrieval unit searches the data storage unit according to the input retrieval item to obtain the ancient building digital resources corresponding to the retrieval item and all related ancient building digital resources under the corresponding retrieval identifier.

The present invention unifies multiple data types, assigns them an independent search identifier, and expands all data under the search identifier carried by the search results during the search process, thereby reducing the development complexity and multi-source data maintenance during multi-source data storage.

Specifically, the ancient building digital resources include document data, picture data and audio data of the ancient buildings.

Specifically, the storage mapping relationship includes a code, a mapping rule, a request data subject, a mapping relationship generation time, and a mapping relationship update time.

Specifically, the stored data includes structured data, semi-structured data and unstructured data.

Specifically, the structured data includes a custom MySQL data type.

Specifically, the semi-structured data includes XML or/and JSON text data types that can be identified and parsed, and data that can be stored in fields of a relational database CLOB or stored as files in a distributed file system.

Specifically, the unstructured data includes data that can be stored in a distributed file system.

Specifically, the search identifier is constructed based on the serial number and timestamp when the ancient building digital resource is acquired, and the timestamp is selected to be at the 13-bit millisecond level.

Specifically, the following function is used to obtain the timestamp of the ancient building digital resource:

public static long getTimeStamp(){

java.util.Date date=new java.util.Date();

return date.getTime();

}.

Specifically, the search unit performs direct search based on multiple search items, and the multiple search items are connected by search item connectors, and the search item connectors include "and" and "or".

Compared with the prior art, the present invention has the following beneficial effects:

The present invention stores the data content, data subject and data type of the ancient building digital resources after unified processing, and generates a unique search tag based on the stored content, thereby improving the retrieval efficiency of the data in the subsequent retrieval process.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the structure of an ancient building resource management system provided by this embodiment;

FIG2 is a flow chart of generating a unique retrieval identifier for stored data provided by the present embodiment;

FIG. 3 is a schematic diagram of a flow chart of a user searching for ancient building digital resources provided by this embodiment.

Detailed ways

The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application.

As used in this application and the appended claims, the singular forms "a", "an", "said", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

As shown in FIG1 , an ancient building resource management system based on multi-source data includes a data acquisition unit, a data fusion unit, a data storage unit and a retrieval unit.

Furthermore, the data collection unit is used to collect and analyze various ancient architectural digital resources to obtain corresponding data content, data subject and data type.

The data fusion unit fuses the data content, data subject and data type corresponding to the ancient building according to a preset data storage mapping relationship to obtain fused data.

At the same time, a retrieval identifier is constructed and storage data is generated with the corresponding fusion data.

The types of data stored include structured data, semi-structured data, and unstructured data. Structured data includes data with predefined data types, formats, and structures, which can be stored in relational databases, such as MySQL; semi-structured data includes text data files with recognizable patterns and can be parsed, such as XML, JSON, etc., which can be stored in relational database CLOB fields or as files in distributed file systems. This case uses the former solution; unstructured data is data without a fixed structure, usually saved as different types of files, such as text documents, pictures, videos, etc., which can be stored in distributed file systems.

Structured data, taking MySQL as an example, such as cultural relics registration information

Semi-structured data, taking JSON format as an example.

Unstructured data storage, taking hbase to store pictures as an example.

//Store the image

/**

*@param tableName table name;

*@param rowkey row number;

*@param colFamily column family

*@param colName column name;

*@param bs column value, here is the picture;

* @param imgType.

Image type, used when reading images. The column name of the image type is specified as imageType, and imgType here refers to the column value of the column name imageType

*/

public static void storeImage(String tableName,String rowkey,StringcolFamily,String colName,byte[]bs,String imgType)throws IOException{

HTable table=new HTable(configuration,tableName);

java.util.List<Put>puts=new java.util.ArrayList<Put>().

//Store binary image

Put put=new Put(Bytes.toBytes(rowkey));

put.add(Bytes.toBytes(colFamily),Bytes.toBytes(colName),bs).

//Store image type

Put putx=new Put(Bytes.toBytes(rowkey));

putx.add(Bytes.toBytes(colFamily),Bytes.toBytes("imageType"),Bytes.toBytes(imgType)).

puts.add(put);

puts.add(putx);

//put.a

//table.put(put);

table.put(puts);

table.close();}.

As shown in Figure 2, the process of generating the unique retrieval identifier of stored data is as follows:

Get the data information of the requested data storage: including the subject of the requested data, the storage type corresponding to the requested data, and the data storage area identifier.

Get the serial number when requesting data storage. When requesting data storage to the storage medium corresponding to the pre-stored data type, a corresponding serial number will be generated (generated in an incremental manner).

Get the timestamp when the data storage is requested. The timestamp when the data storage is requested can be obtained through the following function to obtain the current 13-digit millisecond timestamp:

public static long getTimeStamp(){

java.util.Date date=new java.util.Date();

return date.getTime();}.

Through the preset retrieval identifier generation rules, a unique retrieval identifier is generated according to the serial number and timestamp of the stored data. The generation of the retrieval identifier can be used by users to quickly find the stored data information, thereby improving data query efficiency.

Generate a unique search identifier as follows:

The data storage unit is used to store the storage data obtained by fusion.

The retrieval unit searches the data storage unit according to the input retrieval item to obtain the ancient building digital resources corresponding to the retrieval item and all related ancient building digital resources under the corresponding retrieval identifier.

As shown in Figure 3, the specific process when a user searches for ancient building digital resources is as follows:

Receive data query request, obtain data query conditions and corresponding retrieval identifier (such as SQL).

According to the search identifier corresponding to the data query request, the data query type corresponding to the data query request is determined. Among them, the data query condition includes multiple query items, and the multiple query items are connected by query item conjunctions, and the query item conjunctions include "and" and "or"; the query item consists of fields, operators and field values.

Utilize the parsing rules corresponding to the data query type to parse the data query conditions and obtain the search results.

The query conditions are parsed using the parsing rules corresponding to the query request type. First, the grammatical correctness of the query request is verified; then, the query conditions are parsed to obtain the fields, field values (or ranges), and operators contained in the query; finally, the query request is converted into the query conditions corresponding to the search engine.

The purpose of the present invention is to provide a method for fusion processing of multi-source data, so that when storing data with a relatively large amount, a relatively wide source, and a relatively diverse data type, it is possible to quickly find a suitable storage medium for efficient storage, and when reading the required data, it is possible to quickly find the storage file and storage location where the data to be read is located from the storage medium, and quickly read the data, thereby reducing the development complexity of multi-source data storage and the cost of multi-source data maintenance and use, which is conducive to improving the research and development efficiency and quality of R&D personnel.

As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments can still be modified, or some of the technical features therein can be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims (9)

1. The historic building resource management system based on the multi-source data is characterized by comprising a data acquisition unit, a data fusion unit, a data storage unit and a retrieval unit;

the data acquisition singular element is used for acquiring various ancient architecture digital resources and analyzing the same to obtain corresponding data contents, data subjects and data types;

The data fusion unit fuses the data content, the data theme and the data type corresponding to the ancient architecture according to a preset data storage mapping relation to obtain fusion data;

meanwhile, constructing a retrieval identifier and generating storage data with corresponding fusion data;

the data storage unit is used for storing the storage data obtained by fusion;

and the retrieval unit retrieves the data storage unit according to the input retrieval items to obtain the ancient architecture digital resources corresponding to the retrieval items and all relevant ancient architecture digital resources under the corresponding retrieval identifications.

2. The multi-source data based historic building resource management system of claim 1, wherein the historic building digital resources comprise historic building literature data, picture data and audio data.

3. The multi-source data based historic building resource management system of claim 1, wherein the storage mapping relationship comprises a code, a mapping rule, a request data theme, a mapping relationship generation time, and a mapping relationship update time.

4. The multi-source data based historic building resource management system of claim 1, wherein the stored data comprises structured data, semi-structured data, and unstructured data.

5. The multi-source data based historian resource management system of claim 4, wherein the structured data comprises custom MySQL data types.

6. The multi-source data based historian resource management system of claim 4, wherein the semi-structured data comprises identifiable and parsed XML or/and JSON text data types, and wherein the fields of the relational database CLOB can be stored or data stored as files in a distributed file system.

7. The multi-source data based historian resource management system of claim 4, wherein the unstructured data comprises data storable in a distributed file system.

8. The multi-source data based historic building resource management system of claim 1, wherein the search identifier is constructed based on a serial number and a time stamp when the historic building digital resource is obtained, wherein the time stamp is selected to be 13-bit millisecond level.

9. The multi-source data based historic building resource management system according to claim 1, wherein the search unit performs direct search according to a plurality of search terms, the plurality of search terms being connected by a search term connection word, the search term connection word including "and", "or".