BioMart developers, A user describes a problem with programmatic access to BioMart as follows:
> When accessing the data sets for the mart ENSEMBL_MART_PLANT via the > MartService at biomart.org, an error is being generated if the > virtualschema=default parameter is not included. > > Example: > > this isn't working > http://www.biomart.org/biomart/martservice?type=configuration&dataset=alyrata_eg_gene > > and this is > http://www.biomart.org/biomart/martservice?type=configuration&dataset=alyrata_eg_gene&virtualschema=default > > The services are accessed via the MartService urls. To access the mart in > question we are using the url: > > http://www.biomart.org/biomart/martservice?type=configuration&dataset=alyrata_eg_gene > > which currently responds: > Dataset name conflict for alyrata_eg_gene. Need to further qualify with the > virtualSchema param as well > > If I add the virtualschema parameter as default, the correct information is > retrieved: > > http://www.biomart.org/biomart/martservice?type=configuration&dataset=alyrata_eg_gene&virtualschema=default > > However, based upon the documentation, the virtualschema is 'default' by > default. Do we have to alter the client code to include the > virtualschema=default parameter? Based on our reading of the docs it > shouldn't be required, e.g. accessing > http://www.gramene.org/biomart/martservice?type=configuration&dataset=alyrata_eg_gene > it is unnecessary. > > If this doesn't make sense, let me know. I would appreciate any advice you could provide. -- Ken Youens-Clark [email protected] Gramene.org Project Manager Ware Lab/CSHL/USDA-ARS _______________________________________________ Users mailing list [email protected] https://lists.biomart.org/mailman/listinfo/users
