Hervé Ménager

Thanks @joncison and @piotrgithub1. Here's my two cents: - format: start with JSON, as it is probably what edamToolAnnotator currently produces, and what bio.tools produces. XML, from experience, is a...

Hello @joncison @piotrgithub1 @hansioan, here's an update from the "FR" team. @ValentinMarcon has been working to create a proof-of-concept interface that instead of updating a DB would save created/modified tool...

Hi @matuskalas @bgruening, Thanks a lot for reporting this. There are three different matters here: 1. the pull request cannot be usefully merged here, modifications would be automatically erased by...

excellent summary @matuskalas , thanks. Now, regarding the problem of multiple packages related to one bio.tools entry, I would strongly argue that: 1- we do not try to solve this...

Hi, for the purpose of the ELIXIR [bio.tools](bio.tools) registry, a data format was developed some time ago, which we still use, while striving for increased interoperability. The format, [biotoolsSchema](https://biotoolsschema.readthedocs.io/en/latest/index.html), was...

Note for @mr-c : here's what I got from toil[cwl] running a workflow on a single machine, at some point I hear complaints about disk usage, although I never specified...

👍

This mapping is now being integrated in the Galaxy source code, in the bio.tools fork: https://github.com/bio-tools/galaxy This is based on John Chilton's work

No PR yet, fork is at github.com/bio-tools/galaxy. Le ven. 4 mars 2016 07:34, Michael R. Crusoe [email protected] a écrit : > Great! Is there a (standing) pull request we can...

Sorry for the delayed answer. As far as I'm concerned, I don't mind at all. Any opinion, @bgruening? On Sat, Mar 5, 2016 at 2:31 PM Jon Ison [email protected] wrote:...