18
edits
Changes
Add an *AMAZING* PostgreSQL / recommendation engine talk
Most developers know that they should be writing tests along with their code, but not every developer knows how or where to get started. This talk will walk through the nuts and bolts of the testing a medium-sized Drupal site with many integrated moving parts. We’ll talk about unit testing of individual functions with [http://www.simpletest.org/en/overview.html SimpleTest] (and how that has changed how we write functions), functional testing of the user interface with [http://casperjs.org/ casperjs]. We will discuss automating deployment with [http://www.phing.info/ phing], [http://drupal.org/project/drush drush], [http://jenkins-ci.org/ jenkins-ci] & github, which, combined with our tests, removes the “hold-your-breath” feeling before updating our live site.
[[Category:Code4Lib2013]]
== Relations, Recommendations and PostgreSQL ==
* William Denton, Web Librarian, York University, wdenton@yorku.ca
* Dan Scott, Systems Librarian, Laurentian University, dscott@laurentian.ca
In 2012, a ragtag group of library hackers from various Ontario
universities, funded with only train tickets and fueled with Tim Hortons
coffee, assembled under the Scholars Portal banner to build a common
circulation data repository and recommendation engine: the Scholars
Portal Library Usage-based Recommendation Engine (SPLURGE). PostgreSQL,
the emerging darling of the old-school relational database world, is the
heart of SPLURGE, and the circulation data for Ontario's 400,000
university students is its blood. Two of the contributors to this effort explore the PostgreSQL features
that SPLURGE uses to ease administration efforts, simplify application
development, and deliver high performance results. If you don't use
PostgreSQL for your data, you might want to try it after this
presentation; if you already do, you'll pick up some new tips and tricks.
[[Category:Code4Lib2013]]
