Sabela
Sabela
Currently, both fields are mandatory, but they should be optional (well, if the user is setting the `dataUseConditions` field they should provide at least one of these two but I'm...
This field will be used for handovers regarding the query response, not the Beacon (`beaconHandover`) or the dataset(s) (`datasetHandover`).
Update documentation so it reflects the last changes done to the spec (version number, add changes to the examples, add new parameters, etc.). Notice that the examples are still showing...
New endpoint: /genomic_snp New objects: * `BeaconGenomicSnpRequest` * `BeaconGenomicSnpResponse`
New endpoint: `/genomic_region` New objects: * `BeaconGenomicRegionRequest` * `BeaconGenomicRegionResponse`
This endpoint will list the terms for filtering (see #281) that this Beacon understands.
Add new parameter named `filters` which will accept any filtering terms displayed in `/filtering_terms`. These terms will be applied to the query.
The idea is to provide a way of specifying what queries/fields are implemented by each Beacon and, if implemented, what authentication level is required. Also, the access level per dataset...