Suggestion On Functionality For Published Workflows

Question: Suggestion On Functionality For Published Workflows

9.1 years ago by

I have never used myExperiment but it sounds like a good site to use for posting published workflows. The tricky bit is to get people to post their workflows there. Would Galaxy be willing to suggest that users publish workflows there? I think galaxy is great, but what it lacks at the moment is exactly something like this myExperiment.org which can provide the "social" elements: direct interaction between users, posting of workflows, collaboration, etc. I gather Galaxy is starting work in this direction, but perhaps it would be better to see to what extent galaxy could integrate with an existing solution. Tim. Message: 4 Date: Wed, 11 Nov 2009 09:25:23 +0100 To: galaxy-user@bx.psu.edu Subject: Re: [galaxy-user] Suggestion on functionality for published workflows Message-ID: <b66932c30911110025t45b73d6amd777817dffe3d025@mail.gmail.com content-type:="" text="" plain;="" charset="iso-8859-1" hi,="" would="" it="" be="" an="" idea="" to="" post="" galaxy="" objects="" on="" myexperiment.org?="" it="" seems="" like="" a="" good="" place="" to="" share="" these="" types="" of="" workflows="" and="" histories.="" although="" now="" mostly="" used="" by="" taverna="" users,="" any="" kind="" of="" (scientific)="" digital="" object="" can="" be="" placed="" there.="" cheers,="" jelle="" 2009="" 11="" 10="" timothy="" hughes="" <timothy.hughes@medisin.uio.no=""> out a page -- Tim Hughes PhD (http://digitised.info) Medical Genetics Department Oslo University Hospital Ullevĺl Kirkeveien 166 0407 Oslo Norway

galaxy • 719 views

ADD COMMENT • link •

modified 8.9 years ago by Jeremy Goecks • 2.2k • written 9.1 years ago by Timothy Hughes • 30

9.1 years ago by

James Taylor • 320

United States

James Taylor • 320 wrote:

We're in communication with myExperiment about this. Once we have a portable representation of workflows that can be moved between Galaxy instances, this will be quite easy.

ADD COMMENT • link written 9.1 years ago by James Taylor • 320

8.9 years ago by

Jeremy Goecks • 2.2k

Jeremy Goecks • 2.2k wrote:

Hi Assaf, I'm cc'ing the galaxy-user list because this is a good discussion to have and because this is good information to share. To your questions: First, to be clear: we've not broken/replaced/removed any functionality with any recent changes; these changes provide enhancements. I assume we're starting from the history grid. When you make a history importable from the grid, you can see the link to its public location by clicking on the text "importable" in the history's status column. This link takes you to a page where you can see two links for each importable history: a link for importing the history and a link for viewing the history. The view link takes you to a page where you can view the history *or* import the history (there's a link at the top of the page to import it). This is a difficult issue and one that's in flux and open for discussion. Right now, when you make a history importable, it is public in the sense that anyone can import it. Yes, they have to know the history's encoded ID, but "security through obscurity" is not a model that Galaxy employs. If someone wants to share a history with a limited subset of people and keep the history private, they can do so via the history sharing mechanism. Because "enable import" already makes a history accessible by everyone, it is reasonable that doing so makes the history "public." The basic sharing categories, then, haven't changed. What's changed, of course, is that Galaxy now makes it possible to find public/importable items. As I said, we're in the process of changing the history sharing language to make clearer what is happening; hopefully these changes will help users decide when to make a history public and when to share it with a limited set of other people. Another option is to allow users to make a history public but hide it from the list of public items. This is effectively what making a history importable does, and it's not a great solution. FYI, there are distinct advantages when users can view a history rather than having to import it: (a) it's less work to view the history; (b) it's not necessary to clutter your histories with imported histories; (c) it's not necessary to understand how to use Galaxy to view a history; and (d) users can (eventually) annotate/rate/comment on shared/public histories, thereby providing a single place to work with a shared history. Best, J.

ADD COMMENT • link written 8.9 years ago by Jeremy Goecks • 2.2k

Hi Jeremy, Thanks for you reply, but let me rephrase my question: Jeremy Goecks wrote, On 01/12/2010 01:29 PM: The existing functionality of the 'import via link' is great, and I use it a lot. My question is about the new "list public histories page": http://main.g2.bx.psu.edu/history/list_public The history I shared (via link) appears there, but there's no action associated with it. Meaning: I can see that it is public, but I can't do anything about with (and my expectation would be that I would be able to click on it and import it, because it is public). Otherwise, what's the purpose of the "list public histories" page? is it just to let me know about the names and owners and dates of public histories (but without the ability to import them?). -gordon

ADD REPLY • link written 8.9 years ago by Assaf Gordon • 320

That's a bug. The history name should provide a link that you can use to view/import/tag the history. I'll fix it momentarily. Thanks, J.

ADD REPLY • link written 8.9 years ago by Jeremy Goecks • 2.2k

You need to have a username for the history's link to appear. Create a username by navigating (User Menu)->Preferences->Manage your information. Best, J.

ADD REPLY • link written 8.9 years ago by Jeremy Goecks • 2.2k

Please log in to add an answer.

Similar posts • Search »