diff --git a/manuscript.html b/manuscript.html index f5edbbc..0f21d98 100644 --- a/manuscript.html +++ b/manuscript.html @@ -58,8 +58,8 @@ - - + + @@ -90,9 +90,9 @@ - - - + + + @@ -109,9 +109,9 @@

BrAPI Success Stories

This manuscript -(permalink) +(permalink) was automatically generated -from plantbreeding/BrAPI-Manuscript2@f12e37e +from plantbreeding/BrAPI-Manuscript2@0ca6605 on February 20, 2024.

Authors

@@ -275,6 +275,11 @@

Analytics (QBMS, Mr Bean, etc)

  • Alternate solutions/ why is it better with BrAPI
  • future related use cases, areas to improve
    • +

    Modern breeding programs can utilize data management systems to maintain both phenotypic and genotypic data. Numerous systems are available for adoption. To fully leverage the benefits of digitalization in this ecosystem, breeders need to utilize data from different sources to make efficient data-driven decisions. With increased computational power at their disposal, scientists can construct more advanced analysis pipelines by combining various data sources.

    + +

    To meet this demand, many breeding management systems have developed customized built-in analysis pipelines. However, these pipelines are static and may not accommodate evolving needs. As a result, API interfaces have been developed to facilitate data communication with other systems. The Breeding API (BrAPI) project specifies a standardized interface for plant phenotype/genotype databases, enabling them to share data with crop breeding applications. This promotes interoperability among plant breeding databases and allows third-party plugins to integrate with the ecosystem, delivering added value.

    +

    In the QBMS development team, we have identified a technical barrier between the breeding management systems’ BrAPI interface and the scientists who create analysis scripts and pipelines. This barrier arises from the complexity of managing API backend processes, such as authentication, tokens, TCP/IP protocol, JSON format, pagination, stateless calls, asynchronous communication, database IDs, and more. To bridge this gap, we have developed the QBMS R package. This package abstracts the technical complexities, providing breeders (our end users) with stateful action verbs/functions that are familiar to them when navigating their GUI systems. This enables them to query and extract data into a standard data frame structure, consistent with their use of R language, one of the most common statistical tools in the breeding community.

    +

    Since its release on the official CRAN repository in October 2021, the QBMS R package has garnered over 7250 downloads. Several tools, such as MrBean, rely on the QBMS package as their source data adapter. Moreover, the community has started building extended solutions on top of it. QBMS can serve as a cornerstone in the breeding modernization revolution by providing access to actionable data and enabling the creation of dashboards to reduce the time between harvest and decision-making for the next breeding cycle.

    brapi sync