Tripal User's Meeting 2018/02/02

Reminders

• Consider adding your modules into the Tripal GitHub organization.
  • You can make your own team in the github repo.  Ask stephen/lacey/meg for permission to join the Tripal organization.
  • If not, please tag the repo as Tripal.  
• Remember to update the status of your modules on the Tripal.info site.
  • If you need a login let us know. You have to email one of the admins.
• If you have a new site or major updates to your existing site let us know and we can publish those on the Tripal news feed and twitter accounts.
  • http://tripal.info/sites_using_tripal 
  • We need to reach out to new tripal sites to encourage them to get their site on tripal.info etc.  
  • Let’s (Shawna please talk to Stephen) about who in the outreach team is responsible for reaching out.  Ethy will try to reach out to those present at PAG
  • Additional tripal.info needs?  We will add training videos.  
• API in March
• Send us your logo if you have shared a module with the community and would like it showcased on the Tripal.info site.
• If you publish on your site please remember to cite Tripal (Sanderson et. al. 2013). A Tripal v3 paper will be submitted this year. (We did not have a Tripal v2 paper).

Agenda

Thank You to those who participated in our Hackathon, User's Meeting and Workshop in San Diego

• 25 people attended the Hackathon/User's Meeting
• 50-80 people were in attendance during the talks at the Tripal Workshop
• Expect another Tripal PAG event next year!
• Tripal workshop at ASPB in july/ASHS?
• Would be nice to improve Tripal outreach efforts by giving talks at other conferences/sessions about Tripal3.  IE tripal talk in the ontology session.  Or include a standardized “Tripal slide” to include in all talks.  Could host on tripal.info.
• Please fill out the survey about our PAG events: Even if you did not attend we'd like to receive your feedback about it.
• https://utk.co1.qualtrics.com/jfe/form/SV_9tN0NUsNmv65Nat

• Need to videotape trainings.  Time is OK for those present.  Please add further training suggestions below and/or training topics you are willing to host (this is in the survey!)
• Currently we have dev calls on the first Friday of the month
• We could add a call on the third Friday of the month - does 8am US Pacific, 11am US Eastern, 5pm European Central work?
• Perhaps offer two times… one for Americas and another for Europe?
• Suggest alternating between organized training and tripal therapy topic
• Training: Suggestions from last month's meeting:
• How to write a Tripal Module to define a content and add some fields.
• Web Services
• Setting up Site-wide searching.
• Intro to Chado -- where to put stuff.  
• Visualization tools for Chado.
• How to use the Natural Diversity module (or not use it).
• Tripal Therapy Sessions
• Bring your problems and we'll have folks to help debug. The idea is to meet all together and then break out into separate sessions to work together on a problem.
• 3rd Friday of each month at the same time.
• Is meeting 2x per month too much? Other suggestions?

• Is Tripal FAIR?
• Findable, Accessible, Interoperable, Reusable
• We can't enforce but can enable.
• Findable: metadata support? can this be enforced? 
• Who would enforce metadata?  Core? Extension modules?
• PeanutBase/LIS has a genome metadata module based on MIxS and its plant extension from the Genomic Standards Consortium.
• Upcoming module for genome metadata that adheres to some recommendations. 
• Federated searching
• Encourage module authors: Have to choose metadata standard. Tricky if none exist, or no standard.
• Accessible: ?
• Interoperable: ?
• Reusable: shared modules.

• We can allow for inclusion in the Tripal User's Guide for folks who want to put it there.
• We can link from the User's Guide to your GitHub project page
• Suggested standards
• Insist that there be documentation (could use a dedicated support person here)
• Step-by-Step setup instructions with screen shots
• Step-by-Step usage instructions with screen shots
• ?API guide if there is API
• How does this module approach CHADO storage
• New documentation.  The maps are helpful and you could use this to show where
• Not just function description but also examples of use
• Drupal.org has its own set of documentation standards: encourage people to look at them.
• Tripal Core uses doxygen
• https://www.drupal.org/docs/develop/standards
• How to document API, with examples
• Open Layers, http://openlayers.org/en/latest/examples/
• GeoServer API, http://docs.geoserver.org/stable/en/user/rest/index.html#rest
• Best practices for writing modules: handling updates and uninstalls (Ethy)
• Recommendation is develop the uninstall as you write the install
• Feedback on github issue template? https://github.com/tripal/tripal/issues/251  (click create new issue to see the template)