Hierarchical label management method and system based on SpringBoot

Abstract

The invention relates to the technical field of databases, in particular to a hierarchical label management method and system based on SpringBoot, and the method comprises the steps: obtaining label configuration generation information input by a user, and generating a corresponding cache key value according to the label configuration generation information; analyzing the tag configuration generation information to add corresponding tag configuration information; updating the cache key value according to the newly added label configuration information; and when a label editing instruction input by a user is obtained, searching the corresponding hierarchical label in the label configuration information according to the cache key value, and executing the corresponding label editing instruction. In order to solve the problem that the processing efficiency of a label management system is reduced when the number of labels is large, Redis cache is introduced, in the process of generating label configuration and editing label data every time, corresponding cache key values are constructed for storage, and when the corresponding labels are queried, the corresponding cache key values are stored, so that the processing efficiency of the label management system is improved. And the corresponding label information can be directly queried and processed according to the cache key value, so that the processing efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of databases, and particularly relates to a hierarchical label management method and system based on Spring Boot. Background Art

[0002] With the rapid development of Internet technology, web applications have been widely used in various fields. In many business scenarios, such as content management systems, product classification management of e-commerce platforms, knowledge management systems, etc., it is necessary to effectively classify and label a large amount of data for quick retrieval, screening, and analysis. As an important classification and organization method, hierarchical label management can clearly present the hierarchical structure relationship of data and improve the efficiency and accuracy of data management. Hierarchical labels are usually a series of labels configured according to a tree structure, and the associated storage of labels is achieved by establishing the corresponding superior-subordinate relationship for each label.

[0003] For example, Chinese Patent CN202310828504.1 discloses a method, device, equipment, and medium for constructing and querying hierarchical labels. The hierarchical label construction method includes: obtaining at least two label words in the description data of the object to be processed; constructing at least one candidate multi-level label that meets the hierarchical requirements according to each label word, where the hierarchical requirements include the hierarchical quantity requirements; determining the label association degree of different label words under the same candidate multi-level label in the description data; and selecting the target multi-level label from each candidate multi-level label according to the label association degree corresponding to each candidate multi-level label. The above solution improves the accuracy of the determined target multi-level label, ensures that there is a close connection between the label words in the target multi-level label, facilitates accurate focusing on different objects to be processed based on the target multi-level label, and improves the accuracy of the query results for data query based on the target multi-level label.

[0004] For another example, Chinese Patent CN202010494685.5 discloses a method and device for generating a label hierarchical structure, including: screening out label pairs with an associated relationship according to the occurrence times of each label in each file object; generating a label relationship graph according to each label pair, where the nodes in the relationship graph are labels and the weight of the edge is the co-occurrence times of the two labels in the same file object; clustering each node in the label relationship graph and calculating the membership degree of adjacent nodes to generate a label hierarchical structure. This implementation can solve the technical problem of the unique position of labels in the label hierarchical structure.

[0005] However, during the actual implementation process, the inventor found that in such technical solutions, as the number of hierarchical tags increases, the total number of tag trees, the number of levels of the tag trees, and the number of parallel tags at the same level also increase, which leads to the problem that it is relatively difficult to search for and maintain specific tags. Summary of the Invention

[0006] In view of the above problems existing in the prior art, a hierarchical tag management method based on Spring Boot is provided herein;

[0007] On the other hand, a hierarchical tag management system for implementing this method is also provided.

[0008] The specific technical solutions are as follows:

[0009] A hierarchical tag management method based on Spring Boot includes:

[0010] Step S1: Obtain the tag configuration generation information input by the user, and generate a corresponding cache key value according to the tag configuration generation information;

[0011] Step S2: Parse the tag configuration generation information to add corresponding tag configuration information;

[0012] Step S3: Update the cache key value according to the newly added tag configuration information;

[0013] Step S4: When obtaining the tag editing instruction input by the user, search for the corresponding hierarchical tag in the tag configuration information according to the cache key value and execute the corresponding tag editing instruction.

[0014] On the other hand, a user editing process is also included before step S1;

[0015] The user editing process includes:

[0016] Step A1: Generate user information according to the user creation instruction input by the user;

[0017] Step A2: Add permission group information to the user information, and configure corresponding page permissions and tag operation permissions;

[0018] The page permissions are used to provide corresponding interaction pages and interaction controls;

[0019] The tag operation permissions are used to control the tag editing instructions that can be input.

[0020] On the other hand, in step S4, when obtaining the tag editing instruction, first perform verification according to the tag operation permissions to determine whether to respond to the tag editing instruction.

[0021] On the other hand, the step S1 includes:

[0022] Step S11: Obtain the label configuration generation information, and parse the label identification code from the label configuration generation information;

[0023] Step S12: Calculate the current cache key value parameter according to the label identification code;

[0024] Step S13: Determine whether there is a matching cache key value for the current cache key value parameter;

[0025] If so, update the label configuration information corresponding to the matched cache key value;

[0026] If not, use the current cache key value parameter as the cache key value.

[0027] On the other hand, the step S2 includes:

[0028] Step S21: Parse the parent node information and the top-level node information from the label generation information respectively;

[0029] Step S22: Create a label tree according to the top-level node information, and then add the corresponding parent node information and construct the hierarchical relationship according to the label tree in advance to form the label configuration information.

[0030] On the other hand, in the step S22, the method for creating the label tree includes:

[0031] Create a top-level node according to the top-level node information included in the label generation information, and then create an empty set as the label tree according to the label generation information.

[0032] On the other hand, when the label editing instruction is to add a label, the step S4 includes:

[0033] Step A41: Parse the label content and the associated parent node information from the label editing instruction;

[0034] Step A42: Add the label content according to the parent node information, calculate the cache key value corresponding to the label content and then store it;

[0035] Step A43: Update the label tree according to the label content.

[0036] On the other hand, when the label editing instruction is to delete a label, the step S4 includes:

[0037] Step B41: Parse the identifier of the corresponding hierarchical label from the label editing instruction;

[0038] Step B42: Calculate the corresponding cache key value according to the identifier;

[0039] Step B43: Search for the corresponding hierarchical label according to the cache key value and delete it;

[0040] Step B44: Update the label tree.

[0041] On the other hand, when the label editing instruction is to update the label, the step S4 includes:

[0042] Step C41: Parse the identifier of the corresponding hierarchical label from the label editing instruction;

[0043] Step C42: Calculate the corresponding cache key value according to the identifier;

[0044] Step C43: Search for the corresponding hierarchical label according to the cache key value and update the label content;

[0045] Step C44: Update the label tree.

[0046] A hierarchical label management method based on SpringBoot for implementing the above hierarchical label management method, including:

[0047] A key value calculation module, which obtains the label configuration generation information input by the user and generates the corresponding cache key value according to the label configuration generation information;

[0048] A configuration generation module, which is connected to the key value calculation module;

[0049] The configuration generation module parses the label configuration generation information to add the corresponding label configuration information;

[0050] A key value update module, which is connected to the label generation module;

[0051] The key value update module updates the cache key value according to the newly added hierarchical label;

[0052] A label editing module, which is connected to the key value update module;

[0053] When the label editing module obtains the label editing instruction input by the user, it searches for the corresponding hierarchical label according to the cache key value and executes the corresponding label editing instruction.

[0054] The above technical solution has the following advantages or beneficial effects:

[0055] In view of the problem that the processing efficiency of the existing label management system decreases when the number of labels is large, in this solution, Redis cache is introduced into the label management system. During the process of generating label configurations and editing label data each time, corresponding cache key-values are constructed and saved. Then, when querying the corresponding labels, the corresponding label information can be directly queried and processed according to the cache key-values, improving the processing efficiency. Brief Description of the Drawings

[0056] Referring to the accompanying drawings, the embodiments of the present invention will be described more fully. However, the accompanying drawings are only for illustration and explanation, and do not constitute a limitation to the scope of the present invention.

[0057] Figure 1 It is a schematic diagram of the whole of the embodiment of the present invention;

[0058] Figure 2 It is a schematic diagram of the user editing process in the embodiment of the present invention;

[0059] Figure 3 It is a schematic diagram of step S1 in the embodiment of the present invention;

[0060] Figure 4 It is a schematic diagram of step S2 in the embodiment of the present invention;

[0061] Figure 5 It is a schematic diagram of step A4 in the embodiment of the present invention;

[0062] Figure 6 It is a schematic diagram of step B4 in the embodiment of the present invention;

[0063] Figure 7 It is a schematic diagram of step C4 in the embodiment of the present invention;

[0064] Figure 8 It is a schematic diagram of the system in the embodiment of the present invention. Detailed Embodiments

[0065] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without making creative efforts belong to the scope of protection of the present invention.

[0066] It should be noted that, without conflict, the embodiments in the present invention and the features in the embodiments can be combined with each other.

[0067] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but it is not intended to limit the present invention.

[0068] The present invention includes:

[0069] A hierarchical label management method based on Spring Boot, as Figure 1 shown, includes:

[0070] Step S1: Obtain the label configuration generation information input by the user, and generate the corresponding cache key value according to the label configuration generation information;

[0071] Step S2: Parse the label configuration generation information to add the corresponding label configuration information;

[0072] Step S3: Update the cache key value according to the newly added label configuration information;

[0073] Step S4: When obtaining the label editing instruction input by the user, search for the corresponding hierarchical label in the label configuration information according to the cache key value and execute the corresponding label editing instruction.

[0074] Specifically, aiming at the problem that the processing efficiency of the label management system in the prior art decreases when the number of labels is large, Redis cache is introduced into the label management system in this solution. During the process of generating label configuration and editing label data each time, the corresponding cache key value is constructed and saved. Then, when querying the corresponding label, the corresponding label information can be directly queried according to the cache key value and processed, improving the processing efficiency.

[0075] Specifically, before constructing the hierarchical label, it is first necessary to define the label configuration information corresponding to the hierarchical label. Among them, the label configuration information is the configuration data structure for hierarchical label data, and the configuration data type is in JSON form. Each key represents the unique code identifier of the configuration data item, and the value corresponding to the key is the specific meaning of the code identifier. The main configuration items are: label unique identifier field, label name field, parent label identifier field, top-level node information, label description, creation time, update time, and other configuration data structure fields related to its own business.

[0076] Then, according to the constructed label configuration information above, when creating the corresponding label, the label data can be parsed and stored according to the defined configuration data structure, and during the subsequent editing process, operations such as data screening, classification, and integration can be performed according to the hierarchical relationship of the labels and various configuration attributes, and the label data result in the corresponding format can be directly generated and output according to the requirements.

[0077] Meanwhile, considering the problem that the retrieval efficiency will be affected when the number of hierarchical tags increases, a Redis cache middleware is introduced to store the tag configuration data and tag data. According to the tag configuration data structure, corresponding data structures are designed, including tag configuration data and tag data. Redis is used to store the tag configuration data and tag data: for the tag configuration data, the unique identifier of the tag configuration is used as the key of the Hash, and the corresponding value is the specific configuration content of the list; for the tag data, the unique identifier of the tag is used as the key of the Hash, and the corresponding value is a hash table containing the information of the corresponding tag configuration items.

[0078] Based on the above settings, when constructing the tag configuration information, first calculate the generated information of the tag configuration to obtain the corresponding cache key value as the identifier, and then perform relevant search processes based on this cache key value. Define the data structure of the hierarchical tags through the tag configuration information, and on this basis, perform operations such as tag tree construction, addition and editing of hierarchical tags.

[0079] In one embodiment, a user editing process is further included before step S1;

[0080] As Figure 2 shown, the user editing process includes:

[0081] Step A1: Generate user information according to the user creation instruction input by the user;

[0082] Step A2: Add permission group information to the user information and configure the corresponding page permissions and tag operation permissions;

[0083] The page permissions are used to provide the corresponding interaction pages and interaction controls;

[0084] The tag operation permissions are used to control the tag editing instructions that can be input.

[0085] Then in step S4, when obtaining the tag editing instruction, first verify it according to the tag operation permissions to determine whether to respond to the tag editing instruction.

[0086] Specifically, to achieve a better multi-user collaboration effect, in this embodiment, the concepts of user roles and permission groups are introduced. Different permission groups are configured according to the business requirements of multiple different users when using the database, and then different permission sets are assigned to each permission group and permission group user. The permission groups include operation permissions such as creation, query, update, and deletion of tags at all levels.

[0087] Before performing any tag operations, verify the user's permissions. By setting up a permission verification middleware in the backend code, intercept the user's operation requests. Based on the type of the user's operation requests, determine whether the user has the corresponding permissions. Only after the permission verification passes is the corresponding operation allowed to be executed.

[0088] Among them, the permission group information includes page permissions in addition to the above-mentioned tag operation permissions. Page permissions are used to verify the user account when the user logs in to the system to determine whether the corresponding front-end pages and controls can be provided for the user to access and operate.

[0089] Taking the operation of adding tag configurations as an example, this operation may include the following operations in actual applications:

[0090] First, perform system initialization, set the super administrator account and password. The super administrator has all the permissions of this system;

[0091] The super administrator adds, deletes, modifies, and associates permission groups and users in the permission groups.

[0092] Before the user enters the specific target page, first judge whether the user is logged in;

[0093] If not logged in, then jump to the login page and carry the jump path target page to the login page;

[0094] Judge whether the currently logged-in user has the target page permissions. If there are permissions, then jump to the target page; otherwise, jump to the page without permissions.

[0095] If already logged in or logged in successfully, enter the target page.

[0096] First, perform an operation to query the page data within the permissions of the currently logged-in user. If there is no data, then the page presents an empty data page; correspondingly, if the target page is the tag configuration page, then query the tag configuration data within the permissions of the current user; correspondingly, if the target page is the tag page, then query the tag data within the permissions of the current user;

[0097] Secondly, judge whether the user has the permission to add a button; correspondingly, if the target page is the tag configuration page, then judge whether the currently logged-in user has the permission to add tag configurations; correspondingly, if the target page is the tag page, then judge whether the currently logged-in user has the permission to add tags;

[0098] If the user has the permission to configure new labels, when clicking the button for configuring new labels, a pop-up window for configuring new labels will be displayed on the page. The form in the pop-up window for configuring new labels includes and more than includes label_setting_code (unique identifier for label configuration), label_setting_name (name of label configuration), label_setting_desc (description of label configuration), id (field name for unique identifier of the label), pid (field name for unique identifier of the parent label of the label), root_id (value of the unique identifier of the top-level label of the label), and label_field_list (configuration of other fields of the label).

[0099] After the user fills out the form in the pop-up window for configuring new labels, if they confirm to add, they click the OK button in the form of the pop-up window for configuring new labels. If they cancel the addition, the pop-up window for configuring new labels will be closed and the addition of new label configuration ends.

[0100] If the user confirms to click the button for adding new label configuration, first the client performs preliminary form verification, such as whether the unique identifier for label configuration, the name of label configuration, etc. are all filled out and comply with the filling rules. If the client verification passes, an interface for adding new label configuration will be sent to the backend.

[0101] When the interface for adding new label configuration receives the request data, it first verifies whether the currently logged-in user has the permission to add new label configuration. If not, an error message "No permission" will be prompted. If so, the subsequent steps will be executed.

[0102] In other embodiments, it may be necessary to configure the user permission group first. The process in this embodiment includes:

[0103] The super administrator enters the permission group or the user interface of the permission group, authorizes the label configuration for the TESTGROUP group or authorizes the label configuration for the TEST user, so that the TEST user has the permission to access the label configuration page and add new label configurations. The key for constructing the permission group is ELEMENT_PERMISSION_USERGROUP_TESTGROUP, and the value content is

[0104] ELEMENT_CODE auth label_setting_page 1 add_setting_label 0 label_page 1 add_label 1

[0105] The key for constructing the user of the permission group is ELEMENT_PERMISSION_USER_TEST, and the value content is

[0106] ELEMENT_CODE auth label_setting_page 0 add_setting_label 1 label_page 1 add_label 1

[0107] The authorization explanations for the TESTGROUP permission group and the user TEST within the group for the resources label_setting_page and add_setting_label are as follows: TESTGROUP has the permission for label_setting_page, but does not have the permission for add_setting_label; the user TEST has the permission for add_setting_label, but does not have the permission for label_setting_page. According to the OR operation of the authorization of the permission group and its users within the group for the same resource, the user TEST under the TESTGROUP permission group will finally have the permissions for label_setting_page and add_setting_label.

[0108] In one embodiment, as Figure 3 shown, step S1 includes:

[0109] Step S11: Obtain label configuration generation information, and parse the label identification code from the label configuration generation information;

[0110] Step S12: Calculate the current cache key value parameter according to the label identification code;

[0111] Step S13: Determine whether there is a matching cache key value for the current cache key value parameter;

[0112] If so, update the label configuration information corresponding to the matched cache key value;

[0113] If not, use the current cache key value parameter as the cache key value.

[0114] Specifically, to achieve the effective generation of label configuration, in this embodiment, after receiving the label configuration generation information, first parse the label identification code from the label configuration generation information.

[0115] Among them, the label configuration generation information usually includes:

[0116]

[0117] Then, the cache key value can be constructed according to the label identification code. The specific construction method includes: LABEL_SETTING_${label_setting['label_setting_code']}, which is LABEL_SETTING_blog in the example data.

[0118] Then, search in the cache middleware to determine whether there is a matching cache key value for the current cache key value parameter. Usually, this part of the data does not exist. If a match is found, it indicates that the user's instruction may be incorrect, and it needs to be converted into an instruction to modify the label configuration information.

[0119] In one embodiment, as Figure 4 shown, step S2 includes:

[0120] Step S21: Parse the parent node information and the top-level node information from the label generation information respectively;

[0121] Step S22: Create a label tree according to the top-level node information, and then add the corresponding parent node information and construct the hierarchical relationship in advance according to the label tree to form the label configuration information.

[0122] The method for creating the label tree includes:

[0123] Create a top-level node according to the top-level node information included in the label generation information, and then create an empty set as the label tree according to the label generation information.

[0124] Specifically, to achieve a better label establishment effect, in this embodiment, first parse the parent node information and the top-level node information from the label generation information respectively, and then initialize the top-level node data, including judging whether there is a key LABEL_CHILD_IDS_${label_setting_code}_${root_id} constructed in Redis according to the label configuration's label_setting_code. In the example data of blog, judge whether LABEL_CHILD_IDS_blog_0 exists in Redis. If it does not exist, save the set data with the key LABEL_CHILD_IDS_blog_0 and the value being empty to Redis, which indicates that there are no nodes in the top level of the label configured currently.

[0125] Then, create a label tree according to the top-level node information, including judging whether the content with the key LABEL_CHILD_IDS_${label_setting['label_setting_code']}_${label[label_setting['pid']]} has been constructed in Reids according to the value of the label_setting_code in the request data. If it does not exist, construct the above key with an empty set object content, which means that the child nodes of the current node are empty. If the above key already exists, add the value corresponding to the current request data id to the child node set. Add the parent node information that needs to be added in the current new addition process through the above process.

[0126] In addition, it is also necessary to update the label configuration information and add new cache key values.

[0127] In one embodiment, when the label editing instruction is to add a new label, as Figure 5 shown, step S4 includes:

[0128] Step A41: Parse the label content and the associated parent node information from the label editing instruction;

[0129] Step A42: Add the label content according to the parent node information, calculate the cache key value corresponding to the label content and store it;

[0130] Step A43: Update the label tree according to the label content.

[0131] Specifically, to implement the update process of the label, in this embodiment, first parse the label content and the associated parent node information from the label editing instruction.

[0132] Among them, for the parent node information, the corresponding cache key value can be calculated and searched to determine the associated parent node, the corresponding label tree, and the level on the label tree.

[0133] Subsequently, fill in the label content, for example:

[0134]

[0135] The id is the label unique identifier field specified by the id field in the label configuration item with the label_setting_code of blog, the pid is the label parent unique identifier field specified by the pid field in the label configuration item of blog, the name is the label name field specified by the label field in the label configuration item of blog, and the label_setting_code is an inherent field of the label data, representing the reference of its label configuration.

[0136] Then, calculate the cache key corresponding to the tag content for subsequent lookup. Finally, reconstruct the hierarchical relationship of the tag tree, including:

[0137] Based on the value of label_setting_code in the request data, determine whether the content with key LABEL_CHILD_IDS_${label_setting['label_setting_code']}

[0138] _${label[label_setting['pid']]} exists in Redis. In the example data, the key construction result is LABEL_CHILD_IDS_blog_0. If the constructed key already exists, put the value with id 100000 of the current tag tree into the set corresponding to the key. If it does not exist, construct an empty set corresponding to the key. It is worth mentioning that for the root_id of the blog tag configuration in the example data itself being 0, when initializing the top-level tag bytes after creating the tag, at least the set corresponding to its key is empty.

[0139] In one embodiment, when the tag editing instruction is to delete a tag, as Figure 6 shown, step S4 includes:

[0140] Step B41: Parse the identifier of the corresponding hierarchical tag from the tag editing instruction;

[0141] Step B42: Calculate the corresponding cache key based on the identifier;

[0142] Step B43: Search for the corresponding hierarchical tag according to the cache key and delete it;

[0143] Step B44: Update the tag tree.

[0144] Specifically, to implement the tag deletion process, in this embodiment, first parse the identifier of the corresponding hierarchical tag from the tag editing instruction, then calculate the corresponding cache key based on this identifier, then search for the corresponding hierarchical tag according to the cache key and delete it, so as to achieve a faster search process. Finally, update the hierarchical relationship of the tag tree.

[0145] In one embodiment, when the tag editing instruction is to update a tag, as Figure 7 shown, step S4 includes:

[0146] Step C41: Parse the identifier of the corresponding hierarchical tag from the tag editing instruction;

[0147] Step C42: Calculate the corresponding cache key based on the identifier;

[0148] Step C43: Search for the corresponding hierarchical label according to the cache key value and update the label content;

[0149] Step C44: Update the label tree.

[0150] Specifically, to achieve a better update effect, in this embodiment, first, the identifier of the corresponding hierarchical label is parsed from the label editing instruction, then the corresponding cache key value is calculated according to the identifier, and the corresponding hierarchical label is searched according to the cache key value and the label content is updated. Finally, the hierarchical relationship of the label tree is updated.

[0151] Specifically, when it is necessary to update the basic attributes of a label (such as label name, description, etc.), first, the record to be updated is located according to the key of the label's Hash, and then the update operation is executed. If there is a change in the label hierarchical relationship, for example, moving a label from one parent label to another parent label, it is necessary to update the corresponding record in the label hierarchical relationship at the same time to ensure the accuracy of the hierarchical relationship.

[0152] A hierarchical label management method based on Spring Boot is used to implement the above hierarchical label management method, as Figure 8 shown, including:

[0153] Key value calculation module 1, which obtains the label configuration generation information input by the user and generates the corresponding cache key value according to the label configuration generation information;

[0154] Configuration generation module 2, which is connected to the key value calculation module 1;

[0155] Configuration generation module 2 parses the label configuration generation information to add the corresponding label configuration information;

[0156] Key value update module 3, which is connected to the configuration generation module 2;

[0157] The key value update module updates the cache key value according to the newly added hierarchical label;

[0158] Label editing module 4, which is connected to the key value update module 3;

[0159] When the label editing module 4 obtains the label editing instruction input by the user, it searches for the corresponding hierarchical label according to the cache key value and executes the corresponding label editing instruction.

[0160] The above are only the preferred embodiments of the present invention, and thus do not limit the implementation manners and protection scope of the present invention. For those skilled in the art, it should be realized that all the solutions obtained by equivalent substitution and obvious changes made by using the description and illustrations of the present invention should be included within the protection scope of the present invention.

Claims

1. A hierarchical label management method based on SpringBoot, characterized in that, Including: Step S1: Obtain the tag configuration generation information input by the user, and generate a corresponding cache key value according to the tag configuration generation information; Step S2: Parse the tag configuration generation information to add corresponding tag configuration information; Step S3: Update the cache key value according to the newly added tag configuration information; Step S4: When obtaining the tag editing instruction input by the user, search for the corresponding hierarchical tag in the tag configuration information according to the cache key value and execute the corresponding tag editing instruction.

2. The hierarchical label management method according to claim 1, wherein Before the step S1, it further includes a user editing process; The user editing process includes: Step A1: Generate user information according to the user creation instruction input by the user; Step A2: Add permission group information to the user information, and configure corresponding page permissions and tag operation permissions; The page permissions are used to provide corresponding interactive pages and interactive controls; The tag operation permissions are used to control the tag editing instructions that can be input.

3. The hierarchical label management method according to claim 2, wherein In the step S4, when obtaining the tag editing instruction, first verify it according to the tag operation permissions to determine whether to respond to the tag editing instruction.

4. The hierarchical label management method according to claim 1, characterized in that The step S1 includes: Step S11: Obtain the tag configuration generation information, and parse the tag identification code from the tag configuration generation information; Step S12: Calculate the current cache key value parameter according to the tag identification code; Step S13: Determine whether there is a matching cache key value for the current cache key value parameter; If so, update the tag configuration information corresponding to the matched cache key value; If not, use the current cache key value parameter as the cache key value.

5. The hierarchical label management method according to claim 1, characterized in that The step S2 includes: Step S21: Parse the parent node information and the top-level node information from the tag generation information respectively; Step S22: Create a tag tree according to the top-level node information, and then add the corresponding parent node information to the tag tree in advance and construct a hierarchical relationship to form the tag configuration information.

6. The hierarchical label management method according to claim 5, wherein In the step S22, the method for creating the tag tree includes: Create a top-level node according to the top-level node information included in the tag generation information, and then create an empty set as the tag tree according to the tag generation information.

7. The hierarchical label management method according to claim 5, wherein When the tag editing instruction is to add a tag, the step S4 includes: Step A41: Parse the tag content and the associated parent node information from the tag editing instruction; Step A42: Add the tag content according to the parent node information, and calculate the cache key value corresponding to the tag content and then store it; 8. The hierarchical label management method according to claim 5, characterized in that, Step A43: Update the tag tree according to the tag content. When the tag editing instruction is to delete a tag, the step S4 includes: Step B41: Parse the identifier of the corresponding hierarchical tag from the tag editing instruction; Step B42: Calculate the corresponding cache key value according to the identifier; Step B43: Search for the corresponding hierarchical tag according to the cache key value and delete it; Step B44: Update the tag tree.

9. The hierarchical label management method according to claim 5, wherein, When the label editing instruction is to update the label, step S4 includes: Step C41: Parse the identifier of the corresponding hierarchical label from the label editing instruction; Step C42: Calculate the corresponding cache key value according to the identifier; Step C43: Search for the corresponding hierarchical label according to the cache key value and update the label content; Step C44: Update the label tree.

10. A hierarchical label management method based on Spring Boot, characterized in that, A device for implementing the hierarchical label management method according to any one of claims 1-9, comprising: A key value calculation module, which obtains label configuration generation information input by a user and generates a corresponding cache key value according to the label configuration generation information; A configuration generation module, which is connected to the key value calculation module; The configuration generation module parses the label configuration generation information to add corresponding label configuration information; A key value update module, which is connected to the configuration generation module; The key value update module updates the cache key value according to the newly added hierarchical label; A label editing module, which is connected to the key value update module; When the label editing module obtains a label editing instruction input by a user, it searches for the corresponding hierarchical label according to the cache key value and executes the corresponding label editing instruction.

Images