CN117710796A - Labeling task management method and labeling task management system - Google Patents
Labeling task management method and labeling task management system Download PDFInfo
- Publication number
- CN117710796A CN117710796A CN202211093269.XA CN202211093269A CN117710796A CN 117710796 A CN117710796 A CN 117710796A CN 202211093269 A CN202211093269 A CN 202211093269A CN 117710796 A CN117710796 A CN 117710796A
- Authority
- CN
- China
- Prior art keywords
- subtask
- user
- data
- processed
- labeling
- 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.)
- Pending
Links
- 238000002372 labelling Methods 0.000 title claims abstract description 130
- 238000007726 management method Methods 0.000 title claims abstract description 70
- 230000004913 activation Effects 0.000 claims abstract description 34
- 238000012545 processing Methods 0.000 claims description 58
- 230000002349 favourable effect Effects 0.000 abstract 1
- 238000000034 method Methods 0.000 description 5
- 238000013523 data management Methods 0.000 description 4
- 238000007789 sealing Methods 0.000 description 4
- 238000003745 diagnosis Methods 0.000 description 2
- 238000002059 diagnostic imaging Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 201000010099 disease Diseases 0.000 description 2
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004195 computer-aided diagnosis Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H30/00—ICT specially adapted for the handling or processing of medical images
- G16H30/20—ICT specially adapted for the handling or processing of medical images for handling medical images, e.g. DICOM, HL7 or PACS
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H30/00—ICT specially adapted for the handling or processing of medical images
- G16H30/40—ICT specially adapted for the handling or processing of medical images for processing medical images, e.g. editing
Abstract
The invention provides a labeling task management method, which comprises the following steps: when a labeling task is started, a plurality of subtasks of the labeling task are firstly created, each subtask has a task name used for distinguishing the subtask from other subtasks, and then activation logic of the subtasks is set, and execution authority required by each subtask and execution authority of each user role are started; searching the execution authority corresponding to the user role according to the logged-in user role; displaying the task name of the activated subtask corresponding to the searched execution authority so as to enable the user to select to start the subtask; and providing the data to be processed to the user after the user opens the subtask. The labeling task management method is favorable for accurately, efficiently and universally managing the labeling task. In addition, a labeling task management system is provided.
Description
Technical Field
The invention relates to a management method, in particular to a labeling task management method and a labeling task management system.
Background
In the field of artificial intelligence based medical imaging computer aided diagnosis, high quality labeling is believed to play an important role in the model training and performance evaluation phase. The labeling quality of the medical image is influenced by factors such as the medical imaging level of labeling personnel, the management level of labeling process and the like. At present, in the labeling task implementation process, the management method for labeling personnel and labeling flow is low in efficiency and easy to make mistakes, and labeling quality is affected.
Disclosure of Invention
The invention aims to provide a labeling task management method which is beneficial to accurately, efficiently and universally managing labeling tasks.
It is another object of the present invention to provide a labeling task management system that facilitates accurate, efficient and versatile management of labeling tasks.
The invention provides a labeling task management method, which comprises the following steps: when a labeling task is started, a plurality of subtasks of the labeling task are firstly created, each subtask has a task name used for distinguishing the subtask from other subtasks, and then activation logic of the subtasks is set, and execution authority required by each subtask and execution authority of each user role are started; searching the execution authority corresponding to the user role according to the logged-in user role; displaying the task name of the activated subtask corresponding to the searched execution authority so as to enable the user to select to start the subtask; and providing the data to be processed to the user after the user opens the subtask.
The labeling task management method enables the subtasks to be sequentially activated according to the set activation logic, and the user can only start the activated subtasks corresponding to the execution authority of the user roles used by the subtasks, so that the labeling tasks can be accurately, efficiently and universally managed.
In another exemplary embodiment of the labeling task management method, the labeling task management method further includes: after creating a plurality of subtasks of the labeling task, labeling tools used by the subtasks are set. The step of providing the data to be processed to the user after the user opens the subtask is specifically as follows: and after the user starts the subtask, the corresponding marking tool is called, and the data to be processed are provided for the user in the marking tool. Therefore, when different subtasks are started, only the marking tool related to the subtask is called, and the functions of all marking tools required by the marking task are not required to be integrated together, so that the software development difficulty is reduced, and the marking tool is more convenient to adjust.
In still another exemplary embodiment of the labeling task management method, the labeling task management method further includes: after a plurality of subtasks of the labeling task are created, setting the data source of the data to be processed of each subtask. The step of providing the data to be processed to the user after the user opens the subtask is specifically as follows: and after the user opens the subtask, acquiring the data to be processed from the data source of the data to be processed corresponding to the subtask and providing the data to the user. Thereby facilitating data management.
In still another exemplary embodiment of the labeling task management method, the labeling task management method further includes: when a labeling task is started, the initial data to be labeled is stored. The step of setting the data source of the data to be processed of each subtask comprises the following steps: setting the data source of the data to be processed of the subtask at the starting point of the activation logic as the initial data to be marked. The labeling task management method further comprises the following steps: and storing the data processed by the user when the user completes the subtask. The step of setting a data source of the data to be processed of each subtask further comprises: and setting the data processed by the user as a data source of the data to be processed of the next subtask in the activation logic. Therefore, the data are subjected to sealing management, and the quality and traceability of the marking are guaranteed.
In still another exemplary embodiment of the labeling task management method, the labeling task management method further includes: and recording the time information, the user role information and the operation subtask information of the subtask completion when the user completes the subtask. Therefore, the completion time of the subtasks, the roles of the users who complete the subtasks and the operations of the users on the subtasks can be conveniently checked.
The invention also provides a labeling task management system, which comprises a processing module. When receiving a marking task request data, the processing module firstly creates a plurality of subtasks of the marking task, each subtask has a task name used for distinguishing the subtask from other subtasks, and then sets activation logic of the subtasks, and opens execution authority required by each subtask and execution authority of each user role. The processing module also searches the execution authority corresponding to the user role according to the logged-in user role. The processing module also generates image data for displaying the task name of the activated subtask corresponding to the searched execution authority so as to enable the subtask to be selected by a user. The processing module also outputs the data to be processed to provide for the user after receiving the starting signal of the user for starting the subtask. The labeling task management system enables the subtasks to be sequentially activated according to the set activation logic, and the user can only start the activated subtasks corresponding to the execution authority of the user roles used by the subtasks, so that the labeling tasks can be accurately, efficiently and universally managed.
In another exemplary embodiment of the annotation task management system, the processing module further sets annotation tools for use by the subtasks after creating the subtasks of the annotation task. The processing module also calls a corresponding marking tool after receiving an opening signal of the user for opening the subtask, and outputs data to be processed in the marking tool to provide the data to the user. Therefore, when different subtasks are started, only the marking tool related to the subtask is called, and the functions of all marking tools required by the marking task are not required to be integrated together, so that the software development difficulty is reduced, and the marking tool is more convenient to adjust.
In yet another exemplary embodiment of the labeling task management system, the labeling task management system further comprises a plurality of labeling modules, each labeling module running a labeling tool. The processing module also starts the corresponding marking module to call the corresponding marking tool after receiving the starting signal of the user starting subtask, and outputs the data to be processed in the marking tool to provide for the user.
In yet another exemplary embodiment of the labeling task management system, the processing module further sets a data source of the data to be processed for each sub-task after creating the plurality of sub-tasks of the labeling task. The processing module also acquires the data to be processed from the data source of the data to be processed corresponding to the subtask after receiving the starting signal of the subtask started by the user, and outputs the data to be processed to be provided for the user. Thereby facilitating data management.
In yet another exemplary embodiment of the labeling task management system, the labeling task management system further comprises a storage module. And the processing module stores the initial data to be marked into the storage module when receiving the marking task request data. The processing module also sets the data source of the data to be processed of the subtask at the starting point of the activation logic as the initial data to be marked. And the processing module is used for storing the data processed by the user into the storage module when receiving a completion signal for completing the subtasks by the user. The processing module also sets the data after the user processing as a data source of the data to be processed of the next subtask in the activation logic. Therefore, the data are subjected to sealing management, and the quality and traceability of the marking are guaranteed.
In still another exemplary embodiment of the labeling task management system, the processing module further stores time information of completion of the subtask, user role information, and operation subtask information to the storage module when receiving a completion signal of completion of the subtask by the user. Therefore, the completion time of the subtasks, the roles of the users who complete the subtasks and the operations of the users on the subtasks can be conveniently checked.
Drawings
The following drawings are only illustrative of the invention and do not limit the scope of the invention.
FIG. 1 is a flow chart of an exemplary embodiment of a method of labeling tasks.
Fig. 2 is used to illustrate subtasks and activation logic in one example application.
FIG. 3 is a block diagram of an exemplary embodiment of a labeling task management system.
Description of the reference numerals
50. Processing module
60. Storage module
70. Labeling module
A. B, C1, C2, D, E subtasks
Detailed Description
For a clearer understanding of the technical features, objects and effects of the present invention, embodiments of the present invention will now be described with reference to the drawings, in which like reference numerals refer to identical or structurally similar but functionally identical components throughout the separate views.
In this document, "schematic" means "serving as an example, instance, or illustration," and any illustrations, embodiments described herein as "schematic" should not be construed as a more preferred or advantageous solution.
For the sake of simplicity of the drawing, the parts relevant to the present invention are shown only schematically in the figures, which do not represent the actual structure thereof as a product.
FIG. 1 is a flow chart of an exemplary embodiment of a method of labeling tasks. As shown in fig. 1, the labeling task management method includes the following steps S10 to S40.
S10: when a labeling task is started, a plurality of subtasks of the labeling task are firstly created, each subtask has a task name used for distinguishing the subtask from other subtasks, and then activation logic of the subtasks is set, and execution permission required by each subtask and execution permission of each user role are started.
S20: and searching the execution authority corresponding to the user role according to the logged-in user role.
S30: and displaying the task name of the activated subtask corresponding to the searched execution authority so as to enable the user to select to open the subtask.
S40: the data to be processed is provided to the user after the user opens the subtask.
The labeling task management method is implemented in the architecture of a server+terminal or a server+web page, for example, but is not limited thereto.
The following description is provided in connection with a specific example of a method for managing a task using the present labeling, and is not intended to limit the scope of the invention. Step S10 is performed, for example, on a server. As shown in FIG. 2, when a labeling task is started by the server, subtask A, subtask B, subtask C1, subtask C2, subtask D and subtask E are created first, and activation logic of the subtasks is set. The labeling task is, for example, labeling a CT image, the subtask A is, for example, marking a focus area, the subtask B is, for example, checking whether the marked focus area is accurate, the subtask C1 and the subtask C2 are, for example, disease diagnosis, the subtask D is, for example, summarizing disease diagnosis results, and the subtask E is, for example, final checking. The activation logic is represented by the arrow in fig. 2, which means: the subtask A can automatically activate the subtask B after being completed, the subtask A or the subtask C1 and the subtask C2 can be activated according to the selection of a user when the subtask B is completed, the subtask C1 and the subtask C2 can automatically activate the subtask D after being completed, and the subtask E can be automatically activated after the subtask D is completed. Where sub-task a is the starting point of the activation logic, which may be automatically activated after the activation logic is set up.
The setting of the execution rights required to open the subtasks is performed, for example, according to the contents shown in table 1 below.
Table 1:
setting the execution authority of each user role is performed, for example, according to the contents shown in table 2 below.
Table 2:
| user roles | Execution rights |
| Role 1 | First level |
| Role 2 | Second-level |
| Role 3 | Three stages |
| Role 4 | Three stages |
In step S20, the login is performed, for example, on a terminal or a web page, and the search is performed, for example, on a server. If the logged-in user role is 'role 3', the corresponding execution authority is found to be 'three-level'.
In step S30, the presentation is performed on a terminal or a web page, for example. Specifically, for example, the server searches for the corresponding activated subtask according to the searched execution authority, and sends the task name of the searched subtask to the terminal or the webpage to be presented to the user for the user to select to open the subtask. If the subtask a is in an activated state and the logged-in user role is "role 3", the task name of the subtask a is sent by the server to the terminal or the web page to be presented to the logged-in user.
In step S40, the user opens a subtask, for example, on a terminal or a web page, and the terminal or the web page sends a signal to the server after receiving the opening operation of the user, and the server outputs the data to be processed to the terminal or the web page to provide the data to the user.
When a plurality of labeling tasks are started, step S10 is executed for each labeling task, and task names of activated subtasks of all labeling tasks corresponding to the found execution authority are displayed in step S30. When a plurality of user roles are logged in at the same time at different terminals or web pages, steps S20 to S40 are independently performed for each logged-in user role.
The labeling task management method enables the subtasks to be sequentially activated according to the set activation logic, and the user can only start the activated subtasks corresponding to the execution authority of the user roles used by the subtasks, so that the labeling tasks can be accurately, efficiently and universally managed.
In an exemplary embodiment, step S10 further includes: after creating a plurality of subtasks of the labeling task, labeling tools used by the subtasks are set. The step S40 specifically includes: and after the user starts the subtask, the corresponding marking tool is called, and the data to be processed are provided for the user in the marking tool. Therefore, when different subtasks are started, only the marking tool related to the subtask is called, and the functions of all marking tools required by the marking task are not required to be integrated together, so that the software development difficulty is reduced, and the marking tool is more convenient to adjust. The adjustment includes increasing, decreasing, and replacing.
In a specific example of using the present labeling task management method, the setting of the labeling tools used by each subtask is performed on the server, for example, according to the contents shown in table 1 above. The tools 1, 2 and 3 are for example different software, which can be installed on a terminal and/or a server, for example. In step S40, after the user opens the subtask, the corresponding labeling tool is operated and the data to be processed is opened in the labeling tool.
In an exemplary embodiment, step S10 further includes: after a plurality of subtasks of the labeling task are created, setting the data source of the data to be processed of each subtask. The step S40 specifically includes: and after the user opens the subtask, acquiring the data to be processed from the data source of the data to be processed corresponding to the subtask and providing the data to the user. Thereby facilitating data management.
Specifically, in the present exemplary embodiment, step S10 further includes: when a labeling task is started, the initial data to be labeled is stored, for example, to a server. The initial data to be annotated is, for example, an original CT image. The step of setting the data source of the data to be processed of each subtask comprises the following steps: setting the data source of the data to be processed of the subtask at the starting point of the activation logic as the initial data to be marked. For example, in the example shown in fig. 2, the subtask a is the start point of the activation logic, and the data source is the initial data to be marked (see table 1). As shown in fig. 1, in the exemplary embodiment, the labeling task management method further includes step S50: the user processed data is stored, for example, to a server when the user completes the subtask. The step of setting a data source of the data to be processed of each subtask further comprises: and setting the data processed by the user as a data source of the data to be processed of the next subtask in the activation logic. For example, in the example shown in fig. 2, the data source of the data to be processed of the subtask B is the data of the subtask a after the user processing (see table 1). Therefore, the data are subjected to sealing management, and the quality and traceability of the marking are guaranteed.
In an exemplary embodiment, step S50 further includes: when the user completes a subtask, time information for completion of the subtask, user role information, and operation subtask information are recorded, for example, in a server. Therefore, the completion time of the subtasks, the roles of the users who complete the subtasks and the operations of the users on the subtasks can be conveniently checked.
FIG. 3 is a block diagram of an exemplary embodiment of a labeling task management system. The labeling task management system is used for implementing the labeling task management method. As shown in FIG. 3, the labeling task management system includes a processing module 50. In the exemplary embodiment, the labeling task management system includes, for example, a server, and the processing module 50 is disposed on the server, but is not limited thereto.
When receiving a labeling task request data, the processing module 50 creates several subtasks of the labeling task, each subtask has a task name for distinguishing from other subtasks, and sets activation logic of the several subtasks, and opens execution authority required by each subtask and execution authority of each user role. The processing module 50 has a default setting, for example, where the default setting includes information such as the number of subtasks to be created, activation logic, correspondence between subtasks and execution rights, and correspondence between user roles and execution rights. The processing module 50 creates sub-tasks and sets activation logic of several sub-tasks, execution authority required for opening each sub-task, and execution authority of each user character, for example, according to the default setting. The default settings are preset in the processing module 50 by a developer, for example, and can be adjusted as needed. The processing module 50 may also create subtasks and set activation logic for several subtasks, starting the execution authority required for each subtask, and the execution authority of each user role according to the information input by the user.
The processing module 50 also searches for execution rights corresponding to the user role according to the logged-in user role, wherein the logging-in is performed on the terminal or the web page, for example. The processing module 50 also generates image data for presenting the task name of the activated subtask corresponding to the found execution authority for the user to select to open the subtask, wherein the presentation is performed on a terminal or a web page, for example. Specifically, for example, the processing module 50 searches for a corresponding activated subtask according to the searched execution authority, and sends the task name of the searched subtask to the terminal or the web page to be presented to the user for the user to select to open the subtask.
The processing module 50 also outputs the data to be processed to the user after receiving an on signal for the user to turn on the subtask. The user opening subtask is performed on a terminal or a web page, for example, and the terminal or the web page sends a signal to the processing module 50 after receiving the opening operation of the user, and the processing module 50 outputs the data to be processed to the terminal or the web page for providing to the user, for example.
When the processing module 50 receives the plurality of labeling task request data, subtasks and activation logic of a plurality of subtasks are created for each labeling task request data, execution authority required by each subtask and execution authority of each user role are opened, and image data for displaying task names of the activated subtasks of all labeling tasks corresponding to the searched execution authority are generated. When a plurality of user roles log in simultaneously, the processing module 50 searches for the execution authority corresponding to the user role independently for each logged-in user role, generates image data for displaying the task name of the activated subtask corresponding to the searched execution authority, and outputs the data to be processed to provide to the user after receiving the opening signal for the user to open the subtask.
The labeling task management system enables the subtasks to be sequentially activated according to the set activation logic, and the user can only start the activated subtasks corresponding to the execution authority of the user roles used by the subtasks, so that the labeling tasks can be accurately, efficiently and universally managed.
In the illustrative embodiment, the processing module 50 also sets the annotation tool used by each subtask after creating several subtasks for the annotation task. The processing module 50 also invokes the corresponding annotation tool after receiving the user's turn-on signal to turn on the subtask and outputs the data to be processed in the annotation tool for the user. Therefore, when different subtasks are started, only the marking tool related to the subtask is called, and the functions of all marking tools required by the marking task are not required to be integrated together, so that the software development difficulty is reduced, and the adjustment is more convenient when a certain marking tool is adjusted, and the adjustment comprises the addition, the reduction and the replacement.
In the illustrative embodiment, as shown in FIG. 3, the labeling task management system further includes a plurality of labeling modules 70, each labeling module 70 running a labeling tool. Several marking modules 70 may operate, for example, with different marking tools, but are not limited thereto. The processing module 50 also initiates the corresponding annotation module 70 to invoke the corresponding annotation tool upon receipt of an on signal from the user to turn on the subtask and to output the data to be processed in the annotation tool for provision to the user. The labeling module 70 is disposed, for example, in a server, but is not limited thereto. In other exemplary embodiments, the annotation task management system further comprises a terminal coupled to the server, for example, and the annotation module 70 may be disposed at the terminal, for example.
In the illustrative embodiment, the processing module 50 also sets the data source of the data to be processed for each subtask after creating a number of subtasks for the labeling task. The processing module 50 also obtains the data to be processed from the data source of the data to be processed corresponding to the subtask after receiving the opening signal of the subtask by the user, and outputs the data to be processed to provide for the user. Thereby facilitating data management.
Specifically, in the present exemplary embodiment, as shown in fig. 3, the labeling task management system further includes a storage module 60, which is disposed, for example, in a server. The processing module 50 also stores the initial data to be marked in the storage module 60 when receiving a marking task request data. The initial data to be annotated is, for example, an original CT image. The processing module 50 also sets the data source of the data to be processed of the subtask located at the start point of the activation logic as the initial data to be annotated. The processing module 50 also stores the data processed by the user to the storage module 60 when receiving a completion signal for the user to complete the subtask. The processing module 50 also sets the user-processed data as a data source for the data to be processed for the next subtask in the activation logic. Therefore, the data are subjected to sealing management, and the quality and traceability of the marking are guaranteed.
In the exemplary embodiment, processing module 50 also stores time information for completion of the subtask, user role information, and operational subtask information to storage module 60 upon receipt of a completion signal from the user to complete the subtask. Therefore, the completion time of the subtasks, the roles of the users who complete the subtasks and the operations of the users on the subtasks can be conveniently checked.
It should be understood that although the present disclosure has been described in terms of various embodiments, not every embodiment is provided with a separate technical solution, and this description is for clarity only, and those skilled in the art should consider the disclosure as a whole, and the technical solutions in the various embodiments may be combined appropriately to form other embodiments that will be understood by those skilled in the art.
The above list of detailed descriptions is only specific to practical examples of the present invention, and they are not intended to limit the scope of the present invention, and all equivalent embodiments or modifications, such as combinations, divisions or repetitions of features, without departing from the technical spirit of the present invention are included in the scope of the present invention.
Claims (11)
1. The labeling task management method is characterized by comprising the following steps:
when a labeling task is started, a plurality of subtasks of the labeling task are firstly created, each subtask has a task name used for distinguishing the subtask from other subtasks, and then activation logic of the subtasks is set, and execution authority required by each subtask and execution authority of each user role are started;
searching the execution authority corresponding to the user role according to the logged-in user role;
displaying the task name of the activated subtask corresponding to the searched execution authority so as to enable the user to select to start the subtask; and
the data to be processed is provided to the user after the user opens the subtask.
2. The labeling task management method of claim 1, wherein the labeling task management method further comprises: after a plurality of subtasks of the labeling task are created, labeling tools used by the subtasks are set; the step of providing the data to be processed to the user after the user opens the subtask is specifically as follows: and after the user starts the subtask, the corresponding marking tool is called, and the data to be processed are provided for the user in the marking tool.
3. The labeling task management method of claim 1, wherein the labeling task management method further comprises: after a plurality of subtasks of the labeling task are created, setting data sources of data to be processed of each subtask; the step of providing the data to be processed to the user after the user opens the subtask is specifically as follows: and after the user opens the subtask, acquiring the data to be processed from the data source of the data to be processed corresponding to the subtask and providing the data to the user.
4. The labeling task management method of claim 3, wherein the labeling task management method further comprises: when a labeling task is started, storing initial data to be labeled; the step of setting the data source of the data to be processed of each subtask comprises the following steps: setting the data source of the data to be processed of the subtask at the starting point of the activation logic as the initial data to be marked; the labeling task management method further comprises the following steps: storing the data processed by the user when the user completes the subtask; the step of setting a data source of the data to be processed of each subtask further comprises: and setting the data processed by the user as a data source of the data to be processed of the next subtask in the activation logic.
5. The labeling task management method of claim 1, wherein the labeling task management method further comprises: and recording the time information, the user role information and the operation subtask information of the subtask completion when the user completes the subtask.
6. The labeling task management system is characterized by comprising a processing module (50), wherein when receiving labeling task request data, the processing module (50) firstly creates a plurality of subtasks of a labeling task, each subtask is provided with a task name used for distinguishing the subtask from other subtasks, and then sets activation logic of the subtasks, and opens execution permission required by each subtask and execution permission of each user role; the processing module (50) also searches the execution authority corresponding to the user role according to the logged-in user role; the processing module (50) also generates image data for displaying the task name of the activated subtask corresponding to the searched execution authority so as to enable the subtask to be selected by a user; the processing module (50) also outputs data to be processed to provide to a user after receiving an opening signal for the user to open a subtask.
7. The labeling task management system of claim 6, wherein the processing module (50) further sets labeling tools used by each subtask after creating a plurality of subtasks for a labeling task; the processing module (50) also calls a corresponding marking tool after receiving an opening signal of the user for opening the subtask and outputs data to be processed in the marking tool to be provided for the user.
8. The labeling task management system of claim 7, further comprising a plurality of labeling modules (70), each of the labeling modules (70) running a labeling tool; the processing module (50) also activates the corresponding marking module (70) to invoke the corresponding marking tool and output the data to be processed in the marking tool for the user after receiving an activation signal for the user to activate the subtask.
9. The labeling task management system of claim 6, wherein the processing module (50) further sets a data source of data to be processed for each subtask after creating a plurality of subtasks for the labeling task; the processing module (50) also acquires the data to be processed from the data source of the data to be processed corresponding to the subtask after receiving the starting signal of the subtask started by the user, and outputs the data to be processed to the user.
10. The labeling task management system of claim 9, further comprising a storage module (60); the processing module (50) also stores initial data to be marked into the storage module (60) when receiving marking task request data; the processing module (50) also sets the data source of the data to be processed of the subtask at the starting point of the activation logic as the initial data to be marked; the processing module (50) also stores the data processed by the user to the storage module (60) when receiving a completion signal of the user for completing the subtasks; the processing module (50) also sets the user-processed data as a data source for the data to be processed for the next subtask in the activation logic.
11. The labeling task management system of claim 10, wherein the processing module (50) further stores time information for completion of a subtask, user role information, and operational subtask information to the storage module (60) upon receipt of a completion signal from a user to complete the subtask.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211093269.XA CN117710796A (en) | 2022-09-08 | 2022-09-08 | Labeling task management method and labeling task management system |
| PCT/CN2023/110804 WO2024051406A1 (en) | 2022-09-08 | 2023-08-02 | Annotation task management method and annotation task management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211093269.XA CN117710796A (en) | 2022-09-08 | 2022-09-08 | Labeling task management method and labeling task management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117710796A true CN117710796A (en) | 2024-03-15 |
Family
ID=87933593
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211093269.XA Pending CN117710796A (en) | 2022-09-08 | 2022-09-08 | Labeling task management method and labeling task management system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN117710796A (en) |
| WO (1) | WO2024051406A1 (en) |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5795297A (en) * | 1996-09-12 | 1998-08-18 | Atlantis Diagnostics International, L.L.C. | Ultrasonic diagnostic imaging system with personal computer architecture |
| EP3846176A1 (en) * | 2013-09-25 | 2021-07-07 | HeartFlow, Inc. | Systems and methods for validating and correcting automated medical image annotations |
-
2022
- 2022-09-08 CN CN202211093269.XA patent/CN117710796A/en active Pending
-
2023
- 2023-08-02 WO PCT/CN2023/110804 patent/WO2024051406A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024051406A1 (en) | 2024-03-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20160071065A1 (en) | Information processing device, non-transitory computer readable medium, and information processing method | |
| RU2714609C1 (en) | Automation of document generation | |
| US7386793B2 (en) | Apparatus, method and program for supporting a review | |
| CN111126026B (en) | Method and tool for generating visual report form by analyzing SQL statement | |
| CN109688046A (en) | Issue management method, apparatus, equipment and storage medium | |
| US5964872A (en) | Method and system for tailoring common environments | |
| JP5747698B2 (en) | Requirements management support device | |
| CN111061733B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| Goderis et al. | Benchmarking workflow discovery: a case study from bioinformatics | |
| CN112036843A (en) | Flow element positioning method, device, equipment and medium based on RPA and AI | |
| CN117710796A (en) | Labeling task management method and labeling task management system | |
| US11816770B2 (en) | System for ontological graph creation via a user interface | |
| CN115510361A (en) | Data chart page generation method based on visual configuration and related equipment | |
| Gomez et al. | Experimenting with a Machine Generated Annotations Pipeline | |
| CN111814439B (en) | Automatic description method and device for flow chart | |
| CN112286879B (en) | Metadata-based data asset construction method and device | |
| CN110515653B (en) | Document generation method and device, electronic equipment and computer readable storage medium | |
| US8839097B2 (en) | System and method for information encapsulation for providing multiple deliverable formats from one information source | |
| JP2004110378A (en) | Object-oriented development supporting method and device | |
| CN115659182B (en) | Model updating method, device and equipment | |
| US11940964B2 (en) | System for annotating input data using graphs via a user interface | |
| WO2024065445A1 (en) | Method and apparatus for extending function block capability, electronic device, and storage medium | |
| CN110673895B (en) | Method and device for Hibernate to create Session factory | |
| US20220358445A1 (en) | Training assignment tool | |
| CN115470127B (en) | Page compatibility processing method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |