added section about miappe isa to brapi service

content/03.03.federation-infrastructure.md

@@ -29,6 +29,11 @@ To integrate those BrAPI endpoint provider into a single service and URL scheme,
 <!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. -->
 Agrosystem Integration of germplasm collections in context of data trustee models among private economy and public research, integration of ex-situ genebanks (EU H2020 projects AGENT, INCREASING), integrated agrosystems and plant research infrastructure
 
+#### MIAPPE ISA to BrAPI service
+
+Phenotyping is crucial in the breeding process as it enables the identification of desirable traits, selection of breeding lines, and evaluation of breeding success. In the plant community, MIAPPE (Minimal Information About a Plant Phenotyping Experiment) [@doi:10.1111/nph.16544] is the established standard for phenotyping experiments and is commonly serialized as ISA Tab [@doi:10.1038/ng.1054]. Although ISA Tab is easy to read for non-technical experts due to its file-based approach, it lacks programmatic access, 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, 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.
+
 #### MIAPPE "BrAPI to ISA" service
 
 Since the release of BrAPI 1.3, efforts have been made to incorporate support for the Minimum Information About Plant Phenotyping Experiments (MIAPPE) standard into the specification [@doi:10.1111/nph.16544]. 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. Leveraging BrAPI as a standardized RESTful web service API specification, we employ the ISA standard for storing metadata and phenotyping data in a standardized manner. This data is structured in the ISA-TAB file format and subjected to validation using the [MIAPPE ISA configuration](https://github.com/ELIXIR-Belgium/isatab-validation). The "BrAPI to ISA" service functions as a converter between BrAPI RESTful endpoints and ISA-TAB, facilitating the archiving of metadata and data and thereby enhancing data preservation and accessibility. The [BrAPI2ISA](https://github.com/elixir-europe/plant-brapi-to-isa) tool is designed to be compatible with BrAPI 1.3, and we invite contributions from the community to extend support for the latest versions of BrAPI.

content/metadata.yaml

@@ -172,6 +172,14 @@ authors:
     initials: PK
     affiliations:
       - Leibniz Institute of Plant Genetics and Crop Plant Research
+  - name: Manuel Feser
+    github: feserm
+    orcid: 0000-0001-6546-1818
+    email: [email protected]
+    initials: MF
+    affiliations:
+      - Leibniz Institute of Plant Genetics and Crop Plant Research
+      - Graduate School DILS, Bielefeld Institute for Bioinformatics Infrastructure (BIBI)
   - name: Gouripriya Davuluri
     email: [email protected]
     initials: GD