Add Jenna Hershberger to author list

content/03.01.02.GridScore.md

@@ -1,9 +1,13 @@
 #### GridScore
 
-<!-- Sebastian R -->
+<!-- Sebastian R with edits from Jenna -->
 <!-- Make distinct from Field Book, highlight what makes GridScore different -->
 <!-- Better flow is needed between Field Book and GridScore -->
 
-[GridScore](https://ics.hutton.ac.uk/get-gridscore/) [@doi:10.1186/s12859-022-04755-2] 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.
+[GridScore](https://ics.hutton.ac.uk/get-gridscore/) [@doi:10.1186/s12859-022-04755-2] is a multi-platform, web-based application for recording phenotypic observations that harnesses mobile devices to enrich the data collection process. 
+The GridScore interface closely mirrors the look and feel of printed field plans, creating an intuitive user experience. 
+GridScore performs a wide range of functions, including data validation, data visualization, georeferencing, cross-platform support, and data synchronization across multiple devices. 
+The application's data collection approach employs a top-down view onto the trial and offers field navigation mechanisms using barcodes, QR codes, or guided walks that 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.
+BrAPI has further increased the value of GridScore by integrating it into the overarching plant breeding workflow. 
+Trial designs and trait definitions can be imported into GridScore using BrAPI and a finalized trial can be exported via BrAPI to any compatible database.

content/03.01.03.ClimMob.md

@@ -2,6 +2,12 @@
 
 <!-- Marie-Angelique -->
 
-[ClimMob](https://climmob.net/) [@doi:10.1016/j.compag.2023.108539] 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.
+In traditional breeding, a small number of researchers design complicated trials in search of the best solutions for few target environments. 
+[ClimMob](https://climmob.net/) [@doi:10.1016/j.compag.2023.108539] is a software suite for an alternative research paradigm in experimental agriculture. 
+ClimMob applies the principles of citizen science and choice experiments to scale the data collection process, mostly in the format of rankings. 
+Although these data may not be as detailed as from a centralized experiment, they can inform decisions across a wide range of environments with increased external validity. 
+Applications of ClimMob include crop variety testing, 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.
+ClimMob uses BrAPI to retrieve curated germplasm information from breeding databases for trial design, subsequently enabling the automatic upload of collected ClimMob-collected data to a central breeding database for long-term storage and analysis. 
+Analyzed data can also be pushed from ClimMob to breeding databases, providing breeders with insights into the potential adoption of the tested crop varieties.

content/03.01.04.Image_Breed.md

@@ -1,5 +1,7 @@
 #### ImageBreed
 
-[ImageBreed](https://imagebreed.org/) [@doi:10.1002/ppj2.20004] is an image collection pipeline tool to support regular use of UAVs and UGVs. High-throughput phenotyping has been gaining significant traction lately as a way to collect large amounts 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. 
-
-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. 
+Unoccupied aerial and ground vehicles (UAVs and UGVs) enable the high throughput collection of images and other sensor data in the field, but the rapid processing and management of these data is often a bottleneck for breeding programs seeking to deploy these technologies for time-sensitive decision making.
+[ImageBreed](https://imagebreed.org/) [@doi:10.1002/ppj2.20004] is an open-source, BrAPI-compliant image processing tool that supports the routine use of UAVs and UGVs in breeding programs through standardized pipleines.
+It creates orthophotomosaics, applies filters, assigns plot polygons, and extracts ontology-based phenotypes from raw UAV-collected images.
+The BrAPI standard is used to push these phenotypes back to a central breeding database where they can be analyzed with other experiment data.
+The ImageBreed team has collaborated with others in the community to enhance the BrAPI image data standards, which it uses to upload raw images to a central breeding database, or any other BrAPI-compatible long term storage service.

content/03.01.05.PHIS.md

@@ -1,8 +1,14 @@
 #### PHIS 
 
 <!-- Isabelle -->
-[PHIS](http://www.phis.inrae.fr/) [@doi:10.1111/nph.15385], the Hybrid Phenotyping Information System, is an ontology-driven information system based on semantic web technologies, based on the [OpenSILEX](https://github.com/OpenSILEX/) framework. PHIS is deployed in several field and greenhouse platforms of the French national [PHENOME](https://www.phenome-emphasis.fr/) and European [EMPHASIS](https://emphasis.plant-phenotyping.eu/) 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](http://www.phis.inrae.fr/) [@doi:10.1111/nph.15385], the Hybrid Phenotyping Information System, is an ontology-driven information system based on semantic web technologies and the [OpenSILEX](https://github.com/OpenSILEX/) framework. 
+PHIS is deployed in several field and greenhouse platforms of the French national [PHENOME](https://www.phenome-emphasis.fr/) and European [EMPHASIS](https://emphasis.plant-phenotyping.eu/) infrastructures. 
+It manages and collects data from basic phenotyping and high-throughput phenotyping experiments on a daily basis. 
+PHIS unambiguously identifies 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 ([MIAPPE](https://www.miappe.org/) [@doi:10.1111/nph.16544]). 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 the [FAIDARE](https://urgi.versailles.inrae.fr/faidare/) data portal [@https://hal.inrae.fr/hal-04638310].
+PHIS has been designed to be BrAPI-compliant, encompassing the Core, Phenotyping, and Germplasm BrAPI modules. 
+This enables integration with other BrAPI-compliant systems and platforms, simplifying the exchange of accession and phenotyping data across systems.
+BrAPI-enabled interoperability 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.
+BrAPI compliance also ensures that PHIS is compatible with other standards such as the Minimal Information About a Plant Phenotyping Experiment ([MIAPPE](https://www.miappe.org/) [@doi:10.1111/nph.16544]) and enables the indexing of PHIS in [FAIDARE](https://urgi.versailles.inrae.fr/faidare/) [@https://urgi.versailles.inrae.fr/faidare].
+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. 
 
-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.

content/03.01.06.PIPPA.md

@@ -1,8 +1,14 @@
 #### PIPPA
 
 <!-- Rafael -->
-[PIPPA](https://pippa.psb.ugent.be) [@https://pippa.psb.ugent.be] is a data management system used for collecting data from the [WIWAM](https://www.wiwam.be/) [@https://www.wiwam.be] 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.
+[PIPPA](https://pippa.psb.ugent.be) [@https://pippa.psb.ugent.be] is a data management system used for collecting data from the Weighing, Imaging and Watering Machines ([WIWAM](https://www.wiwam.be/)) [@https://www.wiwam.be] range of automated high-throughput phenotyping platforms. 
+These platforms have been deployed by research institutes and commercial breeders across Europe. 
+They can be set up 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 (genotype, growth media, manual treatments) to pots, and importing, exporting, and visualizing data. 
+It also supports the integration of image analysis scripts and connects 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 [FAIDARE](https://urgi.versailles.inrae.fr/faidare/) [@https://hal.inrae.fr/hal-04638310] which allows the data to be found alongside data from other BrAPI compatible repositories.
+To share the phenotypic data from PIPPA 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 [FAIDARE](https://urgi.versailles.inrae.fr/faidare/) [@https://urgi.versailles.inrae.fr/faidare], allowing 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, [@doi:10.1038/sdata.2016.18] which are becoming best practices in plant research data management. The BrAPI technical standard, in combination with the [MIAPPE](https://www.miappe.org/) [@doi:10.1111/nph.16544] 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.
+Throughout its development, the PIPPA project has adhered to guidelines set forth by BrAPI and the [MIAPPE](https://www.miappe.org/) [@doi:10.1111/nph.16544] scientific standard. 
+Current efforts are focused on delivering a public BrAPI v2.1 endpoint and increasing the availability of public high-throughput datasets via BrAPI.

content/03.01.07.Trait_Selector_BrAPP.md

@@ -4,8 +4,11 @@
 <!-- the "BrAPP" description part should better fit at the beginning of the section. -->
 <!-- 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](https://github.com/solgenomics/BrAPI-Trait-selector) 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.
+The [Trait Selector BrAPP](https://github.com/solgenomics/BrAPI-Trait-selector) is a JavaScript-based application used to visually search and select traits from an ontology. The Trait Selector employs a visual aid, an image of a plant, to connect plant anatomy with relevant trait ontology terms. 
+Instead of scrolling through a long list of possible traits, the user can click on pieces of the image to show the traits associated with specific plant structures.
+The Trait Selector BrAPP can be used to quickly find specific traits or to identify accessions that have a specific phenotype of interest.
 
-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. 
+The Trait Selector BrAPP has been successfully added to Cassavabase and MGIS, and it can be integrated into any website or system with a BrAPI-compatible data source. 
+A breeding database would need to only implement the BrAPI endpoints for Traits, Observations, and Variables, while a genebank would require only Traits and Germplasm Attributes. 
 
 <!-- (example screenshots coming + supplementary data: links to the git and the doc) -->