Tripal at the 2018 GMOD hackathon

Tripal Logo

The 2018 Tripal hackathon took place at the Plant & Animal Genomes conference in San Diego January 11th & 12th. I'd post the itinerary and workshop sessions were, but I didn't take great notes. Instead, I'll share about the sessions I took part in. Thursday we discussed Controlled Vocabularies in the morning, and Tripal Core issues (generally Tripal 3 issues) in the afternoon. Friday was a general round-table and a Tripal 3 bundles and fields live demo.

I want to thank everyone who came out to the Tripal workshop at the 2018 Plant & Animal Genome Conference for making it a success. Special thanks to Meg Staton and Ethy Cannon for organizing.

Day One

Controlled Vocabularies

In the morning I ran a tutorial on Controlled Vocabularies, their increased importance in Tripal 3, and how Chado stores them. If you're interested in learning more, I've already written detailed Controlled Vocabulary Term guides for my Tripal Fields Generator tool, so check out the documentation there if you're interested in learning more.

Tripal 3 Issue Queue

In the afternoon I bounced between working on some of the issues we've found migrating to Tripal 3, and answering questions about creating fields and bundles in Tripal 3 using the GUI. Now that I've been working in Tripal 3 for a while, the concepts seem crystal clear, but it took me a while to wrap my head around them. I'm hoping to post my experience here to ease the transition for other sites converting from Tripal 2 to Tripal 3.

Day Two

Round Table Discussion

I don't have much to write about this discussion: I enjoyed meeting members of the Tripal community, learning about the sites that use or will use Tripal, and hearing about some of the new modules being developed. It looks like Tripal 4 is in the works to keep up with Drupal 8's release (see below) but it won't be available in 2018. In the meantime the community is exploring the Tripal 3 upgrade process.

Tripal 3 Development Demo

It was clear the first day that the Tripal community is ready to start thinking about migrating to Tripal 3, and had a lot of the same questions I did starting out. To address this, I ran a live code demo of creating a new module that defined a bundle and field with code rather than using the GUI. I'm proud to report we made it through the whole process without any technical glitches. Going through the demo made me realize that maybe I do understand this stuff a little. Lesson learned: if you really want to see if you've mastered something, do it in front of a group, without advanced notice or preparation or time to collect your thoughts.

Coming Soon - Tripal 3 Guides

For those not in the know, Tripal is a Drupal module, and the Drupal development lifecycle dictates that as new versions of Drupal get released, old ones enter long term support (LTS), security fixes only, and finally, deprecation. Once security fixes are no longer released for a version, it's only a matter of time before new exploits are developed and sites running old Drupal releases

drupal release lifecycle Don't freak out! The Drupal production life cycle means that as new versions get released, support for old versions drops.

Tripal 3 is the first step in getting the community ready for the death of Drupal 7. My hope is that I can share some what I've learned in the upgrade process, as a neophyte to Drupal, Chado, and Tripal. Hopefully it will solidify what I've learned, and perhaps it will ease the transition of other sites.