SOPs

What is a SOP?
19 SOPs visible to you, out of a total of 20

This workflow uses a slightly modified version of the Santa Cruz Reaction (SCR) protocol by Kapp et al. 2021 for library building of museum specimens. The reaction volumes can be halved to reduce reagent costs, lower volumes have not been tested yet. Please cite the original publication if using this method: https://doi.org/10.1093/jhered/esab012

Creators: Alyssa Paul, Carla Gustave, Owain Powell, Ben Price

Submitter: Ben Price

DOI: 10.48546/workflowhub.sop.20.1

No description specified

Creators: Ben Price, Owain Powell, Alyssa Paul, Carla Gustave, Jordan Beasley

Submitter: Ben Price

DOI: 10.48546/workflowhub.sop.22.1

No description specified

Creator: Felix Shaw

Submitter: Felix Shaw

Tutorial and specification for packaging IEEE 2791-2020 (BioCompute Objects/BCOs) as RO-Crate Research Objects.

BioCompute Object (BCO) is a standard (IEEE 2791-2020) for describing computational workflows for regularory submission, e.g. a genomics workflow as part of personalized medicine.

RO-Crate is a community-based specification for research data packaging of Research Objects with rich metadata, based on open standards and vocabularies like JSON-LD and schema.org.

BCO RO-Crate is the combination ...

Creators: Stian Soiland-Reyes, Jonathon Keeney, Hadley King, Janisha Patel, Alex Coleman

Submitter: Stian Soiland-Reyes

No description specified

Creator: Ambarish Kumar

Submitter: Ambarish Kumar

Detects SNPs and short INDELs.

Creator: Ambarish Kumar

Submitter: Ambarish Kumar

Detects SNPs and short INDELs.

Creator: Ambarish Kumar

Submitter: Ambarish Kumar

This is a project specific guide for the Bioiversity Genomics Europe (BGE project use of WorkflowHub.

The BY-COVID project is producing workflows. We need to register those workflows in WorkflowHub:

  1. To give visibility to the workflows created by the project and by the different networks and communities within the project
  2. To give visibility to the workflows used by project that were created
  3. To share workflows across the project, within project networks and externally
  4. To credit and cite the people making the workflows and the networks to which they belong
  5. To track the versions of ...
Powered by
(v.1.16.0)
Copyright © 2008 - 2024 The University of Manchester and HITS gGmbH