Extension of Workflow classes
We, as area A, are putting the hands on workflow classes and hence generating new developments based on the feedback from real use cases.
There are already a couple of ideas that would lead to a couple on new classes extending the eln/workflow arsenal.
A "breaking sample" or "cutting sample" Task class (this will live in the eln path, though)
A Task where no input or output is needed because it is part of a bigger procedure (directly into workflow2 path)
We will try to implement these simple classes equipped with some simple normalize function.
I guess @ladinesa would like to checkout this as the second point would directly affect the features needed in the visualization tool.