Integrating plant phenotypic and genotypic data in the AGENT project: a BrAPI service implementation.
other · Level V
Where this comes from
- Record sourced from PubMed, PMID 42097287.
- Also identified by DOI 10.1093/bioinformatics/btag287 and PMC identifier 13211978.
- Licence recorded as CC BY.
- The licence permits redistribution, so the abstract is shown in full and the full text is available from the publisher.
Abstract
The AGENT project established a network of actively cooperating European genebanks, integrating genomic and phenotypic data from accessions of wheat and barley. Due to specific storage demands for phenotypic and genotypic data, the project used separate database instances and backend technologies to manage integrated phenotypic and genotypic data. We discuss the challenges encountered when integrating dispersed data to serve through a single interface such as the Plant Breeding Application Programming Interface, BrAPI. We examine how the consistent mappability of genebank data to the BrAPI model can enable the implementation of effective services. The advantages of BrAPI in transparently linking distributed data entities through embedded, unique identifiers are highlighted. We present a technical solution involving a BrAPI proxy, which combines and merges separate BrAPI endpoints. Finally, we demonstrate the AGENT BrAPI implementation with an illustrative example that validates a suggested SNP for a trait from the literature by linking phenotypic, genotypic and passport data. The BrAPI proxy implementation and documentation is available at the Python Package Index (https://pypi.org/project/brapi-proxy) and archived in Zenodo (doi: 10.5281/zenodo.19436445). A Jupyter Notebook file for the validation example using a marker-trait relationship found in the literature.
Medical subject headings
- Phenotype
- Genotype
- Hordeum
- Triticum
- Software
- Databases, Genetic