Methods, systems, computing devices, and storage media for configuring data

Abstract

Embodiments of the present specification relate to a method, system, device and medium for configuring data. The method comprises, in response to detecting a user triggered element data operation request about any scene, providing an element data configuration interface about the operation request to the user to obtain a configuration operation of the user; obtaining information of a target element to which the configuration operation is directed based on the configuration operation performed by the user on the element data configuration interface; determining whether the obtained information of the target element conforms to a configuration rule of element data of the target element; and in response to determining that the obtained information of the target element conforms to the configuration rule of the element data of the target element, generating or updating the element data about the target element; interacting with the user through the configuration interface to obtain the configuration operation and the target element directed thereto, checking the information of the target element based on the configuration rule, and configuring the data in a low-code mode. Thus, compatibility of multi-scene heterogeneous data in a low-cost low-code mode is achieved.

Description

Technical Field

[0001] The embodiments in this specification generally relate to the field of data processing, and more specifically to a method, system, computing device, and storage medium for configuring data. Background Technology

[0002] With the continuous growth of new demands, new systems need to be developed to address these demands. This necessitates the development of data and code corresponding to various elements in new scenarios, enabling the configuration, updating, modification, querying, assembly, rendering, and interaction of data related to the scenarios involved in new projects. The current challenge lies in achieving compatibility with the various element data within new scenario types using a low-cost, low-code approach when facing diverse new scenarios and their corresponding data requirements. Element data refers to the data materials of elements with specific, heterogeneous scenario attributes. A scenario typically includes multiple elements, each corresponding to several related data sets.

[0003] Therefore, a configuration scheme for heterogeneous data in multiple scenarios is needed to achieve compatibility with heterogeneous data in multiple scenarios in a low-cost, low-code mode. Summary of the Invention

[0004] To address the aforementioned issues, this specification provides a method, system, computing device, and storage medium for configuring data, enabling compatibility with heterogeneous data across multiple scenarios in a low-cost, low-code manner.

[0005] According to a first aspect of this specification, a method for configuring data is provided, comprising: in response to detecting a user-triggered element data operation request for any scenario, providing the user with an element data configuration interface for the operation request to obtain the user's configuration operation; based on the configuration operation performed by the user in the element data configuration interface, obtaining information about the target element for which the configuration operation is performed; determining whether the obtained information about the target element conforms to the configuration rules of the element data of the target element; and in response to determining that the obtained information about the target element conforms to the configuration rules of the element data of the target element, generating or updating element data about the target element.

[0006] In some embodiments, the configuration rules for the element data of the target element include at least one of the following: structural rules for the data structure information of the target element; type rules for the data type information of the target element; and usage rules for the target element.

[0007] In some embodiments, the structural rules include one or more of the following: a uniqueness rule for indicating that the defined attribute is exclusive; a non-empty rule for indicating that the value of the defined attribute is non-empty; and an attribute boundary rule for indicating the range of the value of the defined attribute.

[0008] In some embodiments, the rules for using elements include at least one of the following: assembly rules, for indicating the display area where the defined attribute data is displayed; sorting rules, for indicating the order in which the attribute data displayed in the defined display area is arranged; and download rules, for indicating that the defined attribute data must be downloaded before it can be displayed on the query results page in response to a query request.

[0009] In some embodiments, the method for configuring data further includes generating or dividing a display area based on at least one of the following: the type of the scene, the type of the target element, the context related to the target element, the context related to the attribute data, and the operation performed by the user.

[0010] In some embodiments, the information of the target element includes at least one of the following: the data structure of the target element, the type name of the target element, the attribute name of the target element, the attribute value of the target element, the type of the attribute data of the target element, the data assembly rule of the target element, and the data sorting rule of the target element.

[0011] In some embodiments, the data type information includes at least one or more of the following: text, rich text, integer, image, video, and attachment.

[0012] In some embodiments, the method for configuring data further includes: storing the data structure information of the target element in a relational data manner; and storing the data type information and attribute data information of the target element in a non-relational data manner.

[0013] In some embodiments, the method for configuring data further includes: in response to detecting a user-triggered query request for any scenario, determining the keywords contained in the query request; based on the keywords, determining the scenario, element type, and / or element data associated with the query request; and generating a query result page for the query request based on the configuration rules and usage rules of the corresponding element data for the associated scenario, element type, and / or element data.

[0014] In some embodiments, generating a query results page for a query request includes: determining type rules and usage rules corresponding to the query request based on the associated element types; determining the data type of the element data associated with the query request based on the corresponding type rules; determining the display area and assembly order of the element data associated with the query request based on the corresponding usage rules; assembling the query results page for the query request based on the determined data type, display area, and assembly order; and generating the query results page to display the element data included in the associated element types.

[0015] In some embodiments, the method for configuring data further includes: determining a project to be managed based on a first management operation performed by the user on the query results page, wherein the project to be managed is related to a scenario type, a type of element to be managed, and / or data of element to be managed; presenting a management interface to the user regarding the project to be managed based on a second management operation performed by the user on the query results page, so as to obtain a third management operation from the user; and performing a predetermined operation on the element data related to the project to be managed based on the third management operation performed by the user on the management interface.

[0016] In some embodiments, the third management operation includes one or more of the following: adding element data, editing element data, deleting element data, and exporting element data; the predefined operation includes one or more of the following: providing an element data configuration interface, providing an export configuration interface, and providing a deletion configuration interface.

[0017] According to a second aspect of this specification, a system for configuring data is provided, comprising: a configuration operation acquisition module configured to, in response to detecting a user-triggered element data operation request for any scenario, provide the user with an element data configuration interface for the operation request, so as to acquire the user's configuration operation; an element information acquisition module configured to, based on the configuration operation performed by the user in the element data configuration interface, acquire information about the target element targeted by the configuration operation; a configuration rule verification module configured to determine whether the acquired target element information conforms to the configuration rules of the target element's element data; and an element data generation module configured to, in response to determining that the acquired target element information conforms to the configuration rules of the target element's element data, generate or update element data about the target element.

[0018] According to a third aspect of this specification, a computing device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; the memory storing instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method of the first aspect of this specification.

[0019] In a fourth aspect of this specification, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause a computer to perform the method of the first aspect of this specification.

[0020] It should be understood that the descriptions in this section are not intended to identify key or essential features of the embodiments described herein, nor are they intended to limit the scope of this specification. Other features of this specification will become readily apparent from the following description. Attached Figure Description

[0021] The above and other features, advantages, and aspects of the embodiments of this specification will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements.

[0022] Figure 1 A schematic diagram of scenario 100 for implementing a method for configuring data according to an embodiment of the present invention is shown.

[0023] Figure 2 A schematic diagram of the structure of the data configuration system 200 provided in an embodiment of this specification is shown.

[0024] Figure 3 A flowchart of a method 300 for configuring data according to an embodiment of this specification is shown.

[0025] Figure 4 A flowchart of a method 400 for querying element data according to an embodiment of this specification is shown.

[0026] Figure 5 A flowchart of a method 500 for configuring a query results page according to an embodiment of this specification is shown.

[0027] Figure 6 A flowchart of a method 600 for managing element data according to an embodiment of this specification is shown.

[0028] Figure 7 A schematic diagram of an element data configuration interface provided in an embodiment of this specification is shown.

[0029] Figure 8 This diagram illustrates the effect of displaying assembled element data according to an embodiment of this specification.

[0030] Figure 9 This diagram illustrates another element data configuration interface provided in an embodiment of this specification.

[0031] Figure 10 This diagram illustrates an element data query result provided in an embodiment of this specification.

[0032] Figure 11 A schematic diagram illustrating the operation flow of the newly added element provided in the embodiments of this specification is shown.

[0033] Figure 12 A block diagram of an electronic device according to an embodiment of this specification is shown. Detailed Implementation

[0034] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this specification, including various details of these embodiments to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this specification. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0035] The term "comprising" and its variations as used herein signify open inclusion, i.e., "including but not limited to". Unless otherwise stated, the term "or" means "and / or". The term "based on" means "at least partially based on". The terms "one example embodiment" and "one embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0036] As described above, when faced with new demands and corresponding data requirements that vary from one another, traditional data configuration methods, such as configuring, updating, modifying, querying, assembling, rendering, and interacting with data related to new demand scenarios, struggle to be compatible with element data in new scenario types through low-cost, low-code models. For example, data systems that use inherent attributes often find it difficult to be compatible with data materials with targeted heterogeneous attributes in new scenario types in a low-cost, low-code manner, resulting in a longer cycle for carrying new element data and providing services.

[0037] To at least partially address one or more of the aforementioned problems and other potential issues, this specification provides an example embodiment of a scheme for configuring data. In this scheme, by detecting a user-triggered element data operation request for any scenario, an element data configuration interface is provided to the user to obtain the user's configuration operation. Then, based on the configuration operation performed by the user in the element data configuration interface, information about the target element targeted by the configuration operation is obtained. It is determined whether the obtained target element information conforms to the configuration rules of the target element's element data. Subsequently, in response to determining that the obtained target element information conforms to the configuration rules of the target element's element data, element data about the target element is generated or updated. This allows for interaction with the user through a data configuration interface to obtain information about the configuration operation and its target element, and to verify the target element information based on configuration rules, configuring new data in a low-code manner. Therefore, it enables compatibility with heterogeneous data across multiple scenarios in a low-cost, low-code manner.

[0038] Figure 1A schematic diagram of scenario 100 for implementing a method for configuring data according to an embodiment of the present invention is shown. Figure 1 As shown, scenario 100 includes server 110, terminal device 130, and network 140. Server 110 and terminal device 130 can interact via network 140 (e.g., the Internet) to configure corresponding element data 160-160n for multiple scenarios 150-15n. Figure 1 The element data 160-16n in the diagram is just an illustration, and the numbering is not a limitation on the quantity. For example, element data 160 includes all element data corresponding to scene 150.

[0039] Terminal device 130 may include, but is not limited to, at least one of the following: mobile phone, laptop computer, tablet computer, handheld computer, desktop computer, intelligent voice interaction device, and smart home appliance.

[0040] In some embodiments, server 110 can interact with multiple terminal devices 130 via network 140 to configure different element data in multiple different scenarios, and can also configure element data for different users in the same scenario, or configure different types of element data in the same scenario.

[0041] Regarding server 110, it may have one or more processing units, including dedicated processing units such as GPUs, FPGAs, and ASICs, as well as general-purpose processing units such as CPUs. Additionally, one or more virtual machines may run on each server 110.

[0042] Server 110 can also be a cloud service center, which can use a large number of physical servers as a whole through computer cluster software. The cloud service center can deploy the data configuration method and data configuration system provided in the embodiments of this specification.

[0043] In some embodiments, a portion or all of the methods or systems for configuring data provided in the embodiments of this specification can be deployed on both server 110 and terminal device 130. In some embodiments, server 110 can be integrated with certain terminal devices or can be set up separately from each other.

[0044] Figure 2 A schematic diagram of the structure of a data configuration system 200 provided in an embodiment of this specification is shown. In some embodiments, the data configuration system 200 includes, for example, a configuration operation acquisition module 202, an element information acquisition module 204, a configuration rule verification module 206, and an element data generation module 208.

[0045] Regarding the configuration operation acquisition module 202, it is configured to provide the user with an element data configuration interface for the operation request in response to detecting a user-triggered element data operation request for any scenario, so as to acquire the user's configuration operation.

[0046] The element information acquisition module 204 is configured to acquire information about the target element targeted by the configuration operation performed by the user in the element data configuration interface.

[0047] Regarding the configuration rule verification module 206, it is configured to determine whether the information of the acquired target element conforms to the configuration rules of the target element's element data.

[0048] The element data generation module 208 is configured to generate or update element data about the target element in response to determining that the information of the acquired target element conforms to the configuration rules of the element data of the target element.

[0049] The data configuration system provided in the embodiments of this specification can be used to execute the data configuration method provided in the embodiments of this specification. Its implementation principle and technical effects are similar, as detailed below. Figures 3 to 11 The description of the methods for configuring data provided in the embodiments of this specification will not be repeated here.

[0050] Figure 3 A flowchart of a method 300 for configuring data according to an embodiment of this specification is shown. Method 300 may be performed by, for example... Figure 1 The server 110 shown executes method 300, which can be mounted on... Figure 2 The data configuration system 200 shown is implemented through system 200, and can also be used in... Figure 12 The method is performed at the illustrated electronic device 1200. It should be understood that method 300 may also include additional steps not shown and / or the steps shown may be omitted, and the scope of this specification is not limited in this respect.

[0051] Figure 7 A schematic diagram of an element data configuration interface provided in an embodiment of this specification is shown. Figure 8 This diagram illustrates the effect of displaying assembled element data according to an embodiment of this specification. Figure 9 A schematic diagram of another element data configuration interface provided in an embodiment of this specification is shown below. Figure 1-3 and Figure 7-9 The method for configuring data according to embodiments of this specification is further described.

[0052] In step 302, if the server 110 detects a user-triggered element data operation request for any scenario, it provides the user with an element data configuration interface for the operation request in order to obtain the user's configuration operation.

[0053] Regarding element data, it includes, for example, at least data materials with targeted, heterogeneous scene attributes. Please refer to [reference needed]. Figure 7 Elements such as “Ant Forest Data”, “Tree Name”, “Growth Area”, “Tree Image”, “Tree Description”, “Energy Tree” and “Energy Recipients” are all considered element data.

[0054] Please refer to Figure 8 This illustrates a set of element data related to "Magnolia denudata" in the "Ant Forest - Back Mountain Forest Story" scene, showcasing elements such as: "Magnolia denudata" (value of element data "tree name"), "Common in Northern China" (value of element data "growing region"), "In Hangzhou, Magnolia denudata is the earliest blooming magnolia. The petals and sepals of the Magnolia genus are collectively called tepals. Its outer three tepals are degenerate, only about 1-2 cm long" (value of element data "tree description"), and "Magnolia denudata image" (value of element data "tree image"). It should be understood that other element data related to the plant "Magnolia denudata" are not included in this example, according to the assembly rules. Figure 8 The illustrative display shows that, according to predetermined configuration rules, it can be assembled and displayed in the display area of ​​other pages.

[0055] In step 304, server 110 obtains information about the target element targeted by the configuration operation based on the configuration operation performed by the user in the element data configuration interface.

[0056] In some embodiments, the information of the target element includes at least one of the following: the data structure of the target element, the type name of the target element, the attribute name of the target element, the attribute value of the target element, the type of the attribute data of the target element, the data assembly rule of the target element, and the data sorting rule of the target element.

[0057] In some embodiments, the data type information includes at least one or more of the following: text, rich text, integer, image, video, and attachment. Scene developers, maintenance personnel, and users can configure the data type of the target element data according to the actual situation and usage requirements of the scene to select a format that meets the needs of element data management, data assembly, and front-end page display.

[0058] Regarding configuration operations, these include, for example, operations performed by the user on the configuration interface through interactive operations, such as selecting, inputting, modifying, editing, copying, and clicking on various elements in the configuration interface; through these configuration operations, it is possible to achieve, for example, selecting input boxes, defining the type name of the target element, configuring the type attribute of the target element, configuring the data value of the target element, configuring the structural rules of the target element, and configuring the usage rules of the target element, so as to realize the configuration and management of heterogeneous element data for new scenarios and / or multiple scenarios.

[0059] Please refer to Figure 7 and Figure 9 ,exist Figure 7 and Figure 9 In the illustrated configuration interface, users can achieve the following through configuration operations:

[0060] Configuration of element type names, such as Figure 7 "Ant Forest Data"

[0061] Configuration of data names for other elements within a specific element type, such as Figure 7 Other element data names included in the "Ant Forest Data" element type include "Tree Name", "Growth Area", "Tree Description", "Energy Tree", and "Energy Group", as well as their corresponding English names "name", "address", "image", "description", "energy", and "peopleGroup".

[0062] Configuration of element data with different attributes, such as Figure 7 The attributes include full fields, unique fields, required fields, and fields that need to be uploaded. For example, "tree name", "growing area", "tree image", "tree description", "receive energy tree" and "receiver group" are all full fields; among them, "tree name" is a unique field, "tree name", "tree image" and "receive energy tree" are required fields, and "tree image" is a field that needs to be uploaded.

[0063] Configuration of element data values, such as Figure 7 The value of "recipient group" is [11111, 22222]; for example... Figure 7 The value for "tree image" requires the user to click upload. After uploading, a thumbnail of the current image can be previewed; for example... Figure 7 The value of "Growth Region" is "Chengdu"; for example... Figure 7 The value of "Tree Name" is "Haloxylon ammodendron"; for example... Figure 7 The value of "Tree Description" is "The Haloxylon ammodendron is very strong"; for example... Figure 7 The value of "Receive Energy Tree" is "35000".

[0064] In step 306, server 110 determines whether the information of the acquired target element conforms to the configuration rules of the target element's element data.

[0065] Regarding configuration rules, the configuration rules for element data under each element type in each scenario may be different. There are many types of configuration rules for element data. For example, target element A is restricted by a type of element data configuration rule. This type of element data configuration rule includes b specific configuration rules to constrain the various element data of target element A.

[0066] For example, refer to Figure 7-9 The data shown for the various elements of the scenario "Ant Forest" includes elements such as "tree name", "growing area", "tree image", "tree description", "energy tree to receive" and "users to receive". These elements all belong to the element type "Ant Forest data", and the element type "Ant Forest data" belongs to the "Ant Forest" scenario.

[0067] Therefore, the method for configuring data provided in the embodiments of this specification can configure element data for elements required in different scenarios through the use of multiple configuration rules and combinations of multiple configuration rules, so as to meet the compatibility requirements of heterogeneous data in various scenarios.

[0068] In step 308, if the server 110 determines that the information of the acquired target element conforms to the configuration rules of the target element's element data, it generates or updates the element data about the target element.

[0069] The above solution provides an interactive interface to the user, responding to user-executed configuration operations to configure and manage element data, such as adding and configuring new elements, and editing and modifying target elements. Furthermore, it uses pre-set configuration rules to validate the target element's information and configure new data in a low-code manner. This achieves compatibility with heterogeneous data across multiple scenarios in a low-cost, low-code manner.

[0070] In some embodiments, the configuration rules for the element data of the target element include at least one of the following: structural rules for the data structure information of the target element; type rules for the data type information of the target element; and usage rules for the target element.

[0071] Regarding structural rules, in some embodiments, structural rules include one or more of the following: uniqueness rules for indicating that the defined attribute is exclusive; non-empty rules for indicating that the defined attribute value is non-empty; and attribute boundary rules for indicating the range of the defined attribute value.

[0072] Please refer to Figure 7 The element data included in the "unique field" are all subject to the "uniqueness rule". The scope of application of the "uniqueness rule" can also be determined according to the pre-defined rules. The "uniqueness rule" applies to a certain scenario, several scenarios, a certain sub-scenario of a scenario, or a certain type of element. The element data subject to the "uniqueness rule" has exclusive name and / or value within the scope of application of the "uniqueness rule", that is, it is not repeated.

[0073] Please continue to refer to this. Figure 7 For example, "uniqueness rule 1" is applied to the "Ant Forest" scenario. For example, in the "Ant Forest" scenario, the value of "tree name" is exclusive. If the value of the element data "tree name" in target element A is "camphor tree", then the value of the element data "tree name" in target element B cannot be "camphor tree".

[0074] Please refer to Figure 7 All elements in the "required fields" are subject to the "not null rule," meaning that the values ​​of these elements cannot be null. For example, see reference... Figure 7 Under the element type "Ant Forest Data", for any target element to be created, the values ​​of its three element data, "Tree Name", "Tree Image" and "Number of Energy Received", cannot be empty.

[0075] Please refer to Figure 7-9 For example, if the attribute value of the element data "Energy Received" is in the range of "0-n (positive integer)", then the value of this element data cannot be a floating-point number, a negative number, etc.; if the attribute value of the element data "Growth Region" is in the range of "a certain region on Earth", then the value of this element data cannot be a region outside of Earth, such as Mars.

[0076] For example, when it is necessary to manage element data of the same type, multiple groups of elements under the element data type can be displayed in the form of a data table, such as using the column name of the data table as the name of each element data, and the row of the data table corresponding to the value of each element data.

[0077] Figure 10 This diagram illustrates an example of an element data query result provided in an embodiment of this specification. Please refer to... Figure 10 Taking the "Back Mountain Forest Story" element type as an example, if the column names are Element Number, Creation Time, Tree Name, Growing Region, Tree Description, and Energy Received; where Element Number and Tree Name are both subject to uniqueness rules, the values ​​of the element data in these two columns will not be repeated. It should be understood that in this scenario, if the tree names are the same, then these are two identical element data, while different trees can have the same growing region.

[0078] It should be understood that, depending on the data requirements of the scenario, rules other than uniqueness rules, non-empty rules, and attribute boundary rules can also be configured to constrain element data in the target scenario, thereby enabling support for heterogeneous data in multiple scenarios.

[0079] In some embodiments, the rules for using elements include at least one of the following: assembly rules, for indicating the display area where the defined attribute data is displayed; sorting rules, for indicating the order in which the attribute data displayed in the defined display area is arranged; and download rules, for indicating that the defined attribute data must be downloaded before it can be displayed on the query results page in response to a query request.

[0080] Regarding the attribute data of the target element, such as the name of the target element, the value of the target element, and how the attribute data of the target element is presented using rules.

[0081] Regarding usage rules, these rules constrain the expression and presentation of element data on the page. The page here includes configuration pages used by developers, operations personnel, administrators, and users, for example... Figure 7 As shown in Figure 9; it also includes the final scene page displayed to the user, such as... Figure 8 The spatial arrangement of the element data shown.

[0082] Regarding the assembly rules, it is possible to indicate the location of the defined attribute data in the page, such as which page (homepage, a specific page) it is displayed on, and which area within a page it is displayed in (such as top, middle, left, right). The specific area can be predefined.

[0083] Regarding sorting rules, it can indicate the sorting rules (such as front and back, left and right, top and bottom) between the defined attribute data in its defined display area and other attribute data in the same display area.

[0084] In some embodiments, server 110 generates or divides the display area based on at least one of the following: the type of scene, the type of target element, the context related to the target element, the context related to attribute data, and the operation performed by the user.

[0085] Regarding the display areas, such as the homepage, title bar, summary bar, cover image, and content area, they are divided according to the actual needs of each scenario.

[0086] It should be understood that the same element data in the same scene may be presented with different sorting rules and assembly rules in different display areas.

[0087] Therefore, by using a combination of rules, the expression and presentation of element data on the page can be constrained, so that element data can be presented in a variety of ways in the same scene, and different presentation methods can be provided according to different scenes to adapt to heterogeneous data in multiple scenes.

[0088] In some embodiments, server 110 stores the data structure information of the target element in a relational data manner; and stores the data type information and attribute data information of the target element in a non-relational data manner.

[0089] Regarding attribute data information, such as the name, value, and type of element data, for example... Figure 10 For example, elements 0001 and 0002 are of type "Ant Forest Story". The column name of each element type is the attribute name, and the value of each column is the attribute value. For example, the attribute name is "Tree Name" and the attribute value is "European Spruce".

[0090] In some embodiments, relational databases constrain element types and their corresponding rules, such as full attributes and required attributes. Since the element data is actually stored in a non-relational database, the rules such as attribute constraints and null checks that are natively present in relational databases are missing. Therefore, this solution stores the rules in the manner of relational databases to standardize the data content when element attributes are actually changed.

[0091] In some embodiments, a non-relational database stores element data and the values ​​of these element data, supports horizontal expansion of element types, and the element data attributes are not constrained by the data table header. The values ​​corresponding to a certain key in the JSON are stored in JSON format and simultaneously satisfy the conditions for querying.

[0092] Therefore, by using both relational and non-relational data storage methods, the data configuration method provided in the embodiments of this specification can support loose data structures, store complex data structures, and support various types of data structures. This enables low-code updates while being compatible with the storage of heterogeneous data and supporting richer query languages.

[0093] Figure 4 A flowchart of a method 400 for querying element data according to an embodiment of this specification is shown. Method 400 may be derived from, for example... Figure 1 The server 110 shown executes method 400, which can be mounted on... Figure 2 The data configuration system 200 shown is implemented through system 200, and can also be used in... Figure 12 The method is performed at the illustrated electronic device 1200. It should be understood that method 400 may also include additional steps not shown and / or the steps shown may be omitted, and the scope of this specification is not limited in this respect.

[0094] In step 402, if the server 110 detects a query request triggered by the user regarding any scenario, it determines the keywords contained in the query request.

[0095] In step 404, server 110 determines the scenario, element type, and / or element data associated with the query request based on keywords.

[0096] In step 406, server 110 generates a query result page for the query request based on the associated scene, element type and / or element data, and the configuration rules and usage rules of the corresponding element data.

[0097] Keywords can be complete values, names, ID numbers, or parts thereof related to element data.

[0098] For example, uniqueness rules can be used to link element data belonging to the same element type. Please refer to [reference needed]. Figure 10 For example, elements numbered 0001 and 0002 are both of the "Ant Forest Data" element type. Element 0001 has the "Tree Name" attribute value of "European Spruce," while element 0002 has the "Tree Name" attribute value of "Adirondack Spruce." Through uniqueness rules, when a user queries the "Tree Name" attribute, other field information associated with the same "Tree Name" attribute can be accurately presented. For example, if a user searches for "European Spruce," the system will present element data such as the growing region, tree image, and tree description associated with "European Spruce." If a user searches for "Spruce," it may simultaneously display multiple different element data related to spruce. Similarly, if a user searches for "Northeast," the system will present element data for all trees growing in the "Northeast." And if a user searches for "Energy Count," the system will present element data with the same attribute value.

[0099] It should be understood that the above query results can be presented, for example, in the form of a data table. For example, the names of the element data can be presented by the column names of the data table, and the values ​​corresponding to each column can be presented by the rows of the data table. The element data in each row belongs to the same element number. For example, the attributes of the element data in the same row are all related to "European Spruce", and the attributes of the element data in the same row are all related to "Camphor Tree", etc.

[0100] Therefore, the embodiments of the present invention can support the query of heterogeneous element data and can support query in all scenarios.

[0101] Figure 5 A flowchart of a method 500 for configuring a query results page according to an embodiment of this specification is shown. Method 500 may be provided by, for example... Figure 1The server 110 shown executes method 500, which can be mounted on... Figure 2 The data configuration system 200 shown is implemented through system 200, and can also be used in... Figure 12 The method is performed at the illustrated electronic device 1200. It should be understood that method 500 may also include additional steps not shown and / or the steps shown may be omitted, and the scope of this specification is not limited in this respect.

[0102] In step 502, server 110 determines the type rules and usage rules corresponding to the query request based on the associated element type.

[0103] In step 504, server 110 determines the data type of the element data associated with the query request based on the corresponding type rules.

[0104] Regarding data types, such as text, numbers, images, and videos, different data types have their own display formats on the query results page.

[0105] In step 506, server 110 determines the display area and assembly order of the element data associated with the query request based on the corresponding usage rules.

[0106] In step 508, server 110 assembles the query result page for the query request based on the determined data type, display area, and assembly order.

[0107] In step 510, server 110 generates a query results page to display the element data included in the associated element type.

[0108] Therefore, the method for configuring data provided in the embodiments of this specification can display different query results based on different query keywords, and can present these query results in different formats.

[0109] Furthermore, the method for configuring data provided in the embodiments of this specification can also select element data from the query results page to enter the configuration page and complete the re-editing of the element data. The specific implementation is described in detail in method 600.

[0110] Figure 6 A flowchart of a method 600 for managing element data according to an embodiment of this specification is shown. Method 600 may be derived from, for example... Figure 1 The server 110 shown executes method 600, which can be mounted on... Figure 2 The data configuration system 200 shown is implemented through system 200, and can also be used in... Figure 12The method is performed at the illustrated electronic device 1200. It should be understood that method 600 may also include additional steps not shown and / or the steps shown may be omitted, and the scope of this specification is not limited in this respect.

[0111] In step 602, server 110 determines the items to be managed based on the first management operation performed by the user on the query results page. The items to be managed are related to the scene type, the type of element to be managed, and / or the data of the element to be managed.

[0112] In step 604, server 110 presents a management interface for the project to be managed to the user based on the second management operation performed by the user on the query results page, so as to obtain the user's third management operation.

[0113] In some embodiments, the third management operation includes one or more of the following: adding element data, editing element data, deleting element data, and exporting element data.

[0114] In step 606, server 110 performs a predetermined operation on element data related to the project to be managed, based on the third management operation performed by the user in the management interface.

[0115] In some embodiments, the predetermined operation includes one or more of the following: providing an element data configuration interface, providing an export configuration interface, and providing a delete configuration interface.

[0116] For example, please refer to Figure 10 Taking the element type "Ant Forest Story" as an example, searching for the keyword "spruce" yielded... Figure 10 The elements 0001 and 0002 shown in the image can be used to create new element data by clicking "Add" on the query feedback page; any attribute value of element 0001 or element 0002 can be selected for editing, for example, selecting the "Tree Description" attribute of "Element 0002" will modify the attribute value of "Tree Description"; for example, selecting "Element 0001" and selecting delete will delete all attribute values ​​in that row; import operations are also supported, and batch import is also supported.

[0117] Therefore, the data configuration method provided by the embodiments of the present invention can support management operations in the query and display interface of element data, and can provide a configuration interface to users in various scenarios, so as to efficiently realize the configuration and management of element data.

[0118] It should be understood that the above embodiments only illustrate the configuration of element data under the "Ant Forest Data" type. The data configuration method provided in the embodiments of this specification can also be applied to scenarios such as the mini-programs "Back Mountain Forest Story", "Helping the Blind", "Design Charity", "Audiobooks", "Ant Charity Activities", "Love Grocery Store", "Charity Resume", "Incubator Official Website", "Blue Envelope", and "Mental Health Charity Services". Furthermore, it can be applied to other scenarios according to new needs. Developers, operators, and users only need to configure heterogeneous element data in new scenarios based on the data configuration method and / or the data configuration system provided in the embodiments of this specification to achieve low-code and low-cost data updates, data configurations, data management, and other operations to adapt to various needs in new scenarios.

[0119] For ease of understanding, the following references Figure 11 The illustrated process for adding a new element further describes the method for configuring data provided in the embodiments of this specification.

[0120] Step 1102: Define the element type name.

[0121] For example, define the element type name as "Ant Forest Story".

[0122] Step 1104: Configure element type attributes.

[0123] For example, define the attributes that this type of data possesses, such as tree name, growing region, tree image, tree description, number of claimed energy points, and the number of people who claimed the tree.

[0124] Step 1106: Configure uniqueness rules.

[0125] For example, you can define a unique constraint attribute for selected element data (such as "tree name" being subject to a unique rule). If this attribute conflicts with existing element data when adding a new element, the element data will be considered non-standard and will not be persisted to the JSON data table.

[0126] Step 1108: Configure non-emptiness rules.

[0127] For example, define the range of required attributes for this type of element data, which cannot be empty. If the attribute is missing when adding a new element, the element data will be non-standard and will not be persisted to the JSON data table.

[0128] Step 1110: Configure download rules.

[0129] For example, define the range of attributes that need to be downloaded for this type of data (e.g., "tree image" needs to be downloaded). The attributes that need to be downloaded are all file types such as images or videos that can only be previewed after downloading. This type of data is stored in the form of file addresses. When actually querying, it is necessary to determine whether the attribute matches the download rule. If it matches, the method to download the file needs to be triggered, and the original file can be previewed.

[0130] Step 1112: Configure usage rules.

[0131] For example, define the range of attributes that should be returned for this type of data in different scenarios, such as display scenarios, query scenarios, configuration scenarios, etc.; do not return attribute data that is not required in a specific scenario; and define the assembly rules and sorting rules for the returned data in each scenario to determine the final page content.

[0132] Therefore, the method for configuring data provided in the embodiments of this specification fully entrusts the user with the right to design and define element data types, and provides a configuration management platform for element data in a visual manner. It also provides rules including at least element type names, element data attributes, various structural rules, type rules, and usage rules, such as uniqueness rules, non-emptiness rules, attribute boundary rules, download rules, assembly rules, and sorting rules.

[0133] Furthermore, the system fully entrusts users with the rights to the rules for using the returned data (assembly rules and sorting rules, etc.). The system dynamically processes the returned data to accommodate situations where the returned parameters are inconsistent in different contexts (for example, the homepage returns several selected attributes; the details page returns all attributes).

[0134] In addition, in terms of data management, the actual element attribute data is constrained by configuration rules. The management of element data depends on the user's configuration rules for element types, and these rules are implemented by predefined rule configuration. Therefore, this solution will provide the definition of heterogeneous element types in multiple scenarios with zero new code.

[0135] Therefore, it can support full coverage of element data across all scenarios, encompass all data structures, break down scenario boundaries, provide an online and visual platform for data management, and enable the management of multi-scenario element data and related services with zero new code additions.

[0136] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0137] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0138] Figure 12 A schematic step diagram of an example electronic device 1200 that can be used to implement embodiments of the contents of this specification is shown. For example, as Figure 1 The server 110 shown can be implemented by an electronic device 1200. As shown, the electronic device 1200 includes a processing unit (CPU) 1201, which can perform various appropriate actions and processes according to computer program instructions stored in read-only memory (ROM) 1202 or loaded from storage unit 1208 into random access memory (RAM) 1203. The random access memory 1203 may also store various programs and data required for the operation of the electronic device 1200. The processing unit 1201, ROM 1202, and RAM 1203 are interconnected via a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0139] Multiple components in electronic device 1200 are connected to input / output interface 1205, including: input unit 1206, such as keyboard, mouse, microphone, etc.; output unit 1207, such as various types of monitors, speakers, etc.; storage unit 1208, such as disk, optical disk, etc.; and communication unit 1209, such as network card, modem, wireless transceiver, etc. Communication unit 1209 allows device 1200 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0140] The various processes and procedures described above, such as methods 300 to 600, can be executed by processing unit 1201. For example, in some embodiments, methods 300 to 600 may be implemented as computer software programs tangibly contained in a machine-readable medium, such as storage unit 1208. In some embodiments, part or all of the computer program may be loaded and / or installed on device 1200 via read-only memory 1202 and / or communication unit 1209. When the computer program is loaded into random access memory 1203 and executed by processing unit 1201, one or more actions of methods 300 to 600 described above can be performed.

[0141] This specification relates to methods, apparatus, systems, electronic devices, computer-readable storage media, and / or computer program products. A computer program product may include computer-readable program instructions for performing various aspects of this specification.

[0142] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0143] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge computing devices. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to computer-readable storage media within the respective computing / processing device.

[0144] The computer program instructions used to perform the operations described herein may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is customized by utilizing the status information of the computer-readable program instructions to execute the computer-readable program instructions, thereby implementing various aspects of this specification.

[0145] Various aspects of this specification are described herein with reference to flowchart illustrations and / or step diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It should be understood that each step in the flowchart illustrations and / or step diagrams, as well as combinations of steps in the flowchart illustrations and / or step diagrams, can be implemented by computer-readable program instructions.

[0146] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more steps of the flowchart and / or diagram of steps. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more steps of the flowchart and / or diagram of steps.

[0147] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more steps of a flowchart and / or a diagram of steps.

[0148] The flowcharts and step diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this specification. In this regard, each step in a flowchart or step diagram may represent a module, segment, or part of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the step may occur in a different order than those indicated in the drawings. For example, two consecutive step diagrams may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each step in a step diagram and / or flowchart, and combinations of steps in step diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0149] Various embodiments of this specification have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical applications, or technological improvements to the embodiments in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for configuring data, comprising: In response to detecting a user-triggered element data operation request for any scenario, an element data configuration interface for the operation request is provided to the user in order to obtain the user's configuration operation; Based on the configuration operation performed by the user in the element data configuration interface, obtain information about the target element for which the configuration operation is performed; Determine whether the information of the acquired target element conforms to the configuration rules of the target element's element data; as well as In response to determining that the information of the acquired target element conforms to the configuration rules of the target element's element data, element data about the target element is generated or updated; The configuration rules for the element data of the target element include at least one of the following: Structural rules regarding the data structure information of the target element; Type rules regarding the data type information of the target element; and Rules for using target elements.

2. The method according to claim 1, wherein the structural rules include one or more of the following: Uniqueness rules used to indicate that a defined attribute is exclusive; Non-nullability rules used to indicate that the value of the qualified attribute is not null; and Attribute boundary rules are used to indicate the range of defined attribute values.

3. The method of claim 1, wherein the usage rules include at least one of the following: Assembly rules are used to indicate the display area for the defined attribute data; Sorting rules are used to indicate the order in which attribute data is displayed within a defined display area; as well as Download rules are used to indicate that restricted attribute data must be downloaded before it can be displayed on the query results page when responding to a query request.

4. The method according to claim 3, further comprising: The display area is generated or divided based on at least one of the following: the type of scene, the type of target element, the context related to the target element, the context related to attribute data, and the operation performed by the user.

5. The method according to any one of claims 1-4, wherein the information of the target element includes at least one of the following: The target element's data structure, target element's type name, target element's attribute name, target element's attribute value, target element's attribute data type, target element's data assembly rules, and target element's data sorting rules.

6. The method according to claim 5, wherein the data type information includes at least one or more of the following: text type, rich text type, integer type, image type, video type, and attachment type.

7. The method of claim 6, further comprising: The data structure information of the target element is stored in a relational data format; as well as The data type information and attribute data information of the target element are stored in a non-relational data format.

8. The method according to claim 6, further comprising: In response to detecting a user-triggered query request regarding any scenario, determine the keywords contained in the query request; Based on the keywords, determine the scenario, element type, and / or element data associated with the query request; as well as Based on the associated scenario, element type, and / or element data, and according to the configuration and usage rules of the corresponding element data, a query result page for the query request is generated.

9. The method of claim 8, wherein generating a query results page for the query request comprises: Based on the associated element type, determine the type rules and usage rules corresponding to the query request; Based on the corresponding type rules, determine the data type of the element data associated with the query request; Based on the corresponding usage rules, determine the display area and assembly order of the element data associated with the query request; Based on the determined data type, display area, and assembly order, assemble the query result page for the query request; as well as Generate the query results page to display the element data included in the associated element types.

10. The method of claim 9, further comprising: Based on the first management operation performed by the user on the query results page, the items to be managed are determined, and the items to be managed are related to the scenario type, the type of element to be managed, and / or the data of the element to be managed. Based on the second management operation performed by the user on the query results page, a management interface for the project to be managed is presented to the user in order to obtain the user's third management operation; as well as Based on the third management operation performed by the user in the management interface, a predetermined operation is performed on the element data related to the project to be managed.

11. The method according to claim 10, wherein, The third management operation includes one or more of the following: adding element data, editing element data, deleting element data, and exporting element data; The pre-defined operations include one or more of the following: providing an element data configuration interface, providing an export configuration interface, and providing a delete configuration interface.

12. A data configuration system, comprising: The configuration operation acquisition module is configured to, in response to detecting a user-triggered element data operation request for any scenario, provide the user with an element data configuration interface for the operation request, so as to acquire the user's configuration operation; The element information acquisition module is configured to acquire information about the target element targeted by the configuration operation based on the configuration operation performed by the user in the element data configuration interface. The configuration rule verification module is configured to determine whether the information of the acquired target element conforms to the configuration rules of the target element's element data. as well as The element data generation module is configured to generate or update element data about the target element in response to determining that the information of the acquired target element conforms to the configuration rules of the element data of the target element; the configuration rules of the element data of the target element include at least one of the following: structural rules about the data structure information of the target element; type rules about the data type information of the target element; and usage rules about the target element.

13. A computing device, comprising: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-11.

14. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method of any one of claims 1-11.

Images