Michael Baudis
Michael Baudis
See https://github.com/ga4gh-beacon/beacon-v2/issues/125
Beacon v2 responses are very chatty & require _many_ parameters in their `meta` elements which only serve verification purposes (e.g. that the beacon could interpret the query ...). This, however,...
There is currently no way to exclude specific ontologyTerms in filter queries although this would be desirable to expand query options (especially regarding the limitation of not having Booleans) and...
For some responses one could envision the use of alternative schemas which do not represent an entry type and/or have an id. A practical example here would be the export...
Pagination should not be required parameter in beaconReceivedRequestSummary since it doesn't make sense in Boolean and count responses (and also not if all data is returned but here YMMV). https://github.com/ga4gh-beacon/beacon-v2/blob/eb8958fad3a04499d41f7f528292d29d2f23ccbf/framework/src/responses/sections/beaconReceivedRequestSummary.yaml#L50
See https://github.com/ga4gh-beacon/beacon-v2/commit/16db543100221f40453f0dbe2950375fb65d58e3
While the `/filtering_terms` endpoint provides a standard way to inform about terms being used/queryable for a beacon there is currently no information about supported genomic variation query parameters or the...
`ResultsetInstance` was missing the "type" parameter which leads to errors when creating instances. Tis is an urgent fix w/o any changes to the schema etc. and IMO should directly go...
Some streamlining of the entryTypesDefinition schema. I think this is just a streamlining of the code which was a bit confusing but please check ...
The parameter descriptions in the EntryTypeDefinitions schema seem somewhat hard to parse and potentially misleading - this is a go at cleaning them up a bit.