-
I'm testing http://gigwaV2.southgreen.fr/gigwaV2/rest/Rice-MSU7/brapi/v1 using BRAVA and my server generates a 500 error on the "/allelematrix-search POST with markerprofileDbId" call.
The reason i…
-
I am validating [my BrAPI endpoint](http://bioinformatics.cribi.unipd.it/brapi/v1/), so far only with test data, and I found an error that, on my humble opinion, is a misspelled property name. The err…
-
Generated from comment in #16
If the server has a small default page size, not all "calls" will be collected for testing
-
-
Hi,
We're considering adding an option to allow non-BrAPI defined parameters when validaring resources. This would mean that deprecated parameters and extra parameters would not raise an error or w…
-
Hello every one, I am about to complete implementing BRAPI calls for SNP-seek, to query genotypic, phenotypic and passport data for the 3024 rice genomes. My main concern is the huge genotype matrix i…
-
Here is a short idea for a new call which returns the direct descendants of a germplasm object.
Request:
`GET` `https://{server}/brapi/{version}/germplasm/{germplasmDbId}/progeny`
Response:
`…
-
Hi,
Should we consider JSON LD for version 2?
http://json-ld.org/
-
I don't think the POST parameters are working for calls such as allelematrix-search. Should you be using the param("param1", "value1") statement in the code instead of defining the parameter in the ur…
-
I remember having raised this question in Seattle last summer. We need consistency in the way we format the calls call's response where IDs are involved. Because clients will probably want to be able …