Re: [mart-dev] upstream_flank length question

2007-07-25 Thread Syed Haider
Hi Marcin I can see given your filter, only one sequence is expected with NO HEADER attributes, which is not returned. The expected out is: Sequence You may specify one attribute for header, say $query-addAttribute('chromosome_name'); and you will have your sequence when there is only

[mart-dev] upstream_flank length question

2007-07-24 Thread Marcin Piechota
Dear all, I have a newbie question. When I issue this query: $input = ENSG0204389; $query = BioMart::Query-new('registry'=$registry, 'virtualSchemaName'='default'); $query-setDataset('hsapiens_gene_ensembl'); $query-addFilter('ensembl_gene_id', [$input]);

Re: [mart-dev] upstream_flank

2007-06-28 Thread Bogdan
Richard, XML: a Filter tag Perl API: addFilter webservice query API: described by type=attributes martview webpage: displayed in the attributes section What you are suggesting is for it to be treated solely EITHER as an Attribute OR as a Filter OR as a third, independent,

Re: [mart-dev] upstream_flank

2007-06-28 Thread Arek Kasprzyk
On 28 Jun 2007, at 12:23, Bogdan wrote: Richard, XML: a Filter tag Perl API: addFilter webservice query API: described by type=attributes martview webpage: displayed in the attributes section What you are suggesting is for it to be treated solely EITHER as an Attribute OR as a

Re: [mart-dev] upstream_flank

2007-06-28 Thread Bogdan
Arek, thank you for replying, Hope you can put up with that for a little while longer of course :) Bogdan

[mart-dev] upstream_flank

2007-06-27 Thread Bogdan
Dear all, when using the 'XML' button in martview, and asking for upstream_flank, we may get something similar to this: Filter name = upstream_flank value = 800/ Attribute name = gene_stable_id / Attribute name = 5utr / In the system I'm building, there's an automatic check for the correctness

Re: [mart-dev] upstream_flank

2007-06-27 Thread Bogdan
Dear Richard, thank you for explanation. However, as far as I understand both the response to '?type=filtersdataset=' and the 'XML' page in martview are generated by the same web-services API; if this is the case, then why do we find 'upstream_flank' in 'attributes' in one case, and 'filters'

Re: [mart-dev] upstream_flank

2007-06-27 Thread Richard Holland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Currently the system does this for AttributeFilters: XML: a Filter tag Perl API: addFilter webservice query API: described by type=attributes martview webpage: displayed in the attributes section What you are suggesting is for it to be