A data management system, method, apparatus, electronic device and storage medium

Abstract

The application provides a data management system, method, device, electronic equipment and storage medium, and belongs to the technical field of data. The method comprises the following steps: in the case that a page access trigger is received, sending request information to a server; rendering a target field according to attribute information sent by the server; obtaining list data sent by the server, and filling the list data into a position corresponding to the target field, wherein the filled list data and the corresponding target field have the same attribute information. In one management platform, the same attribute information is configured for the target field and the list data of the commodity display interface in different scenes, so that the commodities in different scenes have different attribute information, the clarity of commodity data display is improved, and commodity management and maintenance are facilitated.

Description

Technical Field

[0001] This application relates to the field of data technology, and in particular to a data management system, method, apparatus, electronic device, and storage medium. Background Technology

[0002] When operators configure product data in the backend, they will classify and store products according to product type. Currently, there are two storage methods: one is to place products from different scenarios in the same menu, and the other is to configure a menu for products in each scenario.

[0003] When placing products from different scenarios in the same table, the displayed information differs across scenarios, requiring a separate set of fields for each scenario. This redundancy leads to redundant fields, resulting in empty lists and poor page display and product interaction. Furthermore, since the fields are pre-configured, performing a union operation on these fields can lead to unclear meanings. For example, regular products require fields like name, price, and origin, while flash sale products require fields like name, flash sale price, flash sale time, and inventory. The displayed field information for regular and flash sale products differs, making a union operation difficult.

[0004] In the case of configuring a menu for each product in each scenario, multiple menus need to be configured, which increases the workload of backend development and maintenance.

[0005] Currently, there is no good solution for pages that contain product fields for different scenarios. Summary of the Invention

[0006] The purpose of this application is to provide a data management system, method, apparatus, electronic device, and storage medium to solve the problem of unclear product fields in different scenarios on the same platform. The specific technical solution is as follows:

[0007] Firstly, a data management system is provided, the system comprising:

[0008] The target terminal is connected to the server and is used to send request information to the server when a page access is triggered. The request information is used to request the attribute information of the target field in the current display interface of the target terminal. The current display interface is a product display interface in a scene.

[0009] The server is configured to receive request information sent by the target terminal and send the attribute information to the target terminal according to the request information;

[0010] The target terminal is further configured to render the target field according to the attribute information, obtain the list data sent by the server, and fill the list data into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

[0011] Secondly, a data management method is provided, applied to a target terminal, the method comprising:

[0012] Upon receiving a page access trigger, a request message is sent to the server, wherein the request message is used to request the attribute information of the target field in the current display interface of the target terminal, and the current display interface is a product display interface in a scene;

[0013] Render the target field based on the attribute information sent by the server;

[0014] The list data sent by the server is obtained and filled into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

[0015] Optionally, sending request information to the server upon receiving a page access trigger includes:

[0016] Determine the region code corresponding to the received page access trigger, wherein the region code is a region data in a region record in the current channel, the current channel contains multiple region records, and the region code can identify the region record in which it is located;

[0017] The attribute information associated with the region code corresponding to the page access trigger is determined based on the association relationship, wherein the server stores the correspondence between region codes and attribute information.

[0018] The request information carrying the attribute information is sent to the server, wherein the request information includes the region code.

[0019] Optionally, after filling the list data into the positions corresponding to the target field, the method further includes:

[0020] Receive submission instruction;

[0021] The list data is uploaded to the server according to the submission instruction.

[0022] Optionally, before uploading the list data to the server according to the submission instruction, the method further includes:

[0023] Determine the target fields corresponding to the target list data and the target attribute information corresponding to the target fields;

[0024] The target list data is validated using the target attribute information.

[0025] In the event of a verification failure, a prompt message is sent, which prompts the user to re-render the target field corresponding to the target list data.

[0026] Optionally, after performing attribute validation on the target list data using the target attribute information, the method further includes:

[0027] If the verification is successful, the list data will be uploaded to the server;

[0028] The attribute information is stored in a local cache so that the target field of the same area record can be rendered using the attribute information.

[0029] Thirdly, a data rendering method is provided, applied to a server, the method comprising:

[0030] Receive request information sent by the target terminal, wherein the request information is used to request attribute information of a target field in the current display interface of the target terminal;

[0031] The attribute information is retrieved based on a reflection mechanism;

[0032] The preset interface is determined based on the region code contained in the request information;

[0033] The preset interface is invoked to send the attribute information to the target terminal, so that the target terminal renders the target field according to the attribute information.

[0034] Fourthly, a data management device is provided, applied to a target terminal, the device comprising:

[0035] The sending module is used to send request information to the server when a page access trigger is received. The request information is used to request the attribute information of the target field in the current display interface of the target terminal. The current display interface is a product display interface in a scene.

[0036] A rendering module is used to render the target field based on the attribute information sent by the server;

[0037] The acquisition module is used to acquire list data sent by the server and fill the list data into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

[0038] Fifthly, a data rendering apparatus is provided for use on a server, the apparatus comprising:

[0039] A receiving module is used to receive request information sent by a target terminal, wherein the request information is used to request attribute information of a target field in the current display interface of the target terminal;

[0040] The crawling module is used to crawl the attribute information based on the reflection mechanism;

[0041] The determination module is used to determine the preset interface based on the region code contained in the request information;

[0042] The sending module is used to call the preset interface to send the attribute information to the target terminal, so that the target terminal renders the target field according to the attribute information.

[0043] In a sixth aspect, an electronic device is provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0044] Memory, used to store computer programs;

[0045] A processor, when executing a program stored in memory, implements any of the steps of the data management method described above.

[0046] In a seventh aspect, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when executed by a processor, the computer program implements any of the steps of the data management method described above.

[0047] Beneficial effects of the embodiments in this application:

[0048] This application provides a data management method, which includes: when a target terminal receives a page access trigger, it sends request information to a server; renders a target field based on attribute information sent by the server; obtains list data sent by the server; and fills the corresponding position of the target field with the list data. This application, within a management platform, configures the same attribute information for the target field and list data for product display interfaces in different scenarios, ensuring that products in different scenarios have different attribute information, improving the clarity of product data display, and facilitating product management and maintenance.

[0049] Of course, implementing any product or method of this application does not necessarily require achieving all of the above advantages at the same time. Attached Figure Description

[0050] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 A schematic diagram of the hardware environment for a data management method provided in an embodiment of this application;

[0052] Figure 2 A flowchart illustrating a data management method provided in this application embodiment;

[0053] Figure 3 A schematic diagram of the region list display interface provided in this application embodiment.

[0054] Figure 4 This is a schematic diagram of a typical product display interface provided in an embodiment of this application;

[0055] Figure 5 This is a schematic diagram of a special offer product display interface provided in an embodiment of this application;

[0056] Figure 6 A flowchart illustrating a method for sending request information provided in an embodiment of this application;

[0057] Figure 7 This is a schematic diagram of the structure of a data management device provided in an embodiment of this application;

[0058] Figure 8 This is a schematic diagram of another data management device provided in an embodiment of this application;

[0059] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0061] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustration and has no specific meaning in itself. Therefore, "module" and "part" may be used interchangeably.

[0062] In existing technologies, when the data displayed by the system lacks commonalities, it is necessary to split the data into multiple menus based on multiple dimensions, or to redundantly put common fields of all data into a single menu list. Both of these methods have drawbacks. Splitting menus requires creating more menus as the commonalities of the data increase, leading to a growing number of menus and high development costs. Redundant fields result in cluttered list information and difficulty in searching for content.

[0063] To address the aforementioned issues, this application provides a data management system. The system includes interconnected target terminals and a server. When an operator wants to manage product data for a specific scenario, they need to click on the product content within that scenario on the target terminal. The target terminal's page then redirects to the scenario page, which includes multiple fields, each corresponding to multiple product data items. The target terminal triggers a request based on the received page, sending request information to the server to request attribute information for the target field in the current scenario's display interface. The server sends the attribute information back to the target terminal based on the request information. The target terminal renders the target field based on the attribute information, then obtains the list data sent by the server and fills the corresponding positions of the target field with the list data, ensuring that the filled list data has the same attribute information as the target field.

[0064] In this application, within a management platform, the same attribute information is configured for the target fields and list data for product display interfaces in different scenarios. This ensures that products in different scenarios have different attribute information, eliminating the need to create a menu for each scenario's products, reducing development workload, and preventing product data from different scenarios from being mixed in one menu. This improves the clarity of product data display and facilitates product management and maintenance.

[0065] To address the problems mentioned in the background art, according to one aspect of the embodiments of this application, an embodiment of a data management method is provided.

[0066] Optionally, in the embodiments of this application, the above-described data management method can be applied to, for example, Figure 1 The hardware environment shown consists of terminal 101 and server 103. Figure 1 As shown, server 103 is connected to terminal 101 via a network and can be used to provide services to the terminal or clients installed on the terminal. Database 105 can be set up on the server or independently of the server to provide data storage services for server 103. The network mentioned above includes, but is not limited to, wide area network, metropolitan area network or local area network. Terminal 101 includes, but is not limited to, PC, mobile phone, tablet computer, etc.

[0067] The data management method in this application embodiment can be executed by server 103, or it can be jointly executed by server 103 and terminal 101.

[0068] This application provides a data management method that can be applied to a server or a target terminal, for displaying product data from an operations management backend system in a clear and simple manner.

[0069] The following will describe in detail a data management method provided in the embodiments of this application, with reference to specific implementation methods. Figure 2 As shown, the specific steps are as follows:

[0070] Step 201: Upon receiving a page access trigger, send a request message to the server.

[0071] The request information is used to request the attribute information of the target field in the current display interface of the target terminal.

[0072] In this embodiment of the application, the target terminal is equipped with an operation management backend system, the interface of which is shown in the figure below. Figure 3 As shown. Figure 3 As shown, the first-level menu is "Region Management," and the second-level menu is "Region List." All template data is displayed under the Region List menu. The Region List interface includes three search criteria: Channel, Region Name, and Region Code. Channels have three options: Product Management, Credit Card Management, and User Management, each containing one business function. For Product Management, there is a Region List with multiple region records. Each record includes a region name, a region code, and a "View Content" option. Clicking the corresponding "View Content" will take you to the specific details of the product corresponding to that region name or region code.

[0073] Figure 3 In the diagram, area list ① is a second-level menu, ② is the "Product Management" channel, and in the following implementation plan, data information is described according to the "Product Management" channel. ③ is the data under the "Product Management" channel, which includes multiple area records. Each area record corresponds to a scenario. In this embodiment, there are three area records, representing three scenarios: ordinary product scenario, flash sale product scenario, and crowdfunding product scenario. Each area record corresponds to a unique area code, and each area record includes a "View Content" operation. When operators click "View Content," they can access a detailed list of product content in that area record, and this detailed list can only be accessed by clicking "View Content."

[0074] Compared to existing technologies that require adding menus to the left-hand menu bar and then writing the page content for each dish separately, this application eliminates the need to repeatedly write menu pages, thus reducing development costs. Moreover, the template customization allows for the definition of not only table titles but also search criteria, including region names and region codes, making it convenient for operators to customize and improving flexibility.

[0075] After the operations staff clicks "View Content," the page redirects to a display interface for the corresponding scenario. This interface includes multiple fields, each corresponding to multiple data entries. If the operations staff clicks... Figure 3 The "View Details" option for regular products will redirect to... Figure 4 A menu for common Chinese goods. For example... Figure 4 As shown, ① is the menu operation, ② is the unique area code CH0001_RE01, corresponding to ordinary products, and ③ are the custom fields of the ordinary product template, namely: name, price, place of origin and operation.

[0076] If the operator clicks Figure 3 The "View Details" option for discounted items will redirect you to... Figure 5 A menu of discounted items. For example... Figure 5 As shown, ① is the menu operation, ② is the unique area code CH0001_RE02, corresponding to the special offer product, and ③ are the custom fields of the special offer product template, which are: name, flash sale price, flash sale time, inventory, status, and operation.

[0077] In this embodiment of the application, when the user clicks "View Content", it will start from... Figure 3 The interface redirects to Figure 4 or Figure 5 The content details list displayed on the interface is triggered when the target terminal receives an access request to the server. This request requests attribute information for the target fields in the currently displayed interface. The attribute information includes the field name's default value, field description, whether the field is hidden, whether the field is required, field hints, and extended fields. The default field name is the field's name itself; the field description is a technical explanation of the field name; the field hints are explanations shown to operations personnel; and extended fields are custom fields. The field names should be semantically clear, conform to data specifications, and have a length within a preset range for easy user viewing. For example, the preset length range is 1-7.

[0078] Step 202: Render the target field based on the attribute information sent by the server.

[0079] In this embodiment, the server receives a request from the target terminal. Based on the request, the server retrieves attribute information using Java reflection and then sends this attribute information to the target terminal. The target terminal renders the target field based on the attribute information sent by the server. The rendered content includes: field name default value, field description, whether the field is hidden, whether the field is required, field hints, extended fields, and a combination of default value and whether it is hidden. Specifically, the target terminal renders the field using JavaScript.

[0080] Optionally, since the "View Content" clicked by the operator corresponds to a region code, the request information sent by the target terminal also carries the region code. The server pre-stores multiple interfaces, each corresponding to a region code. The server determines the target interface based on the region code in the request information and calls the target interface to send the attribute information to the target terminal.

[0081] Step 203: Obtain the list data sent by the server and populate the list data into the corresponding positions of the target fields.

[0082] After the target terminal renders the target field, it obtains the list data sent by the server. Each target field corresponds to multiple list data. The server fills the list data into the position under the corresponding target field, so that the list data has the same attribute information as the corresponding target field.

[0083] The list data sent by the server can be obtained in two ways: the target terminal sends a data request to the server, and the server sends the list data to the target terminal according to the data request; or, after the target terminal finishes rendering the target field, it sends rendering completion information to the server, and the server sends the list data to the target terminal according to the data request.

[0084] In this application, within a management platform, the same attribute information is configured for the target fields and list data for product display interfaces in different scenarios. This ensures that products in different scenarios have different attribute information, eliminating the need to create a menu for each scenario's products and preventing the mixing of product data from different scenarios into a single menu. This improves the clarity of product data display and facilitates product management and maintenance.

[0085] As an optional implementation method, such as Figure 6 As shown, sending request information to the server upon receiving a page access trigger includes:

[0086] Step 601: Determine the region code corresponding to the received page access trigger.

[0087] The region code is a region data in a region record in the current channel. The current channel contains multiple region records, and the region code can identify the region record it belongs to.

[0088] In this embodiment of the application, the current channel includes a data list, which includes multiple regional records. Each regional record includes multiple regional data, and the regional code is one of the regional data in the regional record. The regional data can identify the regional record in which it is located.

[0089] Step 602: Determine the attribute information associated with the region code corresponding to the page access trigger based on the association relationship.

[0090] The server stores the correspondence between region codes and attribute information.

[0091] The target terminal stores the correspondence between region codes and attribute information, with different region codes corresponding to different attribute information.

[0092] For example, the attribute information corresponding to the area code CH0001_RE01 is the attribute information of ordinary products, and the attribute information corresponding to the area code CH0001_RE02 is the attribute information of flash sale products. In the field name attribute information, the field name of ordinary products includes name, price, place of origin, and operation, while the field name of flash sale products includes name, flash sale price, flash sale time, inventory, status, and operation.

[0093] The target terminal determines the corresponding region code triggered by this page access based on the region code in the request information, and determines the attribute information corresponding to that region code.

[0094] Step 603: Send the request information carrying attribute information to the server.

[0095] The target terminal sends a request message containing attribute information and a region code to the server, so that the server sends the attribute information to the target terminal and determines the target port based on the region code.

[0096] As an optional implementation, after the target terminal fills the list data into the corresponding position of the target field, the operator will instruct the submitter to submit the filled list data. The target terminal receives the submission instruction and then uploads the list data to the server according to the submission instruction. Before uploading, the target terminal also needs to perform attribute verification on the list data through attribute information.

[0097] Specifically, the server determines the target list data, which is a column of table data. The target list data should have the same attribute information as the target field of that column. The server determines the actual attribute information of the target list data and the target attribute information of the target field, and then performs attribute validation on the target list data based on the target attribute information, specifically determining whether the actual attribute information of the target list data and the target attribute information are consistent.

[0098] If the server determines that the actual attribute information of the target list data matches the target attribute information, it indicates that the attribute information verification was successful. The server then uploads the list data to the server and stores the target attribute information in the local cache. When the target field of the record in this area needs to be rendered again, it is not necessary to retrieve the attribute information from the server; the locally stored attribute information can be used directly, improving rendering efficiency, data management efficiency, and page generation efficiency.

[0099] If the server determines that the actual attribute information of the target list data is inconsistent with the target attribute information, indicating that the attribute information verification has failed, it will perform error handling and send a prompt message. This prompt message is used to instruct the user to re-render the target field corresponding to the target list data. For example, when verification fails, the target terminal will display a prompt box, prompting the user to re-render the target field.

[0100] Optionally, users can validate the target list data using target attribute information when creating or modifying it. Hiding fields reduces the workload for operations staff, and specifying whether fields are required prevents the upload of multiple empty data entries to the server's database.

[0101] In this application, data from different scenarios can be separated through template definition, with neither redundant fields nor ambiguous shared fields, making data management clearer and easier to maintain for users.

[0102] Optionally, this application embodiment also provides a data management processing flowchart, the specific steps of which are as follows.

[0103] 1. Upon receiving a page access trigger, send a request message to the server, which includes the region code.

[0104] 2. Based on the request information, the server retrieves the attribute information using Java reflection, determines the target interface based on the region code, and sends the attribute information to the target terminal through the target interface.

[0105] 3. The target terminal renders the target field based on the attribute information using JavaScript.

[0106] 4. The target terminal obtains the list data sent by the server and fills the list data into the corresponding positions of the target fields.

[0107] 5. The target terminal performs attribute validation on the target list data using the target attribute information. If the validation is successful, proceed to step 6; if the validation fails, proceed to step 7.

[0108] 6. The target terminal uploads the list data to the server.

[0109] 7. The target terminal sends a prompt message, which prompts the user to re-render the target field corresponding to the target list data.

[0110] Based on the same technical concept, embodiments of this application also provide a data management device, applied to a target terminal, such as... Figure 7 As shown, the device includes:

[0111] The first sending module 701 is used to send request information to the server when a page access trigger is received. The request information is used to request the attribute information of the target field in the current display interface of the target terminal. The current display interface is a product display interface in a scene.

[0112] Rendering module 702 is used to render the target field based on the attribute information sent by the server;

[0113] The acquisition module 703 is used to acquire list data sent by the server and fill the list data into the corresponding positions of the target fields. The filled list data has the same attribute information as the corresponding target fields.

[0114] Optionally, the first transmitting module 701 includes:

[0115] The first determining unit is used to determine the region code corresponding to the received page access trigger, wherein the region code is a region data in a region record in the current channel, the current channel contains multiple region records, and the region code can identify the region record in which it is located.

[0116] The second determining unit is used to determine the attribute information associated with the region code corresponding to the page access trigger based on the association relationship, wherein the server stores the correspondence between region codes and attribute information.

[0117] The sending unit is used to send request information carrying attribute information to the server, wherein the request information includes a region code.

[0118] Optionally, the device further includes:

[0119] The receiving module is used to receive submission instructions;

[0120] The first upload module is used to upload list data to the server according to the submission instructions.

[0121] Optionally, the device further includes:

[0122] The determination module is used to determine the target fields corresponding to the target list data and the target attribute information corresponding to the target fields.

[0123] The validation module is used to validate the target list data based on the target attribute information.

[0124] The second sending module is used to send a prompt message in the event of a verification failure. The prompt message is used to remind the user to re-render the target field corresponding to the target list data.

[0125] Optionally, the device further includes:

[0126] The second upload module uploads the list data to the server if the verification is successful.

[0127] The storage module is used to store attribute information in a local cache so that the target field of the same area record can be rendered using the attribute information.

[0128] Based on the same technical concept, embodiments of this application also provide a data management device applied to a server, such as... Figure 8 As shown, the device includes:

[0129] The receiving module 801 is used to receive request information sent by the target terminal, wherein the request information is used to request the attribute information of the target field in the current display interface of the target terminal;

[0130] The crawling module 802 is used to crawl attribute information based on reflection mechanism;

[0131] The determination module 803 is used to determine the preset interface based on the region code contained in the request information;

[0132] The sending module 804 is used to call a preset interface to send attribute information to the target terminal, so that the target terminal can render the target field according to the attribute information.

[0133] According to another aspect of the embodiments of this application, this application provides an electronic device, such as... Figure 9 As shown, the system includes a memory 903, a processor 901, a communication interface 902, and a communication bus 904. The memory 903 stores a computer program that can run on the processor 901. The memory 903 and the processor 901 communicate through the communication interface 902 and the communication bus 904. When the processor 901 executes the computer program, it implements the steps of the above method.

[0134] The memory and processor in the aforementioned electronic devices communicate with each other via a communication bus and a communication interface. The communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0135] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0136] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0137] According to another aspect of the embodiments of this application, a computer-readable medium having processor-executable non-volatile program code is also provided.

[0138] Optionally, in embodiments of this application, the computer-readable medium is configured to store program code for the processor to execute the above-described method:

[0139] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments, and will not be repeated here.

[0140] In specific implementation, the embodiments of this application can be referred to the above embodiments and have corresponding technical effects.

[0141] It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described herein, or combinations thereof.

[0142] For software implementation, the techniques described herein can be implemented by units that perform the functions described herein. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

[0143] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0144] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0145] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0146] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0147] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0148] If the aforementioned function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks. It should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. In the absence of further restrictions, an element defined by the phrase "comprising a..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0149] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A data management system, characterized in that, The system includes: A target terminal, connected to a server, sends a request to the server upon receiving a page access trigger. This request requests attribute information for a target field within the current display interface of the target terminal, which is a product display interface within a specific scenario. The attribute information for target fields in different scenarios is defined using different templates, and a pre-built association between the attribute information of target fields in different scenarios and their corresponding scenarios is established. Target fields within the same scenario are stored in the same template, while target fields in different scenarios are stored in different templates. The system supports searching for templates within a specific scenario based on its region code. The region code identifies the region record, and different region records indicate different scenarios. The server is configured to receive request information sent by the target terminal, and send attribute information in the corresponding scenario to the target terminal according to the request information and the association relationship; The target terminal is further configured to render the target field according to the attribute information of the corresponding scenario sent by the server, and obtain the list data sent by the server, and fill the list data into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

2. A data management method applied to a target terminal, characterized in that, The method includes: Upon receiving a page access trigger, a request is sent to the server. This request requests attribute information of a target field within the current display interface of the target terminal, which is a product display interface within a specific scenario. The attribute information of the target field in different scenarios is defined using different templates, and a pre-built association between the attribute information of the target field in different scenarios and the corresponding scenarios is established. Target fields in the same scenario are stored in the same template, while target fields in different scenarios are stored in different templates. The system also supports searching for templates based on the region code of the corresponding scenario. The region code identifies the region record, and different region records indicate different scenarios. The target field is rendered based on the attribute information of the corresponding scenario sent by the server based on the association relationship; The list data sent by the server is obtained and filled into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

3. The method according to claim 2, characterized in that, The step of sending a request message to the server upon receiving a page access trigger includes: Determine the region code corresponding to the received page access trigger, wherein the region code is region data in a region record in the current channel, and the current channel contains multiple region records; The attribute information associated with the region code corresponding to the page access trigger is determined based on the association relationship, wherein the server stores the correspondence between region codes and attribute information; The request information carrying the attribute information is sent to the server, wherein the request information includes the region code.

4. The method according to claim 2, characterized in that, After filling the list data into the positions corresponding to the target field, the method further includes: Receive submission instruction; The list data is uploaded to the server according to the submission instruction.

5. The method according to claim 4, characterized in that, Before uploading the list data to the server according to the submission instruction, the method further includes: Determine the target fields corresponding to the target list data and the target attribute information corresponding to the target fields; The target list data is validated using the target attribute information. In the event of a verification failure, a prompt message is sent, which prompts the user to re-render the target field corresponding to the target list data.

6. The method according to claim 5, characterized in that, After performing attribute validation on the target list data using the target attribute information, the method further includes: If the verification is successful, the list data will be uploaded to the server; The attribute information is stored in a local cache so that the target field of the same area record can be rendered using the attribute information.

7. A data rendering method, applied to a server, characterized in that, The method includes: The system receives request information sent by the target terminal, wherein the request information is used to request attribute information of a target field in the current display interface of the target terminal; wherein the attribute information of the target field in different scenarios is defined using different templates, and the association relationship between the attribute information of the target field in different scenarios and the corresponding scenarios is pre-built; target fields in the same scenario are stored in the same template and target fields in different scenarios are stored in different templates, and it supports searching for templates in the corresponding scenario based on the region code in the corresponding scenario; the region code can identify the region record, and different region records are used to indicate different scenarios; Based on the aforementioned relationships and reflection mechanisms, attribute information in the corresponding scenarios is retrieved; The preset interface is determined based on the region code contained in the request information; The preset interface is invoked to send the attribute information of the corresponding scenario to the target terminal, so that the target terminal renders the target field according to the attribute information of the corresponding scenario. The list data is sent to the target terminal, causing the target terminal to fill the list data into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

8. A data management device, applied to a target terminal, characterized in that, The device includes: The sending module is used to send request information to the server upon receiving a page access trigger. The request information requests attribute information of a target field within the current display interface of the target terminal, which is a product display interface within a scene. The attribute information of the target field in different scenes is defined using different templates, and a pre-built association between the attribute information of the target field in different scenes and the corresponding scenes is established. Target fields in the same scene are stored in the same template, while target fields in different scenes are stored in different templates. The module also supports searching for templates within a scene based on the corresponding scene's region code. The region code identifies the region record, and different region records indicate different scenes. The rendering module is used to render the target field based on the attribute information of the corresponding scenario sent by the server based on the association relationship; The acquisition module is used to acquire list data sent by the server and fill the list data into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

9. A data rendering device, applied to a server, characterized in that, The device includes: The receiving module is used to receive request information sent by the target terminal, wherein the request information is used to request attribute information of target fields in the current display interface of the target terminal; wherein the attribute information of target fields in different scenarios is defined using different templates, and the association relationship between the attribute information of target fields in different scenarios and the corresponding scenarios is pre-built; target fields in the same scenario are stored in the same template and target fields in different scenarios are stored in different templates, and it supports searching for templates in the corresponding scenario based on the region code in the corresponding scenario; the region code can identify the region record, and different region records are used to indicate different scenarios; The crawling module is used to crawl attribute information in the corresponding scenario based on the aforementioned relationship and reflection mechanism; The determination module is used to determine the preset interface based on the region code contained in the request information; The sending module is used to call the preset interface to send attribute information under the corresponding scenario to the target terminal, so that the target terminal renders the target field according to the attribute information under the corresponding scenario. The sending module is further configured to send list data to the target terminal, so that the target terminal fills the list data into the position corresponding to the target field, wherein the filled list data has the same attribute information as the corresponding target field.

10. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the steps of the method described in any one of claims 2-7.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 2-7.

Images