GuilhemSempere

cool ;-) So where do we go from here? I guess the API is not going to be updated just like that? Is it good practice to extend the request...

Are these going to be supported at some point? We are facing similar issues in reading "custom" VCF files that may contain ambiguity codes. Writing an adhoc VcfCodec seems complicated...

Do you mean that /maps/{mapDbId}/markers and /markers-search would become equivalent, apart from the fact that the first one limits the range of data to that which is linked to the...

Actually, the plain GA4GH specs do not support these filtering parameters: https://rest.ensembl.org/documentation/info/gavariants. They were added as an enrichment to the Gigwa V2 implementation because we wanted to make it API-driven...

Our issues are different. I was only mentioning the lookup results under the divider line, not being removed after closing/re-opening the widget Anyway... 4 years later, I finally spent some...

What about simply supporting regex searches? Are there any cases we would'nt be able to deal with?

I don't see major problems implementing this in Gigwa's allelematrix call, but indeed we'd rather have this functionality well defined and made official before starting something. I think @patrick-koenig you...

As far as I know when you launch variant calling on sequencing data you do get different kinds of variants. At least SNPs and INDELs. Sometimes CNVs or structural variants...

May I suggest something along these lines? GET /brapi/v1/marker-types-search{?markerDbIds}{?name}{?matchMethod}{?pageSize}{?page}

From my point of view defining a fixed set of marker types is feasible but is a separate matter. The need I was trying to express was for a way...