Task management method and system based on metadata driving

Abstract

The invention discloses a task management method and system based on metadata driving. The task management method comprises the steps that fields in system task information are extracted for metadata description, and basic information, format description, interface description, merging description, circulation description, association description, collection description and backflow description of the fields are defined; various metadata descriptions and actual result data generated in the execution process of each preorder unit are comprehensively utilized, a scientific and reasonable task assessment scheme is formulated, a complete task closed-loop management mechanism is formed, and the task completion quality and efficiency are effectively assessed.

Description

Technical Field

[0001] The present application relates to the technical field of system task management, and mainly to a metadata-driven task management method and system. Background Art

[0002] Task management is common in daily work. The simpler ones include reminders on mobile phones, and the more complex ones include multiple departments working together to collect and evaluate the quality of a series of complex forms. For the latter, in the past, it was necessary to develop a series of forms based on business scenarios and configure corresponding processes to support them. Different business scenarios have different requirements, so the current existing technology needs to develop a series of forms for complex business scenarios. Summary of the invention

[0003] Based on the summary of various complex business scenario requirements, this solution proposes a metadata-driven task management method and develops a more general system to avoid duplication of work caused by various customized forms and processes.

[0004] According to one aspect of the present invention, a metadata-driven task management method is proposed, comprising:

[0005] Extract the fields in the system task information for metadata description, and define the basic information, format description, interface description, merge description, flow description, association description, collection description, and return flow description of the fields;

[0006] These descriptions define how the fields will be processed during task scheduling, execution, and assessment, including how to construct task forms, how to schedule, how to execute, and how to assess.

[0007] The basic information specifically includes: the code, name, entity and version number of the field, setting a unique identifier for the field, and recording in detail the basic information such as the code, name and business entity of the field.

[0008] Based on the format description and the interface description, dynamically generate a task form that meets business requirements;

[0009] The format description and the interface description specifically include: the format description clearly specifies the data representation format, data type (such as string, integer, date, etc.) and legal value range of the field to ensure the validity and accuracy of data input.

[0010] The interface describes the display form of the design field on the software user interface, such as label display mode, input box style, whether it is editable, etc., to improve user experience and operation efficiency.

[0011] Based on the merge description and the flow description, a task scheduling plan is parsed and output, and the subject and object roles and flow process of the task are clearly defined;

[0012] The merging description and the flow description specifically include: the merging description formulates task merging rules. When specific conditions are met, multiple tasks can be merged and processed according to the rules. The flow description stipulates the flow path in the task process, clarifies which departments or positions the task needs to pass through, and formulates corresponding flow strategies.

[0013] Based on the association description, the collection description and the return flow description, a specific implementation plan for task execution is generated to guide the user to complete the work content required for the task, while ensuring the accuracy and completeness of data collection, and feeding back the specific implementation plan to the system;

[0014] The association description, the collection description and the reflow description specifically include: the association description defines the association relationship between the field and other data, triggers auxiliary information query through the field, and provides a corresponding query interface to realize the linkage function; the collection description determines the appropriate collection control type for the field, such as text input, drop-down selection, date selector, etc., to support data collection requirements; the reflow description sets whether and how the field data should flow back to the task management system after the task is executed, so as to ensure the integrity of the data and subsequent analysis and utilization.

[0015] By comprehensively utilizing various metadata descriptions and the actual result data generated during the execution of previous units, a scientific and reasonable task assessment plan is formulated, a complete task closed-loop management mechanism is formed, and the quality and efficiency of task completion are effectively evaluated.

[0016] According to a second aspect of the present invention, a computer-readable storage medium is provided, on which one or more computer programs are stored. When the one or more computer programs are executed by a computer processor, any of the above methods is implemented.

[0017] According to a third aspect of the present invention, a metadata-driven task management system is proposed, the system comprising:

[0018] Task form construction unit: dynamically generates task forms that meet business requirements based on format description and interface description metadata;

[0019] Task scheduling unit: Based on the merge description and flow description metadata, it parses and outputs the task scheduling plan, clearly defining the subject and object roles and flow process of the task;

[0020] Task execution unit: based on the association description, collection description and return flow description, generates a specific implementation plan for task execution, guides the user to complete the work required for the task, ensures the accuracy and completeness of data collection, and feeds back the specific implementation plan to the system;

[0021] Task assessment unit: Comprehensively use various metadata descriptions and the actual result data generated during the execution of previous units to formulate a scientific and reasonable task assessment plan, form a complete task closed-loop management mechanism, and effectively evaluate the quality and efficiency of task completion.

[0022] The above one or more technical solutions in the embodiments of the present application have at least one of the following technical effects:

[0023] The metadata-driven task management method and system described in the present invention extend metadata-driven from forms to the entire process of task management, including task forms, task scheduling, task execution, and task assessment. This not only expands the scope of use of metadata-driven, but also utilizes unified metadata descriptions to maintain a high degree of uniformity in business requirements throughout the entire task management process.

[0024] The present invention supports the diversity of tasks, supports defining tasks through metadata descriptions, supports gradually executing tasks according to these descriptions through a metadata-driven module, and completes closed-loop management of tasks. It is suitable for scenarios such as the issuance of various task instructions and data reporting that are common in daily work between superiors and subordinates in government departments and superiors and subordinates in enterprises and institutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings are included to provide a further understanding of the embodiments and are incorporated into and constitute a part of this specification. The accompanying drawings illustrate the embodiments and are used together with the description to explain the principles of the present invention. It will be easy to recognize other embodiments and many expected advantages of the embodiments because they become better understood by reference to the following detailed description. The elements of the drawings are not necessarily to scale with each other. The same reference numerals refer to corresponding similar parts.

[0026] Figure 1 A schematic diagram of system task metadata driving according to an embodiment of the present invention is shown;

[0027] Figure 2 A schematic diagram of describing system task metadata according to a specific embodiment of the present invention is shown;

[0028] Figure 3 A schematic diagram of a metadata driving module according to a specific embodiment of the present invention is shown;

[0029] Figure 4It is a structural diagram of a computer system suitable for implementing an electronic device of an embodiment of the present application. DETAILED DESCRIPTION

[0030] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant invention, rather than to limit the invention. It should also be noted that, for ease of description, only the parts related to the relevant invention are shown in the accompanying drawings.

[0031] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0032] Figure 1 A schematic diagram of system task metadata driving according to an embodiment of the present invention is shown as follows: Figure 1 As shown:

[0033] Extract the fields in the system task information for metadata description, and define the basic information, format description, interface description, merge description, flow description, association description, collection description, and return flow description of the fields;

[0034] The basic information specifically includes: the code, name, subject and version number of the field. A document management system is used to record and maintain the basic information; a version control system is used to track the change history of the assessment plan.

[0035] Based on the format description and the interface description, dynamically generate a task form that meets business requirements;

[0036] The format description and the interface description specifically include: the format description clearly specifies the data representation format, data type and legal value range of the field. Optionally, a template engine is used: such as Jinja2, Mustache, etc., to generate a standardized table template, and through database design, the data table structure is defined to ensure data consistency and integrity.

[0037] The interface describes the display form of the design field on the software user interface, wherein the front-end development framework, such as React, Vue.js, etc., can be used to build the user interface. UI / UX design tools, such as Figma, Sketch, etc., can be used to design the user interface prototype.

[0038] like Figure 2 FIG. 1 shows a schematic diagram of describing system task metadata according to a specific embodiment of the present invention. In this embodiment, the task form construction unit is as follows:

[0039] {

[0040] Format description: ID card number, length 18 digits, format conforming to GB11643 standard;

[0041] Interface description: Display style of ID card number: font, color, etc., defined by style language; desensitization rules of ID card number, defined by regular expression;

[0042] }

[0043] In some application scenarios, metadata is used to describe the form structure, field types, validation rules and other information; programming interfaces (APIs) are used to provide APIs to dynamically generate and present forms, as well as process data submitted by forms. Use the configuration interface: Provide a user-friendly interface so that non-technical personnel can also configure and manage form templates.

[0044] Based on the merge description and the flow description, a task scheduling plan is parsed and output, and the subject and object roles and flow process of the task are clearly defined;

[0045] The merge description and the flow description specifically include: the merge description formulates the task merge rules. When specific conditions are met, multiple tasks can be merged and processed according to the rules, wherein data integration tools such as Apache Nifi, Talend, etc. are used to integrate multi-source data into a single view, and ETL processes are used: ETL tools are used to process data integration. The flow description specifies the flow path in the task process, clarifies which departments or positions the task needs to pass through, and formulates corresponding flow strategies, wherein, optionally, workflow engines such as Camunda, Activiti, etc. are used to define and execute business processes, and task schedulers such as Cron, Airflow, etc. are used to schedule the execution time of tasks.

[0046] In this embodiment, the task scheduling unit is as follows:

[0047] {

[0048] Merge description: Tasks related to objects with the same ID number within a week need to be merged;

[0049] Circulation description: The object needs to be circulated among departments A, B, and C in sequence;

[0050] }

[0051] In some application scenarios, tasks are created and started by the subject role. Tasks are assigned to one or more object roles; the object roles perform tasks according to the task requirements; problems and progress information generated during the execution are fed back to the subject role; the subject role reviews and confirms the completed tasks; after confirmation, the subject role closes the task.

[0052] Based on the association description, the collection description and the return flow description, a specific implementation plan for task execution is generated to guide the user to complete the work content required for the task, while ensuring the accuracy and completeness of data collection, and feeding back the specific implementation plan to the system;

[0053] The association description, the collection description and the reflow description specifically include: the association description defines the association relationship between the field and other data, triggers auxiliary information query through the field, and provides a corresponding query interface to realize the linkage function; the collection description determines the appropriate collection control type for the field; the reflow description sets whether and how the field data should be reflowed to the task management system after the task is executed.

[0054] The task execution unit in this embodiment is as follows

[0055] {

[0056] Association description: query the family background of the object through the ID card number association;

[0057] Collection description: Use mobile terminal devices to verify identity;

[0058] Flowback description: The collected content needs to be returned as the result of the task execution for subsequent environmental assessment;

[0059] In some application scenarios, data collection tools (such as Scrapy), data processing and analysis libraries (such as NLTK, Pandas), and data storage solutions (such as MongoDB and PostgreSQL) are also involved. In addition, task scheduling (such as scheduled tasks) and automation scripts (such as Python scripts) are also used to realize automatic data collection, processing, and analysis.

[0060] By comprehensively utilizing various metadata descriptions and the actual result data generated during the execution of previous units, a scientific and reasonable task assessment plan is formulated, a complete task closed-loop management mechanism is formed, and the quality and efficiency of task completion are effectively evaluated.

[0061] In this embodiment, the task assessment unit is as follows:

[0062] {

[0063] Comprehensive description of various metadata: If the identity verification is passed, the item will be scored full marks, otherwise, the item will be scored zero marks;

[0064] }

[0065] like Figure 3 As shown, a schematic diagram of a metadata driving module according to a specific embodiment of the present invention is shown:

[0066] Task form construction unit: dynamically generates task forms that meet business requirements based on format description and interface description metadata;

[0067] Task scheduling unit: Based on the merge description and flow description metadata, it parses and outputs the task scheduling plan, clearly defining the subject and object roles and flow process of the task;

[0068] Task execution unit: based on the association description, collection description and return flow description, generates a specific implementation plan for task execution, guides the user to complete the work required for the task, ensures the accuracy and completeness of data collection, and feeds back the specific implementation plan to the system;

[0069] Task assessment unit: Comprehensively use various metadata descriptions and the actual result data generated during the execution of previous units to formulate a scientific and reasonable task assessment plan, form a complete task closed-loop management mechanism, and effectively evaluate the quality and efficiency of task completion.

[0070] In summary, the metadata-driven task management method and system described in this solution supports the diversity of tasks, supports the definition of tasks through metadata descriptions, and supports the closed-loop management of tasks by gradually executing tasks according to these descriptions through metadata-driven modules.

[0071] Reference below Figure 4 , which shows a schematic diagram of the structure of a computer system 400 suitable for implementing an electronic device of an embodiment of the present application. Figure 4 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0072] like Figure 4 As shown, the computer system 400 includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage part 408 into a random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the system 400 are also stored. The CPU 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0073] The following components are connected to the I / O interface 405: an input section 406 including a keyboard, a mouse, etc.; an output section 407 including a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 410 as needed, so that a computer program read therefrom is installed into the storage section 408 as needed.

[0074] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 409, and / or installed from the removable medium 411. When the computer program is executed by the central processing unit (CPU) 401, the above functions defined in the method of the present application are executed. It should be noted that the computer-readable storage medium of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, - but not limited to - a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable storage medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, device, or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wireless, wireline, optical cable, RF, etc., or any suitable combination of the foregoing.

[0075] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0076] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0077] The modules involved in the embodiments of the present application may be implemented by software or by hardware.

[0078] As another aspect, the present application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiment; or it may exist independently without being assembled into the electronic device. The above computer-readable storage medium carries one or more programs. When the above one or more programs are executed by the electronic device, the electronic device: extracts the fields in the system task information for metadata description, defines the basic information, format description, interface description, merge description, flow description, association description, collection description and reflux description of the fields; comprehensively uses various metadata descriptions and the actual result data generated during the execution of the previous units to formulate a scientific and reasonable task assessment plan, form a complete task closed-loop management mechanism, and effectively evaluate the quality and efficiency of task completion.

[0079] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above invention concept. For example, the above features are replaced with the technical features with similar functions disclosed in this application (but not limited to) by each other to form a technical solution.

Claims

1. A metadata-driven task management method, characterized in that: The following steps are involved: Extract the fields in the system task information for metadata description, and define the basic information, format description, interface description, merge description, flow description, association description, collection description, and return flow description of the fields; Based on the format description and the interface description, dynamically generate a task form that meets business requirements; Based on the merge description and the flow description, a task scheduling plan is parsed and output, and the subject and object roles and flow process of the task are clearly defined; Based on the association description, the collection description and the return flow description, a specific implementation plan for task execution is generated to guide the user to complete the work content required for the task, while ensuring the accuracy and completeness of data collection, and feeding back the specific implementation plan to the system; By comprehensively utilizing various metadata descriptions and the actual result data generated during the execution of previous units, a scientific and reasonable task assessment plan is formulated, a complete task closed-loop management mechanism is formed, and the quality and efficiency of task completion are effectively evaluated.

2. The task management method according to claim 1, characterized in that: The basic information specifically includes: the code, name, entity and version number of the field.

3. The task management method according to claim 1, characterized in that: The format description and the interface description specifically include: the format description clearly specifies the data representation format, data type and legal value range of the field, and the interface description designs the display form of the field on the software user interface.

4. The task management method according to claim 1, characterized in that: The merging description and the flow description specifically include: the merging description formulates task merging rules. When specific conditions are met, multiple tasks can be merged and processed according to the rules. The flow description stipulates the flow path in the task process, clarifies which departments or positions the task needs to pass through, and formulates corresponding flow strategies.

5. The task management method according to claim 1, characterized in that: The association description, the collection description and the reflow description specifically include: the association description defines the association relationship between the field and other data, triggers auxiliary information query through the field, and provides a corresponding query interface to realize the linkage function; the collection description determines the appropriate collection control type for the field; the reflow description sets whether and how the field data should be reflowed to the task management system after the task is executed.

6. A metadata-driven task management system, characterized in that: The following steps are involved: Task form construction unit: dynamically generates task forms that meet business requirements based on format description and interface description metadata; Task scheduling unit: Based on the merge description and flow description metadata, it parses and outputs the task scheduling plan, clearly defining the subject and object roles and flow process of the task; Task execution unit: based on the association description, collection description and return flow description, generates a specific implementation plan for task execution, guides the user to complete the work required for the task, ensures the accuracy and completeness of data collection, and feeds back the specific implementation plan to the system; Task assessment unit: Comprehensively use various metadata descriptions and the actual result data generated during the execution of previous units to formulate a scientific and reasonable task assessment plan, form a complete task closed-loop management mechanism, and effectively evaluate the quality and efficiency of task completion.

7. A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 5.

8. A computing system comprising a processor and a memory, wherein the processor is configured to execute the method according to any one of claims 1 to 5.

Images