CN113392382B - Data management method, electronic device and readable storage medium - Google Patents
Data management method, electronic device and readable storage medium Download PDFInfo
- Publication number
- CN113392382B CN113392382B CN202110563583.9A CN202110563583A CN113392382B CN 113392382 B CN113392382 B CN 113392382B CN 202110563583 A CN202110563583 A CN 202110563583A CN 113392382 B CN113392382 B CN 113392382B
- Authority
- CN
- China
- Prior art keywords
- data
- role
- authority information
- user identifier
- user
- 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.)
- Active
Links
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
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Entrepreneurship & Innovation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Hardware Design (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Storage Device Security (AREA)
Abstract
The invention discloses a data management method, electronic equipment 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; acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task 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 a correlated manner. According to the authority information associated with the role labels associated with the user identifications, the subtask data corresponding to the user identifications and the authority information are associated, and the problem that the data confidentiality is low due to the fact that the authority information corresponding to the user identifications is prone to error when the user identifications are independently set 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
Along with the development of enterprise informatization, more and more data are stored in the form of electronic files, when other departments are required to perform collaborative verification, the electronic files are required to be sent to the other departments, the personnel distributed inside the other departments to perform collaborative verification on the data, in the existing collaborative work system, the authority of each user is required to be set independently, once the personnel flow, the authority of the relevant staff is required to be set, errors are easy to occur in the setting process, the relevant data are easy to be checked by people without the authorities, the data are easy to leak, and the confidentiality of the data is low.
The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present invention and is not intended to represent an admission that the foregoing is prior art.
Disclosure of Invention
The invention mainly aims to provide a data management method, aiming at associating subtask data corresponding to the user identification and the authority information according to the authority information associated with the role label associated with the user identification, and solving the problem that the authority information corresponding to the user identification is easy to make mistakes and the confidentiality of the data is low when the user identification is independently set.
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;
acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task 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 a correlated manner.
Further, after the step of determining the first subtask data corresponding to the first user identifier according to the 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, 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 task progress of each role label according to the total number of subtasks corresponding to each role label and the number of completed subtasks;
and outputting the task progress corresponding to each role label.
Further, after the step of determining the first subtask data corresponding to the first user identifier according to the 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, the method further includes:
when a viewing instruction is received, determining the user identification corresponding to the viewing instruction;
and determining the subtask data associated with the user identification, and outputting the subtask data.
Further, after the step of determining the first subtask data corresponding to the first user identifier according to the 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, the method further includes:
receiving a data modification instruction;
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 data modification instruction, wherein the second user identifier is a user identifier corresponding to a user initiating the data modification instruction;
acquiring modification rights associated with the second user identifier;
and when the modification authority comprises the modification authority of the second sub-task data, executing the modification instruction according to the data to update the second sub-task data.
Further, before the step of obtaining the role tag associated with the first user identifier and determining the 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 tag associated with the first user identifier and determining the first permission information associated with the role tag, the method further includes:
receiving an adding instruction of authority information;
determining a user identifier corresponding to the addition instruction of the authority information;
and updating the authority information corresponding to the user identifier according to the adding instruction of the authority information.
Further, after the step of determining the first subtask data corresponding to the first user identifier according to the 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, the method further includes:
receiving a first data uploading instruction and a second data uploading instruction, wherein different user identifications corresponding to the first data uploading instruction and the second data uploading instruction are different in role labels corresponding to the different user identifications;
determining first uploading data corresponding to the first data uploading instruction and second uploading data corresponding to the second data uploading instruction;
and outputting prompt modification information when the first uploading data is not matched with the second uploading data.
In order to achieve the above object, the present 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 implementing the steps of the data management method as described above when being executed by the processor.
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.
According to the technical scheme, a role label associated with a first user identifier is obtained, and first authority information associated with the role label is determined; acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task data; and determining first subtask data corresponding to the first user identification according to a matching result between the first right information and the second right information, and associating and storing the first user identification and the first subtask data, so that subtask data corresponding to the right information can be associated by associating the user identification according to the right information associated with the role label associated with the user identification, namely, the right setting of the user can be completed by defining the role positioning of the user in the task, and setting errors of the right information in the process of independently setting the right information corresponding to each user are avoided, so that the confidentiality of the task data can be improved.
Drawings
FIG. 1 is a schematic diagram of a device architecture of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart of a first embodiment of a data management method according to the present invention;
fig. 3 is a flowchart of a second embodiment of the data management method according to the present invention.
The achievement of the objects, functional features and advantages of the present invention 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 for purposes of illustration only and are not intended to limit the scope of 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;
acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task 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 a correlated manner.
In the related art, it is necessary to set authority information for each user's account separately, and when the flow of people is large, errors easily occur in setting authority information for each user separately, resulting in task data being viewed or edited by users who should not have authority, resulting in low confidentiality of task data.
According to the technical scheme, a role label associated with a first user identifier is obtained, and first authority information associated with the role label is determined; acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task 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 a correlated manner. Therefore, the user identification and the subtask data corresponding to the authority information can be associated according to the authority information associated with the role labels associated with the user identification, namely, the authority setting of the user can be completed by definitely locating the roles of the user in the task, and setting errors of the authority information in the process of independently setting the authority information corresponding to each user are avoided, so that 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 in the embodiment of the 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 the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a touch screen and/or keys, etc. and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., a memory), such as a disk memory, the memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
It will be appreciated by those skilled in the art that the structure of the terminal shown in fig. 1 is not limiting of the terminal and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
As shown in fig. 1, an operating system, a network communication module, a user interface module, and a data management program may be included in the memory 1005, which is a type of computer storage medium.
In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a background server and performing data communication with the background 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 call 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;
acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task 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 a correlated manner.
Further, the processor 1001 may call a data management program stored in the memory 1005, and further 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 task progress of each role label according to the total number of subtasks corresponding to each role label and the number of completed subtasks;
and outputting the task progress corresponding to each role label.
Further, the processor 1001 may call a data management program stored in the memory 1005, and further perform the following operations:
when a viewing instruction is received, determining the user identification corresponding to the viewing instruction;
and determining the subtask data associated with the user identification, and outputting the subtask data.
Further, the processor 1001 may call a data management program stored in the memory 1005, and further perform the following operations:
receiving a data modification instruction;
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 a data management program stored in the memory 1005, and further perform the following operations:
determining a second user identifier corresponding to the data modification instruction, wherein the second user identifier is a user identifier corresponding to a user initiating the data modification instruction;
acquiring modification rights associated with the second user identifier;
and when the modification authority comprises the modification authority of the second sub-task data, executing the modification instruction according to the data to update the second sub-task data.
Further, the processor 1001 may call a data management program stored in the memory 1005, and further 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 a data management program stored in the memory 1005, and further perform the following operations:
receiving an adding instruction of authority information;
determining a user identifier corresponding to the addition instruction of the authority information;
and updating the authority information corresponding to the user identifier according to the adding instruction of the authority information.
Further, the processor 1001 may call a data management program stored in the memory 1005, and further perform the following operations:
receiving a first data uploading instruction and a second data uploading instruction, wherein different user identifications corresponding to the first data uploading instruction and the second data uploading instruction are different in role labels corresponding to the different user identifications;
determining first uploading data corresponding to the first data uploading instruction and second uploading data corresponding to the second data uploading instruction;
and outputting prompt modification information when the first uploading data is not matched with the second uploading data.
As shown in fig. 2, the data management method according to the first embodiment of the present invention includes the steps of:
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 a product, a finance, a technology, and the like, a product role corresponds to a user who puts forward a requirement, for example, a user who puts forward a certain item to be subsidized, a finance role corresponds to a user who evaluates the requirement and pays a lot, for example, in a case that a company can make a profit, the user who can evaluate the item and give a chargeable amount, and a technology role corresponds to a user who actually pays money, for example, a user who actually pays money for the item; when the role label is set, 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 label associated with a corresponding user identifier can be obtained, first authority information associated with the role label is determined according to the role label so as to be matched with second authority information associated with task data, subtask data which is authorized to view or edit by the user identifier is found, the first user identifier is associated with the subtask data, and when a viewing or editing instruction is received, whether the user identifier has authority to view or edit the subtask data corresponding to the instruction is verified.
In addition, the user identifier may be associated with a first product tag, such as a table, a stool, etc., and may include a second product tag related to the task when acquiring task data in a preset interface, and when the first product tag matches with the second product tag, the task data acquiring step is executed, and second permission information associated with each piece of subtask data of the task data is acquired, where the task data includes at least one piece of subtask data.
Step S200, acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task data;
in this embodiment, a user may input information related to a task in a preset interface to create a task, when a new task instruction is detected, acquire and store information in the preset interface as task data, where the task data is formed by at least one subtask data, 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 a user identifier corresponding to the viewing or editing instruction is output in 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 a correlated mode.
In this embodiment, the first authority information is authority information associated with the role tag, when the first user identifier is associated with the role tag, the user identifier has authority to view or edit subtask data associated with second authority information matched with the first authority information associated with the role tag, so when the first authority information is matched with the second authority information, the subtask data associated with the second authority information and the first authority information corresponding to the first authority information are associated and stored, when a viewing or editing instruction is received, the subtask data associated with the user identifier is obtained according to the user identifier corresponding to the viewing or editing instruction, and the subtask 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; acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task data; and determining first subtask data corresponding to the first user identification according to a matching result between the first right information and the second right information, and associating and storing the first user identification and the first subtask data, so that subtask data corresponding to the right information can be associated by associating the user identification according to the right information associated with the role label associated with the user identification, namely, the right setting of the user can be completed by defining the role positioning of the user in the task, and setting errors of the right information in the process of independently setting the right information corresponding to each user are avoided, so that the confidentiality of the task data can be improved.
As shown in fig. 3, in this embodiment, after the step S300, the second embodiment of the data management method according to the present invention proposed based on the first embodiment 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 task progress of each role label according to the total number of subtasks corresponding to each role label and the number of subtasks completed;
and step S700, outputting the task progress corresponding to each role label.
In this embodiment, the user identifiers corresponding to the same role label are the same in the tasks corresponding to the role label, that is, only one person in the same role label can complete the subtasks corresponding to the role label, the total number of subtasks corresponding to the role label is determined, whether the task state of the subtasks corresponding to the role label is completed is determined, the number of the subtasks whose states are completed is counted, the task completion progress corresponding to the role label is finally obtained according to the comparison between the number of the subtasks completed and the total number of the subtasks, and each role label and the task completion progress corresponding to the role label are output on a preset overview interface, so that each user can see the completion conditions of all tasks on the preset overview interface, and convenience is brought to the task completion progress of a task creator or manager for the manager to follow up the task progress in a targeted manner.
In addition, in this embodiment, one user identifier may be associated with multiple role labels, when one user identifier is associated with multiple role labels, since the task corresponding to each role label 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 label is determined according to the role label corresponding to the task, for example, the user identifier named Zhang San is associated with two role labels, namely finance and technology, respectively, where the finance role needs to complete five tasks, the technology role needs to complete eight characters, and when Zhang San completes the task corresponding to three finance roles and the task corresponding to four technology roles, the number of completed tasks corresponding to each role label is calculated, so as to count the completion progress of each role, namely the completion progress of the finance role is 60%, and the completion progress of the technology role is 50%. In the same task, the tasks of the users corresponding to the same role label in the role are the same, so that the task completion progress corresponding to each role label can be counted according to the total number of subtasks corresponding to the role label and the number of completed subtasks, and an administrator can conveniently check the task completion progress.
Based on the third embodiment of the data management method according to the present invention set forth in 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 the subtask data associated with the user identification, and outputting the subtask data.
In this embodiment, when a viewing instruction is received, the user identifier corresponding to the viewing instruction is determined, the user identifier is a user identifier corresponding to a user triggering the viewing instruction, then sub-task data associated with the user identifier is determined, the associated sub-task data is sub-task data with associated second permission information matched with the first permission information of the user identifier, that is, viewing permission corresponding to the user identifier includes viewing permission of the sub-task data, that is, a user corresponding to the user identifier has permission to view the sub-task, so that the sub-task data associated with the user identifier is output for viewing by a user corresponding to the user identifier.
Based on the fourth embodiment of the data management method according to the present invention set forth in the first embodiment, in this embodiment, after the step S300, the method further includes:
receiving a data modification instruction;
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 updating the second subtask data, a corresponding role identifier is determined according to the modification instruction of the data, that is, a user identifier corresponding to a user triggering the modification instruction of the data is triggered, and whether modification permission corresponding to the user identifier includes modification permission of the second subtask data is determined, if so, the step of updating the second subtask data according to the modification instruction of the data is executed.
In a fifth embodiment of the data management method according to the present invention, the step of updating the second subtask data according to the modification instruction of the data further includes:
determining a second user identifier corresponding to the data modification instruction, wherein the second user identifier is a user identifier corresponding to a user initiating the data modification instruction;
acquiring modification rights associated with the second user identifier;
and when the modification authority comprises the modification authority of the second sub-task data, executing the modification instruction according to the data to update the second sub-task data.
In this embodiment, the corresponding second subtask data is determined according to the modification instruction of the data, the modification authority of the second subtask data is determined, then a corresponding second user identifier is determined according to the modification instruction of the data, the second user identifier is a user identifier corresponding to a user initiating the modification instruction of the data, the modification authority corresponding to the second user identifier is determined according to the second user identifier, the modification authority corresponding to the second user identifier is compared with the modification authority of the second subtask data, and when the modification authority corresponding to the second user identifier includes the modification authority of the second subtask data, that is, when the user corresponding to the second user identifier has the authority to modify the second subtask data, the modification instruction according to the data is executed to update the second subtask data; when the modification authority corresponding to the second user identifier does not contain the modification authority of the second subtask data, that is, the user corresponding to the second user identifier does not modify the authority of the second subtask data, the second subtask data cannot be updated according to the modification instruction of the data. When a modification instruction of data is received, a user identification corresponding to the modification instruction of the data and corresponding subtask data are determined, and when modification rights associated with the user identification contain modification rights of the subtask data, the subtask data can be updated according to the modification instruction of the data, so that confidentiality of the task data is improved.
Based on the sixth embodiment of the data management method according to the present invention set forth in 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 tag on the preset interface, where setting the role tag at least includes the following steps: naming the role labels; and setting authority information corresponding to the role labels 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 tag, acquiring corresponding authority information from the preset interface, and storing the authority information in association with the role tag so that subtask data corresponding to second authority information matched with first authority information associated with the role tag can be found and associated when the user identification is associated with the role tag. Therefore, the role label can be preset, the authority information corresponding to the role label is set, the role label and the authority information are associated and stored, so that the corresponding authority information is obtained for the user identifier by associating the role label and the user identifier, errors in the process of independently setting the authority information corresponding to each user identifier by an administrator are avoided, and the confidentiality of task data is improved.
Based on the seventh embodiment of the data management method according to the present invention set forth in the first embodiment, in this embodiment, after step S3100, the method further includes:
receiving an adding instruction of authority information;
determining a user identifier corresponding to the addition instruction of the authority information;
and updating the authority information corresponding to the user identifier according to the adding instruction of the authority information.
In this embodiment, after associating a user identifier with a user tag, an administrator may input permission information added to the user identifier at a preset interface and send an addition instruction of the permission information, after receiving the addition instruction of the permission information, the system determines a corresponding user identifier according to the addition instruction of the permission information, where the user identifier is a user identifier corresponding to permission information updated according to the addition instruction of the permission information, and after determining the user identifier, updates the permission information corresponding to the user identifier according to the addition instruction of the permission information. Therefore, the confidentiality of task data is improved by associating the user identification with the role label, and the authority information except the associated role label is added to the user identification through the authority information adding instruction, so that the system is more flexible.
Based on the eighth embodiment of the data management method according to the present invention set forth in 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 different user identifications corresponding to the first data uploading instruction and the second data uploading instruction are different in role labels corresponding to the different user identifications;
determining first uploading data corresponding to the first data uploading instruction and second uploading data corresponding to the second data uploading instruction;
and outputting prompt modification information when the first uploading data is not matched with the second uploading data.
In this embodiment, when there is a subtask in the system that needs to be uploaded by multiple parties at the same time, and whether the data uploaded by the multiple parties match is compared to check whether the actual execution of the task is performed according to the plan, so that the administrator can supervise the actual execution of the task. Therefore, the system receives the transmitted data uploading instructions, judges whether the data uploading instructions come from the users corresponding to the same role labels by determining the user identifications corresponding to the data uploading instructions, and updates the corresponding subtask data according to the data uploading instructions which are transmitted most recently by the users corresponding to the user identifications when coming from the users corresponding to the same role labels; when users corresponding to labels of different roles come from, 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 uploading data are not matched, outputting information for prompting the user corresponding to each data uploading instruction to modify. All the parties can only see the data uploaded by the own party and cannot view task data uploaded by users corresponding to other role labels. For example, when finance and technology need to check the payment, the finance role uploads the approved payment amount estimated according to the project to the system, the technology role uploads the actual payment amount to the system, the system receives the data of the simultaneous payment subtask, the data uploaded by finance is matched with the data uploaded by technology, and when the two data are the same, the technology is described to pay according to the finance batch payment; when the two data are different, it is indicated that at least one of the two parties uploading the data has uploaded the wrong data or one party does not transact according to the specified flow, so that the batch money is different from the actual expenditure, so that the data uploaded by the two parties are returned and checked whether the uploaded data are wrong, if not, the communication with the other party is needed. Therefore, when the data are required to be uploaded by multiple parties for checking, confidentiality of task data uploaded by all the parties can be guaranteed, and authenticity and accuracy of similar checking operation are further guaranteed.
In addition, in order to achieve the above object, the present method provides an electronic device including a memory, a processor, and a data management program stored on the memory and executable on the processor, the data management program implementing the steps of the data management method as described above when executed by the processor.
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 foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (7)
1. A data management method, characterized in that the data management method comprises the steps of:
acquiring a role tag associated with a first user identifier, and determining first authority information associated with the role tag, wherein the first user identifier can be associated with a plurality of role tags, the role tags comprise a product role tag, a financial role tag and a technical role tag, the product role tag corresponds to a user who puts out a requirement, the financial role tag corresponds to a user who evaluates and pays the requirement, and the technical role tag corresponds to a user who actually pays the money;
acquiring task data and acquiring second authority information associated with each piece of sub-task data of the task data, wherein the task data comprises at least one piece of sub-task data;
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 a correlated manner;
when a viewing instruction is received, determining the user identification corresponding to the viewing instruction;
determining the subtask data associated with the user identification and outputting the subtask data;
receiving a data modification instruction;
determining second subtask data corresponding to the modification instruction of the data;
determining a second user identifier corresponding to the data modification instruction, wherein the second user identifier is a user identifier corresponding to a user initiating the data modification instruction;
acquiring modification rights associated with the second user identifier;
and when the modification authority comprises the modification authority of the second sub-task data, executing the modification instruction according to the data to update the second sub-task data.
2. The data management method as claimed in 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 authority information and the second authority information, and associating and storing the first user identifier and the first subtask data, 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 task progress of each role label according to the total number of subtasks corresponding to each role label and the number of completed subtasks;
and outputting the task progress corresponding to each role label.
3. The data management method according to claim 1, wherein before the step of acquiring the role tag associated with the first user identification and determining the first authority information associated with the role tag, further comprising:
setting a role label and acquiring authority information corresponding to the role label;
and associating the role label with the corresponding authority information.
4. The data management method according to claim 1, wherein after the step of acquiring the role tag associated with the first user identification and determining the first authority information associated with the role tag, further comprises:
receiving an adding instruction of authority information;
determining a user identifier corresponding to the addition instruction of the authority information;
and updating the authority information corresponding to the user identifier according to the adding instruction of the authority information.
5. The data management method as claimed in 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 authority information and the second authority information, and associating and storing the first user identifier and the first subtask data, the method further comprises:
receiving a first data uploading instruction and a second data uploading instruction, wherein different user identifications corresponding to the first data uploading instruction and the second data uploading instruction are different in role labels corresponding to the different user identifications;
determining first uploading data corresponding to the first data uploading instruction and second uploading data corresponding to the second data uploading instruction;
and outputting prompt modification information when the first uploading data is not matched with the second uploading data.
6. 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 according to any one of claims 1 to 5.
7. A readable storage medium, wherein a data management program is stored on the readable storage medium, which when executed by a processor, implements the steps of the data management method according to any one of claims 1 to 5.
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 CN113392382A (en) | 2021-09-14 |
| CN113392382B true 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) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114021940B (en) * | 2021-10-29 | 2022-07-19 | 广州市联科软件股份有限公司 | Multi-role multi-link circulation task allocation method and system |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104392310A (en) * | 2014-11-13 | 2015-03-04 | 深圳市玖昔物联科技发展有限公司 | Networked work coordinated management system |
| 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 |
Family Cites Families (1)
| 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 |
-
2021
- 2021-05-21 CN CN202110563583.9A patent/CN113392382B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 (1)
| Title |
|---|
| 基于Django实现四方博客;谢建华等;《电脑知识与技术》;第15卷(第23期);第51-54页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113392382A (en) | 2021-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107679749B (en) | Authority application approval method and authorization management platform | |
| CN111031036B (en) | Block chain-based vaccine information monitoring method and device and computer equipment | |
| US20170337395A1 (en) | Employment eligibility verification system and method | |
| US8103596B1 (en) | License verification system and method | |
| US10826951B2 (en) | Electronic content sharing | |
| AU2018217898A1 (en) | System and interfaces for managing temporary workers | |
| KR102180377B1 (en) | Integrated work management solution system | |
| WO2003079152A2 (en) | Human resources management system and method | |
| CN110852816A (en) | Block chain based automatic invoicing method, terminal equipment and storage medium | |
| CN113392382B (en) | Data management method, electronic device and readable storage medium | |
| CN112184158A (en) | Rental business approval method, device, equipment and medium | |
| US11430063B2 (en) | Trading proposal arrangement, system and method | |
| US20180349269A1 (en) | Event triggered data retention | |
| CN116756711A (en) | Data processing method, device, equipment and medium | |
| US9569416B1 (en) | Structured and unstructured data annotations to user interfaces and data objects | |
| JP6133529B1 (en) | Method and system for updating electronic approval document | |
| CN113498592B (en) | Method and system for digital property authentication and management | |
| TWI738724B (en) | Dynamic enterprise resource planning method and dynamic enterprise resource planning system | |
| US10148786B1 (en) | Method of generating a unified user profile | |
| CN113256243A (en) | Project budget full life cycle management device and method | |
| US11755197B1 (en) | Move tool system | |
| CN110889763A (en) | Financial management system based on big data | |
| JP4570933B2 (en) | Macro delivery system | |
| TWM545951U (en) | Dynamic enterprise resource planning system | |
| JP2007058253A (en) | Method of supporting estimation in system development, system for supporting estimation in system development, and program therefor |
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 |