CN118170767A

CN118170767A - Data management method, device and storage medium

Info

Publication number: CN118170767A
Application number: CN202410586229.1A
Authority: CN
Inventors: 王春龙; 杨波; 杨丰; 胡微微
Original assignee: Shenzhen Qixun Xinyou Technology Co ltd
Current assignee: Shenzhen Qixun Xinyou Technology Co ltd
Priority date: 2024-05-13
Filing date: 2024-05-13
Publication date: 2024-06-11

Abstract

The application discloses a data management method, equipment and a storage medium, which relate to the technical field of data processing and disclose the data management method, comprising the following steps: outputting a service demand configuration interface when receiving a wide table construction instruction; determining or acquiring demand data based on the service demand configuration action received by the service demand configuration interface; extracting key fields and parameter fields according to the demand data; determining a programming language code segment according to the key field and the parameter field; and transmitting the key fields and the parameter fields as parameters to the programming language code segment, and executing the programming language code segment to generate a target wide table. The user who does not understand the code writing technology can obtain the automatically generated wide table by inputting the service requirement, and the beneficial effect of reducing the technical threshold of the wide table construction is achieved.

Description

Data management method, device and storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a data management method, a data management device, and a readable storage medium.

Background

The large wide table is a database table structure for storing a large amount of data, which improves data processing efficiency by merging a plurality of narrow tables containing data of one subject only into one wide table containing data of a plurality of subjects.

In the construction of large broad tables, it is often necessary for a skilled artisan to use database languages, such as SQL, and data processing tools, such as ETL tools, to conduct targeted design and construction after collecting business needs of each department.

Thus, the construction of a large wide table has certain threshold requirements for code writing technology.

The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present application and is not intended to represent an admission that the foregoing is prior art.

Disclosure of Invention

The application mainly aims to provide a data management method, data management equipment and a readable storage medium, and aims to solve the technical problem that the construction of a large-width table has a certain threshold requirement on a code writing technology.

In order to achieve the above object, the present application provides a data management method, which includes:

outputting a service demand configuration interface when receiving a wide table construction instruction;

determining or acquiring demand data based on the service demand configuration action received by the service demand configuration interface;

extracting key fields and parameter fields according to the demand data;

Determining a programming language code segment according to the key field and the parameter field;

and transmitting the key fields and the parameter fields as parameters to the programming language code segment, and executing the programming language code segment to generate a target wide table.

In one embodiment, after the step of transferring the key field and the parameter field as parameters to the programming language code segment and executing the programming language code segment to generate the target broad table, the method further includes:

outputting a target broad table editing interface, and receiving authority configuration actions of a user based on the broad table configuration interface;

Determining or acquiring authority configuration information based on the authority configuration action, and determining the authority range of each role by analyzing the authority configuration information, wherein the authority range comprises a data access range, a data operation type and a data access level;

and implementing authority control in the target wide table according to the authority range of each role.

In an embodiment, the step of implementing authority control in the target wide table according to the authority range of each role includes:

according to the authority range of each role, determining a visualization realization tool corresponding to each role, wherein the visualization realization tool comprises at least one of a view creation tool, a front-end tool and a middleware;

And calling the visual realization tool based on the authority range and the target wide table of each role, and creating a data access interface corresponding to each role.

In an embodiment, the step of determining a visualization implementation tool corresponding to each role according to the authority range of each role includes:

determining a first visual implementation tool corresponding to each role according to the authority range of each role;

detecting a prior art stack and determining a second visualization implementation tool compatible with the prior art stack;

evaluating the display effect of the first visual implementation tool and the second visual implementation tool;

and determining a visual implementation tool to be called according to the display effect.

In an embodiment, the step of determining the visual implementation tool to be invoked according to the display effect further includes:

when the display effect of the second visual realization tool is better than that of the first visual realization tool;

Evaluating computational overhead of the second visualization implementation tool and the first visualization implementation tool;

When the calculation cost of the second visual implementation tool is smaller than or equal to that of the first visual implementation tool, determining that the second visual implementation tool is the visual implementation tool to be called;

And when the calculation cost of the second visual implementation tool is greater than that of the first visual implementation tool, determining that the first visual implementation tool is the visual implementation tool to be called.

In an embodiment, after the step of creating the data access interface corresponding to each role, the step of calling the visualization implementation tool based on the authority range and the target wide table of each role further includes:

when a data access request sent by a user is received, role information corresponding to the user is determined;

Acquiring a data access target interface associated with the role information;

and outputting the data access target interface to the user so as to provide data access service.

In an embodiment, after the step of outputting the data access target interface to the user to provide the data access service, the method further includes:

Receiving a data operation instruction of the user based on the data access target interface;

judging whether the data query instruction exceeds the authority range of the user or not by analyzing the data operation instruction;

And when the data query instruction exceeds the authority range of the user, returning error information and prompting the user to have insufficient authority.

In addition, to achieve the above object, the present application also proposes a data management apparatus comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the data management method as described above.

Furthermore, to achieve the above object, the present application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the steps of the data management method as described above.

One or more technical schemes provided by the application have at least the following technical effects:

According to the application, when receiving the wide table construction instruction, a service demand configuration interface is output; determining or acquiring demand data based on the service demand configuration action received by the service demand configuration interface; extracting key fields and parameter fields according to the demand data; determining a programming language code segment according to the key field and the parameter field; and transmitting the key fields and the parameter fields as parameters to the programming language code segment, and executing the programming language code segment to generate a target wide table. The user who does not understand the code writing technology can obtain the automatically generated wide table by inputting the service requirement, and the beneficial effect of reducing the technical threshold of the wide table construction is achieved.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

In order to more clearly illustrate the embodiments of the application or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.

FIG. 1 is a flowchart of a data management method according to a first embodiment of the present application;

FIG. 2 is a diagram of a configuration interface of demand data according to a first embodiment of the data management method of the present application;

FIG. 3 is a flowchart of a second embodiment of a data management method according to the present application;

FIG. 4 is a flowchart of a fourth embodiment of a data management method according to the present application;

fig. 5 is a schematic device structure diagram of a hardware running environment related to a data management method in an embodiment of the present application.

The achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the technical solution of the present application and are not intended to limit the present application.

For a better understanding of the technical solution of the present application, the following detailed description will be given with reference to the drawings and the specific embodiments.

The main solutions of the embodiments of the present application are: outputting a service demand configuration interface when receiving a wide table construction instruction; determining or acquiring demand data based on the service demand configuration action received by the service demand configuration interface; extracting key fields and parameter fields according to the demand data; determining a programming language code segment according to the key field and the parameter field; and transmitting the key fields and the parameter fields as parameters to the programming language code segment, and executing the programming language code segment to generate a target wide table.

In this embodiment, for convenience of description, the following description will be made with the identification data management system as the execution subject.

Because the prior art is a broad-table build, it generally requires a skilled artisan to use database languages such as SQL and data processing tools such as ETL tools to conduct targeted design and build after collecting business needs of each department. The construction of the large wide table has a certain threshold requirement on the code writing technology. The application provides a solution, which enables users who do not understand the code writing technology to obtain the automatically generated wide table through inputting service requirements on the data management system, and achieves the beneficial effect of reducing the technical threshold of the wide table construction.

The data management system abstracts the broad table construction process into a service demand configuration interface and programming language code segment mapping, so that the service demand input by a user is converted into an automatically generated broad table, and the technical threshold of broad table construction is reduced.

The execution subject of the present embodiment may be a data management system, or may be a computing service device having functions of data processing, network communication, and program running, such as a tablet computer, a personal computer, a mobile phone, or a data management device capable of implementing the above functions, which is not particularly limited in this embodiment. The present embodiment and the following embodiments will be described below using a data management system as an execution subject.

Based on this, an embodiment of the present application provides a data management method, and referring to fig. 1, fig. 1 is a schematic flow chart of a first embodiment of the data management method of the present application.

In this embodiment, the data management method includes steps S10 to S50:

step S10, outputting a service demand configuration interface when receiving a wide table construction instruction;

it should be noted that the wide table construction instruction refers to a command or a request for starting the wide table construction process. In the prior art, broad table construction has typically required a skilled artisan to do so using database languages, such as SQL, and data processing tools, such as ETL tools. In the present application, the broad table construction command may be a simple operation command such as clicking a button, sending a message, or executing a command line command.

Additionally, it should be noted that the business requirement configuration interface is a graphical interface for receiving user input of business requirements. On this interface, the user can select and set related options, such as data source, data type, data processing mode, etc., according to his own needs.

It can be understood that when the data management system receives the wide table construction instruction, the wide table construction flow is triggered, and the service requirement of the non-technical user is directly acquired through the output service requirement configuration interface, compared with the prior art that the non-technical user transfers the service requirement to the technical user, and the technical user manually creates the wide table, the technical threshold of wide table creation is reduced, the time and energy of manual operation are greatly reduced, and the working efficiency is improved.

Step S20, determining or acquiring demand data based on the service demand configuration action received by the service demand configuration interface;

It should be noted that, the service requirement configuration action refers to a series of operations performed by the user on the service requirement configuration interface, and these operations are used to input or upload the service requirement to the data management system. The demand data is a set of information acquired from the service demand configuration interface for describing the specific service demands of the user. In order to make a wide table according to the demand data, the wide table can comprise data sources, data types, data use scenes, data processing modes and the like. The data types include structured data, such as data in a relational database, semi-structured data, such as XML, JSON format data, unstructured data, such as text, pictures, video, and the like. Different data types require different data import methods. Data sources, including internal business system databases, external data sources, such as website disclosure data, third party data providers, and manually entered data. Data from different data sources may need to be imported through different technical means such as data extraction and data synchronization. Data processing modes such as data cleaning, data conversion, data encryption and the like. In the data importing process, data needs to be preprocessed to meet the data management policy and business requirements of a large-width table.

It will be appreciated that the business requirement configuration actions aim to simplify and abstract complex programming operations so that non-technical users can also easily accomplish the requirement setting for broad table construction. In practical application, the service requirement configuration action can be used for selecting a specific requirement data uploading mode, and finishing the input of the requirement data by clicking a button, dragging a field, filling in a text box and the like. Referring to fig. 2, fig. 2 is a schematic diagram of a demand data configuration interface according to a first embodiment of the data management method of the present application.

In a first possible data upload embodiment, the data management system supports file selection upload, and the user may select a desired data file from the local file system for upload by clicking a "select file" button. The data management system obtains the demand data by reading the file contents selected by the user.

In a second possible data uploading implementation, the data management system supports drag uploading, and the user can directly drag the required data file from the local file system to the uploading area, and the data management system acquires the required data by reading the file content dragged by the user.

In a third possible data uploading implementation mode, the data management system supports link sharing uploading, and a user can upload a required data file to a cloud storage service, acquire a file link and share the link to an uploading area to realize file uploading. The data management system obtains the demand data by accessing the links shared by the users, downloading the demand data files and reading the content.

In a fourth possible data uploading embodiment, the data management system supports scanning uploading, and if the required data file is a paper version, the user can convert the paper file into a digital file through the scanning device and upload the digital file to the required data configuration interface. The data management system acquires the demand data by reading the digital file contents acquired by the scanning device.

In a fifth possible data upload embodiment, the data management system supports copy-and-paste upload, and if the required data file content already exists in the clipboard, the user can copy-and-paste the content directly to the upload area to effect file upload. The data management system obtains the demand data by reading the written content.

Step S30, extracting key fields and parameter fields according to the requirement data;

it should be noted that the key field is a field for uniquely identifying the data record, such as an order ID, a customer ID, and the like. The parameter field is a field for filtering, sorting or calculating, such as product category, sales, date, etc.

Acquiring raw data to be processed according to a data source and a data range included in the demand data, wherein the data source possibly comprises a database, a file, an application program interface and the like; the data range may relate to a particular time period, region, department, etc.; and performing operations such as data cleaning, data conversion, data aggregation and the like on the original data according to the data processing mode included in the demand data. And extracting the fields of the processed original data, and identifying and extracting key fields and parameter fields in the original data according to the use situations of the data such as data analysis, report display, data mining and the like and the data structure.

Step S40, determining a programming language code segment according to the key field and the parameter field;

Based on information such as type, name, length, precision, etc. of the key field and the parameter field, the structure of the wide table, such as table name, field name, data type, index, etc., can be determined. Meanwhile, according to the types of the key fields and the parameter fields and the corresponding service scenes, the programming language code segments which need to be used can be determined, and the functions of data insertion, data updating, data deleting and the like are corresponding.

And S50, transmitting the key fields and the parameter fields as parameters to the programming language code segment, and executing the programming language code segment to generate a target wide table.

Key and parameter fields may be considered as input and configuration information in the construction of a broad table, which are passed to the code segment in the form of variables or lists, where they are then used for corresponding data processing and broad table generation operations.

For example, if the key field is an integer type field, it may be passed to the code segment as an integer variable; if the parameter field is a string type field, it may be passed to the code segment as a string table. In the code segment, the parameters can be used for carrying out operations such as data query, data conversion, data verification and the like, and finally, the target wide table is generated.

It will be appreciated that in passing parameters it is necessary to ensure that the type and format of the parameters match the expected inputs of the code segments, which may otherwise result in a failure of the code segments to execute or a data processing error. Accordingly, corresponding type conversion and format processing are also required when parameters are transferred.

As can be seen from the foregoing, in this embodiment, the broad form construction process is abstracted into the service requirement configuration interface and the programming language code section mapping through the data management system, so that a user who does not understand the code writing technology can also obtain an automatically generated broad form through inputting the service requirement on the data management system, so that the service requirement input by the user is converted into the automatically generated broad form, and the technical threshold for broad form construction is reduced.

In the second embodiment of the present application, the same or similar content as in the first embodiment of the present application may be referred to the above description, and will not be repeated. On this basis, referring to fig. 3, fig. 3 is a flowchart illustrating a second embodiment of the data management method according to the present application, and after step S50, the data management method further includes steps S51 to S53:

Step S51, outputting a target broad table editing interface, and receiving authority configuration actions of a user based on the broad table configuration interface;

After detecting the generation of the target broad form, the data management system outputs a target broad form editing interface so that the user can perform authority configuration on the interface. The broad table configuration interface may include various controls, such as text boxes, drop down lists, check boxes, etc., for the user to enter or select desired rights configuration information. The user performs operations on the interface, such as setting roles, assigning rights, etc., which are called rights configuration actions.

Step S52, determining or acquiring authority configuration information based on the authority configuration action, and determining the authority range of each role by analyzing the authority configuration information, wherein the authority range comprises a data access range, a data operation type and a data access level;

The specific uploading and acquiring embodiments of the permission configuration information refer to the uploading and acquiring of the requirement data in step S20, and this embodiment is not repeated here again. The data management system determines the authority range of each role by analyzing the authority configuration information. The scope of rights may include a scope of access to data, including a time scope, a geographic scope, a business object scope, etc., for example, some users may only have access to data of a particular region, a particular time period, or a particular business type. By setting the data range, it can be ensured that the user can only access data related to his business and authorized. And also data operation types such as read, modify, delete, etc. And data access levels such as normal users, administrators, etc.

Illustratively, there is a broad table containing the following fields: user ID (user_id), name (name), gender (gender), age (age), position (position), department (department), phone number (phone_number), and electronic mailbox (email). We have the following three roles: common staff (employee), department manager (manager), and administrator (admin).

Common staff (employee): the ordinary staff can only inquire and modify own information, and cannot view or modify the information of other colleagues. Thus, for a common employee, we can set permissions on a broad table so that it can only access and modify the same record as its own user_id.

Department manager (manager): the department director may view and modify the information of the department staff where it is located, but not view or modify the data of other departments. To this end, we can set permissions on a broad table for the department director to be able to access and modify the same records as themselves department.

Administrator (admin): the administrator has the highest authority to access and modify all the data in the wide table. Thus, for an administrator, we can grant all of their rights on a broad table.

It will be appreciated that after implementing the above rights control, the user of each character can only access and modify the data in the broad table within the scope of the authorization. The complex authority setting ensures the security of data and meets the actual demands of users with different roles.

It should be noted that this is just a simple example, and in actual practice, more complex rights setting may be required according to the service scenario and requirements, and the present application is not limited.

And step S53, performing authority control in the target wide table according to the authority range of each role.

It should be appreciated that embodiments of rights control may be implemented by providing customized data access interfaces for different users or roles. The method can facilitate the business department to inquire and analyze the data according to the own requirements, and simultaneously can avoid directly exposing the bottom data and ensure the data safety.

In a first embodiment of the rights control, corresponding views may be created according to the scope of rights of different users or roles, so that users can only access the data they have rights to view. For example, for an average employee, a view may be created that contains only the fields that it has access to; for an administrator, a view may be created that contains all of the fields. Thus, the user is actually querying the views rather than directly accessing the large wide table when querying the data. Through the broad table + view, the problem of sensitive data or data to be protected can be solved. The authority access problem of data stored in a json format in a certain field can be solved by subdividing attribute contents in json by roles, for example, json contents of a certain field are { "a": "income", "b": "expenditure" }, and if only a certain role is allowed to view the a field, then a field can be added to the original stored json field to analyze the a attribute.

In a second permission control embodiment, accessible data fields may be dynamically displayed in the front-end interface according to different permissions of the user or role. For example, dynamic rendering of the table columns may be implemented by JavaScript (object and event driven client scripting language based), HTML (Hypertext Markup Language ), and CSS (CASCADING STYLE SHEET, cascading style sheets) techniques, etc., displaying only fields that the user has permission to view. Thus, the fields that the user sees at the front-end interface are those that they have access to.

In a third rights control embodiment, a middleware system may be developed that is responsible for handling the user's data requests. The middleware system screens and processes the data in the large-width table according to the identity and the authority of the user, and then returns the data meeting the authority requirement to the user. Thus, the user is actually requesting the middleware system when requesting data, rather than directly accessing the large wide table.

It will be appreciated that in practical applications, various ways may be used in combination to achieve more efficient, secure and easy-to-use data access rights control. For example, the manner in which views are created may be used to limit the scope of data access while the customized data access interface is provided by modifying the front-end interface or using middleware.

In summary, the abstract layer for data access is provided in this embodiment, so that the business department can query and analyze data according to its own needs, and meanwhile, directly exposing the underlying data can be avoided, so as to ensure data security.

In the third embodiment of the present application, the same or similar contents as those of the above embodiment can be referred to the above description, and the description is omitted. On this basis, step S53 further includes steps S54 to S55:

s54, according to the authority range of each role, determining a visualization realization tool corresponding to each role, wherein the visualization realization tool comprises at least one of a view creation tool, a front end tool and a middleware;

In a first possible implementation of determining the visualization implementation tool, the appropriate view creation tool, front end tool, middleware, etc. visualization implementation tools are selected according to the scope of authority of each character. For example, for an administrator role, more powerful view creation tools and middleware may need to be used in order to implement more complex data visualization and interaction functions; for a common user role, only a simple front-end tool may be needed to expose the data.

In a second possible implementation of the determining visualization implementation tool, the step S53 may include:

step A11, determining a first visual implementation tool corresponding to each role according to the authority range of each role;

in the embodiment, referring to step S54, the details are not missed here.

Step A12, detecting a prior art stack and determining a second visualization implementation tool compatible with the prior art stack;

it is to be appreciated that the technology stack includes programming languages, frameworks, libraries, etc. that are used.

From the prior art stack, a second visualization implementation tool compatible with the prior art stack is determined. For example, if the data management system has used a certain front-end framework, the modification of the front-end interface may be prioritized. If the data management system already uses some kind of middleware product, the use of middleware may be prioritized.

Step A13, evaluating the display effect of the first visual realization tool and the second visual realization tool;

By comparing the differences in view components, style designs, data processing, and interactive functions of the two tools, it is determined which tool has a better display.

And step A14, determining a visual implementation tool to be called according to the display effect.

In an embodiment of determining a visual implementation tool to be called, selecting the visual implementation tool with better display effect as the visual implementation tool to be called.

In another embodiment for determining a visual implementation to be invoked, the step a14 includes:

Step B11, when the display effect of the second visual realization tool is better than that of the first visual realization tool;

step B12, evaluating the calculation cost of the second visualization realization tool and the first visualization realization tool;

Step B13, when the calculation cost of the second visual implementation tool is smaller than or equal to that of the first visual implementation tool, determining that the second visual implementation tool is the visual implementation tool to be called;

If the display effect of the second visual implementation tool is better than that of the first visual implementation tool, but the calculation cost of the second visual implementation tool is less than or equal to that of the first visual implementation tool, the second visual implementation tool can be determined to be the visual implementation tool to be called. Because in this case the second visualization implementation tool can provide better performance while guaranteeing the display effect.

And step B14, when the calculation cost of the second visual implementation tool is larger than that of the first visual implementation tool, determining that the first visual implementation tool is the visual implementation tool to be called.

But if the computational overhead of the second visualization implementation tool is greater than the computational overhead of the first visualization implementation tool, then the first visualization implementation tool should be determined to be the visualization implementation tool to be invoked. Because in this case the first visualization implementing tool may provide better performance, while the display effect advantage of the second visualization implementing tool is insufficient to compensate for its performance disadvantages.

S55, calling the visual realization tool based on the authority range and the target wide table of each role, and creating a data access interface corresponding to each role.

After the visualization realization tools corresponding to the roles are determined, the corresponding visualization realization tools can be called based on the authority range and the target wide table of the roles, and the data access interface corresponding to the roles is created. In particular, presentation content and operational functionality of the data access interface may be determined based on the scope of authority of each character, and then the interface is created using a corresponding visualization implementation tool. For example, view creation tools may be used to create view components such as data tables, charts, etc., front end tools may be used to implement layout and style design of interfaces, middleware may be used to implement functions such as filtering, sorting, paging, etc. of data.

In summary, according to the embodiment, by determining the corresponding visualization implementation tool according to the authority range of each role, unnecessary computation overhead can be avoided while ensuring the security and privacy of data. By evaluating the different filtering logic to determine the display effect and computational overhead of the alternative visualization implementation tool, an optimal balance between the effect and computational overhead of the data visualization may be achieved.

Based on the above embodiments of the present application, in the fourth embodiment of the present application, the same or similar contents as those of the above embodiments may be referred to the above description, and the description thereof will not be repeated. On this basis, referring to fig. 4, fig. 4 is a flowchart of a fourth embodiment of the data management method according to the present application, and after the step S55, steps S56 to S58 are further included:

step S56, when a data access request sent by a user is received, role information corresponding to the user is determined;

When a user logs in to the system, login information such as a user name and a password is input. When a data access request sent by a user is received, the system can verify whether the login information of the user is correct by comparing the user information in the database, if so, the corresponding role information is determined according to the mapping relation between the login information of the user and the role information of the user, for example, the user name, the password, the role and other information of the user are stored in the database, and the system can acquire the role information of the user by querying the database.

Step S57, acquiring a data access target interface associated with the role information;

The method for generating the data access target interface associated with the role information refers to the third embodiment, and this embodiment is not described in detail herein.

Step S58, outputting the data access target interface to the user to provide a data access service.

In one possible implementation of providing the data access service, step S58 further includes steps S59 to S61:

step S59, receiving a data operation instruction of the user based on the data access target interface;

And receiving a data operation instruction of a user through a data access target interface so as to realize the operation and management of the data.

Step S60, judging whether the data query instruction exceeds the authority range of the user by analyzing the data operation instruction;

When analyzing a data operation instruction of a user, judging whether the instruction accords with the authority range of the user or not so as to ensure that the user can only access and operate the data in the authority range;

Step S61, when the data query instruction exceeds the authority range of the user, returning error information and prompting the user to have insufficient authority.

In a first possible query failure embodiment, if the user attempts to access a field that is not authorized to be viewed, the query may fail directly, returning an error message. For example, the database system may throw an exception with insufficient rights, prompting the user that there is insufficient rights to access the specified fields.

In a second possible query failure embodiment, the data management system automatically hides or replaces fields that the user has no permission to view with other values (e.g., NULL or placeholders) when the data query instructions are outside the user's permission range. So that the user can still query the data of other fields with access permission, but cannot see the sensitive information.

In a third possible embodiment of query failure, the system may prompt the user to apply for the corresponding rights when the user attempts to access the no rights field. The user may obtain access rights by submitting an application or requesting an administrator approval.

In summary, in this embodiment, by determining the role information corresponding to the user and matching the role information with the data access target interface associated with the role information, it is ensured that only the authorized user can access the data, thereby ensuring the security and privacy of the data.

By outputting the data access target interface to the user and receiving the data operation instruction of the user based on the interface, more convenient and efficient data access service can be provided, and user experience is improved.

By analyzing the data operation instruction of the user and judging whether the data query instruction exceeds the authority range of the user, the data can be finely managed, and the user can only access and operate the data in the authority range.

By decoupling the role information of the user and the data access target interface, the expandability and maintainability of the system can be improved, and the subsequent function expansion and optimization can be facilitated.

It should be noted that the foregoing examples are only for understanding the present application, and are not meant to limit the x data management method of the present application, and more forms of simple transformation based on the technical concept are all within the scope of the present application.

The present application provides a data management apparatus, the data management apparatus comprising: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the data management method in the first embodiment.

Referring now to fig. 5, a schematic diagram of a data management device suitable for use in implementing embodiments of the present application is shown. The data management device in the embodiment of the present application may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (Personal DIGITAL ASSISTANT: personal digital assistant), a PAD (Portable Application Description: tablet computer), a PMP (Portable MEDIA PLAYER: portable multimedia player), an in-vehicle terminal (e.g., an in-vehicle navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. The data management device shown in fig. 5 is only an example, and should not impose any limitation on the functions and scope of use of the embodiments of the present application.

As shown in fig. 5, the data management apparatus may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access Memory (RAM: random Access Memory) 1004. In the RAM1004, various programs and data required for the operation of the data management apparatus are also stored. The processing device 1001, the ROM1002, and the RAM1004 are connected to each other by a bus 1005. An input/output (I/O) interface 1006 is also connected to the bus. In general, the following systems may be connected to the I/O interface 1006: input devices 1007 including, for example, a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, and the like; an output device 1008 including, for example, a Liquid crystal display (LCD: liquid CRYSTAL DISPLAY), a speaker, a vibrator, and the like; storage device 1003 including, for example, a magnetic tape, a hard disk, and the like; and communication means 1009. The communication means 1009 may allow the data management device to communicate wirelessly or by wire with other devices to exchange data. While a data management device having various systems is shown in the figures, it should be understood that not all of the illustrated systems are required to be implemented or provided. More or fewer systems may alternatively be implemented or provided.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the ROM 1002. The above-described functions defined in the method of the disclosed embodiment of the application are performed when the computer program is executed by the processing device 1001.

The data management equipment provided by the application adopts the data management method in the embodiment, and can solve the technical problem of data management. Compared with the prior art, the beneficial effects of the data management device provided by the application are the same as those of the data management method provided by the above embodiment, and other technical features of the data management device are the same as those disclosed by the method of the previous embodiment, and are not repeated here.

It is to be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the description of the above embodiments, particular features, structures, materials, or characteristics may be combined in any suitable manner in any one or more embodiments or examples.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

The present application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon for performing the data processing method in the above-described embodiments.

The computer readable storage medium provided by the present application may be, for example, a U disk, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access Memory (RAM: random Access Memory), a Read-Only Memory (ROM: read Only Memory), an erasable programmable Read-Only Memory (EPROM: erasable Programmable Read Only Memory or flash Memory), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this embodiment, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device. Program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to: wire, fiber optic cable, RF (Radio Frequency), and the like, or any suitable combination of the foregoing.

The above-described computer-readable storage medium may be contained in a data management apparatus; or may exist alone without being assembled into the data management device.

The computer-readable storage medium carries one or more programs that, when executed by a data management device, cause the data management device to: and (5) data management.

Computer program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN: local Area Network) or a wide area network (WAN: wide Area Network), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules involved in the embodiments of the present application may be implemented in software or in hardware. Wherein the name of the module does not constitute a limitation of the unit itself in some cases.

The readable storage medium provided by the application is a computer readable storage medium, and the computer readable storage medium stores computer readable program instructions (i.e. a computer program) for executing the data management method, so that the technical problem of data management can be solved. Compared with the prior art, the beneficial effects of the computer readable storage medium provided by the application are the same as those of the data management method provided by the above embodiment, and are not described herein.

The foregoing description is only a partial embodiment of the present application, and is not intended to limit the scope of the present application, and all the equivalent structural changes made by the description and the accompanying drawings under the technical concept of the present application, or the direct/indirect application in other related technical fields are included in the scope of the present application.

Claims

1. A method of data management, said method comprising the steps of:

extracting key fields and parameter fields according to the demand data;

2. The method of claim 1, wherein after the steps of passing the key field and the parameter field as parameters to the programming language code segment and executing the programming language code segment to generate the target width table, further comprising:

3. The method of claim 2, wherein the step of implementing rights control in the target wide table according to the rights range of each character comprises:

4. The method of claim 3, wherein the step of determining a visualization implementation tool corresponding to each character according to the scope of authority of each character comprises:

5. The method of claim 4, wherein the step of determining a visualization implementation tool to invoke based on the display effect further comprises:

6. The method of claim 3, wherein the step of calling the visualization implementation tool to create the data access interface corresponding to each role based on the scope of authority and the target wide table of each role further comprises, after:

Acquiring a data access target interface associated with the role information;

7. The method of claim 6, wherein after the step of outputting the data access target interface to the user to provide a data access service, further comprising:

8. A data processing apparatus, the apparatus comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the data management method according to any one of claims 1 to 7.

9. A storage medium, characterized in that the storage medium is a computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, realizes the steps of the data management method according to any one of claims 1 to 7.