Changes between Version 1 and Version 2 of RelationalModel

Timestamp:

04/18/26 20:37:12 (2 weeks ago)

Author:

231141

Comment:

--

RelationalModel

@@ -37 +37 @@
 This ensures that each !TaskRequest results in exactly one assigned worker, while still allowing flexible and parallel interaction between clients and workers during the offer phase.
 
+=== Subtasks and Progress Tracking ===
+The system models subtasks as a decomposition of a !Task, allowing complex tasks to be broken down into smaller, manageable units.
+
+Subtasks are not independently assignable; instead, they are all performed by the worker assigned to the main task. This design ensures consistency and avoids unnecessary complexity in task assignment.
+
+Each subtask includes its own status (e.g., pending, in progress, completed), which enables detailed tracking of progress within a task.
+
+By monitoring the completion of subtasks, the system can provide a more accurate representation of overall task progress and improve transparency for both clients and workers.
+
 === Category and Matching ===
 Tasks are categorized using the Category entity, while workers can be associated with multiple categories through the Worker_Category relationship. 
@@ -45 +54 @@
 
 === Pricing and Badge System ===
-The system includes a Badge entity that determines the minimum price a client or worker can offer within a specific category. Each worker can have different badges for different categories, modeled through the Worker_Badge relationship.
+The system includes a Badge entity that determines the minimum price a client or worker can offer within a specific category. Each category may consist of multiple subcategories, and the badge for a given category is calculated based on the worker’s ratings across all tasks performed within its subcategories.
+ Each worker can have different badges for different categories, modeled through the Worker_Badge relationship.
 
 This ensures that pricing is controlled and reflects the worker’s experience and rating history.