BioCompute Spring Workshop 2024: Difference between revisions
ChinweokeO (talk | contribs) |
|||
| Line 10: | Line 10: | ||
== Abstract == | == Abstract == | ||
BioCompute | Documenting computational workflows has historically been a challenge for researchers and reviewers. Often, there are no clear guidelines for describing these workflows, leading to ad hoc definitions and descriptions that are insufficient for comprehension and reproducibility. BioCompute, an abbreviation for the IEEE standard 2791-2020, offers a structured framework for describing workflows in a precise yet adaptable manner. A BioCompute Object (BCO) represents a workflow that adheres to this standard. This standard breaks down a workflow into its core components, aligning them with established data standards and ontologies. BioCompute significantly aids in streamlining workflow data, managing complexity across multiple versions, and enhancing reproducibility. | ||
As the field continues to evolve, addressing regulatory concerns becomes paramount, necessitating a common language for all stakeholders. The BioCompute community, comprised of over 400 individuals, has crafted a framework that offers guidance without imposing undue burdens on sponsors or reviewers. To date, BCO has been embraced by three FDA centers, effectively reducing delays in regulatory submissions. An ongoing pilot project involving the BioCompute team, FDA, and industry sponsors aims to improve communication efficiency and fluidity during submission and review processes. | |||
The [https://www.biocomputeobject.org/ BioCompute Portal], serving as the central platform for creating and submitting BCOs, has seen significant improvements in the past year, including Google and ORCID integration and an enhanced user interface. Furthermore, a new Portal instance at the FDA, along with four tools for authoring BCOs directly from various platforms (BCOnexus, Seven Bridges APP, the HIVE, and Galaxy platforms), and expanded documentation, make it easier to create, share, edit, and publish BCOs online. Overall, this project strives to streamline and secure the submission process. The FDA can retrieve BCOs from the public BCODB upon request, and with APIs and authentication tokens, users can directly submit to FDA portal API endpoints and interact with BCOs and their implementations seamlessly. | |||
== Schedule == | == Schedule == | ||
Revision as of 19:05, 11 October 2023
This in-person workshop provides an opportunity to learn about BioCompute Objects and interoperability between 3 platforms that host BioCompute Objects.
Date & Time: May 10th, 2024, 8 AM - 5 PM
Location: Great Room, White Oak Campus, FDA center
Event Registration: Eventbrite
Abstract
Documenting computational workflows has historically been a challenge for researchers and reviewers. Often, there are no clear guidelines for describing these workflows, leading to ad hoc definitions and descriptions that are insufficient for comprehension and reproducibility. BioCompute, an abbreviation for the IEEE standard 2791-2020, offers a structured framework for describing workflows in a precise yet adaptable manner. A BioCompute Object (BCO) represents a workflow that adheres to this standard. This standard breaks down a workflow into its core components, aligning them with established data standards and ontologies. BioCompute significantly aids in streamlining workflow data, managing complexity across multiple versions, and enhancing reproducibility.
As the field continues to evolve, addressing regulatory concerns becomes paramount, necessitating a common language for all stakeholders. The BioCompute community, comprised of over 400 individuals, has crafted a framework that offers guidance without imposing undue burdens on sponsors or reviewers. To date, BCO has been embraced by three FDA centers, effectively reducing delays in regulatory submissions. An ongoing pilot project involving the BioCompute team, FDA, and industry sponsors aims to improve communication efficiency and fluidity during submission and review processes.
The BioCompute Portal, serving as the central platform for creating and submitting BCOs, has seen significant improvements in the past year, including Google and ORCID integration and an enhanced user interface. Furthermore, a new Portal instance at the FDA, along with four tools for authoring BCOs directly from various platforms (BCOnexus, Seven Bridges APP, the HIVE, and Galaxy platforms), and expanded documentation, make it easier to create, share, edit, and publish BCOs online. Overall, this project strives to streamline and secure the submission process. The FDA can retrieve BCOs from the public BCODB upon request, and with APIs and authentication tokens, users can directly submit to FDA portal API endpoints and interact with BCOs and their implementations seamlessly.
Schedule
TBD
Organization Committee
Mark Walderhaug - U.S Food & Drug (FDA)
Luis Santana-Quintero - U.S Food & Drug (FDA)
Raja Mazumder - The George Washington University (GWU)
Jonathon Keeney - The George Washington University (GWU)
Charles Hadley King - The George Washington University (GWU)
Tianyi Wang - The George Washington University (GWU)
Chinweoke Okonkwo - The George Washington University (GWU)
Omar Serang - DNAnexus
Sam Westreich - DNAnexus
Dennis A. Dean, II - Velsera
Phil Webster- Velsera