myexperiment-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Myexperiment-discuss] Upload any type of Workflow you want...


From: Jiten Bhagat
Subject: Re: [Myexperiment-discuss] Upload any type of Workflow you want...
Date: Mon, 27 Oct 2008 22:56:36 +0000
User-agent: Thunderbird 2.0.0.17 (Windows/20080914)

Hi Gernot,

Please see my comments inline...

Gernot Stocker wrote:
Hi myExperiment -Team,
congratulations for this great new feature and it brings me to the question 
whether it could
be also used to exchange xml-based experiment protocols? Within the next days we are going to release a new version of our software iLAP which offers despite other features some kind of ELN functionality. There, experiment protocols can be exported as xml "workflows" which are the basis for a web based data aquisition wizard. First, is it allowed to exchange also iLAP protocols via myExperiment?

Absolutely! You can now upload *any* file to myExperiment under the "workflows" tab. So you can upload your iLAP protocols onto myExperiment now.

When you go to the workflow upload page select "Enter custom metadata" in step 2. Here you can define what type of workflow you are uploading. Select "Custom" from the drop down box (for "Workflow Type") and you will be able to enter in your own custom type of workflow that will be available to everyone next time someone comes to upload a workfow (eg: you can define the workflow type "iLAP protocol" which will then be available in the drop down box). You then need to provide a title and optionally a description of the workflow and a preview image to help people better discover the workflow.

For "extended support" for your own workflow type please see comments below...

Which format do you use for your workflows in order to achieve a better integration of our protocols within myExperiment? Or can we use our own? Is there a developer documentation available for such an integration path?

You can use whatever format you feel suitable for your workflows and choose to always provide custom metadata when uploading it to myExperiment. Alternatively we can work with you on getting permanent extended support for your workflow type, so that users uploading your workflow don't have to provide custom metadata and all metadata (and possibly a preview image) can be obtained from the workflow itself (like we do for Taverna). We're still in the process of putting some developer documentation up about this but the main thing is you will need to provide us with some ruby code that does the recognisation of your workflows, parsing of metadata and (if you want) parsing/generation of preview images. We can then define a "workflow processor" that can be used to recognise your specific type of workflows and provide the extended support.

Other "extended support" features we can develop together for your workflow type are:
- ability to view the internal structure of the workflow.
- ability to index the internals of the workflow so they are used in searches.
- ability to provide different "run" and "launch" options for your workflow.

If you are interested in doing this please contact me offline and we'll be glad to assist you :-)

Sorry for the newbe questions, but your announcement encouraged me to follow 
this idea
with more energy.

Not a problem! We're very glad you like this new feature.

Cheers,
Jits

Thanks, GS

On Thursday 23 October 2008, David De Roure wrote:
The myExperiment team is very pleased to announce that myExperiment can now 
store any type of workflow, not just Taverna ones.  This means that you can 
upload any file as a workflow which can then be shared, discovered, downloaded, 
tagged, rated, commented on, added to packs and so on.

We already have some Trident workflows, and some experimental plans from chemistry 
(Usefulchem EXPLANS). You can upload your own types of workflows by going to the upload 
workflow page (you may be asked to log in). If we can't automatically detect the type of 
workflow and infer data from it (like title and description) you can provide this by 
selecting the "Enter custom metadata" option in step 2.

Note that we currently provide extended support for Taverna 1 workflows only - 
we can automatically detect the type, parse title/description metadata, 
generate preview images, view the internals and enact these workflows all 
directly in myExperiment. In the coming months we aim to work with our user 
communties to provide extended support for other types of workflows.

If you would like to get involved in providing extended support for other types 
of workflows then please contact us. We are keen to work with you in getting 
myExperiment to support as many other workflows types as possible.

Thanks again for all your support!

The myExperiment Team

http://www.myexperiment.org/announcements/20

------------------------------------------------------------------------

_______________________________________________
Myexperiment-discuss mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/myexperiment-discuss





reply via email to

[Prev in Thread] Current Thread [Next in Thread]