On Aug 26, 2011, at 7:23 PM, Duddy, John wrote:
> I'm looking into these, and it seems that the spirit is to store a version of
> the data that is converted, like a FASTQ -> BAM or some such use case, where
> one file can be extracted from the other.
It was originally built for that (hence the
or [mailto:ja...@jamestaylor.org]
Sent: Friday, August 26, 2011 1:52 PM
To: Duddy, John
Cc: galaxy-dev
Subject: Re: [galaxy-dev] Storing a dict as metadata
Not currently, but since a converted dataset is just a dataset, you could reuse
all of the existing upload mechanism, and just add the conv
Not currently, but since a converted dataset is just a dataset, you could reuse
all of the existing upload mechanism, and just add the converted dataset
connection between the two after the fact.
On Aug 26, 2011, at 11:54 AM, Duddy, John wrote:
> Is there a way to upload that converted datas
Sent: Friday, August 26, 2011 5:37 AM
To: Duddy, John
Cc: galaxy-dev
Subject: Re: [galaxy-dev] Storing a dict as metadata
Hey John, are you sure you don't want to use a "converted dataset" rather than
a metadata element for this. This is how we handle most types of secondary
index
Hey John, are you sure you don't want to use a "converted dataset" rather than
a metadata element for this. This is how we handle most types of secondary
indexes for visualization.
If you do it this way, the converter that creates the offset index is just
another tool (but registered in dataty
I'd like to have a datatype with a dict as metadata. This dict() would store
file offsets to enable seeking around to process different sections of the file.
How do I add a dictionary data metadata element?
John Duddy
Sr. Staff Software Engineer
Illumina, Inc.
9885 Towne Centre Drive
San Diego
