diff --git a/README.md b/README.md
index 8943813..a3d9993 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
# Output directory containing the formatted manuscript
The [`gh-pages`](https://github.com/plantbreeding/BrAPI-Manuscript2/tree/gh-pages) branch hosts the contents of this directory at .
-The permalink for this webpage version is .
+The permalink for this webpage version is .
To redirect to the permalink for the latest manuscript version at anytime, use the link .
## Files
@@ -35,4 +35,4 @@ Verifying timestamps with the `ots verify` command requires running a local bitc
## Source
The manuscripts in this directory were built from
-[`f87c4197b7cb26dfecb51960773f70097e1bdfd5`](https://github.com/plantbreeding/BrAPI-Manuscript2/commit/f87c4197b7cb26dfecb51960773f70097e1bdfd5).
+[`01f97e786525879db23a1d72a3716051fe743bd3`](https://github.com/plantbreeding/BrAPI-Manuscript2/commit/01f97e786525879db23a1d72a3716051fe743bd3).
diff --git a/index.html b/index.html
index 770cbf1..1970071 100644
--- a/index.html
+++ b/index.html
@@ -123,8 +123,8 @@
-
-
+
+
@@ -340,9 +340,9 @@
-
-
-
+
+
+
@@ -359,9 +359,9 @@
The Hybrid Phenotyping Information System (PHIS6), based on the OpenSILEX framework, is an ontology-driven information system based on semantic web technologies. PHIS is deployed in several field and greenhouse platforms of the French national PHENOME and European EMPHASIS infrastructures. It manages and collects data from basic phenotyping and high throughput phenotyping experiments on a day to day basis. PHIS unambiguously identifies all the objects and traits in an experiment, and establishes their types and relationships via ontologies and semantics.
-
PHIS has been designed to be BrAPI-compliant. PHIS adheres to the standards and protocols specified by BrAPI and implements various services aligning with the BrAPI standards, encompassing the Core, Phenotyping, and Germplasm modules. This enables integration and compatibility with BrAPI-compliant systems and platforms. This prerequisite served as the basis for formalizing the data model, while also facilitating compatibility with other standards, such as the Minimal Information About a Plant Phenotyping Experiment (MIAPPE7). By integrating BrAPI requirements into its structure, PHIS not only meets the standards of the phenotyping field, but also strengthens its capacity for interoperability and effective collaboration in the wider context of plant breeding and related fields. The fact that data within a PHIS instance can be queried through BrAPI services makes the indexing of PHIS in FAIDARE8 very easy to implement.
-
Furthermore, as PHIS offers BrAPI-compliant Web Services, it simplifies the integration and data exchange with other European information systems that handle phenotyping data. The adherence to BrAPI standards ensures a common interface and compatibility, facilitating communication and collaboration between PHIS and other systems in the European context. This interoperability not only eases data sharing, but also promotes a more coherent and efficient approach to the management and use of phenotyping data on various platforms and research initiatives within the European scientific community.
+
PHIS has been designed to be BrAPI-compliant. PHIS adheres to the standards and protocols specified by BrAPI and implements various services aligning with the BrAPI standards, encompassing the Core, Phenotyping, and Germplasm modules. This enables integration and compatibility with BrAPI-compliant systems and platforms, such as OLGA, a genebank accessions management system, to retrieve accession information. This prerequisite served as the basis for formalizing the data model, while also facilitating compatibility with other standards, such as the Minimal Information About a Plant Phenotyping Experiment (MIAPPE7). By integrating BrAPI requirements into its structure, PHIS not only meets the standards of the phenotyping field, but also strengthens its capacity for interoperability and effective collaboration in the wider context of plant breeding and related fields. The fact that data within a PHIS instance can be queried through BrAPI services enables indexing of PHIS in FAIDARE8.
+
Furthermore, as PHIS offers BrAPI-compliant Web Services, it simplifies the integration and data exchange with other European information systems that handle phenotyping data. The adhesion to BrAPI standards ensures a common interface and compatibility, facilitating communication and collaboration between PHIS and other systems in the European context. This interoperability not only eases data sharing, but also promotes a more coherent and efficient approach to the management and use of phenotyping data on various platforms and research initiatives within the European scientific community.
PIPPA
PIPPA9 is a data management system used for collecting data from the WIWAM10 range of automated high throughput phenotyping platforms. These platforms have been deployed at different research institutes and commercial breeders across Europe. They can be setup in a variety of configurations with different types of equipment including weighing scales, cameras, and environment sensors. The software features a web interface with functionality for setting up new experiments, planning imaging and irrigation treatments, linking metadata to pots (genotype, growth media, manual treatments), importing data, exporting data, and visualizing data. It also supports the integration of image analysis scripts and connections to a compute cluster for job submission.
Francisco J. Agosto-Pérez
+
+
+0000-0002-5059-253X
+·
+agostof
+
+
+Cornell University
+· Funded by Innovation Lab for Crop Improvement Cornell, FFAR
+
Isabelle Alic
+
+
+0000-0002-8961-6068
+·
+Isabelle-inrae
+
+
+MISTEA, University of Montpellier, INRAE, Institut Agro, Montpellier, France
+· Funded by This work was supported by the Agence Nationale de la Recherche, programme Investissements d’avenir, ANR-11-INBS-0012 (Phenome)
+
Sebastian Beier
+
+
+0000-0002-2177-8781
+·
+sebeier
+
+
+Institute of Bio- and Geosciences (IBG-4: Bioinformatics), CEPLAS, Forschungszentrum Jülich GmbH, Wilhelm Johnen Straße, 52428 Jülich, Germany; Bioeconomy Science Center (BioSC), Forschungszentrum Jülich GmbH, 52428 Jülich, Germany
+
+
Gabriel Besombes
+
+·
+Gabriel-Besombes
+
+
+MISTEA, University of Montpellier, INRAE, Institut Agro, Montpellier, France
+· Funded by This work was supported by the Agence Nationale de la Recherche, programme Investissements d’avenir, ANR-11-INBS-0012 (Phenome)
+
+
Alice Boizet
+
+
+0000-0003-4096-6689
+·
+aliceboizet
+
+
+CIRAD, UMR AGAP Institut, Montpellier, France.; AGAP Institut, CIRAD, INRAE, Institut Agro, Université de Montpellier, Montpellier, France.
+
Terry Casstevens
+
+
+0000-0001-7602-0487
+·
+tcasstevens
+
+
+Buckler Lab and Institute for Genomic Diversity, Cornell University
+
+
Arnaud Charleroy
+
+
+0009-0009-7575-3617
+·
+niio972
+
+
+MISTEA, University of Montpellier, INRAE, Institut Agro, Montpellier, France
+· Funded by This work was supported by the Agence Nationale de la Recherche, programme Investissements d’avenir, ANR-11-INBS-0012 (Phenome)
+
+
Keo Corak
+
+·
+keocorak
+
+
+USDA-ARS Genomics and Bioinformatics Research Unit
+
+
Chaney Courtney
+
+·
+chaneylc
+
+
+Clemson University
+
+
Mariano Crimi
+
+
+Integrated Breeding Platform
+
+
Gouripriya Davuluri
+
+
+Leibniz Institute of Plant Genetics and Crop Plant Research
+
+
Jeremy Destin
+
+
+Université Paris-Saclay, INRAE, Bioinformatics, Plant Bioinformatics Facility, Versailles, France; Université Paris-Saclay, INRAE, URGI, Versailles, France
+
+
Ajay Dhungana
+
+·
+GenAjay
+
+
+Louisiana State University (LSU)
+
Manuel Feser
+
+
+0000-0001-6546-1818
+·
+feserm
+
+
+Leibniz Institute of Plant Genetics and Crop Plant Research; Graduate School DILS, Bielefeld Institute for Bioinformatics Infrastructure (BIBI)
+
Valentin Guignon
+
+
+0000-0003-0903-6811
+·
+guignonv
+
+
+Bioversity International, Parc Scientifique Agropolis II, 34397 Montpellier, France
+
+
Corina Habito
+
+
+Integrated Breeding Platform
+
+
Asis Hallab
+
+
+0000-0002-2421-5431
+·
+https://github.com/asishallab
+
+
+Jülich research center, Institute of Bio- and Geosciences (IBG), Bioinformatics (IBG-4) and Bingen Technical University of Applied Sciences, Germany
+
Pascal Neveu
+
+
+0000-0003-4189-7793
+·
+pascalneveu
+
+
+MISTEA, University of Montpellier, INRAE, Institut Agro, Montpellier, France
+· Funded by This work was supported by the Agence Nationale de la Recherche, programme Investissements d’avenir, ANR-11-INBS-0012 (Phenome)
+
+
Tim Parsons
+
+
+0000-0001-6209-2455
+·
+timparsons
+
+
+Breeding Insight, Cornell University
+· Funded by U.S. Department of Agriculture, under agreement numbers [8062-21000-043-004-A, 8062-21000-052-002-A, and 8062-21000-052-003-A]
+
+
Nick Palladino
+
+
+0009-0009-1645-297X
+·
+nickpalladino
+
+
+Breeding Insight, Cornell University
+· Funded by U.S. Department of Agriculture, under agreement numbers [8062-21000-043-004-A, 8062-21000-052-002-A, and 8062-21000-052-003-A]
+
+
Cyril Pommier
+
+
+0000-0002-9040-8733
+·
+cpommier
+
+
+Université Paris-Saclay, INRAE, Bioinformatics, Plant Bioinformatics Facility, Versailles, France; Université Paris-Saclay, INRAE, URGI, Versailles, France
+· Funded by This work was supported by the Agence Nationale de la Recherche, programme Investissements d’avenir, ANR-11-INBS-0012 (Phenome)
+
+
Jean-François Rami
+
+
+0000-0002-5679-3877
+·
+jframi
+
+
+CIRAD, UMR AGAP Institut, Montpellier, France.; AGAP Institut, CIRAD, INRAE, Institut Agro, Université de Montpellier, Montpellier, France.
+
Mathieu Rouard
+
+
+0000-0003-0284-1885
+·
+mrouard
+
+
+Bioversity International, Parc Scientifique Agropolis II, 34397 Montpellier, France
+
+
Joseph Ruff
+
+
+Royal Botanic Gardens, Kew
+
+
Guilhem Sempéré
+
+
+0000-0001-7429-2091
+·
+GuilhemSempere
+
+
+CIRAD (french agricultural research and international cooperation organization); South Green Platform
+
Kauê de Sousa
+
+
+0000-0002-7571-7845
+·
+kauedesousa
+
+
+Digital Inclusion, Bioversity International, Montpellier, France
+
+
Anne Tireau
+
+
+0000-0001-8501-6922
+·
+annetireau
+
+
+MISTEA, University of Montpellier, INRAE, Institut Agro, Montpellier, France
+· Funded by This work was supported by the Agence Nationale de la Recherche, programme Investissements d’avenir, ANR-11-INBS-0012 (Phenome)
+
+
Clarysabel Tovar
+
+
+Integrated Breeding Platform; Leafnode LLC
+
Vivian Bass Vega
+
+
+0009-0002-2476-9888
+·
+VivianBass
+
+
+Bingen Technical University of Applied Sciences, Berlinstraße 109, 55411 Bingen am Rhein, Germany
+
+
Stephan Weise
+
+
+0000-0003-4031-9131
+
+
+Leibniz Institute of Plant Genetics and Crop Plant Research
+
+
Shawn C Yarnes
+
+
+0000-0002-1090-0403
+·
+SCYarnes
+
+
+Breeding Insight, Cornell University
+· Funded by U.S. Department of Agriculture, under agreement numbers [8062-21000-043-004-A, 8062-21000-052-002-A, and 8062-21000-052-003-A]
+
+
+
+
✉ — Correspondence possible via GitHub Issues
+or email to
+Peter Selby <ps664@cornell.edu>.
+
+
Abstract
+
Population growth and climate change require extraordinary efforts to increase efficiency in breeding programs around the world. In the last few years, genomics technologies and genomic prediction approaches have provided a boost in genetic gain in breeding, but has also created a flood of data that needs careful management to be fully harnessed.
+The Breeding API (BrAPI) project is an international, grass-roots effort to enable more efficient data management by enabling interoperability among plant breeding databases and tools, using a standardized RESTful web service API specification for communicating plant breeding data.
+This community driven standard is free to be used by anyone interested in plant breeding data management, including trial data, phenotypic data and genotyping data management.
+This manuscript describes advances in implementations of BrAPI in different breeding tools, and outlook for the current version of BrAPI.
+
Introduction
+
+
To address consequences of climate change and population growth, plant and animal breeding needs to become more efficient and data driven to ensure a healthy, resilient, and sustainable agricultural production system. Modern breeding techniques require large amounts of high quality data to be effective, requiring digital methods for data collection, management, and analysis. Interoperability between breeding software tools, systems, and databases can substantially increase the efficiency of a breeding program. The ability to efficiently share data means access to larger and more complete datasets, enabling more accurate computational models, more accurate predictions, and improved selections.
+
The Breeding API (BrAPI) project is an effort to enable interoperability among breeding tools, systems, and databases. BrAPI is a standardized Representational State Transfer (REST), web service, Application Programming Interface (API), specification for breeding and related agricultural data.1 By using the BrAPI standard, breeding software can more easily become interoperable, allowing groups to more easily share data and software tools.
+
This manuscript will present BrAPI in its latest iteration. This includes a short technical description of the standard and a showcase of the applications, services, and tools available in the BrAPI community. BrAPI has become an essential part of the digital infrastructure for breeding applications and related agricultural projects. It is the intention of this manuscript to demonstrate the value of BrAPI to the wider scientific community as an effective and efficient means to collaborate and share resources.
+
How it works
+
An API is a technical connection between two pieces of software. Just as a Graphical User Interface (GUI) or a Command Line Interface (CLI) allows a human user to interact with a piece of software, an API allows one software application to interact with another. A GUI or CLI might allow a user to input data, read data, and start processes within an application. An API allows one piece of software (sometimes called a client, user agent, or service consumer) to programmatically input data, read data, and start process within another piece of software (sometimes called a server or service provider).
+
A REST style web service is a type of API commonly used in today’s modern web infrastructure. REST is a technical architecture that describes the stateless transmission of data between applications. Typically, RESTful web service APIs are implemented using the standard HTTP protocol that most of the modern internet is built upon. These implementations generally use JavaScript Object Notation (JSON) to represent the data being transferred. Both HTTP and JSON are programming language agnostic, very stable, and very flexible. This means BrAPI can be implemented in almost any piece of software, and can solve a wide range of use cases.
+
Data repositories and service providers can choose to represent their data as a BrAPI compatible API. By mapping the internal data structures to the standard models, data repositories can easily expose data to the outside world. Similarly, they can accept new data from external sources and automatically map the new data into an existing database. Client application developers can take advantage of this standardization by building tools and connectors that integrate with all BrAPI compatible data repositories. Visualization, reporting, analytics, data collection, and quality control tools can be built once and shared with other organizations following the standards. As the number of BrAPI compatible databases, tools, and organizations grows, so does the value added by implementing the standard into a given application.
+
Project Updates
+
Over its lifetime, the BrAPI project has grown and changed substantially. The latest stable version of the specification (v2.1) looks vastly different from the first version (v1.0) released in 2017. The total size of the specification has almost quadrupled in that time, going from 51 endpoints documented in v1.0 to 201 endpoints documented in v2.1. Because of this growth, the specification documents were reorganized into four modules: BrAPI-Core, BrAPI-Germplasm, BrAPI-Genotyping, and BrAPI-Phenotyping. Figure 1 shows a simplified domain map of the whole BrAPI v2.1 data model, divided into the organizational modules. The early versions of the specification focused on read-only phenotype data, with a small consideration to the other domains. Now the specification has a full representation of most of the major concepts applicable to the breeding process. The new specification is also internally consistent, easier to navigate, and allows for read, write, and update capabilities. None of those qualities were a guarantee for the earlier versions.
+
+
+
+Figure 1: A simplified domain map of the whole BrAPI data model, divided into organizational modules. A more detailed Entity Relationship Diagram (ERD) is available on brapi.org.
+
+
+
As the specification has matured, so have the tools, services, and libraries available to the community to work with the specification. Every version of the specification is now released with a change log to guide developers upgrading from a previous version, an Entity Relationship Diagram (ERD) to describe the whole data model visually, and a JSON Schema data model to be used in some automated development efforts. For groups who are using Java, Java Script, Python, R, or Drupal, there are community maintained libraries available that contain full BrAPI implementations ready to be added to some existing code. The BrAPI Test Server and the BRAVA validation tool are both still available to the community for testing purposes, and they have been maintained to support every version of the specification. Finally, there are three new resource list pages on brapi.org to advertise the BrAPI compatible software available in the community. The BrAPPs list page, servers list page, and compatible software list page showcase many of the BrAPI compatible applications and data resources available in the community.
+
Community Growth
+
The international BrAPI Community consists of software developers, breeders, and other scientists working on BrAPI related projects and data sources. This community is what sustains the BrAPI project, builds implementations, maintains development tools, and provides input to enhance the specification. As the project has grown, so has the community. The BrAPI project started in June 2014 with less than ten people coming together to discuss the idea. Over the next ten years, the community has grown to between 200 and 250 members.
+
The BrAPI Hackathons are a major staple of the BrAPI community. Twice a year, the community gathers to discuss the specification and collaborate on BrAPI related projects. This time is very valuable to the community; for some organizations, the hackathon is the only time during the year when they have time to work on anything related to BrAPI. During the COVID-19 pandemic, virtual hackathons took the place of in-person events. While the virtual hackathons do not provide the same level of face-to-face time that is crucial to collaborative work, they did allow for more attendees to gather and share their opinions. Going forward, the community leadership has decided to have one in-person hackathon and one virtual hackathon each year, to balance the advantages of both.
+
Results
+
+
Below are a number of short success stories from the BrAPI community. These tools, applications, and infrastructure projects serve as another indicator of community growth and success over the past 5-10 years. These stories clearly illustrate all the different ways the BrAPI Standard can be used productively and in practice. Figure 2 contains a summary of the tools described below.
+
+
+
+Figure 2: A summary of all the tools described below and the general areas each tool is designed to handle
+
+
+
Phenotyping
+
+
Phenotyping is fundamental to plant breeding, providing the accurate, high-quality data needed for downstream analyses and decisions. It goes beyond simple data collection, requiring a thorough understanding of research questions and strategic data gathering to ensure successful outcomes. Effective phenotyping can make or break a research project, underscoring the importance of mastering its techniques. The BrAPI specification supports phenotypic data throughout the entire breeding pipeline, from initial collection and standardization to publication and archiving. The community has developed BrAPI-compatible tools to facilitate early data standardization, efficient storage, and curation of phenotypic data and trait metadata. Additionally, there are ongoing efforts to create tools for managing images and other high-throughput phenotyping techniques, further enhancing the precision and efficiency of plant breeding research.
+
Field Book
+
+
Phenotypic data collection underpins scientific crop research and plant breeding. Knowledge gained from collected data and its analysis, alongside data visualizations, inform further phenotypic trials and ideally support research hypotheses. The importance of accuracy and efficiency in the collection of this data as well as the infrastructure to facilitate the flow of data from the field to a knowledge base cannot be underestimated.
+
Historically, gathering data in the field was done with pen and paper, or perhaps some version of a digital spreadsheet. The abundance and prevalence of smart phones has allowed the Field Book mobile app2 to enhance data collection. Field Book can create well-formed digital observation records from the moment they are taken. This can improve the efficiency of data collection and reduce human error.
+
In 2018, BrAPI was introduced into Field Book, allowing for the automated the flow of data from the mobile app into a central, BrAPI compatible, database server. This workflow allows data collection and storage to be expedited, removing the need of the user to export and transfer data files manually. Since Field Book’s adoption of BrAPI, many community servers have been integrated to simplify data storage. In this work flow, data is collected and stored completely digitally with little-to-no human involvement.
+
GridScore
+
+
+
+
GridScore3 is a modern mobile application for phenotypic observations that harnesses technological advancements in the area of mobile devices to enrich the data collection process. GridScore focuses on user experience by closely mirroring the look and feel of printed field plans. It also enriches the experience with a wide range of functionalities including data validation, data visualizations, georeferencing, cross-platform support, and data synchronization across multiple devices. GridScore is a multi-platform tool which works on any reasonably modern device with a web browser including laptops, PCs, tablets and phones. Once created, trials can be transferred to collection devices using a Quick Response (QR) code. Its approach towards data collection uses a top-down view onto the trial and offers field navigation mechanisms using barcodes, QR codes, or guided walks which take the data collector through the field in one of 16 pre-defined orders.
+
BrAPI has further increased the value of GridScore by integrating it into the overarching workflow, from trial creation, through data collection, and to its ultimate data storage for further processing. Specifically, trial designs as well as trait definitions can be imported into GridScore using BrAPI and a finalized trial can be exported via BrAPI to any compatible database.
+
ClimMob
+
+
ClimMob4 is a software suite for a different research paradigm in experimental agriculture. In traditional breeding, a few researchers design complicated trials in search of the best solutions for a few target environments. ClimMob enables many participants to carry out reasonably simple experiments across many environments. Taken together, this data across many environments can be very informative. It applies the principles of citizen science and choice experiments to scale the data collection process, mostly in the format of rankings. Although this data may not be as detailed as from a centralized experiment, it can be very useful to inform decisions to a wide range of locations and environments with increased external validity. ClimMob applications include testing crop varieties, evaluating agronomic practices, and investigating climate resilience strategies. The platform supports experiment design, data collection through mobile apps, and data analysis to provide actionable insights.
+
During a crop trial, all farmer-collected data is stored in ClimMob. When data collection is complete, the raw data is automatically uploaded via BrAPI to a central breeding database for long-term storage and analysis. To facilitate this synchronization, ClimMob uses BrAPI to retrieve curated germplasm information from breeding databases when designing a trial, significantly enhancing data quality. Additionally, a process has been developed to push analyzed data from ClimMob to the breeding databases, providing breeders with insights into the potential adoption of the tested crop varieties.
+
ImageBreed
+
High-throughput phenotyping has been gaining significant traction lately as a way to collect lots of data very quickly. Image collection from unmanned aerial and ground vehicles (UAVs and UGVs) are a great way to collect a lot of raw data all at once, then analyze it later. ImageBreed5 is an image collection pipeline tool to support regular use of UAVs and UGVs.
+
When the raw images have been processed through the standardization pipelines in ImageBreed, useful phenotypes can be extracted from the images. The BrAPI standard is used to push these phenotypes back to a central breeding database where they can be analyzed with other data. In addition to this, ImageBreed has the ability to use BrAPI to upload the raw images to the central breeding database, or any other BrAPI compatible long term storage service. In the current version of the standard (V2.1), the BrAPI data models for images are rudimentary, but effective. The ImageBreed team has put in some work into enhancing the BrAPI image data standards, collaborating with others in the community.
+
PHIS
+
+
The Hybrid Phenotyping Information System (PHIS6), based on the OpenSILEX framework, is an ontology-driven information system based on semantic web technologies. PHIS is deployed in several field and greenhouse platforms of the French national PHENOME and European EMPHASIS infrastructures. It manages and collects data from basic phenotyping and high throughput phenotyping experiments on a day to day basis. PHIS unambiguously identifies all the objects and traits in an experiment, and establishes their types and relationships via ontologies and semantics.
+
PHIS has been designed to be BrAPI-compliant. PHIS adheres to the standards and protocols specified by BrAPI and implements various services aligning with the BrAPI standards, encompassing the Core, Phenotyping, and Germplasm modules. This enables integration and compatibility with BrAPI-compliant systems and platforms, such as OLGA, a genebank accessions management system, to retrieve accession information. This prerequisite served as the basis for formalizing the data model, while also facilitating compatibility with other standards, such as the Minimal Information About a Plant Phenotyping Experiment (MIAPPE7). By integrating BrAPI requirements into its structure, PHIS not only meets the standards of the phenotyping field, but also strengthens its capacity for interoperability and effective collaboration in the wider context of plant breeding and related fields. The fact that data within a PHIS instance can be queried through BrAPI services enables indexing of PHIS in FAIDARE8.
+
Furthermore, as PHIS offers BrAPI-compliant Web Services, it simplifies the integration and data exchange with other European information systems that handle phenotyping data. The adhesion to BrAPI standards ensures a common interface and compatibility, facilitating communication and collaboration between PHIS and other systems in the European context. This interoperability not only eases data sharing, but also promotes a more coherent and efficient approach to the management and use of phenotyping data on various platforms and research initiatives within the European scientific community.
+
PIPPA
+
+
PIPPA9 is a data management system used for collecting data from the WIWAM10 range of automated high throughput phenotyping platforms. These platforms have been deployed at different research institutes and commercial breeders across Europe. They can be setup in a variety of configurations with different types of equipment including weighing scales, cameras, and environment sensors. The software features a web interface with functionality for setting up new experiments, planning imaging and irrigation treatments, linking metadata to pots (genotype, growth media, manual treatments), importing data, exporting data, and visualizing data. It also supports the integration of image analysis scripts and connections to a compute cluster for job submission.
+
To share the phenotype data of the experiments linked to publications, an implementation of BrAPI v1.3 was developed which allowed read only access to the data in the BrAPI standardized format. This server was registered on FAIDARE8 which allows the data to be found alongside data from other BrAPI compatible repositories.
+
As the BrAPI ecosystem has matured, it has created a clear path for the further development of PIPPA. THe BrAPI specification demonstrates how to share data in a manner consistent with the FAIR principles,11 which are becoming best practices in plant research data management. The BrAPI technical standard, in combination with the MIAPPE7 scientific standard, have served as guidelines in the current development effort of the PIPPA project. This development is focused on delivering a public BrAPI v2.1 endpoint and making more high throughput datasets publicly available via BrAPI.
+
Trait Selector BrAPP
+
+
+
BrAPPs are simple tools developed by the BrAPI community that are entirely reliant on BrAPI for their data requirements. Often, they are JavaScript based applications or visualizations that fit on a single web page. This means a single BrAPP can be easily shared and used by many organizations and systems, as long as those organizations have the standard BrAPI endpoints available.
+
The Trait Selector BrAPP is used to search and select useful traits, using a visual aid to help the user find exactly what they need. Instead of searching through a long list of possible traits, the user is presented with a cartoon image of a species. They can then click on pieces of the image to show traits associated to that part of the plant. For a breeder, they might use it to quickly find specific traits to study. For a genebank user, they might use it to find varieties that have a specific trait they are interested in.
+
Due to the nature of BrAPPs, the Trait Selector can be integrated into any website or system, assuming there is a BrAPI compatible data source available to connect to. A breeding database would need to only implement the BrAPI endpoints for Traits, Observations, and Variables, while a genebank would require Traits and Germplasm Attributes. Any BrAPI server with either of these sets of endpoints implemented could use this BrAPP. CassavaBase and MGIS are two successful examples of the Trait Selector BrAPP in use.
+
+
Genotyping
+
+
Genotyping has become a cornerstone of most breeding processes, but managing the data can be challenging. Understanding different genotyping protocols for various crops is crucial due to the unique genetic structures of each species. Techniques such as SNP genotyping, Genotyping-by-Sequencing (GBS), SSRs, Whole Genome Sequencing (WGS), and array-based genotyping each offer specific advantages depending on the crop and research objectives. BrAPI supports genotypic data by utilizing existing standards such as VCF12 and the GA4GH Variants schema13. The BrAPI community has developed compatible tools for storing, searching, visualizing, and analyzing genotypic data, making it easier to integrate and utilize this information in breeding programs. Mastery of the various genotyping protocols ensures efficient and effective breeding, while BrAPI compliant tools streamline data management and analysis, enhancing the ability to make data-driven decisions in developing superior crop varieties.
+
Flapjack
+
Flapjack14 is a multi-platform desktop application for data visualization and breeding analysis (eg, pedigree verification, marker-assisted backcrossing and forward breeding) using high-throughput genotype data. Data can be easily imported into Flapjack from any BrAPI compatible data source with genotype data available. Flapjack Bytes is a smaller, lightweight and fully web-based counterpart to Flapjack, which can be easily embedded into a database website to provide similar visualizations online. Traditionally supporting its own text-based data formats, Flapjack’s use of BrAPI has streamlined the end-user experience for data import and work is underway to determine the best methods to exchange analysis results using future versions of the API.
+
DArTView
+
+
DArTView is a desktop application for marker data curation via metadata filtering. DArTView enables genotype variant data visualization and users can easily identify trends or correlations within their data using the tool. Its primary goal is to overcome tedious manual calculation of marker data through common spreadsheet applications like Excel. Users are able to import marker data from csv files, but DArTView has been recently enhanced to be BrAPI compatible. Users can now use any BrAPI compatible server as an input data source. BrAPI provides a consistent data standard across databases and data resources. DArTView’s compatibility with BrAPI also ensures easy integration with other tools and pipelines that would use DArTView for marker filtering and exploration.
+
Initially developed by Diversity Arrays Technology (DArT), the tool is gaining popularity within the breeding community, especially in Africa. Future releases will focus on enhancing the BrAPI compatibility, making it accessible to more breeders and researchers in the region. A web enabled version of DArTView is in development. This new version will allow for further collaboration opportunities with other interested partners who would like to integrate it as part of their pipelines.
+
DivBrowse
+
+
DivBrowse15 is a web platform for exploratory data analysis of huge genotyping studies. The software can be run standalone or integrated as a plugin into existing data web portals. It provides a powerful interactive visualization of variant call matrices with hundreds of millions of variants and thousands of samples. It enables easy data import and export by using well established, standardized, bioinformatics file formats.
+
At its core, DivBrowse combines the convenience of a genome browser with features tailored to the diversity analysis of germplasm. It is able to display genomic features such as nucleotide sequence, associated gene models, and short genomic variants. DivBrowse provides visual access to large VCF files obtained through genotyping experiments. In addition, DivBrowse also calculates and displays variant statistics such as minor allele frequencies, proportion of heterozygous calls, and proportion missing variant calls. Dynamic Principal Component Analyses (PCA) can be performed on a user specified genomic area to provide information on local genomic diversity.
+
Parts of the BrAPI Genotyping module are implemented in DivBrowse. There is a server-side component which provides genotypic data that the DivBrowse database can consume. There is also a client-side GUI component which can visualize genotypic data via any external BrAPI endpoint. In addition to BrAPI, DivBrowse has an internal API to control the tool from a hosting web portal. DivBrowse also has an interface to BLAST, which can be used to directly access genes or other genomic features. The modular structure of DivBrowse allows developers to configure and easily embed links to other external information systems.
+
Gigwa
+
+
Gigwa is a Java EE web application providing a means to centralize, share, finely filter, and visualize high-throughput genotyping data16. Built on top of MongoDB, it is scalable and can support working smoothly with datasets containing billions of genotypes. It is installable as a Docker image or as an all-in-one bundle archive. It is straightforward to deploy on servers or local computers and has thus been adopted by numerous research institutes from around the world. Notably, Gigwa serves as a collaborative management tool and a portal for exposing public data for genebanks and breeding programs at some CGIAR centers17. The total amount of data hosted and made widely accessible using this system has continued to grow over the last few years.
+
The Gigwa development team has been involved in the BrAPI community since 2016 and took part in designing the genotype-related section of the BrAPI standard. Gigwa’s first BrAPI-compliant features were designed for compatibility with the Flapjack visualization tool14. Over time, Gigwa has established itself as the first and most reliable implementation of the BrAPI-Genotyping endpoints. Local collaborators and external partners used it as a reference solution to design a number of tools taking advantage of the BrAPI-Genotyping features (e.g., BeegMac, SnpClust, QBMS).
+
Additional use-cases required Gigwa to also consume data from other BrAPI servers. This led to the implementation of BrAPI client features within Gigwa. A close collaboration was established with the Integrated Breeding Platform team developing the widely used Breeding Management System (BMS). This collaboration means both applications are now frequently deployed together; Gigwa pulling germplasm or sample metadata from BMS, and BMS displaying Gigwa-hosted genotypes within its own UI.
+
+
PHG
+
+
The Practical Haplotype Graph (PHG) is a graph-based computational framework that represents large-scale genetic variation and is optimized for plant breeding and genetics. Using a pangenome approach, each PHG stores haplotypes (the sequence of part of an individual chromosome) to represent the collected genes of a species. This allows for a simplified approach for dealing with large scale variation in plant genomes. The PHG pipeline provides support for a range of genomic analyses and allows for the use of graph data to impute complete genomes from low density sequence or variant data.
+
Users access the crop databases either with direct calls to the PHG embedded server or indirectly using the rPHG library from an R environment. The PHG server accepts BrAPI queries to return information on sample lists and the variants used to define the graph’s haplotypes. In addition, PHG users utilize the BrAPI Variant Sets endpoint query to return links to VCF files containing haplotype data. Work on the PHG is ongoing and it is expected to support additional BrAPI endpoints that allow for fine tuned slicing genotypic data in the near future.
+
DArT Sample Submission
+
+
The DArT genotyping lab is heavily used world wide when it comes to plant genotyping. With over 1200 available organisms and species, client base on every continent and already many million samples processed, DArT provides services for several generic and bespoke genotyping technologies and solutions. Processes of sample tracking and fast data delivery are at the core of the ordering system developed at DArT. The ordering system is tightly integrated with DArTdb - DArT’s custom LIMS operational system, which drives laboratory, quality, and analytical processes.
+
Diversity Arrays Technology was a part of BrAPI community since its inception. DArT developers have worked with the BrAPI community contributing to various aspects of the API specification. One key aspect was establishing a standard API for sending sample metadata to the lab for genotyping. This solution eliminates much of the human error involved with sending samples to an external lab and also allows for an automated process of sample batch transfers. Beyond sample submission, the current implementation also allows for an order status verification, automated data discovery, and data downloads. Data are delivered as standard data packages with self-describing metadata.
+
The current BrAPI implementation at DArT is in production and it is compatible with the newest BrAPI specification. Further details about DArT’s ordering system can be found at DArT Ordering System and also at DArT Help.
+
Germplasm Management
+
+
Germplasm data management is crucial due to the vast quantity of new accessions, variants, and lines created yearly. Germplasm is the basis of variation on which plant breeders rely to upgrade and optimize their breeding programs. This is essential at any scale including individual breeding programs, national initiatives, and international collaborations. BrAPI supports the transmission of germplasm passport data, pedigree trees, and crossing metadata. The BrAPI community has developed compliant tools for storing, searching, and visualizing this metadata, facilitating efficient management. Additionally, there are plans to establish federated networks of genebank data connected via BrAPI, enhancing global accessibility and collaboration in germplasm management.
+
MGIS
+
+
The Musa Germplasm Information System (MGIS) serves as a comprehensive community portal dedicated to banana diversity, a crop critical to global food security18. MGIS offers detailed information on banana germplasm, focusing on the collections held by the CGIAR International Banana Genebank (ITC)19. It is built on the Drupal/Tripal technology, like BIMS20 and Florilège.
+
Since its inception, MGIS developers have actively participated in the BrAPI community. The MGIS team pushed for the integration of the Multi-Crop Passport Data (MCPD) standard into the Germplasm module of the API. MCPD support was added in BrAPI v1.3, and MGIS now provides passport data information on ITC banana genebank accessions (with GLIS DOI), synchronized with Genesys. MGIS also enriches the passport data by incorporating additional information from other germplasm collections worldwide. All the germplasm data is available through the BrAPI Germplasm module implementation. For genotyping data, MGIS integrates with Gigwa16, which provides a tailored implementation of the BrAPI genotyping module. Furthermore, MGIS supports a set of BrAPI phenotyping endpoints, facilitating the exposure of morphological descriptors and trait information supported by ontologies like the Crop Ontology21. MGIS has integrated the Trait Selector BrAPP, and there are use cases implemented to interlink genebank and breeding data between MGIS and the breeding database MusaBase.
+
+
AGENT Portal
+
+
In the global system for ex situ conservation of plant genetic resources (PGR)22, a total of ~5.8 million accessions are conserved in 1750 ex situ genebanks23. Unique and permanent identifiers in the form of DOIs are available for more than 1.7 million accessions24. Each DOI is linked to some basic descriptive data that facilitates the use of these resources. Many DOIs are also linked to additional data from different domains or will be in the future. However, a data space beyond the most basic information is needed that includes genotypic and phenotypic data. This space will help answer questions on the global biological diversity of a plant species, on duplicate detection, on provenance tracking for the identification of genetic integrity, on the selection of the most suitable material for various purposes, and to support further applications in data mining or AI. In this context, the aim of the AGENT project, funded by the European Commission, is to develop a concept for the digital exploitation and activation of this PGR data space,11 and to test it in practice using two important crops, barley and wheat. Thirteen European genebanks and five bioinformatics centers are cooperating and have agreed on standards and protocols for the data flow and data formats25 for central archiving of genotypic and phenotypic data.
+
The BrAPI specification is one of the agreed standards. The implemented BrAPI interface enables AGENT to mine current and historic genotypic and phenotypic information. This will drive the discovery of genes, traits, and knowledge for future missions. The AGENT database backend aggregates curated passport data, phenotypic data, and genotypic data about wheat and barley accessions from the 18 project partners. This data is integrated via BrAPI endpoints and explorable in a web portal. Genotyping data uses the DivBrowse15 storage engine and its BrAPI interface. Soon, the BrAPI implementation will be expanded to enable the integration of analysis pipelines in the AGENT portal, such as the FIGS+ pipeline developed by ICARDA26.
+
+
+
Helium
+
+
Helium27 is a plant pedigree visualization platform designed to account for the specific problems that are unique to plant pedigrees. A pedigree is a representation of how genetically discrete individuals are related to one another and is therefore a representation of the genetic relationship between individual plant lines, their parents and progeny. Plant pedigrees are often used to check for potential genotyping or phenotyping errors, since these errors, by the very nature of Mendelian inheritance, are constrained by the pedigree structure in which they exist28. The accurate representation of pedigrees, and the ability to pull pedigree data from different data sources is important in plant breeding and genetics. Therefore, ways to visualize and interact this complex data in meaningful ways is critical.
+
From its original desktop interface, Helium has developed into a web-based visualization platform implementing BrAPI calls to allow users to import data from other BrAPI compliant databases. The ability to pull data from BrAPI compliant data sources has significantly expanded Helium’s capability and utility within the community. Helium is used in projects ranging in size from tens to tens of thousands of lines and across a wide variety of crops and species. While originally designed for plant data29 it has also found utility in other non-plant projects30 highlighting its broad utility. BrAPI also allows Helium to provide direct dataset links to collaborators, allowing the original data to be held with the data provider and utilizing Helium for its visualization functionality. Our current Helium deployment includes example BrAPI calls to a barley dataset at the James Hutton Institute to allow users to test the system and features it offers.
+
GLIS
+
+
The Global Information System (GLIS) on Plant Genetic Resources for Food and Agriculture (PGRFA) of the International Treaty on Plant Genetic Resources for Food and Agriculture (ITPGRFA) is a web-based global entry point for PGRFA data24. It allows users and third-party systems to access information and knowledge on scientific, technical, and environmental matters to strengthen PGRFA conservation, management, and utilization activities. The system and its portal also enable recipients of PGRFA to make available all non-confidential information on germplasm according to the provisions of the Treaty and facilitates access to the results of their research and development.
+
Thanks to the adoption of Digital Object Identifiers (DOIs) for Multi-Crop Passport Descriptors (MCPD) of PGRFA accessions, the GLIS Portal provides access to 1.7 million PGRFA in collections conserved worldwide. Of these, over 1.5 million are accessible for research, training and plant breeding in the food and agriculture domain.
+
The Scientific Advisory Committee of the ITPGRFA have repeatedly welcomed efforts on interoperability among germplasm information systems. In this context, the GLIS Portal adopted the BrAPI v1 in 2022. Integrating BrAPI among the GLIS content negotiators facilitates queries and the exchange of content for data management in plant breeding. The Portal also offers other protocols (XML, DarwinCore, JSON and JSON-LD) to increase data and metadata connectivity. In the near future, depending on the availability of resources, upgrading to BrAPI v2 is planned.
+
Florilège
+
+
Florilège is a web portal designed primarily for the general public to access public plant genetic resources held by Biological Resource Centers across France. Through this portal, users can browse accessions from over 50 plant genera, spread across 19 genebanks. It allows users to view available seeds and plant material, including options for ordering material. Florilège provides a centralized access to the various French collections of plant genetic resources available to the public.
+
Florilège retrieves accession information from several BrAPI compliant systems. Key among these are OLGA, a genebank accessions management system, and GnpIS, an INRAE data repository for plant genetic resources, phenomics, and genetics31,32. Using BrAPI to gather data from these systems reduced development efforts and enabled standardized data retrieval. As a result, BrAPI has become the de facto standard within the French plant genetic resources community for exchanging information. During development, the Florilège team also proposed several enhancements to the BrAPI specifications themselves, such as additional support for Collection objects or improved reference linking, to better accommodate their specific use case.
+
+
FAIDARE
+
+
FAIDARE8 is a data discovery portal providing a biologist friendly search system over a global federation of 33 plant research databases. It allows a user to identify data resources using a full text search approach combined with domain specific filters. Each search result contains a link back to the original database for visualization, analysis, and download. The indexed data types are very broad and include genomic features, selected bibliography, QTL, markers, genetic variation studies, phenomic studies, and plant genetic resources. This inclusiveness is achieved thanks to a two stage indexation data model. The first, most generic, index provides basic search functionalities and relies on five fields: name, link back URL, data type, species, and exhaustive description. To provide more advanced filtering, the second stage indexation mechanism takes advantage of BrAPI endpoints to get more detailed metadata on genotyping and phenotyping studies.
+
The indexation mechanism relies on a public software package that allows data resource managers to request the indexation of their database. This BrAPI client is able to extract data from any BrAPI 1.3 and 1.2 endpoint. The development of BrAPI 2.x indexation will be initiated in 2025. Since not all databases are willing to implement BrAPI endpoints, it is possible to generate metadata as static, BrAPI compliant, json files, using the standard as a file exchange format.
+
The FAIDARE architecture has been designed by elaborating on the GnpIS Software Architecture31. As a consequence, BrAPI is at the core of its data model. The JSON data files served by the Elasticsearch NoSQL engine are enriched versions of the BrAPI JSON data model. FAIDARE also includes a BrAPI endpoint that serves all indexed metadata. FAIDARE has been adopted by several communities including the ELIXIR and EMPHASIS european infrastructures, and the WheatIS of the Wheat-Initiative. Several databases are added each year to the FAIDARE global federation, allowing to increase both the portal and the BrAPI adoption.
+
+
Breeding Data Management
+
While specialty data management is important for some use cases, often breeders want a central repository of critical data. General breeding data management systems support some level of phenotypic, genotypic, and germplasm data, as well as trial, equipment, and people management. By enabling BrAPI support, these larger systems can connect with smaller tools and specialty systems to provide more functionality under the same user interface. There are several breeding data management systems developed in the BrAPI community, each with their own strengths.
+
DeltaBreed
+
+
DeltaBreed is an open-source breeding data management system designed and developed by Breeding Insight to support USDA-ARS specialty crop and animal breeders. DeltaBreed differs from other related systems in that is customizable to small breeding teams and generalized enough to support the workflows of diverse niche species. DeltaBreed is a unified system that connects a variety of BrAPI applications (see list below). BrAPI integration allows the complexity underlying interoperability to be hidden, shielding users from multifactorial differences between various applications. DeltaBreed, adhering to the BrAPI model, establishes data standards and validations for users and provides a singular framework for data management and user training.
+
DeltaBreed users need not be aware of BrAPI or the specifics of underlying applications but will notice that BrAPI interoperability reduces the need for human-mediated file transfers and data manipulation. Field Book users, for example, can connect to their DeltaBreed program, authenticate, and pull studies and traits directly from DeltaBreed to Field Book on their data collection device. The subsequent step of pushing observations from Field Book to DeltaBreed is straightforward via BrAPI, but is pending implementation until observation transaction handling is improved, intentional and inadvertent repeated measures are differentiated, and a data staging area is implemented for quality control.
+
Breeding Insight integrated several BrAPI applications to support 2021 phenotypic data collection by USDA-ARS blueberry breeders. DeltaBreed was used to create traits in Breedbase, and Field Book was used to pull studies and traits from Breedbase. The workflow also permitted users to push Field Book observations back to Breedbase via BrAPI. This effort served as a successful proof of concept for multi-application BrAPI integration, but highlighted limitations to the process of accepting BrAPI observations from Field Book. The Breeding Insight team is actively working with the rest of the BrAPI community to correct these limitations in future versions of the specification.
The Breeding Management System (BMS), developed by the Integrated Breeding Platform (IBP), is a suite of tools designed to enhance the efficiency and effectiveness of plant breeding. BMS covers all stages of the breeding process, with the emphasis on germplasm management and ontology-harmonized phenotyping. It also features analytics and decision-support tools. With its focus on interoperability, BMS integrates smoothly with BrAPI, facilitating easy connections with a broad array of complementary tools and databases. Notably, the BMS is often deployed together with Gigwa to fulfill the genotyping data management needs of BMS users.
+
The brapi-sync tool, a significant component of BMS’s BrAPI capabilities, was developed by the IBP and released as a BrAPP for community use. Brapi-sync is designed to enhance collaboration among partner institutes within a network such as Innovation and Plant Breeding in West Africa (IAVAO). The tool enables the sharing of germplasm and trial metadata across BrAPI-enabled systems. It helps overcome traditional barriers to collaboration, ensuring data that was once isolated within specific programs or platforms can now be easily shared, integrated, and synchronized.
+
Additionally, brapi-sync improves data management by maintaining links to the original source of each entity it transmits. This retains the original context of the data and establishes a traceability mechanism for accurate data source attribution and verification. Such practices are crucial for maintaining data integrity and fostering trust among collaborative partners, ensuring access to accurate, reliable, and current information.
+
Breedbase
+
+
Breedbase is a comprehensive breeding data management system33,34 that implements a digital ecosystem for all breeding data, including trial data, phenotypic data, and genotypic data. Data acquisition is supported through data collection apps such as Fieldbook2, Coordinate, and InterCross, as well as through drone imagery, Near Infra-Red Spectroscopy (NIRS), and other technologies. Search functions, such as the Search Wizard interface, provide powerful query capabilities. Various breeding-centric analysis tools are available, including mixed models, heritability, stability, PCA, and various clustering algorithms. The original impetus for creating Breedbase was the advent of new breeding paradigms based on genomic information such as genomic prediction algorithms35 and the accompanying data management challenges. Thus, complete genomic prediction workflow is integrated in the system.
+
The BrAPI interface is crucial for Breedbase. Breedbase uses BrAPI to connect with the data collection apps, other projects such as CLIMMOB4, and native BrAPPs built into the Breedbase webpage. Users also appreciate the ability to connect to Breedbase instances using packages such as QBMS36 for data import into R for custom analyses. The Breedbase team has been part of the BrAPI community since its inception, and has continuously adopted and contributed to the BrAPI standard.
+
BIMS
+
+
BIMS (Breeding Information Management System)20 is a free, secure, and online breeding management system which allows breeders to store, manage, archive, and analyze their private breeding program data. BIMS enables individual breeders to have complete control of their own breeding data along with access to tools such as data import/export, data analysis, and data archiving for their germplasm, phenotype, genotype, and image data. BIMS is currently implemented in five community databases, the Genome Database for Rosaceae37, CottonGEN38, the Citrus Genome Database, the Pulse Crop Database, and the Genome Database for Vaccinium. BIMS in these five community databases enables individual breeders to import publicly available data so that they can utilize public data in their breeding program.
+
Right now, BIMS primarily utilizes BrAPI to connect with the Field Book Android App2, enabling seamless data transfer between BIMS and the app. Data transfer through BrAPI between BIMS and other resources such as BreedBase33, GIGWA16, and Breeder Genomics Hub is on the way. Hopefully, the BIMS development team can easily reuse some of the solved use cases and workflows created by others in the BrAPI community.
+
Germinate
+
+
Germinate39 is an open-source plant genetic resources database that combines and integrates various kinds of plant breeding data including genotypic data, phenotypic trials data, passport data, images, geographic information and climate data into a single repository. Germinate is tightly linked to the BrAPI specification and supports a majority of BrAPI endpoints for querying, filtering, and submission.
+
Germinate integrates and connects with other BrAPI-enabled tools such as GridScore for phenotypic data collection, Flapjack for genotypic data visualization, and Helium for pedigree visualization. Additionally, due to the nature of BrAPI, Germinate can act as a data repository for any BrAPI-compatible tool. Thanks to the interoperability provided by BrAPI, the need for manual data handling becomes a rarity with the direct benefit of faster data processing, fewer to no human errors, data security, and data integrity.
+
Analytics
+
While other tools listed above have the capability to do specialized analytics on certain types of data, general analytics tools can cover a wide range of data types and analytical models. The tools developed by the BrAPI community can pull in data from multiple BrAPI compatible data sources and provide enhanced analytical functionality. In many cases, there is no longer a need to import and export large data files to a local computational environment just to run standard analytical models. These tools are able to extract the data they need from a data source without much human intervention or human error.
+
QBMS
+
+
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.
+
The QBMS36 R package eliminates technical barriers scientists experience when using the BrAPI specification in their 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, the QBMS package abstracts the technical complexities, providing breeders with stateful functions familiar to them when navigating their GUI systems. It enables them to query and extract data into a standard data frame structure, consistent with their use of the 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 9400 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 by enabling the creation of dashboards to reduce the time between harvest and decision-making for the next breeding cycle.
+
Mr.Bean
+
+
Mr.Bean40 is a graphical user interface designed to assist breeders, statisticians, and individuals involved in plant breeding programs with the analysis of field trials. By utilizing innovative methodologies such as SpATS for modeling spatial trends, and autocorrelation models to address spatial variability, Mr.Bean proves highly practical and powerful in facilitating faster and more effective decision-making. Modeling Genotype-by-environment interaction poses its challenges, but Mr.Bean offers the capability to explore various variance-covariance matrices, including Factor Analytic, compound symmetry, and heterogeneous variances. This aids in the assessment of genotype performance across diverse environments.
+
Mr.Bean boasts flexibility in importing different file types, yet for users managing their data within data management systems (DMS), the process of downloading from their DMS and importing it into Mr.Bean can be cumbersome. To address this issue, QBMS was integrated into the back-end. This feature prompts users to input the URL of a BrAPI compatible server, enter their credentials (if necessary), and select the specific trial they wish to analyze. Subsequently, users can seamlessly access their dataset through BrAPI and utilize it across the entire Mr.Bean interface.
+
G-Crunch
+
+
G-Crunch is an upcoming user-facing analysis tool that attempts to fill the space of simple, user driven analytics requests, with a generic user interface and the ability to swap out data sources and analysis tools. G-Crunch hopes to streamline repeatable, debuggable, simple analytic requests and results.
+
G-Crunch, as a tool, couldn’t feasibly exist without BrAPI. The support of BrAPI interfaces allows G-Crunch to use one unified request method, and adapt to the user’s (BrAPI-compliant) existing network of tools. This lowers the barrier to entry for adoption, and makes analysis pipelines easily repeatable.
+
ShinyBrAPPs
+
Data management systems are generic and robust centralized applications, with a large community of users, long term development cycles and release plans. BrAPI compliance offers these systems the opportunity to add functionalities in a modular way through the development of external plugin applications that can quickly fulfill specific needs of a group of users. R-Shiny is a R-package that opens the possibility to develop rich and productive interactive web applications to R users and developers. As such it allows user communities to quickly prototype and produce applications that are finely tailored to their needs, thus improving adoption and daily use of data management systems. The Breeding Management System (BMS) of the IBP and Gigwa are BrAPI compliant and are being widely used by breeding programs, including national breeding programs in Africa. CIRAD and the IBP teams have been working together as part of the IAVAO breeders community to develop the Shiny-BrAPPs, a set of R-Shiny applications using BrAPI as a core technology for data exchange. These applications are connected to BMS and/or Gigwa and provide tools for specific use cases. So far, four applications have been developed covering the fields of trial data quality control, single trial statistical analysis, breeding decision support, and raw genotyping data visual inspection.
+
The “BMS trial data explorer” retrieves data from a single multi-location trial and displays data counts and summary boxplot for all variables measured in different studies. It also provides an interactive distribution plot to easily select observations that require curation and a report of candidate issues that needs to be addressed by the breeder. The “STABrAPP” tool is an application for single trial mixed model analysis. It basically provides a GUI to the StatGen-STA R package. The “DSBrAPP” tool is a decision support tool helping breeders to select germplasm according to their various characteristics and save this germplasm list into BMS. These first three apps are grouped into a single repository (ShinyBrAPPs) with modular code shared across applications and make use of the brapir-v1 and brapir-v2 R packages. Finally, the “snpclust” tool enables a user to check and manually correct the clustering of fluorescence based SNP genotyping data.
+
SCT
+
+
The Sugarcane Crossing Tool (SCT) is a lightweight RShiny dashboard application designed to receive, process, and visualize data from a linked BreedBase33 instance. This application is being developed collaboratively with members of the Sugarcane Integrated Breeding System, who have advocated for an application that assists them in designing crosses based on queried information from a list of available accessions. By leveraging existing community resources, the team has been able to develop a simple, BrAPI-enabled, application without possessing extensive programming knowledge or experience. The SCT is presented as an inspiration for similarly positioned scientists to consider developing custom applications for specific tasks.
+
+
+
The crossing tool utilizes a modified version of the BrAPI-R library to access a compliant database, and it employs standard R/JavaScript packages to aggregate and visualize data. Modules within the application allow breeders to query the database (through BrAPI) for information relevant to their decision-making process. This includes the number and sex of flowering accessions, deep pedigree and relatedness information, summarized trial data, and the prior frequency and success of potential cross combinations. Future versions of this tool will provide additional decision support (e.g. ranked potential crosses) to enhance the accuracy and efficiency of crossing.
+
General Infrastructure
+
Adopting BrAPI compatibility into an existing system can be difficult sometimes. The BrAPI Community has developed several tools to make adoption easier. This includes things like pre built code libraries, connectors to other technology standards, and mappers to alternate data types or data files. The goal is to lower the barrier to entry for the BrAPI community, making it easier for other groups to get started and connect their existing data to the standard.
+
MIRA
+
+
In the plant phenotyping community, MIAPPE (Minimal Information About a Plant Phenotyping Experiment)7 is an established standard for phenotyping experiments. It is commonly serialized into the ISA-Tab file type.41 Although ISA-Tab is easy to read for non-technical experts due to its file-based approach, it lacks programmatic accessibility, particularly for web applications. BrAPI, which is aligned with MIAPPE, can help solve this problem.
+
MIRA is a tool that enables the automatic deployment of a BrAPI server on a MIAPPE-compliant dataset in ISA-Tab format. It can be deployed from a Docker image with the dataset mounted. By utilizing the mapping between MIAPPE, ISA-Tab, and BrAPI, there is no need for parsing or manual mapping of datasets that are already compliant with (meta-)data standards. By gaining programmatic access through BrAPI to these datasets, it facilitates the integration of phenotyping datasets into web applications.
+
BrAPI2ISA
+
+
Since the release of BrAPI 1.3, efforts have been made to incorporate support for the MIAPPE standard into the specification7. This integration was finalized in BrAPI 2.0, resulting in full compatibility between the two standards. Consequently, BrAPI now encompasses all attributes necessary for MIAPPE compliance, adhering to standardized descriptions in accordance with MIAPPE guidelines.
+
In some communities and projects, phenotyping data and metadata is archived and published as structured ISA-Tab files, and validated using the MIAPPE ISA configuration. The BrAPI2ISA service functions as a converter between a BrAPI compatible server and the ISA-Tab format. This simplifies, automates, and facilitates the archiving of data, thereby enhancing data preservation and accessibility. The BrAPI2ISA tool is designed to be compatible with BrAPI 1.3, and is open to contributions from the community to extend support for the latest versions of BrAPI.
+
BrAPIMapper
+
+
BrAPIMapper is a full BrAPI implementation designed to be a convenient wrapper for any breeding related data source. BrAPIMapper is provided as a Docker application that can connect to a variety of external data sources including mySQL or PostgreSQL databases, generic REST services, flat files (XML, JSON, CSV/TSV/GFF3/VCF, YAML), or any combination of these. It provides an administration user interface to map BrAPI data models to external data sources. The interface allows administrators to select the BrAPI specification versions to use and which endpoints to enable. Data mapping configuration import and export features simplify upgrades to future BrAPI versions; administrators only have to map missing fields or make minor adjustments. BrAPIMapper supports the primary BrAPI features including paging, deferred search results, user lists, and authentication. Access restrictions to specific endpoints can be managed through the administration interface as well. This tool aims to accelerate BrAPI services deployment while ensuring specification compliance.
+
GraphQL Data-warehouse
+
+
Using the Zendro set of automatic software code generators, a fully functional, efficient, and cloud-capable BrAPI data-warehouse has been created for the current version of the BrAPI data models. Unlike most BrAPI compliant data sources, this data-warehouse supports a GraphQL API rather than a RESTful API. This API provides secure access to data read and write functions for all BrAPI data models. It provides create, read, update, and delete (CRUD) functions that are standardized and accept the same parameters for all data models.
+
The GraphQL server is particularly rich in features. Records are paginated using the highly efficient cursor based pagination model as proposed in the GraphQL standard. Logical filters allow for exhaustive search queries, whose structure is highly intuitive and based around logical triplets. A large collection of operators is available and triplets can be combined to logical search trees using “and” or “or” operators. Searches can be extended over relationships between data models, thus enabling a user to query the warehouse for exactly the required data. Access security is implemented with the OAuth2 user authentication standard42. Authorization is based on user roles and can be configured differently for each single data model read or write function. The generated graphical interface allows for the integration of interactive scientific plots and analysis tools written in JavaScript or WebAssembly.
+
+
The Zendro data-warehouse is capable of forming an efficient cloud of data servers. This is achieved simply by linking other Zendro based warehouses that expose the same GraphQL API to the same data models, or a subset of data models. Any network of such Zendro GraphQL servers can be set up using this configuration approach. The code generated then exposes full access to all data records stored on any node of the network, while maintaining full security control at each node. Importantly, the warehouses are programmed in such a way that any number of data servers can be joined without loss of efficiency.
+
Discussion
+
+
BrAPI for Breeders and Scientists
+
The BrAPI technical specification document is meant to be read and used by software developers. However, the purpose of the specification, and the community around it, is to make things faster, easier, and cheaper for the breeders and scientists working on breeding and other agricultural projects. BrAPI offers a convenient path to automation, interoperability, and data integration for software tools in the breeding domain. All of the example use cases described above can be achieved with manual effort, moving and editing data files by hand. However, when the basic structure and flow of data becomes automated, breeders and scientists can spend less time on data management and more time focusing on the science. For many, the ultimate goal is the development of a digital ecosystem: a collection of software tools and applications that can all work together seamlessly. In this digital ecosystem, data is collected digitally from the beginning, reducing as much human error as possible. The data is checked by quality control and stored automatically, then it can be sent to any internal tool or external lab for further analysis with just the click of a button. This idea might sound too good to be true, but as more tools start sharing a universal data standard, automating data flow becomes easier, and the community gets closer to total interoperability.
+
Looking Ahead
+
The BrAPI specification will continue to grow, enabling more use cases and new types of data. These new use cases might include newer scientific techniques and technologies. Things like drone imaging data, spectroscopy, LIDAR, metabolomics, transcriptomics, high-throughput phenotyping, and machine learning analysis. All of these technologies can open new avenues for research and development of new crop varieties. All of these technologies also generate more data, and require data sharing between different software applications and data repositories. The BrAPI project leadership and community is committed to building the standards to support these new use cases as they arrive and become accepted by the scientific community. In fact, small groups within the BrAPI community have already start building generic data models and proposed communication standards for many of the technologies listed above. These community efforts will eventually become part of the BrAPI standard in a future version of the specification document.
+
Expanding the BrAPI specification is important for the community, however it is just as important not to reinvent or compete with existing functional standards. Additions to the BrAPI specification are reviewed thoroughly by the community to make sure BrAPI is compliant with existing standards and data structures. For example, BrAPI is compliant with MIAPPE, MCPD, and VCF, adding pieces of these existing popular data structures into the overall standard. In some cases, BrAPI will reference other standards instead of including them in the specification. For example, the NOAA CDO standard for weather data, or the Galaxy Analytics API for analytics pipeline controls and information. These standards are perfectly adequate on their own, and recreating them in the BrAPI standard would be redundant.
+
Conclusion
+
The BrAPI project only exists because of the community of breeders, software engineers, and scientists who support and use it. While there were many tools and use cases presented here, it is not an exhaustive list of all BrAPI compliant systems. As long as the standard continues to be supported, there is potential for exponential growth of the community. As more groups make their tools BrAPI compliant, these tools can be shared with the community. As more BrAPI compliant tools are shared with the community, more groups can see the value in implementing BrAPI in their own tools. This feedback loop will allow the community to strengthen and grow.
+
If this manuscript is your first introduction to the BrAPI project, the authors invite you to join the community. More information is always available at brapi.org.
+
Methods
+
The BrAPI Project day-to-day operations are run by the BrAPI Project Coordinator, overseen by the grant PI and Co-PI. The BrAPI Project Coordinator is responsible for the general maintenance of the project infrastructure, as well as coordinating updates to the standard. They organize community events and encourage collaboration between community groups. Long term planning and organization is handled by the BrAPI Advisory board. This is a board of 6 community members who are elected by the community to represent their interest in the project.
+
The standard documentation is stored and maintained in a GitHub repository. The core documentation is written using the OpenAPI 3 documentation standard, and can be easily transformed into other documentation standards as needed. Copies of the core documentation is published on the API documentation sites Apiary and SwaggerHub for maximum accessability by the community. All these online locations are public, and the specification has a standard MIT open source license.
+
New versions of the BrAPI standard are developed periodically based on community demand. Problems and enhancements are collected by the community over time, then implemented together to create a new stable version. This ensures the standard stays up=to-date and relevant to the community, but maintains a certain level of stability over time. Minor version updates are designed to be backward compatible to further enhance the stability of the standard.
+
As discussed above, hackathon events are the primary way the BrAPI community stays together. One in-person and one virtual event per year maintain project momentum and social comradery. The hackathons provide a dedicated time to discuss issues and enhancements with the specification, particular use cases, and generally how the community is run and organized. For some groups, the BrAPI hackathon provide the only time they have to work on BrAPI related implementations, due to other constraints in their normal work.
+
Data Availability Statement
+
No data was generated from this project.
+
Code Availability Statement
+
The all of software and documentation generated by the BrAPI project is free, public, and open source. Everything is available under the MIT open source license, and can be accessed through brapi.org. Most of the other software projects referenced and discussed here are also open source and the text contain links to their repositories or project pages. However, the authors take no responsibility for their availability or licensing.
+
Competing Interests Statement
+
The authors declare no competing interests.
+
Acknowledgements
+
The authors would like to acknowledge the following funding sources:
+
+
USDA NIFA-DSFAS 2022-67021-37024
+
This work was supported by the Agence Nationale de la Recherche, programme Investissements d’avenir, ANR-11-INBS-0012 (Phenome)
+
U.S. Department of Agriculture, under agreement numbers [8062-21000-043-004-A, 8062-21000-052-002-A, and 8062-21000-052-003-A]
+
Innovation Lab for Crop Improvement Cornell, FFAR
+
Research time for Marie-Angélique Laporte and Kauê de Sousa was provided through the 1000FARMS project (INV-031561) funded by the Bill & Melinda Gates Foundation.
+
+
Author Contributions
+
+
Peter Selby: Peter wrote and edited a significant portion of the manuscript. Peter has been the BrAPI Project Coordinator since 2017, managing the day-to-day operations of the BrAPI project.
+
Rafael Abbeloos: Rafael wrote the section on the PIPPA project, and has made significant contributions to the BrAPI compatibility of the PIPPA project.
+
Anne-Francoise Adam-Blondon: Anne-Francoise has made significant contributions to the Florilège and Faidare projects.
+
Francisco Agosto: Francisco wrote the section on the ImageBreed project, and has made significant contributions to the BrAPI compatibility of the ImageBreed project.
+
Michael Alaux: Michael has made significant contributions to the AGENT Portal project.
+
Isabelle Alic: Isabelle wrote the section on the PHIS project, and has made significant contributions to the BrAPI compatibility of the PHIS project.
+
Khaled Al-Shamaa: Khaled wrote the section on the QBMS project, and has made significant contributions to the BrAPI compatibility of the QBMS project.
+
Johan Steven Aparicio: Johan wrote the section on the Mr.Bean project, and has made significant contributions to the BrAPI compatibility of the Mr.Bean project.
+
Jan Erik Backlund: Jan Erik has made significant contributions to the BMS project.
+
Aldrin Batac: Aldrin has made significant contributions to the BMS project.
+
Sebastian Beier: Sebastian wrote the section on the DivBrowse project, and has made significant contributions to the BrAPI compatibility of the DivBrowse project.
+
Alice Boizet: Alice wrote the section on the Florilège project, and has made significant contributions to the BrAPI compatibility of the Florilège, Gigwa and ShinyBrAPPs projects.
+
Matthijs Brouwer: Matthijs has made significant contributions to the AGENT Portal project.
+
Terry Casstevens: Terry has made significant contributions to the PHG project.
+
Keo Corak: Keo wrote the section on the SCT project, and has made significant contributions to the BrAPI compatibility of the SCT project.
+
Chaney Courtney: Chaney wrote the section on the Field Book project, and has made significant contributions to the BrAPI compatibility of the Field Book project.
+
Mariano Crimi: Mariano has made significant contributions to the BMS project.
+
Gouripriya Davuluri: Gouripriya has made significant contributions to the AGENT Portal project.
+
Jeremy Destin: Jeremy has made significant contributions to the Florilège and Faidare projects.
+
Ajay Dhungana: Ajay wrote section introductions for the Phenotyping, Genotyping, and Germplasm topics.
+
Bert Droesbeke: Bert wrote the section on the BrAPI2ISA project, and has made significant contributions to the BrAPI compatibility of the BrAPI2ISA project.
+
Manuel Feser: Manuel wrote the section on the MIRA project, and has made significant contributions to the BrAPI compatibility of the MIRA project.
+
Mirella Flores-Gonzalez: Mirella wrote the section on the Trait Selector BrAPP project, and has made significant contributions to the BrAPI compatibility of the Trait Selector BrAPP and Breedbase projects.
+
Valentin Guignon: Valentin wrote the section on the BrAPI Mapper project, and has made significant contributions to the BrAPI compatibility of the BrAPI Mapper and MGIS projects.
+
Corina Habito: Corina wrote the section on the BMS project, and has made significant contributions to the BrAPI compatibility of the BMS project.
+
Asis Hallab: Asis wrote the section on the Zendro project, and has made significant contributions to the BrAPI compatibility of the Zendro project.
+
Puthick Hok: Puthick has made significant contributions to the DArT Sample Submission project.
+
Lynn Johnson: Lynn wrote the section on the PHG project, and has made significant contributions to the BrAPI compatibility of the PHG project.
+
Sook Jung: Sook wrote the section on the BIMS project, and has made significant contributions to the BrAPI compatibility of the BIMS project.
+
Paul Kersey: Paul has made significant contributions to the AGENT Portal project.
+
Andrzej Kilian: Andrzej has made significant contributions to the DArT Sample Submission and DArTView projects.
+
Patrick König: Patrick has made significant contributions to the AGENT Portal project.
+
Suman Kumar: Suman has made significant contributions to the AGENT Portal project.
+
Josh Lamos-Sweeney: Josh wrote the section on the G-Crunch project, and has made significant contributions to the BrAPI compatibility of the G-Crunch project.
+
Laszlo Lang: Laszlo has made significant contributions to the Zendro project.
+
Matthias Lange: Matthias wrote the section on the AGENT Portal project, and has made significant contributions to the BrAPI compatibility of the AGENT Portal project.
+
Marie-Angélique Laporte: Wrote the section on the ClimMob project, and has made significant contributions to the BrAPI compatibility of the ClimMob project.
+
Kauê de Sousa: Wrote the section on the ClimMob project, and has made significant contributions to the BrAPI compatibility of the ClimMob project.
+
Brandon Madriz: Wrote the section on the ClimMob project, and has made significant contributions to the BrAPI compatibility of the ClimMob project.
+
Taein Lee: Taein has made significant contributions to the BIMS project.
+
Erwan Le-Floch: Erwan has made significant contributions to the AGENT Portal project.
+
Francisco López: Francisco has made significant contributions to the GLIS project.
+
Marco Marsella: Marco wrote the section on the GLIS project, and has made significant contributions to the BrAPI compatibility of the GLIS project.
+
Maud Marty: Maud has made significant contributions to the Florilège and Faidare projects.
+
Célia Michotey: Célia has made significant contributions to the Florilège and Faidare projects.
+
Zachary Miller: Zachary has made significant contributions to the PHG project.
+
Iain Milne: Iain has made significant contributions to the Flapjack, Gridscore, and Germinate projects.
+
Lukas Mueller: Lukas wrote the section on the Breedbase project, and has made significant contributions to the BrAPI compatibility of the Breedbase project. Lukas is also Co-PI on the current BrAPI Grant and has supported the project since its inception.
+
Moses Nderitu: Moses wrote the section on the DArTView project, and has made significant contributions to the BrAPI compatibility of the DArTView project.
+
Tim Parsons: Tim has made significant contributions to the DeltaBreed project.
+
Cyril Pommier: Cyril wrote the section on the Faidare project, and has made significant contributions to the BrAPI compatibility of the Florilège, Faidare, and AGENT Portal projects.
+
Jean-François Rami: Jean-François wrote the section on the ShinyBrAPPs project, and has made significant contributions to the BrAPI compatibility of the ShinyBrAPPs project.
+
Sebastian Raubach: Sebastian wrote the sections on the GridScore and Germinate projects, and has made significant contributions to the BrAPI compatibility of the GridScore, Germinate, and Flapjack projects.
+
Trevor Rife: Trevor has made significant contributions to the Field Book project.
+
Kelly Robbins: Kelly is the PI for the BrAPI Project grant, and has supported all technical and scientific aspects of the project.
+
Mathieu Rouard: Mathieu wrote the section on the MGIS project, and has made significant contributions to the BrAPI compatibility of the MGIS project.
+
Joseph Ruff: Joseph has made significant contributions to the AGENT Portal project.
+
Guilhem Sempéré: Guilhem wrote the section on the Gigwa project, and has made significant contributions to the BrAPI compatibility of the Gigwa project.
+
Paul Shaw: Paul wrote the section on the Helium project, and has made significant contributions to the BrAPI compatibility of the Helium project.
+
Becky Smith: Becky has made significant contributions to the Flapjack project.
+
Nahuel Soldevilla: Nahuel has made significant contributions to the BMS project.
+
Clarysabel Tovar: Clarysabel has made significant contributions to the BMS project.
+
Grzegorz Uszynski: Grzegorz wrote the section on the DArT Sample Submission project, and has made significant contributions to the BrAPI compatibility of the DArT Sample Submission project.
+
Vivian Bass Vega: Vivian has made significant contributions to the Zendro project.
+
Stephan Weise: Stephan has made significant contributions to the AGENT Portal project.
+
Shawn Yarnes: Shawn wrote the section on the DeltaBreed project, and has made significant contributions to the BrAPI compatibility of the DeltaBreed project.
Elsner-Gearing, F. et al. Admixture and reproductive skew shape the conservation value of ex situ populations of the Critically Endangered eastern black rhino. Conserv Genet (2024) doi:10.1007/s10592-024-01611-z.
Adam-Blondon, A.-F. et al. Mining Plant Genomic and Genetic Data Using the GnpIS Information System. in Methods in Molecular Biology 103–117 (Springer New York, 2016). doi:10.1007/978-1-4939-6658-5_5.
The Hybrid Phenotyping Information System (PHIS6), based on the OpenSILEX framework, is an ontology-driven information system based on semantic web technologies. PHIS is deployed in several field and greenhouse platforms of the French national PHENOME and European EMPHASIS infrastructures. It manages and collects data from basic phenotyping and high throughput phenotyping experiments on a day to day basis. PHIS unambiguously identifies all the objects and traits in an experiment, and establishes their types and relationships via ontologies and semantics.
-
PHIS has been designed to be BrAPI-compliant. PHIS adheres to the standards and protocols specified by BrAPI and implements various services aligning with the BrAPI standards, encompassing the Core, Phenotyping, and Germplasm modules. This enables integration and compatibility with BrAPI-compliant systems and platforms. This prerequisite served as the basis for formalizing the data model, while also facilitating compatibility with other standards, such as the Minimal Information About a Plant Phenotyping Experiment (MIAPPE7). By integrating BrAPI requirements into its structure, PHIS not only meets the standards of the phenotyping field, but also strengthens its capacity for interoperability and effective collaboration in the wider context of plant breeding and related fields. The fact that data within a PHIS instance can be queried through BrAPI services makes the indexing of PHIS in FAIDARE8 very easy to implement.
-
Furthermore, as PHIS offers BrAPI-compliant Web Services, it simplifies the integration and data exchange with other European information systems that handle phenotyping data. The adherence to BrAPI standards ensures a common interface and compatibility, facilitating communication and collaboration between PHIS and other systems in the European context. This interoperability not only eases data sharing, but also promotes a more coherent and efficient approach to the management and use of phenotyping data on various platforms and research initiatives within the European scientific community.
+
PHIS has been designed to be BrAPI-compliant. PHIS adheres to the standards and protocols specified by BrAPI and implements various services aligning with the BrAPI standards, encompassing the Core, Phenotyping, and Germplasm modules. This enables integration and compatibility with BrAPI-compliant systems and platforms, such as OLGA, a genebank accessions management system, to retrieve accession information. This prerequisite served as the basis for formalizing the data model, while also facilitating compatibility with other standards, such as the Minimal Information About a Plant Phenotyping Experiment (MIAPPE7). By integrating BrAPI requirements into its structure, PHIS not only meets the standards of the phenotyping field, but also strengthens its capacity for interoperability and effective collaboration in the wider context of plant breeding and related fields. The fact that data within a PHIS instance can be queried through BrAPI services enables indexing of PHIS in FAIDARE8.
+
Furthermore, as PHIS offers BrAPI-compliant Web Services, it simplifies the integration and data exchange with other European information systems that handle phenotyping data. The adhesion to BrAPI standards ensures a common interface and compatibility, facilitating communication and collaboration between PHIS and other systems in the European context. This interoperability not only eases data sharing, but also promotes a more coherent and efficient approach to the management and use of phenotyping data on various platforms and research initiatives within the European scientific community.
PIPPA
PIPPA9 is a data management system used for collecting data from the WIWAM10 range of automated high throughput phenotyping platforms. These platforms have been deployed at different research institutes and commercial breeders across Europe. They can be setup in a variety of configurations with different types of equipment including weighing scales, cameras, and environment sensors. The software features a web interface with functionality for setting up new experiments, planning imaging and irrigation treatments, linking metadata to pots (genotype, growth media, manual treatments), importing data, exporting data, and visualizing data. It also supports the integration of image analysis scripts and connections to a compute cluster for job submission.
diff --git a/v/latest/index.html.ots b/v/latest/index.html.ots
index 73732f1..360f1d4 100644
Binary files a/v/latest/index.html.ots and b/v/latest/index.html.ots differ
diff --git a/v/latest/manuscript.pdf b/v/latest/manuscript.pdf
index 90f27fd..8c05eda 100644
Binary files a/v/latest/manuscript.pdf and b/v/latest/manuscript.pdf differ
diff --git a/v/latest/manuscript.pdf.ots b/v/latest/manuscript.pdf.ots
index 37cb58e..9cf021d 100644
Binary files a/v/latest/manuscript.pdf.ots and b/v/latest/manuscript.pdf.ots differ
+0000-0001-7151-4445
+· 
+BrapiCoordinatorSelby
+
+
+