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. Am I missing a dimension to these files? In any case, I'd have to add the ability to associate the files in the API, probably a new operation in the update method for library contents? John Duddy Sr. Staff Software Engineer Illumina, Inc. 9885 Towne Centre Drive San Diego, CA 92121 Tel: 858-736-3584 E-mail: jduddy@illumina.com -----Original Message----- From: James Taylor [mailto:james@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 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 dataset when I upload/register the main file? I'd also need to know how to write such a file.