CN113392382A - Data management method, electronic device and readable storage medium - Google Patents
Data management method, electronic device and readable storage medium Download PDFInfo
- Publication number
- CN113392382A CN113392382A CN202110563583.9A CN202110563583A CN113392382A CN 113392382 A CN113392382 A CN 113392382A CN 202110563583 A CN202110563583 A CN 202110563583A CN 113392382 A CN113392382 A CN 113392382A
- Authority
- CN
- China
- Prior art keywords
- data
- subtask
- user identifier
- determining
- instruction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The invention discloses a data management method, an electronic device and a readable storage medium, wherein the data management method comprises the following steps: acquiring a role label associated with a first user identifier, and determining first authority information associated with the role label; task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data; and determining first subtask data corresponding to the first user identifier according to a matching result between the first authority information and the second authority information, and storing the first user identifier and the first subtask data in an associated manner. According to the method and the device, the subtask data corresponding to the user identification and the authority information are associated according to the authority information associated with the role label associated with the user identification, so that the problem of low data confidentiality caused by the fact that the authority information corresponding to the user identification is set independently is prone to error is solved.
Description
Technical Field
The present invention relates to the field of collaborative office, and in particular, to a data management method, an electronic device, and a readable storage medium.
Background
With the development of enterprise informatization, more and more data are stored in the form of electronic files, when the collaborative verification of other departments is needed, electronic documents are required to be sent to the other departments, and the data is verified by personnel distributed inside the other departments for collaboration.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a data management method, which aims to associate subtask data corresponding to user identification and authority information according to the authority information associated with a role label associated with the user identification, and solves the problem that the data confidentiality is low because the authority information corresponding to the user identification is set independently is easy to make mistakes.
In order to achieve the above object, the present invention provides a data management method applied to an electronic device, the data management method including the steps of:
acquiring a role label associated with a first user identifier, and determining first authority information associated with the role label;
task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data;
and determining first subtask data corresponding to the first user identifier according to a matching result between the first authority information and the second authority information, and storing the first user identifier and the first subtask data in an associated manner.
Further, after the step of determining first subtask data corresponding to the first user identifier according to a matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in an associated manner, the method further includes:
determining the total number of subtasks corresponding to each role label;
determining the task state corresponding to each role label as the number of completed subtasks;
determining the task progress of each role label according to the total number of the subtasks corresponding to each role label and the number of the completed subtasks;
and outputting the task progress corresponding to each role label.
Further, after the step of determining first subtask data corresponding to the first user identifier according to a matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in an associated manner, the method further includes:
when a viewing instruction is received, determining the user identification corresponding to the viewing instruction;
and determining subtask data associated with the user identifier, and outputting the subtask data.
Further, after the step of determining first subtask data corresponding to the first user identifier according to a matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in an associated manner, the method further includes:
receiving a modification instruction of data;
determining second subtask data corresponding to the modification instruction of the data;
and updating the second subtask data according to the modification instruction of the data.
Further, before the step of updating the second subtask data according to the modification instruction of the data, the method further includes:
determining a second user identifier corresponding to the modification instruction of the data, wherein the second user identifier is a user identifier corresponding to a user initiating the modification instruction of the data;
acquiring modification permission associated with the second user identifier;
and when the modification authority comprises the modification authority of the second subtask data, executing the modification instruction according to the data to update the second subtask data.
Further, before the step of obtaining a role tag associated with a first user identifier and determining first permission information associated with the role tag, the method further includes:
setting a role label and acquiring authority information corresponding to the role label;
and associating the role label with the corresponding authority information.
Further, after the step of obtaining the role label associated with the first user identifier and determining the first authority information associated with the role label, the method further includes:
receiving an adding instruction of the authority information;
determining a user identifier corresponding to the adding instruction of the authority information;
and updating the authority information corresponding to the user identification according to the adding instruction of the authority information.
Further, after the step of determining first subtask data corresponding to the first user identifier according to a matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in an associated manner, the method further includes:
receiving a first data uploading instruction and a second data uploading instruction, wherein the first data uploading instruction and the second data uploading instruction correspond to different user identifications, and the role labels corresponding to the different user identifications are different;
determining first upload data corresponding to the first data upload instruction and second upload data corresponding to the second data upload instruction;
and when the first uploaded data is not matched with the second uploaded data, outputting prompt modification information.
In order to achieve the above object, the method provides an electronic device comprising a memory, a processor and a data management program stored on the memory and executable on the processor, the data management program, when executed by the processor, implementing the steps of the data management method as described above.
In order to achieve the above object, the present method provides a readable storage medium having stored thereon a data management program which, when executed by a processor, implements the steps of the data management method as described above.
In the technical scheme of the invention, a role label associated with a first user identifier is obtained, and first authority information associated with the role label is determined; task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data; according to the matching result between the first authority information and the second authority information, the first subtask data corresponding to the first user identification is determined, and the first user identification and the first subtask data are stored in an associated mode, so that the subtask data corresponding to the user identification and the authority information can be associated according to the authority information associated with the role tag associated with the user identification, namely the authority setting of the user can be completed by determining the role positioning of the user in the task, the authority information is prevented from being set wrongly in the process of independently setting the authority information corresponding to each user, and the confidentiality of the task data can be improved.
Drawings
FIG. 1 is a schematic diagram of an apparatus in a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a data management method according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a data management method according to a second embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The main technical scheme of the invention is as follows:
acquiring a role label associated with a first user identifier, and determining first authority information associated with the role label;
task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data;
and determining first subtask data corresponding to the first user identifier according to a matching result between the first authority information and the second authority information, and storing the first user identifier and the first subtask data in an associated manner.
In the related art, the authority information needs to be set for the account of each user individually, when the personnel flow is large, errors are easy to occur when the authority information of each user is set individually, so that the task data is checked or edited by the user without authority, and the confidentiality of the task data is low.
In the technical scheme of the invention, a role label associated with a first user identifier is obtained, and first authority information associated with the role label is determined; task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data; and determining first subtask data corresponding to the first user identifier according to a matching result between the first authority information and the second authority information, and storing the first user identifier and the first subtask data in an associated manner. Therefore, the subtask data corresponding to the user identification and the authority information can be associated according to the authority information associated with the role tag associated with the user identification, namely, the authority setting of the user can be completed by determining the role positioning of the user in the task, so that the setting error of the authority information in the process of independently setting the authority information corresponding to each user is avoided, and the confidentiality of the task data can be improved.
As shown in fig. 1, fig. 1 is a schematic diagram of a hardware operating environment of a terminal according to an embodiment of the present invention.
As shown in fig. 1, the terminal according to the embodiment of the present invention is an electronic device. The terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may comprise a touch screen and/or keys, etc., and the optional user interface 1003 may also comprise a standard wired interface, a wireless interface, etc. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., a non-volatile memory such as a disk memory), the memory 1005 may optionally also be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration of the terminal shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a data management program.
In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 1001 may be configured to invoke a data management program stored in the memory 1005 and perform the following operations:
acquiring a role label associated with a first user identifier, and determining first authority information associated with the role label;
task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data;
and determining first subtask data corresponding to the first user identifier according to a matching result between the first authority information and the second authority information, and storing the first user identifier and the first subtask data in an associated manner.
Further, the processor 1001 may call the data management program stored in the memory 1005, and also perform the following operations:
determining the total number of subtasks corresponding to each role label;
determining the task state corresponding to each role label as the number of completed subtasks;
determining the task progress of each role label according to the total number of the subtasks corresponding to each role label and the number of the completed subtasks;
and outputting the task progress corresponding to each role label.
Further, the processor 1001 may call the data management program stored in the memory 1005, and also perform the following operations:
when a viewing instruction is received, determining the user identification corresponding to the viewing instruction;
and determining subtask data associated with the user identifier, and outputting the subtask data.
Further, the processor 1001 may call the data management program stored in the memory 1005, and also perform the following operations:
receiving a modification instruction of data;
determining second subtask data corresponding to the modification instruction of the data;
and updating the second subtask data according to the modification instruction of the data.
Further, the processor 1001 may call the data management program stored in the memory 1005, and also perform the following operations:
determining a second user identifier corresponding to the modification instruction of the data, wherein the second user identifier is a user identifier corresponding to a user initiating the modification instruction of the data;
acquiring modification permission associated with the second user identifier;
and when the modification authority comprises the modification authority of the second subtask data, executing the modification instruction according to the data to update the second subtask data.
Further, the processor 1001 may call the data management program stored in the memory 1005, and also perform the following operations:
setting a role label and acquiring authority information corresponding to the role label;
and associating the role label with the corresponding authority information.
Further, the processor 1001 may call the data management program stored in the memory 1005, and also perform the following operations:
receiving an adding instruction of the authority information;
determining a user identifier corresponding to the adding instruction of the authority information;
and updating the authority information corresponding to the user identification according to the adding instruction of the authority information.
Further, the processor 1001 may call the data management program stored in the memory 1005, and also perform the following operations:
receiving a first data uploading instruction and a second data uploading instruction, wherein the first data uploading instruction and the second data uploading instruction correspond to different user identifications, and the role labels corresponding to the different user identifications are different;
determining first upload data corresponding to the first data upload instruction and second upload data corresponding to the second data upload instruction;
and when the first uploaded data is not matched with the second uploaded data, outputting prompt modification information.
As shown in fig. 2, according to a first embodiment of the present invention, the data management method includes the following steps:
step S100, acquiring a role label associated with a first user identifier, and determining first authority information associated with the role label;
in this embodiment, each user has a corresponding user identifier in the system, the user identifier may be associated with a role tag, and one user identifier may be associated with a plurality of role tags, where the role tag includes product, finance, technology, and the like, a product role corresponds to a user who proposes a demand, for example, a user who proposes a certain project and needs to be subsidized, a financial role corresponds to a user who evaluates and batches the demand, for example, in a case where a company can make profits, the project can be evaluated, a user who gives a collectable amount of money is given, and a technology role corresponds to a user who actually deposits money, for example, a user who actually pays money to the project; when the role label is set, the authority information corresponding to the role label can be set at the same time, and the role label is associated with the authority information; when a user needs to complete a task through a system, a role tag associated with a corresponding user identifier can be obtained, first permission information associated with the role tag is determined according to the role tag so as to be matched with second permission information associated with task data, subtask data which are allowed to be checked or edited by the user identifier are found, and the first user identifier is associated with the subtask data so as to verify whether the user identifier has permission to check or edit subtask data corresponding to an instruction or not when the user receives a checking or editing instruction.
In addition, the user identifier may be associated with a first product tag, such as a table, a stool, or the like, and when task data is acquired on a preset interface, a second product tag related to the task may be included, and when the first product tag is matched with the second product tag, the task data is acquired, and second permission information associated with each subtask data of the task data is acquired, where the task data includes at least one subtask data.
Step S200, acquiring task data and second permission information associated with each subtask data of the task data, wherein the task data comprises at least one subtask data;
in this embodiment, a user may input information related to a task on a preset interface to create the task, and when a new task instruction is detected, information in the preset interface is acquired and stored as task data, where the task data is composed of at least one subtask data, and the subtask data is associated with second permission information, and when first permission information is matched with the second permission information, a user identifier associated with a role tag associated with the first permission information may be matched with subtask data associated with the second permission information, so that when a viewing or editing instruction is received, subtask data associated with the user identifier corresponding to the viewing or editing instruction is output on the preset interface.
Step S300, determining first subtask data corresponding to the first user identifier according to a matching result between the first authority information and the second authority information, and storing the first user identifier and the first subtask data in an associated manner.
In this embodiment, the first permission information is permission information associated with the role tag, and when the first user identifier is associated with the role tag, the user identifier has permission to view or edit sub-task data associated with second permission information that matches the first permission information associated with the role tag, so that when the first permission information matches the second permission information, the sub-task data associated with the first role identifier corresponding to the first permission information and the second permission information are stored in an associated manner, so that when a viewing or editing instruction is received, the sub-task data associated with the user identifier is obtained according to the user identifier corresponding to the viewing or editing instruction, and the sub-task data is output.
In summary, in this embodiment, a role tag associated with a first user identifier is obtained, and first permission information associated with the role tag is determined; task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data; according to the matching result between the first authority information and the second authority information, the first subtask data corresponding to the first user identification is determined, and the first user identification and the first subtask data are stored in an associated mode, so that the subtask data corresponding to the user identification and the authority information can be associated according to the authority information associated with the role tag associated with the user identification, namely the authority setting of the user can be completed by determining the role positioning of the user in the task, the authority information is prevented from being set wrongly in the process of independently setting the authority information corresponding to each user, and the confidentiality of the task data can be improved.
As shown in fig. 3, based on the second embodiment of the data management method of the present invention proposed in the first embodiment, in this embodiment, after the step S300, the method further includes:
step S400, determining the total number of subtasks corresponding to each role label;
step S500, determining the task state corresponding to each role label as the number of completed subtasks;
step S600, determining the task progress of each role label according to the total number of the subtasks corresponding to each role label and the number of the completed subtasks;
and S700, outputting the task progress corresponding to each role label.
In this embodiment, the tasks corresponding to the role labels are the same, that is, only one person in the same role label needs to complete the subtasks corresponding to the role labels, determine the total number of the subtasks corresponding to the role labels, determine whether the task state of the subtasks corresponding to the role labels is completed, count the number of the subtasks whose task state is completed, finally obtain the task completion progress corresponding to the role labels according to the comparison between the number of the completed subtasks and the total number of the subtasks, and output the task completion progress corresponding to each role label and the role label on a preset overview interface, so that each user can see the completion of all tasks on the preset overview interface, thereby facilitating the creator or manager of the task to know the completion progress of the tasks, and the management personnel can follow up the progress of the task in a targeted manner.
In addition, in this embodiment, one user identifier may be associated with a plurality of role tags, when one user identifier is associated with a plurality of role tags, since the task corresponding to each role tag is different, the user identifier may be assigned with tasks of different roles, when the task is completed, the number of completed tasks of each tag is determined according to the role tag corresponding to the task, for example, a user identifier named zhang san is associated with two role tags, which are finance and technology, respectively, wherein the finance role needs to complete five tasks, the technology role needs to complete eight personals, when zhang san is completed with tasks corresponding to three finance roles and tasks corresponding to four technology roles, the number of completed tasks corresponding to each role tag is calculated, so as to count the completion progress of each role, that is, the completion progress of finance role is 60%, the completion progress of the technical role is 50%. Because the tasks of the users corresponding to the same role label in the role are the same in the same task, the task completion progress corresponding to each role label can be counted out by counting the total number of the subtasks corresponding to the role label and the number of the completed subtasks according to the role label, and the task completion progress can be conveniently checked by an administrator.
Based on the third embodiment of the data management method in the present invention proposed by the first embodiment, in this embodiment, after the step S300, the method further includes:
when a viewing instruction is received, determining the user identification corresponding to the viewing instruction;
and determining subtask data associated with the user identifier, and outputting the subtask data.
In this embodiment, when a viewing instruction is received, the user identifier corresponding to the viewing instruction is determined, where the user identifier is a user identifier corresponding to a user triggering the viewing instruction, and then subtask data associated with the user identifier is determined, where the associated subtask data is subtask data in which associated second permission information matches with first permission information of the user identifier, that is, viewing permission corresponding to the user identifier includes viewing permission of the subtask data, that is, a user corresponding to the user identifier has permission to view the subtask, so that the subtask data associated with the user identifier is output for a user corresponding to the user identifier to view.
Based on the fourth embodiment of the data management method in the present invention proposed by the first embodiment, in this embodiment, after the step S300, the method further includes:
receiving a modification instruction of data;
determining second subtask data corresponding to the modification instruction of the data;
and updating the second subtask data according to the modification instruction of the data.
In this embodiment, when a modification instruction of data is received, second subtask data corresponding to the modification instruction of the data is determined, where the second subtask data is subtask data to be updated according to the modification instruction of the data, before the second subtask data is updated, a corresponding role identifier is determined according to the modification instruction of the data, that is, a user identifier corresponding to a user who triggers the modification instruction of the data, whether a modification permission corresponding to the user identifier includes a modification permission of the second subtask data is determined, and if the modification permission includes the modification permission, the step of updating the second subtask data according to the modification instruction of the data is performed.
Based on the fifth embodiment of the data management method in the present invention proposed by the fourth embodiment, in this embodiment, before the step of updating the second subtask data according to the modification instruction of the data, the method further includes:
determining a second user identifier corresponding to the modification instruction of the data, wherein the second user identifier is a user identifier corresponding to a user initiating the modification instruction of the data;
acquiring modification permission associated with the second user identifier;
and when the modification authority comprises the modification authority of the second subtask data, executing the modification instruction according to the data to update the second subtask data.
In the embodiment, the corresponding second subtask data is determined according to the modification instruction of the data, determining the modification authority of the second subtask data, determining a corresponding second user identifier according to the modification instruction of the data, the second user identification is the user identification corresponding to the user who initiates the modification instruction of the data, the modification authority corresponding to the second user identification is determined according to the second user identification, comparing the modification authority corresponding to the second user identification with the modification authority of the second subtask data, when the modification right corresponding to the second user identification contains the modification right of the second subtask data, that is, the user corresponding to the second user identifier has the right to modify the second subtask data, so that the modification instruction according to the data is executed to update the second subtask data; and when the modification right corresponding to the second user identifier does not contain the modification right of the second subtask data, namely the user corresponding to the second user identifier does not have the right to modify the second subtask data, the second subtask data cannot be updated according to the modification instruction of the data. Therefore, when a modification instruction of data is received, the user identification corresponding to the modification instruction of the data and the corresponding subtask data are determined, and when the modification authority associated with the user identification contains the modification authority of the subtask data, the subtask data can be updated according to the modification instruction of the data, so that the confidentiality of the task data is improved.
Based on the sixth embodiment of the data management method in the present invention proposed by the first embodiment, in this embodiment, before the step S300, the method further includes:
setting a role label and acquiring authority information corresponding to the role label;
and associating the role label with the corresponding authority information.
In this embodiment, the administrator may set a new role tab on the preset interface, where setting the role tab at least includes the following steps: naming the role tag; and setting the authority information corresponding to the role label to view or edit the authority of the subtask data. And acquiring naming information from the preset interface to update the name of the role label, acquiring corresponding authority information from the preset interface, and storing the authority information in association with the role label so as to find and associate subtask data corresponding to second authority information matched with the first authority information associated with the role label when the user identifier is associated with the role label. Therefore, the role label and the authority information can be stored in an associated manner by presetting the role label and setting the authority information corresponding to the role label, so that the corresponding authority information can be obtained for the user identification by associating the role label and the user identification, errors are avoided in the process that an administrator sets the authority information corresponding to each user identification independently, and the confidentiality of task data is improved.
Based on the seventh embodiment of the data management method in the present invention proposed by the first embodiment, in this embodiment, after step S3100, the method further includes:
receiving an adding instruction of the authority information;
determining a user identifier corresponding to the adding instruction of the authority information;
and updating the authority information corresponding to the user identification according to the adding instruction of the authority information.
In this embodiment, after associating the user identifier with the user tag, the administrator may input the authority information added to the user identifier on a preset interface and send an adding instruction of the authority information, after receiving the adding instruction of the authority information, the system determines the corresponding user identifier according to the adding instruction of the authority information, where the user identifier is the user identifier corresponding to the authority information updated according to the adding instruction of the authority information, and after determining the user identifier, updates the authority information corresponding to the user identifier according to the adding instruction of the authority information. Therefore, the confidentiality of task data is improved by associating the user identification with the role label, and meanwhile, the authority information except the associated role label is added to the user identification through the addition instruction of the authority information, so that the system is more flexible.
Based on the eighth embodiment of the data management method in the present invention proposed by the first embodiment, in this embodiment, after the step S300, the method further includes:
receiving a first data uploading instruction and a second data uploading instruction, wherein the first data uploading instruction and the second data uploading instruction correspond to different user identifications, and the role labels corresponding to the different user identifications are different;
determining first upload data corresponding to the first data upload instruction and second upload data corresponding to the second data upload instruction;
and when the first uploaded data is not matched with the second uploaded data, outputting prompt modification information.
In this embodiment, when there is a subtask in the system that requires uploading data by multiple parties simultaneously and comparing whether the data uploaded by the multiple parties match for checking whether the actual execution of the task is performed according to a plan, so that an administrator can supervise the actual execution of the task. Therefore, the system receives the sent data uploading instruction, judges whether the data uploading instruction is from the user corresponding to the same role label by determining the user identification corresponding to each data uploading instruction, and updates the corresponding subtask data according to the latest data uploading instruction sent by the user corresponding to the user identification when the data uploading instruction is from the user corresponding to the same role label; when the data come from users corresponding to different role labels, receiving each data uploading instruction and determining uploading data corresponding to the data uploading instruction, and when a plurality of uploading data are matched, updating the subtask data according to any uploading data; and when the plurality of uploaded data are not matched, outputting information for prompting the user corresponding to each transmitted data uploading instruction to modify. Each party can only see the data uploaded by the own party, and cannot see the task data uploaded by the user corresponding to other role labels. For example, when the finance and technology need to check the expenditure items, the financial role uploads the approved expenditure amount estimated according to the project to the system, the technical role uploads the actual expenditure amount to the system, the system receives the data of the simultaneous expenditure subtasks, the data uploaded by the finance is matched with the data uploaded by the technology, and when the two data are the same, the technology pays the expenditure items according to the financial batch payment; when the two data are different, at least one of the two parties uploading the data uploads wrong data or one party does not work according to a specified flow, so that the batch cost is different from the actual cost, the data uploaded by the two parties are returned, whether the data uploaded by the party is wrong is checked, and if not, the data uploaded by the party needs to be communicated with the other party. Therefore, when the data uploaded by multiple parties are required to be checked, the confidentiality of the task data uploaded by the parties can be ensured, and the authenticity and the accuracy of similar checking operation are further ensured.
Furthermore, in order to achieve the above object, the method provides an electronic device comprising a memory, a processor and a data management program stored on the memory and executable on the processor, the data management program, when executed by the processor, implementing the steps of the data management method as described above.
Further, in order to achieve the above object, the present method provides a readable storage medium having stored thereon a data management program which, when executed by a processor, implements the steps of the data management method as described above.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A data management method, characterized in that the data management method comprises the steps of:
acquiring a role label associated with a first user identifier, and determining first authority information associated with the role label;
task data are obtained, and second permission information related to each subtask data of the task data is obtained, wherein the task data comprise at least one subtask data;
and determining first subtask data corresponding to the first user identifier according to a matching result between the first authority information and the second authority information, and storing the first user identifier and the first subtask data in an associated manner.
2. The data management method according to claim 1, wherein after the step of determining the first subtask data corresponding to the first user identifier according to the matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in association with each other, the method further comprises:
determining the total number of subtasks corresponding to each role label;
determining the task state corresponding to each role label as the number of completed subtasks;
determining the task progress of each role label according to the total number of the subtasks corresponding to each role label and the number of the completed subtasks;
and outputting the task progress corresponding to each role label.
3. The data management method according to claim 1, wherein after the step of determining the first subtask data corresponding to the first user identifier according to the matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in association with each other, the method further comprises:
when a viewing instruction is received, determining the user identification corresponding to the viewing instruction;
and determining subtask data associated with the user identifier, and outputting the subtask data.
4. The data management method according to claim 1, wherein after the step of determining the first subtask data corresponding to the first user identifier according to the matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in association with each other, the method further comprises:
receiving a modification instruction of data;
determining second subtask data corresponding to the modification instruction of the data;
and updating the second subtask data according to the modification instruction of the data.
5. The data management method of claim 4, wherein the step of updating the second subtask data according to the modification instruction of the data is preceded by the step of:
determining a second user identifier corresponding to the modification instruction of the data, wherein the second user identifier is a user identifier corresponding to a user initiating the modification instruction of the data;
acquiring modification permission associated with the second user identifier;
and when the modification authority comprises the modification authority of the second subtask data, executing the modification instruction according to the data to update the second subtask data.
6. The data management method of claim 1, wherein the step of obtaining the role label associated with the first user identifier and determining the first permission information associated with the role label is preceded by the step of:
setting a role label and acquiring authority information corresponding to the role label;
and associating the role label with the corresponding authority information.
7. The data management method of claim 1, wherein after the steps of obtaining a role label associated with the first user identifier and determining the first permission information associated with the role label, the method further comprises:
receiving an adding instruction of the authority information;
determining a user identifier corresponding to the adding instruction of the authority information;
and updating the authority information corresponding to the user identification according to the adding instruction of the authority information.
8. The data management method according to claim 1, wherein after the step of determining the first subtask data corresponding to the first user identifier according to the matching result between the first permission information and the second permission information, and storing the first user identifier and the first subtask data in association with each other, the method further comprises:
receiving a first data uploading instruction and a second data uploading instruction, wherein the first data uploading instruction and the second data uploading instruction correspond to different user identifications, and the role labels corresponding to the different user identifications are different;
determining first upload data corresponding to the first data upload instruction and second upload data corresponding to the second data upload instruction;
and when the first uploaded data is not matched with the second uploaded data, outputting prompt modification information.
9. An electronic device, characterized in that the electronic device comprises a memory, a processor and a data management program stored on the memory and executable on the processor, the data management program, when executed by the processor, implementing the steps of the data management method according to any one of claims 1 to 8.
10. A readable storage medium, having stored thereon a data management program which, when executed by a processor, implements the steps of the data management method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110563583.9A CN113392382B (en) | 2021-05-21 | 2021-05-21 | Data management method, electronic device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110563583.9A CN113392382B (en) | 2021-05-21 | 2021-05-21 | Data management method, electronic device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113392382A true CN113392382A (en) | 2021-09-14 |
| CN113392382B CN113392382B (en) | 2023-10-20 |
Family
ID=77619013
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110563583.9A Active CN113392382B (en) | 2021-05-21 | 2021-05-21 | Data management method, electronic device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113392382B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114021940A (en) * | 2021-10-29 | 2022-02-08 | 广州市联科软件股份有限公司 | Multi-role multi-link circulation task allocation method and system |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104392310A (en) * | 2014-11-13 | 2015-03-04 | 深圳市玖昔物联科技发展有限公司 | Networked work coordinated management system |
| US20150074014A1 (en) * | 2013-09-12 | 2015-03-12 | Sap Ag | System and method for automated role re-factoring |
| CN108038669A (en) * | 2017-12-25 | 2018-05-15 | 泰康保险集团股份有限公司 | Collocation method, device, equipment and the storage medium of rights management mechanism |
| CN109104412A (en) * | 2018-07-13 | 2018-12-28 | 万翼科技有限公司 | Account right management method, management system and computer readable storage medium |
| CN109598117A (en) * | 2018-10-24 | 2019-04-09 | 平安科技（深圳）有限公司 | Right management method, device, electronic equipment and storage medium |
| US10417613B1 (en) * | 2015-03-17 | 2019-09-17 | Quest Software Inc. | Systems and methods of patternizing logged user-initiated events for scheduling functions |
| CN110287709A (en) * | 2019-05-22 | 2019-09-27 | 深圳壹账通智能科技有限公司 | User's operation authority control method, device, equipment and medium |
| CN111062028A (en) * | 2019-12-13 | 2020-04-24 | 腾讯科技（深圳）有限公司 | Authority management method and device, storage medium and electronic equipment |
| CN111507557A (en) * | 2019-12-09 | 2020-08-07 | 武汉空心科技有限公司 | Multi-role-based work platform task allocation method and system |
| CN111858000A (en) * | 2020-07-10 | 2020-10-30 | 广西农业职业技术学院 | Task decomposition and monitoring management system |
| CN111935073A (en) * | 2020-06-19 | 2020-11-13 | 中国市政工程华北设计研究总院有限公司 | Authority management method and system of cloud platform based on multi-organization architecture |
| CN112445392A (en) * | 2020-10-20 | 2021-03-05 | 北京达佳互联信息技术有限公司 | Organization authority processing method and device, electronic equipment and storage medium |
-
2021
- 2021-05-21 CN CN202110563583.9A patent/CN113392382B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150074014A1 (en) * | 2013-09-12 | 2015-03-12 | Sap Ag | System and method for automated role re-factoring |
| CN104392310A (en) * | 2014-11-13 | 2015-03-04 | 深圳市玖昔物联科技发展有限公司 | Networked work coordinated management system |
| US10417613B1 (en) * | 2015-03-17 | 2019-09-17 | Quest Software Inc. | Systems and methods of patternizing logged user-initiated events for scheduling functions |
| CN108038669A (en) * | 2017-12-25 | 2018-05-15 | 泰康保险集团股份有限公司 | Collocation method, device, equipment and the storage medium of rights management mechanism |
| CN109104412A (en) * | 2018-07-13 | 2018-12-28 | 万翼科技有限公司 | Account right management method, management system and computer readable storage medium |
| CN109598117A (en) * | 2018-10-24 | 2019-04-09 | 平安科技（深圳）有限公司 | Right management method, device, electronic equipment and storage medium |
| CN110287709A (en) * | 2019-05-22 | 2019-09-27 | 深圳壹账通智能科技有限公司 | User's operation authority control method, device, equipment and medium |
| CN111507557A (en) * | 2019-12-09 | 2020-08-07 | 武汉空心科技有限公司 | Multi-role-based work platform task allocation method and system |
| CN111062028A (en) * | 2019-12-13 | 2020-04-24 | 腾讯科技（深圳）有限公司 | Authority management method and device, storage medium and electronic equipment |
| CN111935073A (en) * | 2020-06-19 | 2020-11-13 | 中国市政工程华北设计研究总院有限公司 | Authority management method and system of cloud platform based on multi-organization architecture |
| CN111858000A (en) * | 2020-07-10 | 2020-10-30 | 广西农业职业技术学院 | Task decomposition and monitoring management system |
| CN112445392A (en) * | 2020-10-20 | 2021-03-05 | 北京达佳互联信息技术有限公司 | Organization authority processing method and device, electronic equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| SERGEY V. USOV 等: "Solving some optimization tasks of assigning roles within the framework of well-known estimates of relative damage from leakage of authority in a role-based access control model", pages 1 - 7, XP033681477, Retrieved from the Internet <URL:《网页在线公开：https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=8944724》> * |
| 谢建华等: "基于Django实现四方博客", 《电脑知识与技术》, vol. 15, no. 23, pages 51 - 54 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114021940A (en) * | 2021-10-29 | 2022-02-08 | 广州市联科软件股份有限公司 | Multi-role multi-link circulation task allocation method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113392382B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110636492B (en) | Handover of mobile service providers using blockchains | |
| CN110620810B (en) | Non-linked ownership of continuous asset transfer over blockchain | |
| CN111031036B (en) | Block chain-based vaccine information monitoring method and device and computer equipment | |
| US11102003B2 (en) | Ledger-independent token service | |
| WO2019227573A1 (en) | Collaborative office data stream processing method and apparatus, computer device, and storage medium | |
| CN110852816B (en) | Block chain based automatic invoicing method, terminal equipment and storage medium | |
| US11580096B2 (en) | System for uploading information into a metadata repository | |
| US20220138328A1 (en) | Validation of transaction ledger content using java script object notation schema definition | |
| JP6087452B1 (en) | Paper document management system | |
| KR102166690B1 (en) | Management server and method of digital signature for electronic document | |
| CN111414739A (en) | Excel data entry component, entry method and device | |
| US20120330914A1 (en) | Server, inter-business enterprise information control method and computer program | |
| CN112069134A (en) | Requirement document processing method, device and medium | |
| CN113392382A (en) | Data management method, electronic device and readable storage medium | |
| CN113205304B (en) | Business process configuration method, device, equipment and storage medium | |
| CN112507668A (en) | Project data storage certificate method, storage certificate system, terminal equipment and readable storage medium | |
| CN114710297B (en) | Block chain evidence storing method, device and equipment based on aggregated signature and storage medium | |
| US20220245590A1 (en) | Method and system for collaboratative editing, versioning, conflict resolution, deployment, and automated evaluation of business processes | |
| CN113902392A (en) | Creative project management method, device, terminal and storage medium | |
| CN112069182A (en) | Batch case reporting method, device, equipment and storage medium | |
| US20060095400A1 (en) | Macro delivery system and macro delivery program | |
| CN117710068B (en) | Temporary supplier verification method, device and equipment based on artificial intelligence | |
| TWM545951U (en) | Dynamic enterprise resource planning system | |
| TWI738724B (en) | Dynamic enterprise resource planning method and dynamic enterprise resource planning system | |
| JP6364569B1 (en) | Information processing program, information processing apparatus, and information processing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |