Minimum Information About Plant Phenotyping Experiments
MIAPPE is an open, community driven project to harmonize data from plant phenotyping experiments. MIAPPE provides a specification including a checklist and a data model of metadata required to adequately describe plant phenotyping experiments. Those specifications are implemented in several tools, databases and file templates and exchange formats that allow to validate, store and disseminate MIAPPE-compliant data. We welcome contributions from anyone interested in plant phenotyping data, inluding linked data.
Development of MIAPPE is an open process, so if you would like to contribute by commenting, reviewing or participating to the ongoing development, please let us know via the MIAPPE mailing list.
Mailing list registration
You can subscribe to the MIAPPE mailing list to join the community or simply get the latest informations.
MIAPPE primersSee the support page for full informations
- The latest specifications, data model overview
- The latest specifications field list with descriptions and examples in tsv, PDF and Excel format.
- Training and exchange templates
- Mapping between MIAPPE and other standards (ISA-Tools , Breeding API (BrAPI))
Plant phenotyping data is diverse, dispersed and increasingly plentiful owing to the application of new automated techniques. While various initiatives have explored how to describe plant traits (e.g. the Plant Trait Ontology) and phenotypes, description of the experimental design that provides the context for phenotypic observations is not well-standardized. A basic description of the materials used and the experiment performed is needed to support data discovery and data mining applications. MIAPPE – the Minimal Information About a Plant Phenotyping Experiment – is in development to address these needs.
MIAPPE is a Minimum Information (MI) standard for plant phenotyping. It defines a list of attributes that might be necessary to fully describe a phenotyping experiment, following the model originally established for microarray data. Not all of the elements listed in an MI must be reported in each case. An MI document should rather be considered as a checklist, and consulted by a person describing or depositing the data to ensure the inclusion of all important data characteristics, i.e. what is meaningful for the interpretation and potential replication of the research.
MIAPPE is a logical standard - but there are specific implementations of tools designed to support its use and application, for example, in the ISA-tools framework. We are working with the developers of the Plant Breeding API (BRAPI) to ensure the compliance of BRAPI with the MIAPPE standard, and to coordinate future developments.
MIAPPE was originally been developed in the context of the transPLANT, European Plant Phenotyping Network and ELIXIR-EXCELERATE projects, but we are keen to work with anyone interested in contributing to, reviewing or using the standard, or developing new tools.
MIAPPE v1.1, January 2019
MIAPPE version 1.1,released on 10th January 2019, relied on two requests for comments. Major developments over v1.0 include:
- The extension of MIAPPE’s scope to accommodate woody plants as an additional use-case.
- The specification of a data model for MIAPPE, to facilitate its implementation in various formats and enable its automatic validation.
- Compatibility of the MIAPPE logical standard with common frameworks for representing these data types, namely ISA-Tools and the Breeding API (BrAPI).
- The enrichment of MIAPPE, with the provision of clear definitions and examples for all fields.
A new paper describing the application of MIAPPE v1.1 to a variety of use cases has just been published in the New Phytologist. Meanwhile, improvements can be suggested via email@example.com. Work is now commencing on the next version of MIAPPE, v2.0. Development is at an early stage and all contributions are welcome.
MIAPPE v1, July 2016
The initial version of MIAPPE has been designed as a checklist, following the approach of international deposition databases. It is now extended by MIAPPE v1.1.