MVP tool to convert from one ContentFormat to another (protocol to workflow) #14
Labels
Priority: 3 - Normal
An issue that must be resolved within the normal release cycle.
Type: Feature
Entirely new functionality, with new requirements and mockups as needed.
Milestone
For protocols imported or indexed in our platform... users should have the option to enhance to such an extent that they are fully fleshed out workflows.
This is imagined as a way, for example, of converting protocols.io (or other) protocol "steps" into a set of placeholder tools in a TeselaGen workflow. The user would then convert each step to a proper tool or tools and link them as appropo.
Otherwise, for a simple pdf... it could just be a convenient side-by-side or standard browser tab view that could be torn off so the user could see the protocol steps while creating a workflow... (trivial example).
In any case, the workflow should be cross linked with the protocol.
i.e. in the protocol... a list of linked workflows (where this protocol is utilized).
i.e. in the workflow... a list of linked protocols (that this workflow is based on).
The text was updated successfully, but these errors were encountered: