That is great, I`ll give it a try.
Thank a lot,
From: Greg Von Kuster [g...@bx.psu.edu]
Sent: Tuesday, August 14, 2012 10:38 PM
To: Marc Logghe
Cc: Björn Grüning; firstname.lastname@example.org
Subject: Re: [galaxy-dev] Upload File: how to see all registered formats ?
This issue has been resolve din change set 7491:a7a0a5962648, which will be
included in the next Galaxy release. It is also currently available in the
Galaxy central repository in case you track that repository. The datatypes
registry will load any changes you've made to the datatypes_conf.xml file
installed with the emboss_datatypes tool shed repository (or any other
repository that includes this file). SO display_in_upload will now function
correctly for the installed proprietary datatypes.
Thanks for reporting this issue, and sorry for the inconvenience.
Greg Von Kuster
On Aug 3, 2012, at 4:53 PM, Marc Logghe wrote:
> Hi Greg,
>> You'll need to add the display_in_upload attribute to your local version of
>> the datatypes_conf.xml file installed with your emboss_datatypes repository
>> from the tool shed.
> I'am afraid this does not work. At least not in my hands. Like I indicated
> before, it seems like the upload tool does not take the tool shed
> emboss_datatypes into account, with or without the display_in_upload
> attribute set.
> It seems to work only if you transfer the entire data type definition line to
> the main galaxy datatypes_conf.xml
> That is the workaround I currently use.
>> This may result in a merge at some point if the contents of the
>> datatypes_conf.xml file changes in the emboss_datatypes repository in the
>> main tool shed and you pull the updates to your
>> local repository.
>> Greg Von Kuster
>>> Hi Björn,
>>> I think the issue is that the genbank datatype is coming in via the tool
>>> shed and is not taken into account by the upload tool. The genbank datatype
>>> is defined in
>>> I have added the display_in_upload attribute in the latter file for the
>>> genbank datatype, restarted Galaxy but the type did not appear in the
>>> Should the genbank datatype be added to the main galaxy datatypes_conf.xml
>>> ? Or is it better to explicitly add the emboss' datatypes_conf.xml to the
>>> universe_wsgi.ini (but this will break the tool shed update system, right) ?
> THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY
> TO WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
> CONFIDENTIAL AND EXEMPT FROM DISCLOSURE.
> If the reader of this E-mail message is not the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited. If you have received this communication
> in error, please notify us immediately at abl...@ablynx.com. Thank you for
> your co-operation.
> "NANOBODY" and "NANOCLONE" are registered trademarks of Ablynx N.V.
THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO
WHICH IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND EXEMPT FROM DISCLOSURE.
If the reader of this E-mail message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately at abl...@ablynx.com. Thank you for your
"NANOBODY" and "NANOCLONE" are registered trademarks of Ablynx N.V.
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: