About the datatype.  So you are thinking of a new datatype that applies to 
files that hold the versioned database contents (in this case a structured 
key-value fasta identifier/sequence pairs, right?)  Then the fasta archive 
versioning tool would take only files of that datatype for input. That sounds 

I was just going to have one folder (and its subfolders) in the data library 
that hold all the versioned databases to choose from.  So the versioned 
database tool would just populate its input list based on that subfolder tree.  
But ensuring that it lists only files of a certain datatype sounds beneficial.

Output in any case would be a fasta file that other tools are already 
expecting; I wasn't going to leave that as just "fasta" datatype since it seems 
tools like makeblastdb don't allow anything else as input from user history.

I'm hoping that a global (admin) API key can be used by the tool so that all 
users can get versioned data, but maybe that is a pipe dream.

Sure I'd like to see old patches!

From: Bj?rn Gr?ning [bjoern.gruen...@gmail.com]
Sent: Saturday, August 23, 2014 12:17 AM
To: Dooley, Damion; galaxy-dev@lists.bx.psu.edu
Cc: Hsiao, William
Subject: Re: [galaxy-dev] Concept for a Galaxy Versioned Fasta Data Retrieval 

Hi Damion,

the idea sounds fantastic!
Can we go a step further and use a specific datatype that keeps entire
fasta files versioned and the user can choose which version he wants to
use, in any tool? Please have a look at my talk at GCC2012. Maybe you
are interested in the (old) patches. I would be very interested to
restart this old project.

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:

To search Galaxy mailing lists use the unified search at:

Reply via email to