Data card application building method and system, electronic equipment and storage medium

By obtaining front-end data source information, creating multiple data sources and data sets, and generating data models and entities, the problem of high difficulty in developing data card applications is solved, rapid construction and efficient development are achieved, and the universality and efficiency of data cards are improved. .

CN119089018APending Publication Date: 2024-12-06ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310658074.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-06-05
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The development of existing data card applications is difficult, the response time of customer needs is long, the cost is high, and the business personnel need to have professional database language skills, which limits the universality and portability of data cards.

Method used

By obtaining basic information of front-end data sources, creating multiple types of data sources and initial data sets, generating associated data sets, performing data modeling, performing SQL translation, and generating data entities, realizing the rapid construction of data card applications, reducing development difficulties, Improve efficiency.

Benefits of technology

It realizes the rapid construction of data card applications, reduces development difficulty, allows business experts to master code, improves development efficiency, improves the universality and portability of data cards, supports multiple data source access, and simplifies the abstraction of business requirements. Share with visual components.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119089018A_ABST
    Figure CN119089018A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a data card application building method and system, electronic equipment and a storage medium, and belongs to the technical field of data visualization. The establishment method of the data card application comprises the following steps: acquiring basic information of a data source from a front end, and establishing multiple types of data sources based on the basic information of the data source; creating a plurality of types of initial data sets based on each data source; acquiring a data set operation instruction from a front end, and generating an associated data set based on the data set operation instruction and each initial data set; performing data modeling based on each initial data set and the associated data set to obtain a data model; acquiring a data structure generated based on the data model from a front end, and performing SQL translation on the data structure to obtain a corresponding data entity; and returning the data entity to the front end, so that the front end completes establishment of the data card application based on the data entity. According to the embodiment of the invention, the development difficulty of the data card application is reduced, and efficient establishment of the data card application is realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data visualization technology, and in particular to a method, system, electronic device and storage medium for building a data card application. Background Art

[0002] Data visualization can present complex data relationships and analysis results from massive amounts of data to users in the form of rich charts and good visual effects, and can graph and chart data to "see data simply and intuitively", ultimately achieving business goals such as enterprises discovering data value, and realizing analysis, prediction, monitoring, and decision-making. In short, the so-called "a picture is worth a thousand words" is the simplest and most effective explanation of the role of data visualization.

[0003] Building a data card application is a common way to achieve data visualization, but the data cards in related technologies are highly customized, cannot be flexibly assembled, and the data source used is single. Therefore, when developing data card applications based on customer needs, professional developers must provide technical support to complete it, which results in a long response time to customer needs and increased costs. Summary of the invention

[0004] The main purpose of the embodiments of the present application is to provide a method, system, electronic device and storage medium for building a data card application, aiming to reduce the difficulty of developing data card applications to achieve rapid construction of data card applications, thereby achieving the purpose of timely responding to customer needs and saving development costs.

[0005] To achieve the above purpose, an embodiment of the present application provides a method for building a data card application, which is applied to a backend and includes:

[0006] Obtain basic data source information from the front end, and create multiple types of data sources based on the basic data source information;

[0007] Creating multiple types of initial data sets based on the data sources;

[0008] Acquire a data set operation instruction from the front end, and generate a related data set based on the data set operation instruction and each of the initial data sets;

[0009] Performing data modeling based on each of the initial data sets and the associated data sets to obtain a data model;

[0010] Obtaining a data structure generated based on the data model from the front end, and performing SQL translation on the data structure to obtain a corresponding data entity;

[0011] The data entity is returned to the front end so that the front end completes the construction of the data card application based on the data entity.

[0012] In addition, to achieve the above purpose, the embodiment of the present application also provides a method for building a data card application, which is applied to the front end and includes:

[0013] In response to the input of basic information of the data source, the basic information of the data source is sent to the backend to obtain a data model;

[0014] In response to a data card creation instruction input, generating a data structure of data required for the data card based on the data card creation instruction and the data model;

[0015] Sending the data structure to a backend to obtain a data entity corresponding to the data structure;

[0016] Performing data assembly and page rendering based on the data entity to obtain a data card corresponding to the data card creation instruction;

[0017] Iteration is performed in combination with multiple data sets in the data model to obtain multiple data cards to complete the construction of the data card application.

[0018] In addition, to achieve the above purpose, the embodiment of the present application also provides a data card application construction system, wherein the data card application construction includes a front end and a back end.

[0019] The front end is used for responding to the input of basic information of the data source, sending the basic information of the data source to the back end to obtain the data model;

[0020] The backend is used to obtain basic information of the data source from the frontend, create multiple types of data sources based on the basic information of the data source; create multiple types of initial data sets based on each of the data sources; obtain data set operation instructions from the frontend, generate associated data sets based on the data set operation instructions and each of the initial data sets; perform data modeling based on each of the initial data sets and the associated data sets to obtain a data model; obtain a data structure generated based on the data model from the frontend, perform SQL translation on the data structure to obtain a corresponding data entity; return the data entity to the frontend, so that the frontend completes the construction of the data card application based on the data entity;

[0021] The front end is used to respond to a data card creation instruction, generate a data structure of data required for the data card based on the data card creation instruction and the data model; send the data structure to the back end to obtain a data entity corresponding to the data structure; perform data assembly and page rendering based on the data entity to obtain a data card corresponding to the data card creation instruction; and iterate in combination with multiple data sets in the data model to obtain multiple data cards to complete the construction of a data card application.

[0022] In addition, to achieve the above-mentioned purpose, an embodiment of the present application also provides an electronic device, and the data card application building device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the computer program is executed by the processor, the data card application building method as described above is implemented.

[0023] In addition, to achieve the above-mentioned purpose, an embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method for building a data card application as described above is implemented.

[0024] The embodiment of the present application proposes a method, system, electronic device and storage medium for building a data card application. In the method for building the data card application, first obtain the basic information of the data source from the front end, and create multiple types of data sources based on the basic information of the data source; then create multiple types of initial data sets based on each of the data sources; then obtain the data set operation instructions from the front end, and generate related data sets based on the data set operation instructions and each of the initial data sets; then perform data modeling based on each of the initial data sets and the related data sets to obtain a data model; then obtain the data structure generated based on the data model from the front end, perform SQL translation on the data structure to obtain the corresponding data entity; finally, return the data entity to the front end, so that the front end completes the building of the data card application based on the data entity. The embodiment of the present application realizes the transformation process from data source to data model and then to visual data card application through the above steps. The method for building the data card application reduces the difficulty of developing the data card application, allowing business experts to efficiently focus on business needs, and can efficiently build data card applications without mastering professional skills related to code, thereby improving the development efficiency of data cards. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0026] Figure 1 A flowchart of a method for building a data card application provided in one embodiment of the present application;

[0027] Figure 2 A schematic diagram of a multi-tree structure involved in a method for building a data card application provided in one embodiment of the present application;

[0028] Figure 3 A schematic diagram of the classification of automatic annotation specifications involved in a method for building a data card application provided in one embodiment of the present application;

[0029] Figure 4 A schematic diagram of a process of performing SQL translation on a data structure in a method for building a data card application provided in an embodiment of the present application;

[0030] Figure 5 A flowchart of a method for building a data card application provided in another embodiment of the present application;

[0031] Figure 6 A schematic diagram of an application scenario for creating a data entity involved in a method for building a data card application provided in another embodiment of the present application;

[0032] Figure 7 A schematic diagram of a data card involved in a method for building a data card application provided in another embodiment of the present application;

[0033] Figure 8 A structural diagram of a system for building a data card application provided in one embodiment of the present application;

[0034] Fig. 9 A schematic diagram of the hardware structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0035] In the following description, specific details such as specific system structures, technologies, etc. are proposed for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the embodiments of the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from hindering the description of the embodiments of the present application.

[0036] It should be noted that although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0037] It should also be understood that the references to "one embodiment" or "some embodiments" described in the specification of the embodiments of the present application mean that one or more embodiments of the embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Thus, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0038] In this era of information explosion, many companies are undergoing digital transformation. The ease of use and flexibility of low-code and zero-code can help companies quickly respond to unpredictable market demands in the short term. While empowering business personnel at a low cost, they can quickly iterate user needs, tap high-value needs, and meet the requirements of rapid innovation and delivery, thereby lowering the threshold for digitalization and improving the quality of digital operations. As an important tool under low-code, data cards provide a large amount of quantitative data in a visual way, providing strong support for decision-makers to make decisions quickly.

[0039] However, the data cards in the current related technologies are all attached to a specific field, which greatly limits the versatility and portability of data cards. Therefore, when developing data card applications with low code, business personnel are required to have professional knowledge and skills in database languages, but ordinary business personnel are often lacking in this aspect. They know more about business knowledge. Therefore, if a data card application is to be implemented, it requires the support of professional developers, but this will lead to a long response time for customer needs, which will lead to increased costs.

[0040] Based on this, the embodiments of the present application provide a method, system, electronic device and storage medium for building a data card application. The data card application obtained by the data card application building method can be imagined as a building block with the smallest granularity. Each card service is an independent analysis model that solves a specific problem. Multiple cards are put together to form a report or an application. Each card contains a front-end page and data, and can be quickly assembled into the data report that the user wants.

[0041] The data card application building method, system, electronic device and storage medium provided in the embodiments of the present application are specifically described through the following embodiments. First, the data card application building method in the embodiments of the present application is described.

[0042] The present application embodiment provides a method for building a data card application, referring to Figure 1 , Figure 1 A flowchart of a method for building a data card application provided in an embodiment of the present application is provided. The method for building a data card application can be applied to a backend, such as Figure 1 As shown, the method for building a data card application provided in this embodiment includes steps S10 to S60.

[0043] Step S10, obtaining basic information of the data source from the front end, and creating multiple types of data sources based on the basic information of the data source;

[0044] It should be noted that the execution subject in this embodiment is the backend, that is, the server. The server needs to exchange information with the frontend to support the execution of subsequent steps. The frontend is the frontend web (network, Internet) page. The user can access the frontend web page through a terminal with a network connection function such as a mobile phone and a computer. When the user creates a data set belonging folder and a new data set on the frontend page, it is also necessary to enter the basic information of the data source contained in the data set, which may specifically include the display name, type, description and detailed information (such as host name, port, database name, user name, password, other parameters, etc.) of the data source created by the user on the frontend page. When the user creates the above basic information of the data source through the frontend page, the server can obtain the basic information of the data source and create various types of data sources based on the basic information of the data source.

[0045] Step S20, creating multiple types of initial data sets based on the data sources;

[0046] Based on the aforementioned step S10, it can be known that the user's original intention is to create a data set. Therefore, after completing the creation of the data source, the server will also create data sets related to the data source type, and place these data sources into data sets of corresponding types to obtain an initial data set to support the user's execution actions on the front-end page.

[0047] As an example, corresponding to the above-mentioned step S10 and step S20, the operations performed by the user on the front-end page include: creating a data set belonging folder; selecting a new data source data set, selecting a data source instance, selecting a corresponding data table, creating a new data source data set, and belonging the data source data set to the data set belonging folder; selecting a file type data set (such as a table type data set Excel), selecting a file type data set belonging folder, uploading a local file (such as a table type file in a format such as csv, xls, xlsx, etc.), and generating a file type data set; it can be understood that the data source data set and the file type data set in this embodiment are both initial data sets.

[0048] Step S30, obtaining a data set operation instruction from the front end, and generating a related data set based on the data set operation instruction and each of the initial data sets;

[0049] In this embodiment, the server converts the above-mentioned associated data set entity based on the data set operation instruction from the front end, and then generates an associated data set.

[0050] In some feasible embodiments, the initial data set includes a file type data set and a data source data set, and the above step S30 includes:

[0051] Step S301, generating a multi-branch tree structure based on the data set operation instruction, the file type data set and the data source data set;

[0052] Step S302: parsing and assembling the multi-branch tree structure, acquiring associated field information in combination with a recursive iterative algorithm, and generating an associated data set based on the associated field information.

[0053] It should be noted that the file type dataset is a dataset consisting of data sources that can be manually edited, while the data source dataset is a dataset consisting of data sources directly obtained from the database.

[0054] As an example, in this embodiment, the operations performed by the user on the front-end page include: selecting an associated data set, entering a data set name and selecting an attribution file, selecting a data set (data source data set, file type data set), and after selecting an instance of one of the data sets, different types of data sets can be associated, and according to the selected associated data set, its association (internal, left, right, completely external, union deduplication, union) relationship is selected and associated fields are added to generate a new associated data set entity to create a new associated data set.

[0055] As an example, the server first decomposes the dataset-related entity into multiple independent dataset entities through the parsing module, and then generates a new temporary entity in the assembly module according to the association relationship between different dataset entities. Then, the temporary entity is associated with the dataset entity at the parent level according to the association relationship. In the association process, a multi-tree algorithm can be used to generate Figure 2 The multi-branch tree structure shown in the figure preferentially processes the entity relationship at the bottom level, and through continuous recursive iteration, reduces the number of parent levels of the entities associated with the data set, and finally obtains an entity that can be used to create an associated data set, generates an associated data set based on the entity, and stores the associated data set in the database.

[0056] As an example, the user can drag and drop the file type dataset, data source dataset, and associated dataset in the front-end page to generate a new associated dataset-specific structure (multi-tree structure), and then parse and assemble the structure in the back-end and use a recursive iterative algorithm to obtain the field information of the associated dataset that needs to be output in the end, and generate the associated dataset.

[0057] Step S40, performing data modeling based on each of the initial data sets and the associated data sets to obtain a data model;

[0058] In this embodiment, data modeling is achieved by the server performing unified management and dimensional measurement modeling of each of the initial data sets and the associated data sets. After the server completes data modeling, a data model including all initial data sets and associated data sets can be obtained.

[0059] In some feasible embodiments, the above step S40 includes:

[0060] Step S401, uniformly processing the metadata of each of the initial data sets and the associated data sets to obtain a standard data set;

[0061] As an example, the process of unified management of data source data sets, file type data sets, and associated data sets by the server is as follows: after receiving the file uploaded by the front end, the file type data set stores the file in the file storage system. If the file is an Excel file, the Excel processing module is called to use Excel processing technology to separate field information and data information, and a file type data subset is generated based on the separated field information, and the file type data subset is stored in the database; through the associated entity conversion module, the association relationship of each field information in the associated data set is processed, and an associated data subset is generated based on each field information, and the associated data subset is stored in the database; each data source instance in the data source data set is obtained, and a database data subset is established based on the field information of each data source instance, and the database data subset is stored in the database; the data types of the file type data subset, the associated data subset, and the database data subset in the database are unified to obtain a standard data set, thereby realizing unified management of heterogeneous data sets.

[0062] In addition, after unified data type processing, by establishing a relationship between the generated dataset and the source dataset, the field lineage of the newly generated dataset and the source datasets that the dataset is composed of can be traced, thereby forming a dataset lineage link. Through the dataset lineage link, it is possible to trace back to which initial datasets are the source of the associated dataset, and then display them to the user.

[0063] Step S402, performing dimensional measurement modeling on the standard data set to obtain dimension fields and indicator fields;

[0064] Step S403: Automatically annotate the standard data set based on the dimension field and the indicator field to obtain a data model.

[0065] In this embodiment, the automatic annotation of the standard data set is realized by determining the field type. Figure 3 In this embodiment, data types related to text, time, and geography (including longitude and latitude, cells, grids, buildings, etc.) are automatically labeled as dimension fields, and data types such as data and numerical values ​​(decimals) that can be summed, maximized, and minimized are automatically labeled as indicator fields. After all data types in the standard data set are automatically labeled, the establishment of the data model is considered to be completed.

[0066] As an example, after the data model is established, the user can select the created dataset instance on the front-end page. The page will then display the data preview and field management of the dataset. The data preview returns limited sampling data based on the performance strategy, and the field management automatically annotates the modeling module based on the server-side dataset metadata to display dimensions and indicators.

[0067] It should be noted that, in this embodiment, the field name and field type can be changed according to the given dimension field and indicator field, but the initial field name and field type cannot be changed; and the dimension field and indicator field can be converted to each other, and a new data set will be formed after the conversion to ensure the compatibility of the data set already in use.

[0068] Step S50, obtaining a data structure generated based on the data model from the front end, and performing SQL translation on the data structure to obtain a corresponding data entity;

[0069] It should be noted that after the server completes the establishment of the data model, the user can form the data structure required for the data card through a series of clicks, drags and settings on the front-end page. This data structure is a data structure used to describe the relationship between tables. It only contains the description information of the key-value pair. It is the structural information sent by the front end to the back end and can be used for all relational database types of data sets. However, this data structure still needs to be processed by the server, that is, after SQL translation, the corresponding data entity can be obtained before it can be used for data card development. This data entity is another SQL data structure obtained after the data structure is translated by SQL. It is the result data after the actual execution of the data structure. It is the data obtained by the back end processing the structural information from the front end.

[0070] In some feasible embodiments, the step of performing SQL translation on the data structure to obtain the corresponding data entity in the above step S50 includes:

[0071] Step S501, generating a unified SQL string based on the attributes of the data structure;

[0072] Step S502, performing SQL translation on the unified SQL string based on an SQL translation engine to obtain a dialect SQL string;

[0073] Step S503: acquiring corresponding data entities from the database based on the dialect SQL character string.

[0074] As an example, the server uses the unified SQL (Structured Query Language) to form dialect SQL strings based on various database types according to the data structure from the front end, such as Figure 4As shown, the server first performs filtering and drilling operations according to the sector labels and axis values ​​of the data structure to generate a unified SQL string. The unified SQL string can be converted into an abstract syntax tree through syntax parsing by the SQL translation engine. The syntax tree and the database type of the corresponding data set of the data structure are then semantically parsed to convert it into a semantic tree (logical query plan). After that, on the basis of ensuring equivalence at the semantic level, the semantic tree is converted into a dialect grammar tree of the corresponding dialect, and then the dialect grammar tree is reversed to obtain the final dialect SQL string, thereby ensuring the semantic consistency of the front end when describing the entity.

[0075] This embodiment unifies the field types and SQL functions required for data query in the data card, determines the dialect SQL that needs to be executed by unifying the syntax, semantics, and dialect translation of SQL, and executes queries on the file server and data source database according to the source of the data set, which can avoid the need for different adaptation processes when accessing different data set types.

[0076] Step S60: returning the data entity to the front end, so that the front end completes the construction of the data card application based on the data entity.

[0077] It should be noted that in this embodiment, after obtaining the SQL string of the dialect, the server initiates a connection to the database through the database connection method set in the data source, and returns the corresponding data entity to the front end, so that the front end completes the construction of the data card application based on the data entity.

[0078] It is understandable that, in the process of building a data card application based on the data entity at the front end, the server will update the data in the database according to the data transmitted by the user through the front end.

[0079] It can be seen from the above steps S10 to S60 that in this embodiment, the server needs to receive different information from the front end, and then perform execution actions corresponding to the different information, and finally achieve the purpose of building a data card application.

[0080] This embodiment proposes a method for building a data card application. In the method for building a data card application, basic information of a data source is first obtained from a front end, and multiple types of data sources are created based on the basic information of the data source; multiple types of initial data sets are then created based on each of the data sources; then, a data set operation instruction is obtained from the front end, and an associated data set is generated based on the data set operation instruction and each of the initial data sets; then, data modeling is performed based on each of the initial data sets and the associated data sets to obtain a data model; then, a data structure generated based on the data model is obtained from the front end, and SQL translation is performed on the data structure to obtain a corresponding data entity; finally, the data entity is returned to the front end, so that the front end completes the building of the data card application based on the data entity. This embodiment has the ability to convert data sources in different types of data sets into a visual state, and can unify the data standards of different types of data sets, thereby avoiding the problem of inconsistent database types and methods; this embodiment realizes efficient reuse, can abstract business needs, and share and reuse visual components, allowing business experts to focus on business needs efficiently and build data card applications more efficiently; this embodiment also adopts multi-data source adaptation, adopts unified SQL, unifies the differences in syntax and semantics of multiple data sources, and can access different types of data sources more widely and quickly; this embodiment is based on the data model method, so that the data model can be quickly applied to the data card in a drag-and-drop manner, and can be quickly replaced in the data card, thereby improving the development efficiency of the data card.

[0081] In addition, the present application embodiment also provides a method for building a data card application, referring to Figure 5 , Figure 5 A flowchart of a method for building a data card application provided in another embodiment of the present application is provided. The method for building a data card application can be applied to a front end, such as Figure 5 As shown, the method for building a data card application provided in this embodiment includes steps A10 to A50.

[0082] Step A10, in response to the input of basic information of the data source, sending the basic information of the data source to the backend to obtain a data model;

[0083] It should be noted that the execution subject in this embodiment is the front end, that is, the front end web (network, Internet) page. The main task of the front end page is to receive the user's input instructions and send them to the back end for processing, and then display the processing results on the page to feedback information to the user. When the user creates a data set belonging folder and a new data set, the front end page obtains the basic information of the data source contained in the data set, which may specifically include the display name, type, description and detailed information (such as host name, port, database name, user name, password, other parameters, etc.) of the data source created by the user in the front end page. After obtaining the basic information of the data source, the front end sends this information to the server, so that the server completes the creation of the data model based on the basic information of the data source.

[0084] As an example, the front-end page is built using the vue2.0 framework technology.

[0085] As an example, the front-end page in this embodiment can be displayed in a dashboard, and the user can input various operation instructions through the dashboard.

[0086] As an example, the process of the front end responding to the user inputting basic information of the data source is as follows: after receiving the configuration dashboard instruction, the dashboard configuration page is displayed based on the data model provided by the back end; after receiving the new folder instruction, a new folder is added to the dashboard management page; after receiving the new dashboard instruction, an optional dashboard option is added to the dashboard management page, and the optional entities of the dashboard include: theme entity, view entity and component entity, among which the theme, view and component entities are stored in the database in an encrypted manner.

[0087] Step A20, in response to the input of the data card creation instruction, generating a data structure of the data required for the data card based on the data card creation instruction and the data model;

[0088] It can be understood that after the data model is established on the back end, the user can input a series of instructions for creating data cards through the front-end page, such as creating a new folder, creating an instance, editing an instance, dragging a view, dragging a field, etc. After receiving these instructions, the front-end page will call the content in the data model that is adapted to the instructions and display it on the front-end page. In this embodiment, the premise for creating a data card is to generate the data structure of the data required for the data card.

[0089] In some feasible embodiments, the step of generating a data structure of data required for the data card based on the data card creation instruction and the data model in the above step A20 may specifically include:

[0090] Step A201, creating a corresponding card instance based on the data card creation instruction and the data model;

[0091] Step A202, in response to the view adjustment instruction input, obtaining a corresponding view from the data model based on the view adjustment instruction and placing it into the card instance;

[0092] Step A203, in response to the input of the data setting instruction, setting the dimension data in the card instance based on the data setting instruction and the data model to form a data structure of the data required by the data card.

[0093] It can be understood that in this embodiment, the data card creation instruction corresponds to the user's need to create a data card, the view adjustment instruction corresponds to the user's need to adjust each view component in the page, and the data setting instruction corresponds to the user's need to configure each data in the instance.

[0094] As an example, in this embodiment, the process of creating a data entity can be combined with Figure 6 To understand, the details are as follows: In the dashboard management list, select the created dashboard instance, display the preview page of the data card application, click Edit to enter the development page (dashboard) of the data card application, click Figure 6The left view displays comparison views (bar charts, stacked charts, horizontal bar charts, stacked horizontal bar charts), trend views (discount charts, stacked line charts, combination charts), distribution views (pie charts, doughnut charts, radar charts), relationship views (scatter plots), table views (detailed tables, summary tables) and geographic views (ZGIS charts, Geographic Information System); drag any view on the left to the canvas on the right to display the data of the view (different values ​​can be selected) and style page (different styles can be selected). The data page contains the data model (data set) that needs to be set and the chart type that the view can convert; in the data set position in the data page, select Switch Data Set to pop up the Switch Data Set page. Select a data set to preview the data of the data set and bind the data set to the selected view. After binding, the dimension fields and indicator fields of the data set (from the data model generated by the backend) are automatically displayed. The dimension fields and indicator fields can be dragged and converted to each other, and a new data set will be formed after the conversion; drag the dimension field to the sector label of the chart type to sort it, and the information corresponding to the dimension field can be displayed in the view; drag the indicator field to the axis value to set You can set aggregation information (including sum, average, maximum, minimum, count and other options), and you can also set axis value filtering (including equal to, less than, greater than, not equal to and other options); drag the indicator field or dimension field in the data set to the chart type filter to set the filtering conditions; drag the dimension field to the drill function page (drilling is to change the level of the dimension and transform the granularity of the analysis. It includes drill up and drill down. Through the wizard, users can define the summary rows of analysis factors. For example, for the sales situation of each region and each year, you can generate a total row of the region and the year, or you can generate a total row of the region or the year), and you can set the dimension data that can be accessed upward or downward; based on the above dragging and setting, you can eventually form the data structure required for the data card, which is applicable to data sets of all relational database types.

[0095] Step A30, sending the data structure to a backend to obtain a data entity corresponding to the data structure;

[0096] It should be noted that, in this embodiment, if a data card is to be developed, the data structure needs to be sent to the server for further processing, that is, SQL translation is performed to obtain the corresponding data entity, and then the development of the current data card is continued based on the data entity.

[0097] Step A40, performing data assembly and page rendering based on the data entity to obtain a data card corresponding to the data card creation instruction;

[0098] In this embodiment, after obtaining the data entity returned by the server, the data entity is assembled and rendered by the front-end page, so that the following Figure 7 Data card shown.

[0099] As an example, after a data card is generated, the user can click Save to complete the development of a single data card in the dashboard.

[0100] Step A50, iterating through the multiple data sets in the data model to obtain multiple data cards, so as to complete the construction of the data card application.

[0101] It should be noted that the data card application in this embodiment contains multiple data cards, so the development steps of the above-mentioned single data card need to be repeated multiple times. However, in the process of executing the above-mentioned data card development steps, users can change the data set selection, view selection, data setting and other aspects according to actual needs to ensure that the data card application can cover a variety of different data sets and adapt to more application scenarios.

[0102] In some feasible embodiments, the method for building the data card application may further include:

[0103] Step B, upon receiving a save instruction or offline information, sending a save request to the backend to save the data recorded in the current page into the database;

[0104] Step C: upon receiving a read instruction or re-online information, a read request is sent to the backend to restore the specified data in the database to the current page.

[0105] It should be noted that, in this embodiment, an automatic save mechanism is also provided. If the user does not click Save or the network is suddenly disconnected, the data in the version record will be automatically loaded the next time he enters the development page (dashboard) of the data card application; when the user clicks Save, the data in the version record will be deleted, and the location data of the data page, style page and data card will be saved to the master data.

[0106] As an example, the user can change the category axis in the data page in the development page (dashboard) of the data card application, and the data card on the left will synchronously display the changed data effect; the user can also change the view properties in the style page in the development page (dashboard) of the data card application, and the data card on the left will synchronously display the effect after the style change; the user can also change the chart type in the development page (dashboard) of the data card application, and the chart type of the data card on the left will switch synchronously; the above changes to the data page and style page will be synchronously fed back to the corresponding data card on the left; and changes in the position and shape of the data page, style page and data card will be automatically saved in the version record.

[0107] The present embodiment provides a method for building a data card application. In the method for building a data card application, the front end first responds to the input of basic information of the data source and sends the basic information of the data source to the back end to obtain a data model; then responds to a data card creation instruction and generates a data structure of data required for the data card based on the data card creation instruction and the data model; then sends the data structure to the back end to obtain a data entity corresponding to the data structure; then, data assembly and page rendering are performed based on the data entity to obtain a data card corresponding to the data card creation instruction; finally, multiple data cards are developed and iterated in combination with multiple data sets in the data model to complete the building of the data card application. This embodiment has the ability to convert data sources in different types of data sets into a visual state, and can unify the data standards of different types of data sets, thereby avoiding the problem of inconsistent database types and methods; this embodiment realizes efficient reuse, can abstract business needs, and share and reuse visual components, allowing business experts to focus on business needs efficiently and build data card applications more efficiently; this embodiment also adopts multi-data source adaptation, adopts unified SQL, unifies the differences in syntax and semantics of multiple data sources, and can access different types of data sources more widely and quickly; this embodiment is based on the data model method, so that the data model can be quickly applied to the data card by dragging and dropping, and can be quickly replaced in the data card, thereby improving the development efficiency of the data card; this embodiment is based on the automatic save mechanism, which realizes the effective protection and rollback mechanism of user achievements without the user's perception, thereby improving the user experience.

[0108] In addition, the present application embodiment also provides a data card application construction system, referring to Figure 8 The data card application construction system includes a front end 100 and a back end 200.

[0109] The front end 100 is used for responding to the input of basic information of the data source, sending the basic information of the data source to the back end 200 to obtain a data model;

[0110] The backend 200 is used to obtain basic information of the data source from the frontend 100, create multiple types of data sources based on the basic information of the data source; create multiple types of initial data sets based on each of the data sources; obtain data set operation instructions from the frontend 100, generate associated data sets based on the data set operation instructions and each of the initial data sets; perform data modeling based on each of the initial data sets and the associated data sets to obtain a data model; obtain a data structure generated based on the data model from the frontend 100, perform SQL translation on the data structure to obtain a corresponding data entity; return the data entity to the frontend 100, so that the frontend 100 completes the construction of the data card application based on the data entity;

[0111] The front end 100 is used to respond to a data card creation instruction, generate a data structure of data required for the data card based on the data card creation instruction and the data model; send the data structure to the back end 200 to obtain a data entity corresponding to the data structure; perform data assembly and page rendering based on the data entity to obtain a data card corresponding to the data card creation instruction; develop multiple data cards and iterate in combination with multiple data sets in the data model to complete the construction of the data card application.

[0112] The data card application building system provided in this embodiment and the data card application building method provided in the above embodiments belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as executing the data card application building method.

[0113] In addition, the embodiment of the present application also provides an electronic device, and the data card application construction method provided in the above embodiments can be executed by the back-end and front-end included in the data card application construction system, and the data card application construction system can be implemented by software and / or hardware and integrated in the electronic device. In this embodiment, the electronic device can be a mobile device such as a mobile phone, a notebook, and a tablet computer that can communicate with the network side.

[0114] Reference Fig. 9 , Fig. 9 The hardware structure diagram of an electronic device provided in one embodiment of the present application is shown in FIG. Fig. 9As shown, the electronic device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk storage. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0115] Those skilled in the art will understand that Fig. 9 The structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Fig. 9 As shown, the memory 1005 as a storage medium may include an operating system, a data storage module, a network communication module, a user interface module and a computer program.

[0116] exist Fig. 9 In the electronic device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in this embodiment can be set in the electronic device, and the electronic device calls the computer program stored in the memory 1005 through the processor 1001, and executes the method for building a data card application applied to the electronic device provided in any of the above embodiments.

[0117] The electronic device proposed in this embodiment and the method for building a data card application applied to an electronic device proposed in the above embodiment belong to the same inventive concept. The technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as the method for building a data card application.

[0118] In addition, an embodiment of the present application also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, a method for building a data card application provided in any of the above embodiments is implemented.

[0119] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0120] The above is a specific description of the preferred implementation of the embodiments of the present application, but the embodiments of the present application are not limited to the above-mentioned implementation methods. Technical personnel familiar with the field can also make various equivalent modifications or substitutions without violating the spirit of the embodiments of the present application. These equivalent modifications or substitutions are all included in the scope defined by the claims of the embodiments of the present application.

Claims

1. A method for building a data card application, characterized in that: The method for building the data card application is applied to the back end, including: Obtain basic data source information from the front end, and create multiple types of data sources based on the basic data source information; Creating multiple types of initial data sets based on the data sources; Acquire a data set operation instruction from the front end, and generate a related data set based on the data set operation instruction and each of the initial data sets; Performing data modeling based on each of the initial data sets and the associated data sets to obtain a data model; Obtaining a data structure generated based on the data model from the front end, and performing SQL translation on the data structure to obtain a corresponding data entity; The data entity is returned to the front end so that the front end completes the construction of the data card application based on the data entity.

2. The method for building a data card application according to claim 1, characterized in that: The initial data set includes a file type data set and a data source data set. The step of generating an associated data set based on the data set operation instruction and each of the initial data sets includes: Generate a multi-branch tree structure based on the data set operation instruction, the file type data set and the data source data set; The multi-branch tree structure is parsed and assembled, and associated field information is obtained in combination with a recursive iterative algorithm, and an associated data set is generated based on the associated field information.

3. The method for building a data card application according to claim 1, characterized in that: The step of performing data modeling based on each of the initial data sets and the associated data sets to obtain a data model comprises: Processing the metadata of each of the initial data sets and the associated data sets in a unified manner to obtain a standard data set; Performing dimensional measurement modeling on the standard data set to obtain dimension fields and indicator fields; The standard data set is annotated based on the dimension field and the indicator field to obtain a data model.

4. The method for building a data card application according to claim 1, characterized in that: The step of performing SQL translation on the data structure to obtain the corresponding data entity comprises: Generate a unified SQL string based on the attributes of the data structure; Performing SQL translation on the unified SQL string based on an SQL translation engine to obtain a dialect SQL string; The corresponding data entity is obtained from the database based on the dialect SQL character string.

5. A method for building a data card application, characterized in that: The method for building the data card application is applied to the front end, including: In response to the input of basic information of the data source, the basic information of the data source is sent to the backend to obtain a data model; In response to a data card creation instruction input, generating a data structure of data required for the data card based on the data card creation instruction and the data model; Sending the data structure to a backend to obtain a data entity corresponding to the data structure; Performing data assembly and page rendering based on the data entity to obtain a data card corresponding to the data card creation instruction; Iteration is performed in combination with multiple data sets in the data model to obtain multiple data cards to complete the construction of the data card application.

6. The method for building a data card application as claimed in claim 5, characterized in that: The step of generating a data structure of data required for the data card based on the data card creation instruction and the data model comprises: Create a corresponding card instance based on the data card creation instruction and the data model; In response to a view adjustment instruction input, obtaining a corresponding view from the data model based on the view adjustment instruction and placing it into the card instance; In response to the input of the data setting instruction, the dimension data is set in the card instance based on the data setting instruction and the data model to form a data structure of the data required by the data card.

7. The method for building a data card application as claimed in claim 5, characterized in that: The method for building the data card application also includes: When receiving a save instruction or offline information, a save request is sent to the backend to save the data recorded in the current page into the database; When a read instruction or re-online information is received, a read request is sent to the backend to restore the specified data in the database to the current page.

8. A data card application construction system, characterized in that: The data card application construction system includes a front end and a back end. The front end is used for responding to the input of basic information of the data source, sending the basic information of the data source to the back end to obtain the data model; The backend is used to obtain basic information of the data source from the frontend, create multiple types of data sources based on the basic information of the data source; and create multiple types of initial data sets based on each of the data sources; Acquire a data set operation instruction from the front end, and generate a related data set based on the data set operation instruction and each of the initial data sets; Performing data modeling based on each of the initial data sets and the associated data sets to obtain a data model; Acquire the data structure generated based on the data model from the front end, perform SQL translation on the data structure to obtain the corresponding data entity; return the data entity to the front end, so that the front end completes the construction of the data card application based on the data entity; The front end is used to respond to the data card creation instruction, generate a data structure of data required for the data card based on the data card creation instruction and the data model; send the data structure to the back end to obtain a data entity corresponding to the data structure; perform data assembly and page rendering based on the data entity to obtain a data card corresponding to the data card creation instruction; Iteration is performed in combination with multiple data sets in the data model to obtain multiple data cards to complete the construction of the data card application.

9. An electronic device, characterized in that: The electronic device comprises: a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements a method for constructing a data card application as claimed in any one of claims 1 to 4 and 5 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for building a data card application according to any one of claims 1 to 4 and 5 to 7 is implemented.