1 Aug 2007 11:24
When do you push the button?
Hello Its August 1st! Just wondering, when you're going to push the button, and make myExperiment live? Duncan -- -- Duncan Hull http://www.cs.man.ac.uk/~hulld/ +44 (0) 161 306 5139
Hello Its August 1st! Just wondering, when you're going to push the button, and make myExperiment live? Duncan -- -- Duncan Hull http://www.cs.man.ac.uk/~hulld/ +44 (0) 161 306 5139
Well, we went live early for ISMB, so the button was already pushed. The only change we made today is to remove the August 1st message from the front page!(Continue reading)We encourage people to carry on using the current service for "random play" (to borrow a facebook phrase!) and for demos, and keep up the feedback (which is really useful, thanks). There will be some less random play in more controlled trials with users (Duncan - I think Carole will be talking with you about this...) - this will from September and we will be making a few changes to support that exercise. Meanwhile we are this week putting up a "backup" server in Southampton so there will be a second URL available for people doing demos, just in case of problems with networks going down etc. This is also taking us into a world with multiple myExperiment servers, which is an important step. While people are playing and trialling, the development team is working on the codebase for the next full release later in the year, which will support enactment, versioning and basic EMOs. I'll send instructions to the list to remind people how to try the beta... Thanks -- Dave
If you're visiting myexperiment.org, simply click on "Try the beta today" - the secret word is dolphin. This will take you to the beta service. When you do this you'll be told you can go directly into the beta service by going to http://carlin.myexperiment.org/ so it's handy to bookmark this URL. But don't worry if you lose it, you can always go to myexperiment.org and do the dolphin thing again. BTW The first time you use myexperiment you'll need to create an "openid" if you don't already have one - just follow the instructions. Feel free to give this information to your colleagues so they can join in the fun, but please don't give out the secret word or beta URL anywhere public - this is a "closed beta" service for "friends and family" at this stage (hence the secret word mechanism, which means that public visitors to myexperiment.org need to send us an email to get in). -- dolphin Dave
On 18 Jul 2007, at 10:31, Duncan Hull wrote: > 3. Facebook (which now has lots scientific groups e.g. [3]) > [3] http://www.plos.org/cms/node/239 Somehow I get the feeling that plos.org is not what you expect anymore: Pathology | Travel | Computer Notebooks | Music Download Online Store * Credit Report * Lawyers * Game Is this the library we are to entrust our workflows with? -- -- Stian Soiland, myGrid team School of Computer Science The University of Manchester http://www.cs.man.ac.uk/~ssoiland/
Well yes. Especially since they miss-spell Entrez with Entres. And there is a giant fart button at the bottom :( Paul. Stian Soiland wrote: > > On 18 Jul 2007, at 10:31, Duncan Hull wrote: >> 3. Facebook (which now has lots scientific groups e.g. [3]) >> [3] http://www.plos.org/cms/node/239 > > > Somehow I get the feeling that plos.org is not what you expect anymore: > > > Pathology | Travel | Computer Notebooks | Music Download > > Online Store > > * Credit Report > * Lawyers > * Game > > > > Is this the library we are to entrust our workflows with? >
> We talk a lot about giving credit to people who publish as an incentive > - one obvious thing is to indicate how many times a workflow has been > downloaded. > Please can we introduce some credit and citation feedback Wouldn't it be interesting to know how often a workflow has been run? I imagine that if, by downloading a workflow from myExp (counter++), you actually got a slightly modified version: a version with a Taverna tracking code/workflow identifier inserted into the SCUFL (similar to the code you insert for Google Analytics or other web stat service). So, when you run the workflow, a counter corresponding to that workflow gets knotched up by one iota on a myExp server. And when it runs to *completion* you get a few more iota's. This would not require any special effort on the user's part (but admittedly some special effort on the part of my* developers..). Then, along the same lines as the ISMB micropayment idea, workflow developers can grant some of their "iota's" to workflows that they like. Or trade them in for a higher priority on a bug fix/feature request. :) -scott n.b. When the days of semantic markup arrive, a similar point system would be interesting to use to "harvest" concepts for a view of the global semantic discourse. -- -- M. Scott Marshall tel. +31 (0) 20 525 7522(Continue reading)
On 8 Aug 2007, at 18:45, M. Scott Marshall wrote: > Wouldn't it be interesting to know how often a workflow has been > run? I > imagine that if, by downloading a workflow from myExp (counter++), you > actually got a slightly modified version: a version with a Taverna > tracking code/workflow identifier inserted into the SCUFL (similar to > the code you insert for Google Analytics or other web stat > service). So, > when you run the workflow, a counter corresponding to that workflow > gets > knotched up by one iota on a myExp server. And when it runs to > *completion* you get a few more iota's. This would not require any > special effort on the user's part (but admittedly some special > effort on > the part of my* developers..). There's some privacy issues with such reporting, but we can do it in a slightly similar way if we include it as options: [ ] Report anonymous workflow usage statistics to myXP [ ] Report anonymous service usage statistics to myXP This would be a part of an myExperiment plugin (that would also be able to tell you if there was a new version of the workflow, let you submit the workflow straight to myXP, etc). All that needs to be inserted into the downloaded workflow would be some URI or another identifier (obviously the never-changing LSID is not very good for this) to report which workflow is in question.(Continue reading)
_______________________________________________ Myexperiment-discuss mailing list Myexperiment-discuss@... http://lists.nongnu.org/mailman/listinfo/myexperiment-discuss
RSS Feed2 | |
|---|---|
10 | |
3 | |
1 | |
10 | |
5 | |
2 | |
7 | |
6 | |
8 | |
2 | |
14 | |
3 | |
8 | |
3 | |
3 | |
11 | |
1 | |
4 | |
13 | |
3 | |
12 | |
4 | |
21 | |
1 | |
6 | |
8 | |
3 | |
7 | |
9 | |
10 | |
16 | |
16 | |
10 | |
27 | |
24 | |
22 | |
33 | |
37 | |
68 | |
14 | |
39 | |
10 | |
21 | |
10 | |
15 | |
29 | |
67 | |
13 | |
43 | |
52 | |
39 | |
12 | |
14 | |
24 | |
21 | |
10 | |
4 | |
22 | |
3 | |
10 | |
21 | |
61 | |
30 | |
48 | |
75 |