Welcome to PHENO's documentation!
=================================
.. toctree::
:maxdepth: 4
:hidden:
:caption: 🚀 Getting Started
Getting Started
.. toctree::
:maxdepth: 4
:hidden:
:caption: 📂 OntoBrAPI
PHENO Submission
Validator
Mapping
.. toctree::
:maxdepth: 4
:hidden:
:caption: 💡 Guides
Dataverse
MIAPPE Template
.. toctree::
:maxdepth: 4
:hidden:
:caption: 📚 References
References
| `PHENO `_ is a data portal for the submission, storage and sharing of metadata for plant phenotypic experiments.
| If you're looking for a comprehensive guide of both `PHENO `_ and the `OntoBrAPI `_ platform, then you've come to the right place.
.. admonition:: In a Nutshell, **PHENO**:
1. Receives as input a MIAPPE compliant Excel file
2. Validates it according to the MIAPPE specifications
3. Makes your metadata and associated phenotypic data FAIRly available worldwide through BrAPI compatible search engines
Make your data FAIR using PHENO
-------------------------------
| `FAIR `_ data is increasingly more valued in research, with new projects tending to follow **FAIR** guidelines when working with their data.
| **PHENO** is a tool that helps you make your data **FAIR** by providing a platform for the submission, storage and sharing of metadata for plant phenotypic experiments.
|
| **PHENO** incorporates the **FAIR principles** in the sense that:
| * Data is stored in a secure, open and accessible repository with version control.
| * Enables data findability and reusability through descriptive metadata of phenotypic experiments using `MIAPPE `_.
| * It is interoplable with other data repositories (e.g., `FAIDARE `_) through the use of the `Breeding API (BRAPI) `_.
Getting Started
---------------
| To submit metadata in **PHENO**, users are required beforehand to deposit the actual phenotypic data (e.g., tables, images) in another data holder of choice, for example:
1. `Dataverse `_\*
2. Google Drive / Microsoft OneDrive
3. Other specialized data repositories
| \*Dataverse is a database for any type of scientific data. For portuguese users, learn on :ref:`how to submit your data in DMPortal`, the portuguese Dataverse.
|
| To use PHENO for the first time, please check the :ref:`Getting started with PHENO ` section.
| To get acquainted with the **FAIR** and **MIAPPE standards**, and terms such as **BrAPI** or **FAIDARE**, feel free to check the :ref:`References ` section.
| If you require additional assistance, feel free to contact us directly (hm.rodrigues@itqb.unl.pt).
PHENO in Detail
---------------
.. figure:: /images/PHENO_structure.jpg
:scale: 75%
:align: center
:alt: PHENO structure overview
PHENO structure overview
| **PHENO** ensures data FAIRness by integrating 3 main modules based on international standards:
1. Data submission (MIAPPE)
2. Data storage (RDF)
3. Data sharing (BrAPI)
| 1) In data submission, a Graphical User Interface (GUI) allows the conversion of MIAPPE compliant spreadsheets into n-triples format.
| The GUI allows users to dynamically map the MIAPPE spreadsheet to the appropriate `Plant Phenotype Experiment Ontology (PPEO) `_
| in Javascript Object Notation (JSON). The user can use a predefined MIAPPE - PPEO mapping template available, or adjust any fields as
| deemed necessary. The GUI uses the constraints of the ontology to validate the mapping.
|
| 2) PHENO relies on `OpenLink Virtuoso `_ to store the metadata in triples and create a database
| management system for data curators to validate datasets and select which ones are ready for sharing.
|
| 3) PHENO serves as a BrAPI endpoint where the data stored is made available in JSON to BrAPI calls, in accordance with the `BrAPI specifications `_.
|
| To submit medata in PHENO, check the :ref:`Submitting Metadata in PHENO` section.
| To learn how to browse PHENO for a specific project \(meta\)data, check the :ref:`Getting started with PHENO ` section.