If you install the blast_datatypes repository into your Galaxy instance using 
the tool shed installation process everything necessary is handled for you 
automatically, but I understand you are not yet installing from the tool shed.  

If you are not installing, you'll have to manually download the repository 
contents from the tool shed using the "Repository Actions" pop-up menu and 
place the contained xml.py file in the appropriate location so it can be loaded 
when you start your Galaxy server.  You'll then need to manually add the 
datatype entries in your datatypes_conf.xml file as they used to be.


On Aug 27, 2012, at 9:39 AM, Peter Cock wrote:

> That is helpful Greg - thank you - although I worry the learning
> curve for developing Galaxy tools is getting steeper.
> You've implied 'simple' proprietary datatypes which depend only
> on Galaxy itself (and not other ToolShed entries) can be developed
> without a local ToolShed. That's the situation I'm interested in.
> How would I enable the 'blastxml' datatype (now in the ToolShed
> as 'blast_datatypes')? My guess is adding something to file
> datatypes_conf.xml, which used to include these lines:
> <datatype extension="blastxml" type="galaxy.datatypes.xml:BlastXml"
> mimetype="application/xml" display_in_upload="true"/>
> and:
> <sniffer type="galaxy.datatypes.xml:BlastXml"/>
> Thanks,
> Peter

Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:


Reply via email to