Labeling all of the currently functioning tools in kbase as prototypes seems a little problematic to me. But fair enough. And you're right, I don't think even yury said "everyone". He probably said "some". Sorry to hypobolize. Also, the word beta seems preferable to me than the word prototype. On May 24, 2013 4:43 PM, "Matthew Henderson" <[email protected]> wrote:

On 2), Adam has made it clear that labs are not supposed to be considered "production quality", so I think using prototypes or beta is an accurate description of what the labs are supposed to represent. Currently there is not a roadmap to go from lab to application, which would be considered production quality. Ultimately many of the current labs will be absorbed in one way or another into the narrative.

So you had someone comment that "everyone" was scared away from the labs pages. I would be extremely doubtful of that statement. I would even be doubtful if you replaced "everyone" with "most" people. The fact that Chris is actively promoting the use of certain labs as part of his tutorials suggest that people are in fact using them despite the "prototypes" label.

So I would ask that we not completely remove either a "Beta" or "prototypes" disclaimer from the labs landing area. Google has beta plastered all over things and that doesn't stop people from using them. If prototypes is the problem, then let's change it to Beta.

On Fri, May 24, 2013 at 2:33 PM, Elizabeth M. Glass <[email protected]>wrote:

...

Thanks Chris!

Just as FYI -

2. Good comment and easily fixed. 3. Lynn and I are reviewing the command-line help and a command summary is an item we would like to see added along with a usage example for each, as most end users will still have trouble deciphering how to use it.

We are reorging the tutorials site as we speak - it is too confusing with it all mixed together.

Elizabeth

----- Original Message ----- From: Christopher Henry <[email protected]> To: kbase devel <[email protected]>, [email protected] Outreach <[email protected]>, KBase Microbes List <[email protected]> Cc: Doreen Ware <[email protected]> Sent: Fri, 24 May 2013 16:26:59 -0500 (CDT) Subject: [Microbe] Comments from users at GLBRC retreat

Hi all,

I'm going to do a brain dump of comments from users at the GLBRC retreat. I figure everyone should see these. Doreen, can you add to this list?

1.) David Benton said we should do everything in "awk", but I think he was kidding :)

2.) Yury Bukhman said we shouldn't refer to the apps in KBase labs as prototypes, because it scares everyone away from using them. Currently, the KBase slide stack calls them prototypes.

3.) Audry Gasch gave some awesome input. She was incredibly supporting and helpful during my demo. Here's a few of her comments: -She found the "usage" of the current commands confusing (but she did like that it was there). She thinks the command "usage" should always start with a high level sentence explaining what the command do.

-She found the documentation on the KBase website overwhelming. In particular, she didn't like how the "Command line" documentation and the "Web API" documentation was all mixed together. She would have preferred to see those separated out. But also, she would like to see the same sort of "command links" that you have in IRIS in www.kbase.us as well, where you can go to "Modeling Scripts", then look for your command of interest, and click on it to see detailed descriptions. She also said the command documentation was also too low level. It didn't provide high-level descriptions of what each command was fundamentally meant to do.

-She wanted ALL the documentation to be available somehow online within IRIS. For example, could she type "annnotate_genome --docs" and see the complete documentation of the command with all detail thats on www.kbase.us instead of just the command usage

-She loved the idea of the tutorials being built into IRIS, but there needs to be better descriptions of how to use them there.

-Audrey said she won't use anything in KBase unless she has a good understanding of the fundamental methods the commands use in the background. In the other words, our command documentation should contain links to the papers describing their methods whenever possible, or detailed descriptions of the entire method when no paper exists (e.g. she wants to know that RAST is the annotation technology behind our annotation commands, and Model SEED is the tech behind our modeling commands).

4.) After I ran "fastsa-to-genome" and "annotate-genome", many users asked if they could now go and see their genome in the Workspace Browser and in the Genome Browser.

5.) Steven Slater said he wants his agrobacteria community to set up a workspace with snapshots of all the agrobacteria genomes in KBase, then he wanted his community to be able to annotate those genomes there and share them as the best available agrobacteria annotations available. He also ultimately wanted to see these get integrated into the automatically propagated annotations.

6.) Generally, there was the question is how JGI data would be available in KBase… do we replicate it, or is it "just there"

Chris

_______________________________________________ Microbe mailing list [email protected] https://lists.kbase.us/mailman/listinfo/microbe

_______________________________________________ Microbe mailing list [email protected] https://lists.kbase.us/mailman/listinfo/microbe