composite datatypes: uploading and optional files
Hi there We've got a composite datatype (neostore) for Neo4j databases. Currently the upload is disabled because to upload you need to select each individual file of the database directory (which is tedious). Is there a more efficient way to upload composite datatypes? E.g. as a tar.gz or zip file? If not, has anyone looked into supporting this? (I see @jmchilton was noted as working on a composite uploading for 17.05) Secondly, we're moving to support Neo4j 3.2.0. In this version there is a minor (1 file) change in the files used to store the database. Can composite datatypes have "optional files"? Thanks, Peter
Hi Peter, Am 02.06.2017 um 15:55 schrieb Peter van Heusden:
Hi there
We've got a composite datatype (neostore) for Neo4j databases. Currently the upload is disabled because to upload you need to select each individual file of the database directory (which is tedious). Is there a more efficient way to upload composite datatypes? E.g. as a tar.gz or zip file? If not, has anyone looked into supporting this? (I see @jmchilton was noted as working on a composite uploading for 17.05)
Secondly, we're moving to support Neo4j 3.2.0. In this version there is a minor (1 file) change in the files used to store the database. Can composite datatypes have "optional files"?
Yes this is possible, please have a look at https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/datatypes/blast.... Cheers, Bjoern
Thanks, Peter
___________________________________________________________ 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: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/
participants (2)
-
Björn Grüning
-
Peter van Heusden