-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
b04c91f
commit d436fc3
Showing
6 changed files
with
121 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,23 @@ | ||
### Federated Data Management Infrastructures (AGENT, INCREASING, EURISCO, DataPLANT, NFDI4BioDiversity, FAIRAgro) | ||
### Federated Data Management Infrastructures | ||
<!-- | ||
(AGENT, INCREASING, EURISCO, DataPLANT, NFDI4BioDiversity, FAIRAgro) | ||
* General use case description(s) - AgrosystemIntegration 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 | ||
* Specific tool examples - BraPI endpoints for AGENT, IPK-Genebank, MIAPPE ISA-TAB2BRAPI service | ||
* Alternate solutions/ why is it better with BrAPI - Schema.ORG lightweight meta data harvesting, ARCs as collaborative data decoration, API and publication pipeline | ||
* future related use cases, areas to improve - LIMS to BrAPI proxies | ||
* future related use cases, areas to improve - LIMS to BrAPI proxies --> | ||
|
||
#### AGENT | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
BraPI endpoints for AGENT | ||
|
||
#### IPK-Genebank | ||
|
||
<!-- 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-TAB2BRAPI service | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
MIAPPE and BrAPI are designed to be inter-compatible. ISA-TAB is a file based implementation of MIAPPE. The ISA-TAB2BRAPI service is a converter between the ISA-TAB files and the BrAPI RESTful endpoints. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,26 @@ | ||
### Data visualization (Flapjack, Helium, Tassel, etc) | ||
|
||
### Data visualization | ||
<!-- | ||
* General use case description(s) | ||
* Specific tool examples | ||
* Alternate solutions/ why is it better with BrAPI | ||
* future related use cases, areas to improve | ||
* future related use cases, areas to improve --> | ||
|
||
#### Flapjack | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
Flapjack is a desktop application for visualizing and analyzing genotype data. Data can be easily imported into Flapjack from any BrAPI compatible data source with genotype data available. Flapjack Bytes is the smaller, web based counterpart to Flapjack, which can be imbedded into a database website and provide the visualizations online. | ||
|
||
#### Helium | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
Helium is a platform for reviewing and managing pedigree data. It is BrAPI enabled, so pedigree data can be viewed straight from a database. | ||
|
||
#### Tassel | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
I don't know much about Tassel or its BrAPI compliance. This is filler text for the layout of the manuscript. | ||
|
||
#### Trait Selector BrAPP | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
BrAPPs are simple tools developed by the BrAPI community that are entirely reliant on BrAPI for their data requirements. This means a single BrAPI can be shared and used by many organizations, as long as those organizations have the standard BrAPI endpoints available. For example, the Trait Selector BrAPP is used to search and select useful traits, using a visual aid to help the user find exactly what they need. The BrAPP relies only on the BrAPI Trait endpoints to function, so any data resources with a the Trait endpoints available can add this tool to their system. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,21 @@ | ||
### Sample Submission (DArT) and Genotype DBs (MGIS, GIGWA) | ||
### Samples and Genotypes | ||
|
||
* General use case description(s) | ||
<!-- * General use case description(s) | ||
* Specific tool examples | ||
* Alternate solutions/ why is it better with BrAPI | ||
* future related use cases, areas to improve | ||
* future related use cases, areas to improve --> | ||
|
||
#### DArT Sample Submission | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
The DArT genotyping lab is heavily used world wide when it comes to plant genotyping. Developers at DArT have worked with the BrAPI community to establish a standard API for sending sample metadata to the lab before genotyping. This eliminates much of the human error involved with sending samples to en external lab. | ||
|
||
#### MGIS | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
MGIS has germplasm and genotype data stored for many musa accessions. Through BrAPI, users are able to access this data directly from MusaBase, for use in specific experiments. | ||
|
||
#### GIGWA | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
GIGWA is an efficient storage system for genotype variant data. GIGWA uses BrAPI to query specific variant data out of the database. This allows for more efficient data transfer and analysis. Instead of transferring whole massive files, specific pieces, samples, markers, or chunks of data can be retrieved. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,21 @@ | ||
### Data Portal (FAIDARE, Phenospex?, etc) | ||
### Data Portal | ||
|
||
* General use case description(s) | ||
<!-- * General use case description(s) | ||
* Specific tool examples | ||
* Alternate solutions/ why is it better with BrAPI | ||
* future related use cases, areas to improve | ||
* future related use cases, areas to improve --> | ||
|
||
#### FAIDARE | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
FAIDARE is an indexing and search portal for the wider breeding community. While it can extract data from various sources via a flat file, the preferred method uses the BrAPI standard APIs. As data is added or updated in data repositories around the world, FAIDARE keeps its index up to date automatically through BrAPI. | ||
|
||
#### Phenospex - HortControl | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
HortControl, developed by Phenospex, is a data repository. HortControl has a BrAPI implementation to be used to automate workflows and analytics software. | ||
|
||
#### GLIS | ||
|
||
<!-- Peter S: Stub paragraph to stimulate the writing process. Please edit, rewrite, or delete as needed. --> | ||
GLIS is a service for creating DOIs for agricultural purposes. It also holds basic germplasm information about each accession when a DOI is created for one. GLIS is BrAPI compatible, allowing external searches on the large GLIS database. |