Data management system supporting user-defined enterprise label storage and retrieval

Abstract

The invention belongs to the technical field of enterprise attribute data management, and particularly relates to a data management system supporting custom enterprise label storage and retrieval, comprising: a custom enterprise label generation module for receiving related information of a custom label input by a user and generating an enterprise label based on the related information of the label; the enterprise and label association module associates the defined enterprise label with a specific enterprise to generate association information, and sets a corresponding label value; the enterprise label data synchronization module is used for synchronizing the associated information to a cache queue of a distributed search engine; the custom label storage module is used for effectively storing custom enterprise labels and label values of the custom enterprise labels into a distributed search engine; and the user-defined label query module is used for receiving a query request initiated by a user, triggering a distributed search engine to perform query processing based on the query request and returning a query result. The average query time consumption of the custom enterprise label is shortened, and the query efficiency is greatly improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of enterprise attribute data management, and in particular relates to a data management system that supports storage and retrieval of custom enterprise tags. Background Art

[0002] In enterprise attribute data management, the traditional data management model mainly relies on fixed attribute architectures, which usually include common fields such as enterprise name, unified credit code, location, and contact number. This fixed attribute architecture met the basic needs of most enterprises in the past. However, with the changes in the market environment and the diversification and personalization of new user needs, the traditional fixed attribute architecture has gradually revealed its limitations.

[0003] New users often need to record some specific enterprise information, such as industry characteristics, market preferences, etc., based on their own business characteristics and needs. The requirements for these custom fields change frequently and unpredictably, and the traditional fixed attribute architecture cannot flexibly adapt to these changes. In order to meet these diverse needs, enterprises usually need to rely on frequent custom development to expand database attributes, which undoubtedly reduces development efficiency.

[0004] In addition, in relational databases, when users need to perform fuzzy queries on custom enterprise tags, full table scans are often triggered. As the amount of enterprise data continues to grow, when the data scale reaches tens of millions, the query efficiency problem caused by full table scans becomes more and more prominent. According to the performance of existing technologies, the average query time may be as long as 60 seconds, which seriously affects the real-time performance of data queries and user experience. Summary of the invention

[0005] In order to solve the problem that the fixed attribute architecture in traditional enterprise attribute data management cannot flexibly adapt to the diverse user needs, the present invention provides a data management system that supports storage and retrieval of custom enterprise tags.

[0006] The technical solution of the present invention provides a data management system that supports storage and retrieval of custom enterprise tags. The system is provided with a distributed search engine. The system includes a custom enterprise tag generation module, an enterprise and tag association module, an enterprise tag data synchronization module, a custom tag storage module and a custom tag query module. A custom enterprise tag generation module receives the relevant information of the custom tag input by the user and generates an enterprise tag based on the relevant information of the tag; The enterprise and tag association module associates the defined enterprise tag with the specific enterprise to generate association information and set the corresponding tag value; The enterprise tag data synchronization module synchronizes the associated information to the cache queue of the distributed search engine; Custom tag storage module, which effectively stores custom enterprise tags and their tag values ​​in the distributed search engine; The custom tag query module receives the query request initiated by the user, triggers the distributed search engine to perform query processing based on the query request, and returns the query result.

[0007] As a further limitation of the technical solution of the present invention, the custom enterprise label generation module includes a first receiving unit, a first verification unit and a label generation unit; A first receiving unit receives relevant information of a custom enterprise label input by a user; the relevant information includes a label name, a label code, a label type, and a label description; The first verification unit verifies the input format of the user input information and verifies the uniqueness of the tag name; The tag generation unit generates a unique tag ID based on the tag's related information after verification and inserts a record into the dictionary table.

[0008] By allowing users to customize tags, the system is able to more flexibly adapt to the data management needs of different enterprises. This helps enterprises better organize and classify data, and improve the efficiency and accuracy of data management. By verifying the uniqueness of tag names, the system is able to avoid data redundancy and confusion. This ensures that each tag is unique in the system, thereby improving the consistency and reliability of data. The generated unique tag ID makes data retrieval more efficient and accurate. Users can quickly find related data by entering a tag ID or tag name, thereby improving the efficiency of data retrieval and user experience.

[0009] As a further limitation of the technical solution of the present invention, the first verification unit checks whether the input format of the user input information complies with the character length limit and special character limit requirements.

[0010] As a further limitation of the technical solution of the present invention, the enterprise and label association module includes a second receiving unit, a second verification unit and an association unit; The second receiving unit receives the specific value of the tag input by the user after selecting the target enterprise and the corresponding custom tag; The second verification unit verifies the input format of the user input information and the value of the user input tag; The association unit inserts a record into the enterprise tag table based on the enterprise tag ID, tag code and tag value.

[0011] By allowing users to select tags and enter specific values ​​for specific companies, the system can record and manage corporate data more accurately. This helps companies better understand and utilize their data resources. Through the combination of tags and tag values, the system can display corporate data in a more intuitive and easy-to-understand way. This helps internal personnel and external partners of the company get the required information faster. By storing the associated information of tags and tag values ​​in the company tag table, the system can support more complex data query and analysis operations. This helps companies discover hidden patterns, trends, and associations in the data, so as to make more informed decisions.

[0012] As a further limitation of the technical solution of the present invention, the enterprise tag data synchronization module includes a queue creation unit and a message sending unit; The queue creation unit creates custom enterprise tag switches and queues, and binds the switches to the queues; The message sending unit specifies the switch to be sent and sends the newly added label operation message and the associated enterprise and label operation message to the corresponding queue.

[0013] Synchronizing tag data through a message queue system ensures that data is reliably transmitted and processed between multiple systems or components. The persistence mechanism of the message queue ensures that data is not lost even in the event of a system failure. At the same time, the asynchronous processing characteristics of the message queue can improve the efficiency of data synchronization and reduce system response time. The enterprise tag data synchronization module can support complex data synchronization logic, such as customized message routing rules based on business needs, filtering and conversion of messages, etc. This enables the system to flexibly adapt to different business scenarios and data synchronization needs.

[0014] As a further limitation of the technical solution of the present invention, the queue creation unit defines a name constant of the enterprise tag switch, specifies the switch name, and sets it as persistent storage, defines a queue name constant, creates a corresponding queue, defines a routing key constant for the new tag operation, and binds the switch to the queue; The message sending unit specifies the switch name constant to be sent, the routing key constant of the new operation, the enterprise ID, and the label code, and sends the message to the queue of the label addition operation.

[0015] Through the cooperation of the queue creation unit and the message sending unit, the enterprise tag data can be reliably transmitted and processed between multiple systems or components. The persistent storage switches and queues can ensure that the data will not be lost after the message queue system is restarted, thereby improving the reliability of data synchronization. At the same time, by defining clear routing keys and binding rules, it can ensure that the message is correctly routed to the specified queue, thereby improving the accuracy of data synchronization.

[0016] As a further limitation of the technical solution of the present invention, the custom tag storage module includes an associated information capture unit and a storage processing unit; The associated information capture unit receives messages of operations of adding new tags and messages of operations of associating enterprises with tags in real time; The storage processing unit, after receiving a message of a new tag operation, obtains the enterprise ID and tag code in the message, and stores the tag code as a new field in the enterprise information index; after receiving a related message of an enterprise tag value, obtains the enterprise ID, tag code and tag value in the message, matches the enterprise document in the search engine according to the enterprise ID, locates the corresponding field according to the tag code, and sets the value of the field to a new tag value for storage.

[0017] The custom tag storage module allows enterprises to add custom tags to data as needed, thereby improving the flexibility and scalability of data management. Enterprises can add different tags to data according to different business needs to better classify, search and analyze data.

[0018] The associated information capture unit can receive and process messages of new tag operations and enterprise-tag association operations in real time, thus ensuring real-time data updates. This means that when data changes, tag information will also be updated immediately, ensuring data accuracy and consistency.

[0019] As a further limitation of the technical solution of the present invention, the system is also equipped with a message listener, and the associated information capture unit configures the routing key constant of the new label operation for the message listener and binds it to the new label operation queue; when a new custom enterprise label is added, the relevant operation message is received in real time through the message listener; by specifying the routing key constant of the associated enterprise and label operation for the message listener, the associated enterprise and label operation queue are bound, and the message of the enterprise and label associated operation is received.

[0020] As a further limitation of the technical solution of the present invention, when the storage processing unit stores a new field, the ik_smart word segmenter is used to effectively segment the Chinese text, and the distributed search engine establishes an inverted index based on the word segmentation results generated by the word segmenter, and maps each word segmentation with the document in which it appears; When the storage processing unit stores label values, it uses the ik_smart tokenizer to segment the original text of the label value into individual words, creates an inverted index for each word, and converts continuous character sequences into individual terms that can be indexed and queried.

[0021] As a further limitation of the technical solution of the present invention, the custom tag query module receives a query request initiated by a user, parses the query conditions input by the user, and converts the parsed query conditions into a query syntax that can be understood by a distributed search engine; submits the converted query syntax to the distributed search engine; the distributed search engine quickly locates corporate documents related to the user input tag through an inverted index; and calculates the sorting results through word segmentation technology and relevance scores, and returns the results to the user in order of relevance.

[0022] It can be seen from the above technical solutions that the present invention has the following advantages: By supporting custom enterprise tags, the system enables enterprises to flexibly label data according to their own needs, thereby improving the flexibility and accuracy of data management. With the help of the efficient indexing and retrieval capabilities of the distributed search engine, the system can realize rapid retrieval of custom enterprise tags, improving the efficiency and accuracy of data retrieval. Through automated and intelligent data management processes, the system reduces the cost of enterprise data management and improves the operational efficiency of the enterprise. The redundant storage and fault-tolerant mechanism of the distributed search engine ensures the security and reliability of enterprise data. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0024] Figure 1 is a schematic block diagram of a system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0026] like Figure 1 As shown, an embodiment of the present invention provides a data management system that supports storage and retrieval of custom enterprise tags. The system is provided with a distributed search engine. The system includes a custom enterprise tag generation module, an enterprise and tag association module, an enterprise tag data synchronization module, a custom tag storage module, and a custom tag query module; A custom enterprise tag generation module receives the relevant information of the custom tag input by the user and generates an enterprise tag based on the relevant information of the tag; The enterprise and tag association module associates the defined enterprise tag with the specific enterprise to generate association information and set the corresponding tag value; The enterprise tag data synchronization module synchronizes the associated information to the cache queue of the distributed search engine; Custom tag storage module, which effectively stores custom enterprise tags and their tag values ​​in the distributed search engine; The custom tag query module receives the query request initiated by the user, triggers the distributed search engine to perform query processing based on the query request, and returns the query result.

[0027] The user inputs the relevant information of the custom tag, such as tag name, description, etc., through the custom enterprise tag generation module. The system generates enterprise tags based on this information and stores them in the tag library. The enterprise and tag association module associates the generated enterprise tags with specific enterprises, generates association information, and sets the corresponding tag values. These association information and tag values ​​will be used for subsequent retrieval and query. The enterprise tag data synchronization module synchronizes the association information to the cache queue of the distributed search engine. The distributed search engine will index this information for subsequent fast retrieval. The custom tag storage module effectively stores the custom enterprise tags and their tag values ​​in the distributed search engine. These tags and tag values ​​will be used as search keywords for subsequent query operations. The user initiates a query request through the custom tag query module and enters the query conditions (such as tag name, tag value, etc.). The system triggers the distributed search engine to perform query processing based on these query conditions and returns the query results. The query results will be displayed to the user for further analysis and use.

[0028] It should be noted that the tag name is the unique identifier of the tag, which is used to reference it in the system. The tag code is usually a short and unique string or number combination for quick identification. The tag type is used to define the category or purpose of the tag, such as customer attributes, product characteristics, marketing activities, etc. The tag description is a detailed explanation of the tag, explaining its meaning and purpose. When generating tags, a template is generally designed to record this basic information to ensure that each tag follows the same format. The template can be a spreadsheet or database table, and the specific information of each tag is filled in according to the template. Make sure that each tag has a unique name and code, and the description is clear and accurate. When generating tags, you need to pay attention to ensure that the name and code of each tag are unique in the system to avoid confusion. Follow unified naming and coding rules to maintain the consistency of tags. Make sure that the tag description is clear and accurate, and can accurately reflect the meaning and purpose of the tag. Consider future extensibility when designing the tag system so that new tag types or attributes can be added as needed.

[0029] In some embodiments, the custom enterprise label generation module includes a first receiving unit, a first verification unit, and a label generation unit; A first receiving unit receives relevant information of a custom enterprise label input by a user; the relevant information includes a label name, a label code, a label type, and a label description; The first verification unit verifies the input format of the user input information and verifies the uniqueness of the tag name; The tag generation unit generates a unique tag ID based on the tag's related information after verification and inserts a record into the dictionary table.

[0030] When a user needs to create a custom enterprise tag, he / she will input the relevant information of the tag through a user interface (such as a web form, a mobile application interface, etc.). The first receiving unit is responsible for capturing and receiving the information input by the user, which includes but is not limited to the tag name, tag code, tag type (such as a classification tag, an attribute tag, etc.), and tag description (used to explain the purpose or meaning of the tag).

[0031] After receiving the information input by the user, the first verification unit first checks whether the input format of the information meets the system requirements. For example, the tag name may only contain letters and numbers, and the tag encoding may need to follow specific format rules. Next, the first verification unit verifies the uniqueness of the tag name. This usually involves querying a dictionary table in the database to ensure that no other tags use the same name. If a duplicate name is detected, the system prompts the user to enter a different name.

[0032] If the information entered by the user passes all verifications, the label generation unit will generate a unique label ID based on this information. This ID can be an automatically incremented number, a UUID (universally unique identifier), or other identifier that can ensure uniqueness. Then, the label generation unit will insert a new record in the dictionary table, which contains information such as label ID, label name, label code, label type, label description, etc. This record will be used for subsequent operations such as enterprise and label association, label data synchronization, and label query.

[0033] Since labels are user-defined, the system can continuously expand and update the label system as the enterprise grows and changes. This helps enterprises maintain the timeliness and accuracy of data and provides strong support for data analysis and decision-making.

[0034] Specifically, the first verification unit checks whether the input format of the user input information complies with the character length limit and special character limit requirements.

[0035] In the first verification unit, checking the input format of the user input information is a crucial step, which includes checking the character length limit and special character limit. The following are the specific checking methods: First, the system needs to define the minimum and maximum character lengths for each input information (such as tag name, tag description, etc.). These rules should be set based on actual business needs to ensure data accuracy and readability. The system needs to define which characters are allowed and which characters are special characters and are not allowed. This is usually set based on factors such as business needs, data readability, and security.

[0036] When the user submits input information, the first verification unit captures this information. For each piece of information, the verification unit checks whether its character length falls within the defined range. If the character length does not meet the requirements (i.e. less than the minimum value or greater than the maximum value), the verification unit will return an error message to prompt the user to adjust the input.

[0037] When the user submits the input information, the first verification unit checks the information character by character. For each character in each message, the verification unit checks whether it belongs to the defined allowed character set. If special characters (i.e. characters that are not in the allowed character set) are found, the verification unit returns an error message, prompting the user to remove these characters.

[0038] The character length limit and special character limit are usually checked at the same time. The verification unit checks each piece of information entered by the user according to the defined rules to ensure that all requirements are met.

[0039] If the validation fails, the validation unit will generate a clear and specific error message to tell the user which input information does not meet the requirements and give modification suggestions. The system should provide a user-friendly interface so that users can easily view error messages and modify input information according to the suggestions. By limiting the input of special characters, the system can reduce the risk of security vulnerabilities such as SQL injection. Before storing the information entered by the user in the database, the system should perform further data cleaning to ensure the integrity and security of the data.

[0040] In some embodiments, the enterprise and tag association module includes a second receiving unit, a second verification unit, and an association unit; The second receiving unit receives the specific value of the tag input by the user after selecting the target enterprise and the corresponding custom tag; The second verification unit verifies the input format of the user input information and the value of the user input tag; The association unit inserts a record into the enterprise tag table based on the enterprise tag ID, tag code and tag value.

[0041] The user first selects the target enterprise through a user interface (such as a web form, backend management system, etc.), and then selects the tag to be associated from a list of predefined custom tags. After selecting the tag, the user will enter the specific value of the tag for the selected enterprise. This value can be text, numbers, dates, or other data types, depending on the definition of the tag and the needs of the enterprise. The second receiving unit is responsible for receiving the tag value entered by the user and associating it with the selected enterprise and tag. After receiving the tag value entered by the user, the second verification unit first checks whether the format of the input information meets the system requirements. This may include checking the character length, data type (such as ensuring that the date value meets a specific date format), etc. In addition, the second verification unit will also perform business logic verification on the tag value. For example, if the tag represents the inventory quantity, the verification unit will ensure that the input value is a non-negative integer. If the input information does not meet the format requirements or the business logic verification fails, the verification unit will return an error message and prompt the user to re-enter.

[0042] If the tag value entered by the user passes all validations, the association unit will insert a new record into the enterprise tag table based on the enterprise ID (or unique identifier of the enterprise name), tag ID (or tag code), and tag value. This record will contain enough information to uniquely identify the relationship between the enterprise, tag, and tag value. It may also contain other metadata, such as creation time, creator, etc. After inserting the record, the association unit will update the relevant index or cache to ensure that subsequent data retrieval operations can be performed efficiently.

[0043] Since the association between tags and tag values ​​is established dynamically, the system can flexibly update data as the enterprise grows and changes. This helps enterprises maintain the timeliness and accuracy of data while reducing the cost of data management.

[0044] In some embodiments, the enterprise tag data synchronization module includes a queue creation unit and a message sending unit; The queue creation unit creates custom enterprise tag switches and queues, and binds the switches to the queues; The message sending unit specifies the switch to be sent and sends the newly added label operation message and the associated enterprise and label operation message to the corresponding queue.

[0045] The queue creation unit is first responsible for creating a custom enterprise tag switch in the message queue system. This switch will serve as a transit station for message delivery, used to receive and distribute messages from different sources. The switch creation process usually involves specifying the name of the switch, the type (such as direct exchange, topic exchange, etc.) and other possible configuration parameters.

[0046] Next, the queue creation unit needs to create one or more queues to store messages of a specific type. These queues will be named and configured according to business requirements to ensure that messages can be received and processed correctly. After the switch and queues are created, the queue creation unit needs to bind them. This process involves specifying routing rules between switches and queues to ensure that messages sent to switches can be distributed to the correct queues according to the predetermined rules.

[0047] When a new tag operation or an associated enterprise and tag operation occurs, the message sending unit needs to first specify the switch to which the message is to be sent. This usually involves selecting a custom enterprise tag switch that was created previously. Next, the message sending unit needs to construct a message containing the operation information. These messages usually include the type of operation (such as adding a new tag, associating an enterprise and a tag, etc.), identifiers of related entities (such as enterprise ID, tag ID, etc.), and other possible metadata (such as operation time, operator, etc.). After completing the construction of the message, the message sending unit sends the message to the previously specified switch. According to the routing rules between the switch and the queue, the message will be distributed to the correct queue for processing.

[0048] Synchronizing tag data through a message queue system can make the system easier to expand and maintain. New data sources or data targets can be easily integrated into the existing message queue system without major modifications to the existing system architecture. As middleware, the message queue system can reduce the coupling between different systems. This allows the system to be developed and deployed more independently, improving the flexibility and reusability of the system.

[0049] In some embodiments, the queue creation unit defines a name constant of an enterprise tag switch, specifies a switch name, and sets it to persistent storage, defines a queue name constant, creates a corresponding queue, defines a routing key constant for a new tag operation, and binds the switch to the queue; The message sending unit specifies the switch name constant to be sent, the routing key constant of the new operation, the enterprise ID, and the label code, and sends the message to the queue of the label addition operation.

[0050] In the queue creation unit, a constant needs to be defined to represent the name of the enterprise tag switch. This constant is usually a string, which is used to reference in the subsequent process of creating switches and binding queues. Next, use the defined switch name constant to create a switch in the message queue system. During the creation process, you need to specify the type of switch as a type suitable for enterprise tag management (such as direct exchange, topic exchange, etc.), and set the switch to persistent storage. Persistent storage ensures that the switch still exists after the message queue system is restarted and the binding information in it is not lost. Similarly, a constant needs to be defined to represent the name of the queue. Then, create a queue corresponding to the constant name in the message queue system. The queue creation process usually involves specifying the persistence attributes, exclusive attributes, etc. of the queue. For enterprise tag management, the queue is usually set to persistent to ensure that the queue still exists after the message queue system is restarted. In order to correctly route the message to the specified queue, a routing key constant needs to be defined to represent the operation of adding a tag. This routing key will be used to specify the routing rules of the message when sending the message. Finally, use the defined switch name constant, queue name constant, and routing key constant to bind the switch to the queue. The binding process involves specifying routing rules, i.e. when a message is sent to an exchange, if the routing key of the message matches the specified routing key, the message will be routed to the specified queue.

[0051] In the message sending unit, you first need to specify the switch name constant to which the message is to be sent. This constant should be consistent with the switch name constant defined in the queue creation unit. Next, specify the routing key constant for the new operation. This constant should be consistent with the routing key constant for the new tag operation defined in the queue creation unit. Then, prepare the message content to be sent, including the enterprise ID and tag code. The enterprise ID is used to uniquely identify an enterprise, while the tag code is used to uniquely identify a tag. These two fields will be sent to the queue as part of the message. Finally, use the API or client library of the message queue system to send the prepared message to the specified switch and routing key. According to the routing rules set previously, the message will be routed to the queue corresponding to the new tag operation for processing.

[0052] The design of the queue creation unit and the message sending unit enables the system to support flexible data processing logic. By defining different routing keys and binding rules, different message routing and processing strategies can be easily implemented. This enables the system to flexibly adapt to different business scenarios and data processing requirements.

[0053] Synchronizing enterprise tag data through a message queue system can make the system easier to expand and maintain. New data sources or data targets can be easily integrated into the existing message queue system without major modifications to the existing system architecture. In addition, message queue systems usually provide a wealth of monitoring and management tools, allowing system administrators to easily monitor and manage the data synchronization process, thereby improving the maintainability of the system.

[0054] In some embodiments, the custom tag storage module includes an associated information capture unit and a storage processing unit; The associated information capture unit receives messages of new tag operations and enterprise-tag associated operations in real time. The system also sets up a message listener. The associated information capture unit configures the routing key constant of the new tag operation for the message listener and binds it to the new tag operation queue. When a new custom enterprise tag is added, the message listener receives the relevant operation message in real time. The message listener specifies the routing key constant of the associated enterprise and tag operation for the message listener, binds the associated enterprise and tag operation queue, and receives messages of the enterprise-tag associated operation. This ensures that the system can capture and process the associated information between the enterprise and the custom tag in a timely manner.

[0055] After receiving the message of adding a new tag operation, the storage processing unit must first reasonably define the storage structure of the enterprise tag, obtain the enterprise ID and tag code in the message, and store the tag code as a new field in the enterprise information index; this new field represents the identifier of the custom enterprise tag, which is convenient for identification in subsequent queries. The data type of this field is defined as text type. After receiving the relevant message of the enterprise tag value, the system will further process this data and store it in the search engine. Get the enterprise ID, tag code and tag value in the message, match it to the enterprise document in the search engine according to the enterprise ID, locate the corresponding field according to the tag code, and set the value of the field to the new tag value for storage.

[0056] Specifically, when the storage processing unit stores new fields, it uses the ik_smart word segmenter to effectively segment the Chinese text into appropriate words. The distributed search engine creates an inverted index based on the word segmentation results generated by the word segmenter, and maps each word with the document in which it appears. This significantly improves the speed and ability of subsequent search engines to respond to query requests.

[0057] When the storage processing unit stores the tag value, it uses the ik_smart tokenizer to segment the original text of the tag value into individual words, and creates an inverted index for each word, converting the continuous character sequence into a single term that can be indexed and queried. This ensures that the system can provide efficient and accurate retrieval functions when processing Chinese text.

[0058] The associated information capture unit needs to monitor and receive new tag operation messages and enterprise-tag associated operation messages from message queues (such as RabbitMQ, Kafka, etc.) or event buses in real time. These messages are usually generated and sent by other systems or modules when related operations occur.

[0059] After receiving the message, the associated information capture unit needs to parse the message and extract the key information in the message. For the message of adding a tag operation, the enterprise ID and tag code need to be extracted; for the message of the enterprise and tag association operation, the enterprise ID, tag code and tag value need to be extracted. When the storage processing unit receives the message of adding a tag operation, it first creates a new field for the tag code in the enterprise information index according to the enterprise ID and tag code in the message. This field will be used to store data related to the tag. If the enterprise information index has not been created, the storage processing unit needs to create the index first. When the storage processing unit receives the message related to the enterprise tag value, it first finds the corresponding enterprise document in the search engine (such as Elasticsearch, Solr, etc.) according to the enterprise ID in the message. Then, locate the corresponding field in the document according to the tag code. If the field does not exist (that is, this is the first time to set a value for the tag code), create the field; if the field already exists, update the value of the field to the new tag value. After completing the creation or update of the field, the storage processing unit will store the updated enterprise document back to the search engine to ensure the latest status of the data.

[0060] By storing the tag code as a field in the enterprise information index and using a search engine to store and retrieve data, the performance of data search and query can be significantly improved. Search engines usually have efficient indexing and query mechanisms that can quickly locate the required data, thereby improving the efficiency of data processing.

[0061] In some embodiments, the custom tag query module receives a query request initiated by a user, parses the query conditions input by the user, converts the parsed query conditions into a query syntax that the distributed search engine can understand; submits the converted query syntax to the distributed search engine; the distributed search engine quickly locates corporate documents related to the user input tag through an inverted index; and calculates the sorting results through word segmentation technology and relevance scores, and returns the results to the user in order of relevance.

[0062] You need to be clear about the type of distributed search engine you are using (such as Elasticsearch, Solr, etc.) and be familiar with its query syntax and construction rules. Different search engines may have different query languages ​​and data structures, so the conversion process needs to be performed for specific search engines. Based on the parsed query conditions, start building a query statement that the distributed search engine can understand. This step usually includes the following sub-steps: Map the fields in the query conditions to the corresponding fields in the search engine. For example, if the query condition contains the "title" field, it needs to be mapped to the "title" field in the search engine. Convert the query conditions into a format that the search engine can understand. For example, convert the equal condition into a "term" query, convert the range condition into a "range" query, and convert the fuzzy query into a "match" or "wildcard" query. If the query condition contains multiple sub-conditions, you need to use Boolean queries (such as AND, OR, NOT) to combine these sub-conditions to form a compound query statement.

[0063] Check whether the query statement complies with the search engine's syntax rules to avoid syntax errors. Test the query statement to verify whether it can correctly return the expected result set. This can be achieved by manually executing the query statement in the search engine and checking the results. Optimize the query statement based on the query results and performance. For example, improve query speed and accuracy by adjusting field weights, using indexes, and other strategies.

[0064] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0065] Although the present invention has been described in detail with reference to the accompanying drawings and in combination with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions shall be within the scope of the present invention. Any person of ordinary skill in the art may easily think of changes or substitutions within the technical scope disclosed by the present invention, and these shall be within the scope of protection of the present invention.

Claims

1. A data management system that supports storage and retrieval of custom enterprise tags, characterized in that: The system is provided with a distributed search engine, which includes a custom enterprise tag generation module, an enterprise and tag association module, an enterprise tag data synchronization module, a custom tag storage module and a custom tag query module; A custom enterprise tag generation module receives the relevant information of the custom tag input by the user and generates an enterprise tag based on the relevant information of the tag; The enterprise and tag association module associates the defined enterprise tag with the specific enterprise to generate association information and set the corresponding tag value; The enterprise tag data synchronization module synchronizes the associated information to the cache queue of the distributed search engine; Custom tag storage module, which effectively stores custom enterprise tags and their tag values ​​in the distributed search engine; The custom tag query module receives the query request initiated by the user, triggers the distributed search engine to perform query processing based on the query request, and returns the query result.

2. The data management system supporting storage and retrieval of customized enterprise tags according to claim 1, characterized in that: The custom enterprise label generation module includes a first receiving unit, a first verification unit and a label generation unit; A first receiving unit receives relevant information of a custom enterprise label input by a user; the relevant information includes a label name, a label code, a label type, and a label description; The first verification unit verifies the input format of the user input information and verifies the uniqueness of the tag name; The tag generation unit generates a unique tag ID based on the tag's related information after verification and inserts a record into the dictionary table.

3. The data management system supporting storage and retrieval of customized enterprise tags according to claim 2, characterized in that: The first verification unit checks whether the input format of the user input information meets the character length limit and special character limit requirements.

4. The data management system supporting storage and retrieval of customized enterprise tags according to claim 3, characterized in that: The enterprise and label association module includes a second receiving unit, a second verification unit and an association unit; The second receiving unit receives the specific value of the tag input by the user after selecting the target enterprise and the corresponding custom tag; The second verification unit verifies the input format of the user input information and the value of the user input tag; The association unit inserts a record into the enterprise tag table based on the enterprise tag ID, tag code and tag value.

5. The data management system supporting storage and retrieval of customized enterprise tags according to claim 4, characterized in that: The enterprise tag data synchronization module includes a queue creation unit and a message sending unit; The queue creation unit creates custom enterprise tag switches and queues, and binds the switches to the queues; The message sending unit specifies the switch to be sent and sends the newly added label operation message and the associated enterprise and label operation message to the corresponding queue.

6. The data management system supporting storage and retrieval of customized enterprise tags according to claim 5, characterized in that: The queue creation unit defines the name constant of the enterprise tag switch, specifies the switch name, and sets it as persistent storage, defines the queue name constant, creates the corresponding queue, defines the routing key constant for the new tag operation, and binds the switch to the queue; The message sending unit specifies the switch name constant to be sent, the routing key constant of the new operation, the enterprise ID, and the label code, and sends the message to the queue of the label addition operation.

7. The data management system supporting storage and retrieval of customized enterprise tags according to claim 6, characterized in that: The custom tag storage module includes an associated information capture unit and a storage processing unit; The associated information capture unit receives messages of operations of adding new tags and messages of operations of associating enterprises with tags in real time; The storage processing unit, after receiving a message of a new tag operation, obtains the enterprise ID and tag code in the message, and stores the tag code as a new field in the enterprise information index; after receiving a related message of an enterprise tag value, obtains the enterprise ID, tag code and tag value in the message, matches the enterprise document in the search engine according to the enterprise ID, locates the corresponding field according to the tag code, and sets the value of the field to a new tag value for storage.

8. The data management system supporting storage and retrieval of customized enterprise tags according to claim 7, characterized in that: The system also sets up a message listener. The associated information capture unit configures the routing key constant of the new tag operation for the message listener and binds it to the new tag operation queue. When a new custom enterprise tag is added, the message listener receives the relevant operation message in real time. By specifying the routing key constant of the enterprise-tag association operation for the message listener, bind the enterprise-tag association operation queue, and receive messages of the enterprise-tag association operation.

9. The data management system supporting storage and retrieval of customized enterprise tags according to claim 8, characterized in that: When the storage processing unit stores new fields, it uses the ik_smart word segmenter to effectively segment the Chinese text. The distributed search engine creates an inverted index based on the word segmentation results generated by the word segmenter, and maps each word segment to the document in which it appears. When the storage processing unit stores label values, it uses the ik_smart tokenizer to segment the original text of the label value into individual words, creates an inverted index for each word, and converts continuous character sequences into individual terms that can be indexed and queried.

10. The data management system supporting storage and retrieval of customized enterprise tags according to claim 9, characterized in that: The custom tag query module receives the query request initiated by the user, parses the query conditions entered by the user, and converts the parsed query conditions into query syntax that the distributed search engine can understand; the converted query syntax is submitted to the distributed search engine; the distributed search engine quickly locates the enterprise documents related to the tags entered by the user through the inverted index; The ranking results are calculated through word segmentation technology and relevance scores, and the results are returned to the user in order of relevance.

Images