Agenda

• My-Plant update
• Data Pipeline
• iRODS

Notes

1. My-Plant has about 200 outside unique users, but there is a marked drop of usage recently. Need to think of ways to rejuvenate the site, in connection with facebook/twiter? How to make sure user only need to post once and the content will be distributed properly.

2. Using My-plant to recruit more sequence data from international community such as European users. Need to develop a standard procedure for data submission and retrieving. A comprehensive interface to gather meta information at the time of data submission (for example: contributor's name, contact, affiication, data type, data source, release data, ...) and a interface for how and what to be retrieved from the database (such as what search terms to use, what can be served, sequences, alignments).   This database will also be used by data-intake pipelines such as PHLAWD to query out sequences for analyze, so it will be a expansion of the PHLAWD database that comprised of only 2 tables, taxonomy and sequence.

   Actions:

• Doug will initiate the process of requirement gathering

3. In-take pipeline. Michael and Sharon will work together on installing it on ranger. There were concerns on whether sqlite can scale. According to Stephen, it would not be a problem to conver to mysql if neede. There is some coomunication difficulty with All-all blast pipeline.

   Actions:

• Michael and Sharon work on phlawd
• Sharon send Stephen a email about PHLAWD with mysql instead of sqlite
• Doug get in touch with Gordon

4. 1000 transcriptome pipeline: Michael got the evopipes (Infer gene family phylogenies and summarize the age of duplication events) working and will test it soon after getting the blast database.

5. iRODS - Sheldon had a prelimnary conversation with Nirav