Our workflows are any documents that guide users for the analysis of any type of biomedical data. It could be tutorials consiting of screenshots for the use of some proprietary software tools, large software programs, but most of our workflows consist of scripts in different programming langauges (e.g. R, Python, or shell) that use various open-source tools or libraries.
Workflows from BioWorkflows can be implemented in any languages or tools. Some of them are supposed to be cross-platform and work for most common computing environments, and may work on certain operating systems and may rely on particular libraries or interpreters. You should check for descriptions and reviews of the workflows to determine their run-time environment.
Unlike dockstore that emphasizes on the use of docker containers, nf-core that facilitates the use of nextflow, BioWorkflows.com does not require the use of any particular workflow language or technology. All workflows are however marked with different "tags" so that you can see what technologies they have used, even search for workflows that use particular workflow language.
Another difference is we value the effort for authors to maintain their workflows and create an environment for them to be at least partially compensated.
The source code of premium workflows are masked but you can still check their descriptions, and sample input and output to determine if they are the right workflow to analyze your data.
You will be able to see all source code, as well as download all attached data and scripts after you purchase the workflows. Feel free to try any workflow since all purchases are backed by a 30-day money-back guarantee.
A team plan is convenient if you are managing a team. You can create one or more organizations and invite your team members to the organization. All team members can see each others unpublished workflows so that you know what has been published and has been working on in your team. You will be allowed to buy workflows with a volumn license so that the workflow can be used by all team members. You will also enjoy a discount for all the workflows you purchase. Finally, you are responsible for the disk storage for all team members so you should invite others as collaborators if would like to allow them to join the team but paying for their own resources.
You can create a workflow, set a price, and list it for sale. You can also try to answer questions and claim bounties with either forum posts or workflows. Your earning (after deducting bioworkflows service fee) will be stored as store credit in your account. You can withdraw your credit at any time.
If you register as a developer, you will be paid for any workflow that uses the tool that you develop.
All sales are final after 30 days so you can only withdraw funds from workflows that you sold more than 30 days ago.
Each bounty comes with some specific questions or requirements from the poster. When you see a bounty and think you can resolve it, you can claim the bounty as follows:
1) You can post an answer in the topic and claim the bounty with it.
The bounty poster and accept or deny your claim.
2) If the bounty requests a workflow, you can create a workflow and claim the bounty with it, which basically means that you agree to sell the workflow to the bounty poster regardless of the price you set for your workflow.