TMSS-190: added duration and specified_duration as Subtask properties for reusability. Reused it in shift_successors_until_after_stop_time.

TMSS-280: Move UniqueConstraint for Template to superclass since Django 3.0 use interpolation of class. Actually we use this version already. Check at tmss_test_environment for version

TMSS-207:  renamed TaskConnector to TaskConnectorType, and the related names of the input_role and output_role. Simplified and made code more generic for linking the created TaskBlueprints from the existing TaskDraft and TaskRelationDraft

TMSS-200: Remove SubtaskInputSelectionTemplate since and use TaskRelationSelectionTemplate instead. Fix test.

TMSS-207: raise SubtaskSchedulingException when start/stop times are None. add default start/stop times.

TMSS-206: added easy to use properties successors and predecessors to SubTaks, and expose them via nested urls

TMSS-180: (and TMSS-60) implemented a TMSSSubTaskBusListener in a TMSSClient package, and used it to send/receice TMSS Subtask status changes messages

TMSS-60: added related names to input/outputs/dataproducts of subtask models and viewsets, so we can 'walk the graph'

TMSS-56: as discussed with the architect, the scheduler_input_doc is not needed, so I removed it (which also solved the issue with serializers/scheduling.py where the SubtaskSerializerJSONeditorOnline referred to the incorrect self.instance.specifications_template.schema)

TMSS-61: add functionality to connect observation output to preprocessing pipeline and use that populate demo stuff

TMSS-180: (and TMSS-60) implemented a TMSSSubTaskBusListener in a TMSSClient package, and used it to send/receice TMSS Subtask status changes messages


(cherry picked from commit 7d07a86f)

TMSS-180: (and TMSS-60) implemented a TMSSSubTaskBusListener in a TMSSClient package, and used it to send/receice TMSS Subtask status changes messages


(cherry picked from commit 7d07a86f)

TMSS-180: (and TMSS-60) implemented a TMSSSubTaskBusListener in a TMSSClient package, and used it to send/receice TMSS Subtask status changes messages

TMSS-60: added related names to input/outputs/dataproducts of subtask models and viewsets, so we can 'walk the graph'

TMSS-173: simplified validation of json_strings against schema's. The original design (proof-of-concept) had the validation in the Subtask class, and the suggestion/goal of this ticket TMSS-173 was to change that into a reusable mixin. Using a mixin is certainly possible, and the 1st implementation in this ticket was a good start, but it also showed that the whole class/mixin based approach requires too much administration (keeping track of which fields to use). This new solution with just a validation method is far simpler, and just as reusable.

Jörn Künsemöller authored 5 years ago and Jorrit Schaap committed 4 years ago

TMSS-162: Add user reference to subtask and log on save to also log creation and updates through ORM

Jörn Künsemöller authored 5 years ago and Jorrit Schaap committed 4 years ago

TMSS-162: Add log filtering by subtask, only log updates that affect state and add  functional test for log behavior