The problem is that the uploader in place does not have any metadata support. For metagenomes/metatranscriptomes it is thus useless. best, Folker On May 26, 2013, at 11:01 PM, Shane Canon <[email protected]> wrote:

Its linked off the labs page (Data Uploader).

Here is the direct link…

http://140.221.84.204:7051/

--Shane

On May 26, 2013, at 7:55 PM, Nomi Harris <[email protected]> wrote:

...

I couldn't find it. URL? Nomi

On May 26, 2013, at 4:05 AM, Thomas Brettin <[email protected]> wrote:

...

Word from Henrick (JGI) is that the button exists now.

t

On May 24, 2013, at 5:15 PM, Narayan Desai <[email protected]> wrote:

...

The plan for 6) is that JGI has put a button in their user portal to load data into Shock/ADM on demand. -nld

On May 24, 2013, at 4:26 PM, Christopher Henry wrote:

...

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

_______________________________________________ Kbase-devel mailing list [email protected] https://lists.kbase.us/mailman/listinfo/kbase-devel

_______________________________________________ Kbase-devel mailing list [email protected] https://lists.kbase.us/mailman/listinfo/kbase-devel